<?xml version="1.0" encoding="UTF-8"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>Agricultural</EAR>
            <PRTPAGE P="iii"/>
            <HD>Agricultural Marketing Service</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Oranges, grapefruit, tangerines, and tangelos grown in—</SJ>
                <SJDENT>
                    <SJDOC>Florida, </SJDOC>
                    <PGS>40837-40844</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="8">02-15063</FRDOCBP>
                </SJDENT>
                <SJ>Potatoes (Irish) grown in —</SJ>
                <SJDENT>
                    <SJDOC>Colorado, </SJDOC>
                    <PGS>40844-40847</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="4">02-15064</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Dates (domestic) produced or packed in—</SJ>
                <SJDENT>
                    <SJDOC>California, </SJDOC>
                    <PGS>40876-40879</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="4">02-15058</FRDOCBP>
                </SJDENT>
                <SJ>Limes grown in—</SJ>
                <SJDENT>
                    <SJDOC>Florida, and imported, </SJDOC>
                    <PGS>40876</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="1">02-15057</FRDOCBP>
                </SJDENT>
                <SJ>Specialty crops; import regulations:</SJ>
                <SJDENT>
                    <SJDOC>Raisins, Other-Seedless Sulfured, </SJDOC>
                    <PGS>40879-40881</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="3">02-15059</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reports and guidance documents; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Milk for manufacturing purposes and its production and processing; requirements adoption by State regulatory agencies, </SJDOC>
                    <PGS>40908</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15065</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Agriculture</EAR>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Agricultural Marketing Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Animal and Plant Health Inspection Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Forest Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Animal</EAR>
            <HD>Animal and Plant Health Inspection Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Plant-related quarantine, foreign:</SJ>
                <SJDENT>
                    <SJDOC>Gypsy moth host material from Canada, </SJDOC>
                    <PGS>40874-40876</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="3">02-15074</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Army</EAR>
            <HD>Army Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SUBSJ>Base realignment and closure—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Oakland Army Base, CA, </SUBSJDOC>
                    <PGS>40921</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15005</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Arts</EAR>
            <HD>Arts and Humanities, National Foundation</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Foundation on the Arts and the Humanities</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Blind</EAR>
            <HD>Blind or Severely Disabled, Committee for Purchase From  People Who Are</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Committee for Purchase From People Who Are Blind or Severely Disabled</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Centers</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15013</FRDOCBP>
                    <PGS>40930-40932</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15014</FRDOCBP>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15015</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Medicaid:</SJ>
                <SSJDENT>
                    <SUBSJDOC>Managed care, </SUBSJDOC>
                    <PGS>40988-41116</PGS>
                    <FRDOCBP T="14JNR2.sgm" D="129">02-14747</FRDOCBP>
                </SSJDENT>
                <SSJDENT>
                    <SUBSJDOC>Rule with comment period withdrawn, </SUBSJDOC>
                    <PGS>40987-40989</PGS>
                    <FRDOCBP T="14JNR2.sgm" D="3">02-14748</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Medicaid:</SJ>
                <SUBSJ>State plan amendments, reconsideration; hearings—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Iowa, </SUBSJDOC>
                    <PGS>40932-40933</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15006</FRDOCBP>
                </SSJDENT>
                <SJ>Privacy Act:</SJ>
                <SJDENT>
                    <SJDOC>Systems of records, </SJDOC>
                    <PGS>40933-40946</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="5">02-15004</FRDOCBP>
                    <FRDOCBP T="14JNN1.sgm" D="5">02-15008</FRDOCBP>
                    <FRDOCBP T="14JNN1.sgm" D="6">02-15009</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Ports and waterways safety:</SJ>
                <SUBSJ>Lake Michigan—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Kewaunee Nuclear Power Plant, WI; security zone, </SUBSJDOC>
                    <PGS>40858-40859</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="2">02-15131</FRDOCBP>
                </SSJDENT>
                <SSJDENT>
                    <SUBSJDOC>Point Beach Nuclear Power Plant, WI; security zone, </SUBSJDOC>
                    <PGS>40856-40858</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="3">02-15130</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Lake Ontario—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Oswego, NY; security zone, </SUBSJDOC>
                    <PGS>40851-40853</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="3">02-15127</FRDOCBP>
                </SSJDENT>
                <SSJDENT>
                    <SUBSJDOC>Rochester, NY; security zone, </SUBSJDOC>
                    <PGS>40853-40854</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="2">02-15128</FRDOCBP>
                </SSJDENT>
                <SJDENT>
                    <SJDOC>Long Island Sound Marine Inspection and Captain of Port Zone, CT; regulated navigation area and safety and security zones, </SJDOC>
                    <PGS>40859-40861</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="3">02-15132</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Saint Lawrence River, Messena, NY; temporary security zone, </SJDOC>
                    <PGS>40854-40856</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="3">02-15129</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Tampa, FL; security zone, </SJDOC>
                    <PGS>40861-40863</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="3">02-15185</FRDOCBP>
                </SJDENT>
                <SJ>Regattas and marine parades:</SJ>
                <SJDENT>
                    <SJDOC>Lake Washington, WA; Silver Dollar Casino Cup hydroplane races; safety zone, </SJDOC>
                    <PGS>40863-40865</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="3">02-15183</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Racine Harbor, WI; fireworks display; safety zone, </SJDOC>
                    <PGS>40865-40867</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="3">02-15184</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Industry and Security Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Institute of Standards and Technology</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Oceanic and Atmospheric Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <PGS>40910</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15077</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Committee for Purchase</EAR>
            <HD>Committee for Purchase From People Who Are Blind or Severely Disabled</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Procurement list; additions and deletions, </DOC>
                    <PGS>40909-40910</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15069</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Comptroller</EAR>
            <HD>Comptroller of the Currency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15066</FRDOCBP>
                    <PGS>40981-40983</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15067</FRDOCBP>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15068</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Customs</EAR>
            <HD>Customs Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>COBRA Fees Advisory Conmmittee, </SJDOC>
                    <PGS>40983-40984</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15110</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Defense</EAR>
            <HD>Defense Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Army Department</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Navy Department</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Education</EAR>
            <HD>Education Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Proposed collection; comment request, </SJDOC>
                    <PGS>40921-40922</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15034</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SUBSJ>Workforce Investment Act—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>National Farmworker Jobs Program, </SUBSJDOC>
                    <PGS>40966-40970</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="5">02-15070</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment</EAR>
            <PRTPAGE P="iv"/>
            <HD>Employment Standards Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Minimum wages for Federal and federally-assisted construction; general wage determination decisions, </DOC>
                    <PGS>40970-40971</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-14731</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy</EAR>
            <HD>Energy Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Energy Regulatory Commission</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>EPA</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Air pollutants, hazardous; national emission standards:</SJ>
                <SJDENT>
                    <SJDOC>Secondary aluminum production, </SJDOC>
                    <PGS>41117-41124</PGS>
                    <FRDOCBP T="14JNR3.sgm" D="8">02-14625</FRDOCBP>
                </SJDENT>
                <SJ>Air quality implementation plans; approval and promulgation; various States:</SJ>
                <SJDENT>
                    <SJDOC>California, </SJDOC>
                    <PGS>40867-40870</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="4">02-14512</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Air pollutants, hazardous; national emission standards:</SJ>
                <SJDENT>
                    <SJDOC>Secondary aluminum production, </SJDOC>
                    <PGS>41124-41138</PGS>
                    <FRDOCBP T="14JNP2.sgm" D="3">02-14626</FRDOCBP>
                    <FRDOCBP T="14JNP2.sgm" D="13">02-14627</FRDOCBP>
                    <FRDOCBP T="14JNP2.sgm" D="2">02-14628</FRDOCBP>
                </SJDENT>
                <SJ>Air quality implementation plans; approval and promulgation; various States:</SJ>
                <SJDENT>
                    <SJDOC>California, </SJDOC>
                    <PGS>40897</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="1">02-14511</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Montana; correction, </SJDOC>
                    <PGS>40897-40898</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="2">02-15091</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Air programs:</SJ>
                <SUBSJ>State implementation plans; adequacy status for transportation conformity purposes—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Texas, </SUBSJDOC>
                    <PGS>40922</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15092</FRDOCBP>
                </SSJDENT>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SUBSJ>Agency statements—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Comment availability, </SUBSJDOC>
                    <PGS>40923</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15094</FRDOCBP>
                </SSJDENT>
                <SSJDENT>
                    <SUBSJDOC>Weekly receipts, </SUBSJDOC>
                    <PGS>40922-40923</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15093</FRDOCBP>
                </SSJDENT>
                <SJ>Superfund; response and remedial actions, proposed settlements, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Escambia Wood Preserving Sites, MS, GA, and FL, </SJDOC>
                    <PGS>40923-40924</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15090</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Executive</EAR>
            <HD>Executive Office of the President</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Presidential Documents</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Trade Representative, Office of United States</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Export</EAR>
            <HD>Export-Import Bank</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Advisory Committee, </SJDOC>
                    <PGS>40924</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15016</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FAA</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Class E airspace; correction, </DOC>
                    <PGS>40985</PGS>
                    <FRDOCBP T="14JNCX.sgm" D="1">C2-13214</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airworthiness directives:</SJ>
                <SJDENT>
                    <SJDOC>Boeing, </SJDOC>
                    <PGS>40894-40896</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="3">02-15106</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Federal airways, </DOC>
                    <PGS>40896</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="1">02-14688</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FCC</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Television broadcasting:</SJ>
                <SUBSJ>Telecommunications Act of 1996; implementation—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Cable Act reform provisions; reconsideration petitions denied, </SUBSJDOC>
                    <PGS>40870</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="1">02-15082</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Radio services, special:</SJ>
                <SUBSJ>Amateur service—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Miscellaneous amendments, </SUBSJDOC>
                    <PGS>40898-40907</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="10">02-14774</FRDOCBP>
                </SSJDENT>
                <SJ>Radio stations; table of assignments:</SJ>
                <SJDENT>
                    <SJDOC>Alabama and Michigan, </SJDOC>
                    <PGS>40907</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="1">02-15098</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Proposed collection; comment request, </SJDOC>
                    <PGS>40924-40925</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15083</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Rulemaking proceedings; petitions filed, granted, denied, etc., </DOC>
                    <PGS>40925</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15081</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Election</EAR>
            <HD>Federal Election Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Bipartisan Campaign Reform Act; implementation:</SJ>
                <SJDENT>
                    <SJDOC>Contribution and expenditure; redefinition and regulations reorganization, </SJDOC>
                    <PGS>40881-40894</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="14">02-14902</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Emergency</EAR>
            <HD>Federal Emergency Management Agency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Proposed collection; comment request, </SJDOC>
                    <PGS>40925-40927</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15051</FRDOCBP>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15052</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15053</FRDOCBP>
                    <PGS>40927-40928</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15054</FRDOCBP>
                </SJDENT>
                <SJ>Disaster and emergency areas:</SJ>
                <SJDENT>
                    <SJDOC>Illinois, </SJDOC>
                    <PGS>40928</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15049</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Michigan, </SJDOC>
                    <PGS>40928-40929</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15048</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Micronesia, </SJDOC>
                    <PGS>40929</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15050</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Missouri, </SJDOC>
                    <PGS>40929</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15047</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>West Virginia, </SJDOC>
                    <PGS>40929-40930</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15046</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Energy</EAR>
            <HD>Federal Energy Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>
                    <E T="03">Applications, hearings, determinations, etc.:</E>
                </SJ>
                <SJDENT>
                    <SJDOC>Drew River Mill, Inc., </SJDOC>
                    <PGS>40922</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15023</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Highway</EAR>
            <HD>Federal Highway Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; notice of intent:</SJ>
                <SJDENT>
                    <SJDOC>Clinton County, NY, </SJDOC>
                    <PGS>40978-40979</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15086</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Oakland County, MI, </SJDOC>
                    <PGS>40979</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15085</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Food</EAR>
            <HD>Food and Drug Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Medical devices:</SJ>
                <SUBSJ>Obstetrical and gynecological devices—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Glans sheath devices, </SUBSJDOC>
                    <PGS>40848-40849</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="2">02-15042</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <PGS>40946-40948</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15002</FRDOCBP>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15043</FRDOCBP>
                </SJDENT>
                <SJ>Harmonisation International Conference; pharmaceuticals guidelines availability:</SJ>
                <SJDENT>
                    <SJDOC>Electronic common technical document specification, </SJDOC>
                    <PGS>40948-40949</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15003</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Q1E evaluation of stability data, </SJDOC>
                    <PGS>40949-40950</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15001</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>S7B safety pharmacology studies for assessing potential for delayed ventricular repolarization (QT interval prolongation) by human pharmaceuticals, </SJDOC>
                    <PGS>40950-40951</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15000</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Stability data package for registration in climatic zones III and IV, </SJDOC>
                    <PGS>40951-40952</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-14999</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Forest</EAR>
            <HD>Forest Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SUBSJ>Resource Advisory Committees—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Eastern Idaho, </SUBSJDOC>
                    <PGS>40909</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15040</FRDOCBP>
                </SSJDENT>
                <SSJDENT>
                    <SUBSJDOC>Ravalli County, </SUBSJDOC>
                    <PGS>40908-40909</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15036</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Disease Control and Prevention</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Institutes of Health</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <PRTPAGE P="v"/>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <PGS>40954-40956</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15026</FRDOCBP>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15027</FRDOCBP>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15028</FRDOCBP>
                </SJDENT>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SUBSJ>Facilities to assist homeless—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Excess and surplus Federal property, </SUBSJDOC>
                    <PGS>40956-40961</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="6">02-14722</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Immigration</EAR>
            <HD>Immigration and Naturalization Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Nonimmigrant classes:</SJ>
                <SUBSJ>Aliens—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Special registration requirements; correction, </SUBSJDOC>
                    <PGS>40985</PGS>
                    <FRDOCBP T="14JNCX.sgm" D="1">C2-15037</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Industry</EAR>
            <HD>Industry and Security Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Export transactions:</SJ>
                <SJDENT>
                    <SJDOC>List of unverified persons in foreign countries, guidance to exporters as to ”red flags” (Supplement No. 3 to 15 CFR part 732), </SJDOC>
                    <PGS>40910-40911</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15095</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Reclamation Bureau</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>IRS</EAR>
            <HD>Internal Revenue Service</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Income taxes:</SJ>
                <SUBSJ>Deductions and credits; disallowance for failure to file timely return; cross-reference</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Hearing cancelled, etc.; correction, </SUBSJDOC>
                    <PGS>40896-40897</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="2">02-15107</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Golden parachute payments</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Hearing cancelled, </SUBSJDOC>
                    <PGS>40896</PGS>
                    <FRDOCBP T="14JNP1.sgm" D="1">02-15108</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping:</SJ>
                <SUBSJ>Cold-rolled carbon steel flat products from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>France, </SUBSJDOC>
                    <PGS>40911-40912</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15099</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Extruded rubber thread from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Indonesia, </SUBSJDOC>
                    <PGS>40912-40913</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15102</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Frozen concentrated orange juice from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Brazil, </SUBSJDOC>
                    <PGS>40913-40914</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15100</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Stainless steel plate in coils from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Taiwan, </SUBSJDOC>
                    <PGS>40914-40917</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="4">02-15101</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Import investigations:</SJ>
                <SUBSJ>Brake rotors from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>China, </SUBSJDOC>
                    <PGS>40964-40965</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15044</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Steel concrete reinforcing bar from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Turkey, </SUBSJDOC>
                    <PGS>40965</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15045</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Immigration and Naturalization Service</P>
            </SEE>
            <CAT>
                <HD>RULES</HD>
                <SJ>Security risk assessments:</SJ>
                <SUBSJ>Aviation Transportation and Security Act—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Aviation training for aliens and other designated individuals; flight training screening, </SUBSJDOC>
                      
                    <PGS>41139-41146</PGS>
                      
                    <FRDOCBP T="14JNR4.sgm" D="8">02-15060</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Security risk assessments:</SJ>
                <SUBSJ>Aviation Transportation and Security Act—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Aviation training for aliens and other designated individuals; flight training screening, </SUBSJDOC>
                    <PGS>41146-41152</PGS>
                    <FRDOCBP T="14JNP3.sgm" D="7">02-15061</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Alien trainees; aviation training; provisional advance consent; rescinded, </DOC>
                    <PGS>41152-41153</PGS>
                    <FRDOCBP T="14JNN2.sgm" D="2">02-15062</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Labor</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Employment and Training Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Employment Standards Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Proposed collection; comment request, </SJDOC>
                    <PGS>40965-40966</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15071</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Maritime</EAR>
            <HD>Maritime Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <PGS>40971-40972</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15025</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Foundation</EAR>
            <HD>National Foundation on the Arts and the Humanities</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Proposed collection; comment request, </SJDOC>
                    <PGS>40971</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15079</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Institute</EAR>
            <HD>National Institute of Standards and Technology</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Committees; establishment, renewal, termination, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Advanced Technology Program Advisory Committee, </SJDOC>
                    <PGS>40917</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15029</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Advanced Technology Visiting Committee, </SJDOC>
                    <PGS>40917-40918</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15031</FRDOCBP>
                </SJDENT>
                <SUBSJ>Malcolm Baldrige National Quality Award—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Panel of Judges, </SUBSJDOC>
                    <PGS>40918-40919</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15103</FRDOCBP>
                </SSJDENT>
                <SJDENT>
                    <SJDOC>Manufacturing Extension Partnership National Advisory Board, </SJDOC>
                    <PGS>40919-40920</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15030</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Weights and Measures National Conference, </SJDOC>
                    <PGS>40920</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15032</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NIH</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Heart, Lung, and Blood Institute, </SJDOC>
                    <PGS>40952-40953</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15018</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Environmental Health Sciences, </SJDOC>
                    <PGS>40953</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15019</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Scientific Review Center, </SJDOC>
                    <PGS>40953-40954</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15020</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NOAA</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Fishery conservation and management:</SJ>
                <SUBSJ>West Coast States and Western Pacific fisheries—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Pacific Coast groundfish; correction, </SUBSJDOC>
                    <PGS>40870-40873</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="4">02-14961</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Permits:</SJ>
                <SJDENT>
                    <SJDOC>Endangered and threatened species, </SJDOC>
                    <PGS>40920</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15080</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Marine mammals, </SJDOC>
                    <PGS>40920-40921</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-14962</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Navy</EAR>
            <HD>Navy Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Inventions, Government -owned; availability for licensing, </DOC>
                    <PGS>40921</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15055</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Reactor Safeguards Advisory Committee, </SJDOC>
                    <PGS>40973</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15087</FRDOCBP>
                </SJDENT>
                <SJ>
                    <E T="03">Applications, hearings, determinations, etc.:</E>
                </SJ>
                <SJDENT>
                    <SJDOC>North Atlantic Energy Service Corp., </SJDOC>
                    <PGS>40972-40973</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15089</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Office of U.S. Trade</EAR>
            <HD>Office of United States Trade Representative</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Trade Representative, Office of United States</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Pension</EAR>
            <PRTPAGE P="vi"/>
            <HD>Pension Benefit Guaranty Corporation</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Single-employer plans:</SJ>
                <SUBSJ>Allocation of assets—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Interest assumptions for valuing and paying benefits, </SUBSJDOC>
                    <PGS>40850-40851</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="2">02-15038</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Multiemployer plans:</SJ>
                <SJDENT>
                    <SJDOC>Interest rates and assumptions, </SJDOC>
                    <PGS>40973-40974</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15039</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Personnel</EAR>
            <HD>Personnel Management Office</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Pay administration:</SJ>
                <SJDENT>
                    <SJDOC>Dual compensation reductions for military retirees; repeal, </SJDOC>
                    <PGS>40837</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="1">02-15012</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15010</FRDOCBP>
                    <PGS>40974-40975</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15011</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Presidential</EAR>
            <HD>Presidential Documents</HD>
            <CAT>
                <HD>ADMINISTRATIVE ORDERS</HD>
                <DOCENT>
                    <DOC>Belarus; continuation of waiver authority (Presidential Determination No. 2002-21 of June 3, 2002), </DOC>
                    <PGS>40833</PGS>
                    <FRDOCBP T="14JNO0.sgm" D="1">02-15180</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Vietnam; continuation of waiver authority (Presidential Determination No. 2002-22 of June 3, 2002), </DOC>
                    <PGS>40835</PGS>
                    <FRDOCBP T="14JNO1.sgm" D="1">02-15181</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Public</EAR>
            <HD>Public Health Service</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Disease Control and Prevention</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Food and Drug Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Institutes of Health</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Reclamation</EAR>
            <HD>Reclamation Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Albuquerque Drinking Water Project, NM; hearings, </SJDOC>
                    <PGS>40961-40963</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="3">02-15022</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Elephant Butte and Caballo Reservoirs, NM; resource management plan, </SJDOC>
                    <PGS>40964</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-15021</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>SEC</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Self-regulatory organizations; proposed rule changes:</SJ>
                <SJDENT>
                    <SJDOC>National Association of Securities Dealers, Inc., </SJDOC>
                    <PGS>40975-40977</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="3">02-15076</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Consular services; fee schedules</SJ>
                <SJDENT>
                    <SJDOC>Correction, </SJDOC>
                    <PGS>40849-40850</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="2">02-15096</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface</EAR>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Railroad operation, acquisition, construction, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Permian Basin Railways, Inc., </SJDOC>
                    <PGS>40979-40980</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-14952</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>West Texas &amp; Lubbock Railroad Co., Inc., </SJDOC>
                    <PGS>40980</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="1">02-14951</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Trade</EAR>
            <HD>Trade Representative, Office of United States</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>World Trade Organization:</SJ>
                <SUBSJ>Dispute settlement panel establishment requests—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Japan; U.S. apples; importation restriction measures, </SUBSJDOC>
                    <PGS>40977-40978</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15078</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Coast Guard</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Highway Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Maritime Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Surface Transportation Board</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Comptroller of the Currency</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Customs Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Internal Revenue Service</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Agency information collection activities:</SJ>
                <SJDENT>
                    <SJDOC>Submission for OMB review; comment request, </SJDOC>
                    <PGS>40980-40981</PGS>
                    <FRDOCBP T="14JNN1.sgm" D="2">02-15017</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veterans</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Adjudication; pensions, compensation, dependency, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Cross-reference change in forms to be furnished, </SJDOC>
                    <PGS>40867</PGS>
                    <FRDOCBP T="14JNR1.sgm" D="1">02-15075</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Health and Human Services Department, Centers for Medicare &amp; Medicaid Services, </DOC>
                <PGS>40987-41116</PGS>
                <FRDOCBP T="14JNR2.sgm" D="129">02-14747</FRDOCBP>
                <FRDOCBP T="14JNR2.sgm" D="3">02-14748</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Environmental Protection Agency, </DOC>
                <PGS>41117-41138</PGS>
                <FRDOCBP T="14JNR3.sgm" D="8">02-14625</FRDOCBP>
                <FRDOCBP T="14JNP2.sgm" D="3">02-14626</FRDOCBP>
                <FRDOCBP T="14JNP2.sgm" D="13">02-14627</FRDOCBP>
                <FRDOCBP T="14JNP2.sgm" D="2">02-14628</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Justice Department, </DOC>
                <PGS>41139-41153</PGS>
                <FRDOCBP T="14JNR4.sgm" D="8">02-15060</FRDOCBP>
                <FRDOCBP T="14JNP3.sgm" D="7">02-15061</FRDOCBP>
                <FRDOCBP T="14JNN2.sgm" D="2">02-15062</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <HD SOURCE="HED">Reader Aids</HD>
            <P>Consult the Reader Aids section at the end of this issue for phone numbers, online resources, finding aids, reminders, and notice of recently enacted public laws.</P>
            <P> </P>
            <P>To subscribe to the Federal Register Table of Contents LISTSERV electronic mailing list, go to http://listserv.access.gpo.gov and select Online mailing list archives, FEDREGTOC-L, Join or leave the list (or change settings); then follow the instructions.</P>
        </AIDS>
    </CNTNTS>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="40837"/>
                <AGENCY TYPE="F">OFFICE OF PERSONNEL MANAGEMENT </AGENCY>
                <CFR>5 CFR Parts 550 and 553 </CFR>
                <RIN>RIN 3206-AI92 </RIN>
                <SUBJECT>Repeal of Dual Compensation Reductions for Military Retirees </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Personnel Management. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Office of Personnel Management (OPM) is publishing final regulations recognizing the end of reductions in uniformed service (military) retired or retainer pay previously required by law of military retirees employed by the Federal Government. We are adopting the interim regulations as final without change and provide supplementary information to answer the questions we received. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>The regulations are effective on July 15, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Laurence T. Lorenz on (202) 606-0960, FAX (202) 606-2329, or e-mail 
                        <E T="03">ltlorenz@opm.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Section 651 of the National Defense Authorization Act for Fiscal Year 2000, Public Law 106-65, repealed 5 U.S.C. 5532. This repeal ended two reductions in uniformed service (military) retired or retainer pay previously required of military retirees employed by the Federal Government. This repeal did not change other parts of the Dual Compensation Act of 1964 that gave military retirees a “fresh start” for Federal civilian employment. The law continues to limit crediting military service of retirees as civilian service for employment benefits. For military retirees, the law allows credit only for service in the armed forces during war, or service for which a campaign badge is awarded, or when disability retirement is based on disability resulting from armed conflict or in the line of duty during a war; see 5 U.S.C. 3501 and 3502(a) for retention, 6303(a) for annual leave, and 8411(c) for retirement. The law requires agencies to credit uniformed service of non-retired service members as civilian service. We received many forms of the following four questions: </P>
                <P>
                    1. 
                    <E T="03">Do any Federal pay caps count retired military or retainer pay?</E>
                     No, the remaining Federal pay caps do not count uniformed service (military) retired or retainer pay. 
                </P>
                <P>
                    2. 
                    <E T="03">Why can't agencies count the military service of military retirees for annual leave, retention and retirement purposes?</E>
                     The Dual Compensation Act of 1964 required that retired uniformed (military) service members have a “fresh start” upon appointment to the Federal civil service. As a result, generally agencies may not use the military service of a retiree to grant civilian employment benefits. The law provides exceptions for service in the armed forces during war and campaigns and for retirements based on disability resulting from armed conflict or in the line of duty during a war. In 1999, Public Law 106-65 repealed only the dual pay limitations of the 1964 Act. 
                </P>
                <P>
                    3. 
                    <E T="03">What exceptions allow agencies to credit the military service of non-retirees and some military retirees as civilian service?</E>
                     The law requires agencies to credit uniformed (military) service of non-retirees as civilian service. For military retirees, the law only allows credit for service in the armed forces during a war, service in a campaign for which a campaign badge is awarded or when the retirement is based on disability resulting from an armed conflict or in the line of duty during a period of war. For details about these exceptions see 5 U.S.C. 3501 and 3502(a)—retention, 6303(a)—annual leave, and 8411(c)—retirement. Federal agencies use the law and The Guide to Processing Personnel Actions, especially Chapter 6, to credit uniformed (military) service of retirees. The OPM website, 
                    <E T="03">www.opm.gov/feddata/gppa/gppa.htm</E>
                    , contains a copy of the Guide. 
                </P>
                <P>
                    4. 
                    <E T="03">May military retirees use their veterans' preference?</E>
                     Yes, retirement does not change a service member's entitlement to veterans' preference in Federal hiring. 
                </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                <P>I certify that this regulation will not have a significant economic impact on a substantial number of small entities because it pertains only to Federal agencies. </P>
                <HD SOURCE="HD1">Executive Order 12866, Regulatory Review </HD>
                <P>This rule has been reviewed by the Office of Management and Budget in accordance with Executive Order 12866. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>5 CFR Part 550 </CFR>
                    <P>Administrative practice and procedure, Government employees, Claims, Wages. </P>
                    <CFR>5 CFR Part 553 </CFR>
                    <P>Administrative practice and procedure, Government employees, Military Personnel, Retirement, Wages. </P>
                </LSTSUB>
                <SIG>
                    <FP>U.S. Office of Personnel Management. </FP>
                    <NAME>Kay Coles James, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
                <REGTEXT TITLE="5" PART="550 and 553">
                    <AMDPAR>Accordingly, the interim regulations amending 5 CFR parts 550 and 553 which were published at 65 FR 19643, on April 12, 2000, are adopted as final regulations without change. </AMDPAR>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15012 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6325-38-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Agricultural Marketing Service </SUBAGY>
                <CFR>7 CFR Part 905 </CFR>
                <DEPDOC>[Docket Nos. FV01-905-1 FIR; FV01-905-2 FIR] </DEPDOC>
                <SUBJECT>Oranges, Grapefruit, Tangerines, and Tangelos Grown in Florida; Modifying Procedures and Establishing Regulations To Limit the Volume of Small Red Seedless Grapefruit </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Agriculture (USDA) is adopting, as final rules, without change, two interim final rules that regulated small red seedless grapefruit entering the fresh market 
                        <PRTPAGE P="40838"/>
                        during the 2001-02 season under the marketing order for oranges, grapefruit, tangerines, and tangelos grown in Florida. The order is administered locally by the Citrus Administrative Committee (Committee). This rule finalizes weekly percentages that were established for the first 11 weeks of the season. It also continues in effect the increase in the number of weeks available for percentage of size regulation from 11 to 22 weeks and finalizes the percentages established for the last 6 of those weeks. The interim final rules were intended to supply enough small red seedless grapefruit without saturating all markets, thus helping to stabilize supply and improve grower returns. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>July 15, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>William G. Pimental, Marketing Specialist, Southeast Marketing Field Office, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 799 Overlook Drive, Suite A, Winter Haven, Florida, 33884-1671; telephone: (863) 324-3375, Fax: (863) 325-8793; or George Kelhart, Technical Advisor, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., Stop 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938. </P>
                    <P>
                        Small businesses may request information on complying with this regulation by contacting Jay Guerber, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938, or E-mail: 
                        <E T="03">Jay.Guerber@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This rule is issued under Marketing Agreement 84 and Marketing Order No. 905, both as amended (7 CFR part 905), regulating the handling of oranges, grapefruit, tangerines, and tangelos grown in Florida, hereinafter referred to as the “order.” The order is effective under the Agricultural Marketing Agreement Act of 1937, as amended (7 U.S.C. 601-674), hereinafter referred to as the “Act.” </P>
                <P>The USDA is issuing this rule in conformance with Executive Order 12866. </P>
                <P>This rule has been reviewed under Executive Order 12988, Civil Justice Reform. This rule is not intended to have retroactive effect. This rule will not preempt any State or local laws, regulations, or policies, unless they present an irreconcilable conflict with this rule. </P>
                <P>The Act provides that administrative proceedings must be exhausted before parties may file suit in court. Under section 608c(15)(A) of the Act, any handler subject to an order may file with USDA a petition stating that the order, any provision of the order, or any obligation imposed in connection with the order is not in accordance with law and request a modification of the order or to be exempted therefrom. Such handler is afforded the opportunity for a hearing on the petition. After the hearing USDA would rule on the petition. The Act provides that the district court of the United States in any district in which the handler is an inhabitant, or has his or her principal place of business, has jurisdiction to review USDA's ruling on the petition, provided an action is filed not later than 20 days after the date of the entry of the ruling. </P>
                <P>
                    This rule adopts, without change, the provisions of two interim final rules that regulated the volume of sizes 48 (3
                    <FR>9/16</FR>
                     inches minimum diameter) and 56 (3
                    <FR>5/16</FR>
                     inches minimum diameter) red seedless grapefruit entering the fresh market under the order. This rule finalizes the weekly percentages established for the first 11 weeks of the 2001-02 season. It also continues in effect the increase in the number of weeks available for percentage of size regulation from 11 weeks to 22 weeks and the percentages established for the last 6 of those weeks. The interim final rules were intended to supply enough small red seedless grapefruit without saturating all markets, thus helping to stabilize supply and improve grower returns. These actions were recommended unanimously at two industry meetings on May 22, 2001, and August 29, 2001. 
                </P>
                <P>Section 905.52 of the order provides authority to limit shipments of any grade or size, or both, of any variety of Florida citrus. Such limitations may restrict the shipment of a portion of a specified grade or size of a variety. Under such a limitation, the quantity of such grade or size a handler may ship during a particular week would be established as a percentage of the total shipments of such variety by such handler in a prior period, established by the Committee and approved by the USDA. </P>
                <P>Section 905.153 of the regulations provides procedures for limiting the volume of small red seedless grapefruit entering the fresh market. The procedures specify that the Committee may recommend that only a certain percentage of sizes 48 and 56 red seedless grapefruit be made available for shipment into fresh market channels for any week or weeks during the regulatory period. Currently, the regulation period covers 22 weeks starting the third Monday in September. Under such a limitation, the quantity of sizes 48 and 56 red seedless grapefruit that may be shipped by a handler during a regulated week is calculated using the recommended percentage. By taking the recommended weekly percentage times the average weekly volume of red seedless grapefruit handled by such handler in the previous five seasons, handlers can calculate the total volume of sizes 48 and 56 they may ship in a regulated week. </P>
                <HD SOURCE="HD1">Background </HD>
                <P>
                    For the seasons 1994-95, 1995-96, and 1996-97, returns for red seedless grapefruit had been declining, often not returning the cost of production. On-tree prices for red seedless grapefruit had fallen steadily from $9.60 per carton (
                    <FR>4/5</FR>
                     bushel) during the 1989-90 season, to $3.45 per carton during the 1994-95 season, to $1.41 per carton during the 1996-97 season. 
                </P>
                <P>The Committee determined that one problem contributing to the market's condition was the excessive number of small-sized grapefruit shipped early in the marketing season. In the 1994-95, 1995-96, and 1996-97 seasons, sizes 48 and 56 accounted for 34 percent of total shipments during the 11-week regulatory period, with the average weekly percentage exceeding 40 percent of shipments. This contrasted with sizes 48 and 56 representing only 26 percent of total shipments for the remainder of the season. </P>
                <P>While there is a market for early grapefruit, shipping large quantities of small red seedless grapefruit in a short period oversupplies the fresh market for these sizes and negatively impacts the market for all sizes. For the majority of the season, larger sizes return higher prices than smaller sizes. However, there is a push to get fruit into the market early to take advantage of high prices available at the beginning of the season. The early season crop tends to have a greater percentage of small sizes. This creates a glut of smaller, lower-priced fruit on the market, driving down the price for all sizes. </P>
                <P>
                    The Committee believes that the over shipment of smaller sized red seedless grapefruit contributes to poor returns for growers and lower on-tree values. To address this issue, the Committee successfully used the provisions of § 905.153, and recommended weekly percentage of size regulation during the first 11 weeks of the 1997-98, 1998-99, 1999-2000, and 2000-01 seasons. Under regulation, f.o.b. and on-tree prices have increased and movement has stabilized. 
                    <PRTPAGE P="40839"/>
                </P>
                <P>Average f.o.b. prices were higher during the 11-week percentage of size regulation than for the three years prior to regulation. The average price for red seedless grapefruit in late October was $8.46 per carton for the regulated seasons compared to $7.22 for the same period for the three years before regulation. Prices have also remained at a higher level, with an average f.o.b. price of $7.29 per carton in mid-December during the years with regulation compared to $6.02 for the three prior years. The average season f.o.b. price has also been higher, averaging $7.15 per carton during years with 11-week regulation compared to $5.83 for the three prior seasons without regulation. </P>
                <P>The on-tree returns per box for fresh red seedless grapefruit also improved during 11-week regulation, providing better returns to growers. On-tree returns increased from $2.85 in 1997-98, to $4.52 in 1998-99, to $5.52 for the 1999-2000 season. </P>
                <P>Another benefit of regulation has been in maintaining higher prices for the larger-sized fruit. Larger fruit commands a premium price early in the season. However, the glut of smaller, lower-priced fruit on the early market was driving down the prices for all sizes. During the three years before regulation, the average differential between the f.o.b. carton price for a size 27 and a size 56 was $3.47 at the end of October. However, by mid-December the price for the larger size had dropped to within $1.68 of the price for the smaller-size fruit. </P>
                <P>In the four years of regulation, the average differential between the f.o.b. carton price for a size 27 and a size 56 was $5.38 at the end of October and remained at $3.42 in mid-December. In fact, the average f.o.b. prices for each size were higher during the four years with regulation than for the three years prior to regulation. The average prices for size 27, size 32, size 36, and size 40 during the 11-week period for the last four years were $9.41, $8.12, $7.26, and $6.68, respectively. This compares to the average prices for the same sizes during the same period for the three years prior to regulation of $6.48, $5.63, $5.59, and $5.34, respectively. </P>
                <P>Eleven-week percentage of size regulation also helped stabilize the volume of small sizes entering the fresh market early in the season. During the three years prior to the 11-week regulation, small sizes accounted for over 34 percent of the total shipments of red seedless grapefruit during the 11-week period covered. This compares to 31 percent for the same period during the last four years with 11-week regulation. There has also been a 43 percent reduction in the volume of small sizes entering the fresh market during the 11-week regulatory period from 1995-96 to 2000-01. </P>
                <P>An economic study done by Florida Citrus Mutual (Lakeland, Florida) in April 1998, found that the weekly percentage regulation had been effective. The study stated that part of the strength in early season pricing appeared to be due to the use of the weekly percentage rule to limit the volume of sizes 48 and 56. It said that prices were generally higher across the size spectrum with sizes 48 and 56 having the largest gains, and larger-sized grapefruit registering modest improvements. The rule shifted the size distribution toward the higher-priced, larger-sized grapefruit, helping raise weekly average f.o.b. prices. It further stated that sizes 48 and 56 grapefruit accounted for around 27 percent of domestic shipments during the same 11 weeks during the 1996-97 season. Comparatively, sizes 48 and 56 accounted for only 17 percent of domestic shipments during the same period in 1997-98, as small sizes were used to supply export customers with preferences for small-sized grapefruit. </P>
                <P>Based on available statistical information, the Committee concluded that once shipments of sizes 48 and 56 reached levels above 250,000 cartons a week, prices declined on those and most other sizes of red seedless grapefruit. The Committee believed if shipments of small sizes could be maintained at around or below 250,000 cartons a week, prices should stabilize and demand for larger, more profitable sizes should increase. </P>
                <HD SOURCE="HD1">First Eleven Week 2001-02 Discussion </HD>
                <P>
                    Based on this and prior season experience, on May 22, 2001, the Committee unanimously voted to establish a weekly percentage of 45 percent for the first 2 weeks, 35 percent for week 3, and 25 percent for weeks 4 through 11. The Committee's initial recommendation was issued as a proposed rule published in the 
                    <E T="04">Federal Register</E>
                     on July 31, 2001 (66 FR 39459). No comments were received during the comment period, which expired August 10, 2001. 
                </P>
                <P>
                    The Committee subsequently met on August 29, 2001, and unanimously recommended adjusting the percentages. The Committee determined that the initial recommendation was too restrictive, and recommended raising the percentages from 25 percent to 30 percent for weeks 4 through 10 and 40 percent for week 11 of the regulated period. The Committee's revised recommendation was issued as an interim final rule published in the 
                    <E T="04">Federal Register</E>
                     on September 26, 2001 (66 FR 49088). No comments were received during the comment period, which expired October 9, 2001. 
                </P>
                <P>Based on current 2001-02 crop and marketing information available to the Committee in August, the Committee recommended establishing the weekly percentages at levels higher than 25 percent for the last 8 weeks of the regulated period. The Committee agreed that the percentage recommended for the first two weeks of 45 percent was still appropriate, as was 35 percent for week three. However, the Committee recommended that weeks 4 through 10 should be established at 30 percent, and that week 11 should be established at 40 percent. The Committee recommended setting the percentage for week 11 at a higher level because that week marks the start of the holiday season and a large volume of small sizes are used for gift fruit shipments and fundraisers. </P>
                <P>In setting the weekly percentages at 45 percent for the first two weeks and 35 percent for week 3, the total available allotment would be slightly more than 250,000 cartons in the first three weeks. However, in the last four seasons when percentage size regulations have been effective, shipments of sizes 48 and 56 have never exceeded 250,000 cartons in the first three weeks. Setting the weekly percentages at 25 percent for the 2001-2002 season would have provided a total allotment of approximated 203,300 cartons (25 percent of the total industry base of 813,191 cartons). Consequently, there was room to increase the percentages while holding weekly shipments of sizes 48 and 56 close to the 250,000-carton mark. </P>
                <HD SOURCE="HD1">Discussion of Twenty-Two Week Percentage of Size Regulation </HD>
                <P>
                    This final rule also continues in effect the expansion of the weeks available for limiting the volume of small red seedless grapefruit entering the fresh market from the first 11 weeks of each season to the first 22 weeks, finalizes the weekly base percentages established for the last 6 of the 22-week regulatory period for the 2001-02 season. On August 29, 2001, The Committee recommended the percentages be set at 40 percent for the first 3 weeks (December 3 through December 23) and 30 percent for the remaining eight weeks (December 24 through February 17) of the second 11 weeks. However, because of available timeframes, weekly percentages were established for just the last 6 weeks of the second 11-week regulatory period (January 7 through February 17, 2002). These actions were 
                    <PRTPAGE P="40840"/>
                    issued as an interim final rule published in the 
                    <E T="04">Federal Register</E>
                     on January 8, 2002 (67 FR 801). No comments were received during the comment period, which expired January 23, 2002. 
                </P>
                <P>The continued ability to use percentage size regulations for the first 22 weeks of the season is expected to help the industry stabilize supplies and prices for red seedless grapefruit. This in itself does not limit shipments, but expands the weeks available for percentage of size regulation to 22 weeks so small sizes can be regulated for an additional 11 weeks, if needed. </P>
                <P>The rule creating § 905.153 (December 31, 1996, 61 FR 69011) established procedures for percentage of size regulation of small red seedless grapefruit. It provided a tool, if needed, to help stabilize price and supply. The procedures were established to cover an 11-week period to address problems associated with the oversupply of small-sized red seedless grapefruit early in the season. As previously mentioned, the Committee believed that the overshipment of early, small-sized fruit was depressing the market for all red seedless grapefruit, and concluded that having a tool to limit the amount of small red grapefruit entering the fresh market would be very helpful in addressing this problem. The Committee recommended 11 weeks because at that time the majority of small sizes were being shipped during this period. By the end of the 11 weeks, fruit had usually begun to size, and there were fewer small sizes available. </P>
                <P>However, this is no longer the case. The fruit is not sizing as in past seasons for reasons yet to be determined, leaving a larger supply of smaller sizes available later in the season. For the past three seasons, the volume of small sizes available from December through February has been much larger than in past seasons. Returns on red seedless grapefruit have also been declining during this period. The Committee has concluded that the problems associated with small red seedless grapefruit have begun to extend beyond the 11-week regulation period. The Committee believes the increased volumes of small red seedless grapefruit shipped or available to be shipped during the middle of the season is having a detrimental effect on the market. The Committee recommended increasing the weeks available for percentage of size regulation to address this problem. </P>
                <P>The last three seasons, 1998-99, 1999-2000, and 2000-01, have shown a marked increase in the volume of small-sized red seedless grapefruit available later in the season. For these three seasons, the percentage of the crop represented by small sizes in the month of February has averaged 51 percent. This compares to an average of 26 percent for the same month for the three prior seasons (1995-96, 1996-97, and 1997-98). In fact, the last three seasons have averaged a greater percentage of smaller sizes across each month, October through February, than over the three previous seasons. The trend across the last six seasons has been a continuing increase in the volume of small sizes as a percentage of the overall crop. This is most dramatically evidenced by the 72 percent increase in small sizes as a percentage of the overall crop from February 1996 to February 2001. </P>
                <P>The volume of small-sized red seedless grapefruit available in December, January, and February for the 1998-99, 1999-2000, and 2000-01 seasons were comparable or exceeded volumes available for October, November, and December for the 1995-96, 1996-97, and 1997-98 seasons. The following chart shows the volume of sizes 48 and smaller red seedless grapefruit available for these months as a percentage of the total crop. </P>
                <GPOTABLE COLS="8" OPTS="L2,i1" CDEF="s50,10,10,10,r50,10,10,10">
                    <TTITLE>Sizes 48 and Smaller as a Percentage of Total Crop </TTITLE>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">95-96 </CHED>
                        <CHED H="1">96-97 </CHED>
                        <CHED H="1">97-98 </CHED>
                        <CHED H="1">  </CHED>
                        <CHED H="1">98-99 </CHED>
                        <CHED H="1">99-00 </CHED>
                        <CHED H="1">00-01 </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">October </ENT>
                        <ENT>43 </ENT>
                        <ENT>62 </ENT>
                        <ENT>73 </ENT>
                        <ENT>December </ENT>
                        <ENT>56 </ENT>
                        <ENT>64 </ENT>
                        <ENT>64 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November </ENT>
                        <ENT>34 </ENT>
                        <ENT>56 </ENT>
                        <ENT>61 </ENT>
                        <ENT>January </ENT>
                        <ENT>54 </ENT>
                        <ENT>58 </ENT>
                        <ENT>57 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December </ENT>
                        <ENT>32 </ENT>
                        <ENT>51 </ENT>
                        <ENT>52 </ENT>
                        <ENT>February </ENT>
                        <ENT>50 </ENT>
                        <ENT>49 </ENT>
                        <ENT>54 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>It was following the 1995-96 season that the Committee began its initial discussions regarding the need to control the volume of small-sized red seedless grapefruit entering the fresh market early in the season. Percentage of size regulation was first used to control the volume of small sizes during the first 11 weeks of the 1997-98 season. Small sizes were a problem at those volume levels for the months of October through December for the 1995-96, 1996-97, and 1997-98 seasons. Having comparable or greater volumes of small sizes available during midseason also represents a problem for the industry. </P>
                <P>The University of Florida, Citrus Research and Education Center estimated fresh Florida citrus cost of production per acre for the 2000-2001 season at $882.25 per acre for the SunRidge area, or the interior of the state, $907.72 per acre for the Gulf production area, and $974.46 per acre for the Indian River area, or the Atlantic coast region. Using an average of these estimates, it cost approximately $921 per acre to cultivate citrus for the fresh market in 2000-2001. This average represents a somewhat lower cost of production than what most growers of red seedless grapefruit experience because a major share of production is in the Indian River area. </P>
                <P>
                    The past five seasons red seedless grapefruit production has averaged around 409 boxes (1
                    <FR>3/5</FR>
                     bushels) per acre. For the 2000-2001 season, the estimated average on-tree value for red seedless grapefruit was $2.10 per box. Using these numbers, total on-tree revenue for the 2000-2001 season calculates as approximately $859 per acre. When combined with the cost of production, the average red seedless grapefruit producer in Florida had a negative return of more than $62 per acre or $0.15 per box. 
                </P>
                <P>On-tree returns have been below production costs for seven of the last eight seasons. Growers have benefited from several years of increased on-tree returns due to the 11-week percentage of size regulation. While 11-week regulation has improved the situation, it has not solved all the problems. For the first time since the 1997-98 season, grower returns have decreased. Total on-tree returns declined from $3.36 during the 1999-2000 season to $2.10 for the 2000-01 season. On-tree returns for fresh red grapefruit also declined by 22 percent. </P>
                <P>
                    Comparing on-tree returns for fresh sales by month shows that for the seasons 1997-98, 1998-99, and 1999-2000, there was an average decline in returns of $.60 per box from November to February. By combining this $.60 reduction with the average volume of 4.7 million boxes of red seedless grapefruit moved during this period, the drop in revenue to growers is nearly $2.8 million. During a period when growers are struggling to realize returns at least equal the cost of production; this $.60 can mean the difference between profit and loss. 
                    <PRTPAGE P="40841"/>
                </P>
                <P>
                    F.o.b. prices have also stabilized under 11-week regulation. However, while it has helped eliminate dramatic drops in price during the first 11 weeks, prices have continued to decrease throughout the season. For the seasons 1998-99, 1999-2000, and 2000-01, red seedless grapefruit prices fell from an average f.o.b. price of $7.72 per carton (
                    <FR>4/5</FR>
                     bushel) in November to an average f.o.b. price of $7.02 in February. As with grower returns, after two years of increased average season f.o.b. prices, this past season, 2000-01, represented a $.50 per carton decrease from the prior season. 
                </P>
                <P>The Committee believes the overshipment of smaller sized red seedless grapefruit during the middle of the season is contributing to poor returns and lower prices. Committee members agreed that extending the weeks available for percentage of size regulation an additional 11 weeks provides a tool to address the problems associated with small sizes during the middle of the season. The Committee supports the additional weeks because they have successfully used § 905.153 to address very similar problems for the first 11 weeks of the season. As previously stated, under 11-week regulation, f.o.b. prices and on-tree returns increased and movement stabilized as compared to years with no 11-week percentage of size regulation. </P>
                <P>Much of what the Committee is seeing in the second 11 weeks of the season reminds them of the adverse conditions they were facing during the first 11 weeks for the 1994-95, 1995-96, and 1996-97 seasons. The Committee believes the problems successfully addressed by using the 11-week percentage of size regulation during the first part of the season are the same problems they are now seeing during the middle of the season. Therefore, the Committee believes expanding the period available for percentage of size regulation under § 905.153 from 11 weeks to 22 weeks provides them with the best tool to address these problems. </P>
                <P>On average, 51 percent of red seedless grapefruit is shipped to fresh market channels. There is a processing outlet for grapefruit, with the majority, 49 percent on average, squeezed for juice. This outlet offers limited returns and currently is not profitable. </P>
                <P>For the 2000-2001 season, on-tree returns were negative for processed red seedless grapefruit. During the last five years, only 1999-2000 produced on-tree returns for processed red seedless grapefruit that exceeded one dollar per box. When on-tree returns for processed grapefruit drop below a dollar, there is pressure to shift a larger volume of the overall crop to the fresh market to benefit from the higher prices normally paid for fresh fruit. Because a fair percentage of red seedless grapefruit shipped for processing tend toward the smaller sizes, shifting volume from processing to fresh can mean an additional volume of small sizes on the fresh market, further exacerbating problems with excessive volumes of small sizes. </P>
                <P>Recent statistics from the Florida Department of Citrus show a 40-week inventory of processed grapefruit from the 2000-01 season. This had an additional negative impact on expected returns. Projected on-tree prices for processed red seedless grapefruit for the 2001-02 season are low due to the large quantities of stored juice. This fact, combined with the past history for juice prices, further supports the need to have the additional 11 weeks available to control excessive volumes of small sizes during the middle of the season. </P>
                <P>Shipments during the 11 weeks added by this regulation account for nearly 50 percent of the total volume of red seedless grapefruit shipped to the fresh market. Considering this volume and the limited returns for processing, it is important that returns from the fresh market be maximized during this period. Even a small increase in price when coupled with the volume shipped represents a significant increase in the overall return to growers. </P>
                <P>The 11-week percentage of size regulation in place for the first part of the season has been having the desired effect on early markets the past four seasons. However, when the regulation period ends, there is an increased supply of small red seedless grapefruit shipped to the fresh market. This has had a depressing effect on price and grower returns. The Committee decided it needed to be able to regulate shipments of small-sized red seedless grapefruit during the middle part of the marketing season. Therefore, the Committee voted to increase the weeks available for regulation from 11 to 22 weeks. </P>
                <P>This rule also finalizes the weekly percentages established for the last 6 of the additional 11 regulation weeks for the 2001-02 season. The Committee met August 29, 2001, and recommended that percentages be set at 40 percent for the first 3 weeks (December 3 through December 23) and 30 percent for the remaining eight weeks (December 24 through February 17). However, because of available timeframes, weekly percentages were established for only the last 6 weeks of the second 11-week period at 30 percent (January 7 through February 17, 2002). The percentages were intended to supply enough small-sized red seedless grapefruit to meet market demand, without saturating all markets with these small sizes. </P>
                <P>As stated earlier, for the 1998-99, 1999-2000, and 2000-01 seasons there has been a substantial increase in the volume of small sizes available later in the season. Small sizes available for shipment in December, January, and February for the 1998-99, 1999-2000, and 2000-01 seasons equal or exceed volumes available during October, November, and December for the 1995-96, 1996-97, and 1997-98 seasons. Estimates by the Florida Agricultural Statistics Service show that small sizes represent a large percentage of the 2001-02 crop, accounting for over 83 percent of the fruit per September measurements. </P>
                <P>On-tree returns dropped from $3.36 during the 1999-2000 season to $2.10 for the 2000-01 season. On-tree returns for fresh red grapefruit also declined by 22 percent. In addition, on-tree returns declined an average of $.60 from November to February for the seasons 1997-98, 1998-99, and 1999-2000. By combining this $.60 reduction with an average volume of 4.7 million boxes shipped during this period the loss in grower returns tops nearly $2.8 million. </P>
                <P>In the past three seasons, 1998-99, 1999-2000, and 2000-01, prices of red seedless grapefruit fell from an average f.o.b. price of $7.72 per carton in November to an average f.o.b. price of $7.02 in February. Also, after two years of increased average season f.o.b. prices, the 2000-01 season marked a $.50 per carton decrease from the prior season. </P>
                <P>The Committee believes excessive shipments of small red seedless grapefruit during the second 11 weeks of the season are contributing to the market's poor condition. Shipments of small sizes in December through February exceed those shipped during September through November by nearly 91,000 cartons a week on average. There is a market for small red seedless grapefruit. However, shipping large quantities in a short period oversupplies the market for these small sizes and negatively impacts the market for all sizes. </P>
                <P>
                    To address similar problems with an oversupply of small sizes and decreasing returns, the Committee successfully used the provisions of § 905.153, and recommended weekly regulation of small sizes during the first 11 weeks of the 1997-98, 1998-99, 1999-2000, 2000-01, and 2001-02 seasons. Under the 11-week regulations, prices increased and movement stabilized as compared to seasons without 11-week regulation. 
                    <PRTPAGE P="40842"/>
                </P>
                <P>In making the recommendation to establish weekly percentages for the second 11 weeks, Committee members considered the success of the 11-week regulations during the early season and their experiences from past seasons. Members reviewed shipment data covering the second 11-week period for the last three seasons. The information contained the amounts and percentages of sizes 48 and 56 shipped during each week. </P>
                <P>Committee members agreed limiting the volume of small sizes available for the fresh market has been successful. The Committee believes that the volume of small sizes will be a problem during the middle of the season, and that limiting the volume available for shipment will be beneficial. </P>
                <P>Based on available statistical information, Committee members concluded once shipments of sizes 48 and 56 reached levels above 250,000 cartons a week, prices declined on those and most other sizes of red seedless grapefruit. During the second 11-week period of the last three seasons, shipments of sizes 48 and 56 red seedless grapefruit exceeded 250,000 cartons an average of 5 of the 11 weeks. For the 1998-99, 1999-2000, and 2000-01 seasons, shipments of sizes 48 and 56 red seedless grapefruit from the second 11 weeks exceeded shipments of small sizes from the first 11 weeks by an average of nearly one million cartons. This may have contributed to the problems facing the industry. </P>
                <P>Setting the weekly percentages at 30 percent for the remaining 6 weeks of the second 11-week period during the 2001-02 season provided a total available weekly allotment of approximately 244,000 cartons (30 percent of the total industry base of 813,191 cartons). Setting the weekly percentages at this level allowed total shipments of small red seedless grapefruit to approach the 250,000-carton mark during the regulated period without exceeding it. </P>
                <P>The Committee believes that the problems associated with an uncontrolled volume of small sizes entering the market in the middle of the season will continue without regulation. Therefore, this rule continues in effect the authority for the Committee to use percentage of size regulations during the first 22 weeks of any season, when needed. </P>
                <P>The provisions governing the operation of percentage of size regulation remain the same. The Committee still cannot set restrictions tighter than 25 percent. The method for calculating base and allotment also remains the same. The only changes to § 905.153 are the number of available regulation weeks and the cut off period for overshipments. </P>
                <P>The rules governing percentage size regulation contain a variety of provisions designed to provide handlers with some marketing flexibility. Section 905.153(d) provides allowances for overshipments, loans, and transfers of allotment. This rule makes one slight change to the provisions governing overshipments. During a week of percentage of size regulation, any person who has received an allotment can handle an amount of sizes 48 and 56 red seedless grapefruit equal to their weekly allotment, plus an additional overshipment amount not to exceed 10 percent of that week's allotment. The quantity of overshipments is deducted from the handler's allotment for the following week. Previously, § 905.153 stated that overshipments were not allowed during week 11 because there were no allotments the following week from which to deduct the overshipments. This rule changes this to read that no overshipments are allowed during week 22 to reflect the longer period for which percentages may be established. </P>
                <HD SOURCE="HD1">Final Regulatory Flexibility Analysis </HD>
                <P>Pursuant to requirements set forth in the Regulatory Flexibility Act (RFA), the Agricultural Marketing Service (AMS) has considered the economic impact of this action on small entities. Accordingly, AMS has prepared this final regulatory flexibility analysis. </P>
                <P>The purpose of the RFA is to fit regulatory actions to the scale of business subject to such actions in order that small businesses will not be unduly or disproportionately burdened. Marketing orders issued pursuant to the Act, and rules issued thereunder, are unique in that they are brought about through group action of essentially small entities acting on their own behalf. Thus, both statutes have small entity orientation and compatibility. </P>
                <P>There are approximately 75 grapefruit handlers subject to regulation under the order and approximately 10,000 growers of citrus in the regulated area. Small agricultural service firms, which includes handlers, are defined by the Small Business Administration (SBA) as those having annual receipts of less than $5,000,000, and small agricultural producers are defined as those having annual receipts of less than $750,000 (13 CFR 121.201). </P>
                <P>
                    Based on industry and Committee data, the average annual f.o.b. price for fresh Florida red seedless grapefruit during the 2000-01 season was approximately $7.20 per 
                    <FR>4/5</FR>
                     bushel carton, and total fresh shipments for the 2000-01 season are estimated at 24.7 million cartons of red grapefruit. Approximately 25 percent of all handlers handled 70 percent of Florida grapefruit shipments. Using the average f.o.b. price, about 69 percent of grapefruit handlers could be considered small businesses under SBA's definition. Therefore, the majority of Florida grapefruit handlers may be classified as small entities. The majority of Florida grapefruit producers may also be classified as small entities. 
                </P>
                <P>This rule adopts, without change, the provisions of two interim final rules regulating the volume of sizes 48 and 56 red seedless grapefruit entering the fresh market under the order. The overshipment of small red seedless grapefruit has contributed to poor returns for growers and lower on-tree values. This rule finalizes weekly percentages established for the first 11 weeks of the 2001-02 season. It also continues in effect the increase in the weeks available for percentage of size regulation from 11 weeks to 22 weeks and finalizes the percentages set for the last 6 of those weeks for 2000-01. Authority for these actions is provided in § 905.52 of the order. This rule also uses the provisions of § 905.153. The rule is based on unanimous recommendations of the Committee at meetings on May 22, and August 29, 2001. </P>
                <P>The change increasing the weeks available for regulation from 11 to 22 weeks only provides additional weeks for percentage of size regulation. It in itself does not establish any restriction on shipments. Having the ability to control the volume of small red seedless grapefruit the first 11 weeks of a seasons has been an important tool. The Committee believes the benefits derived under 11 weeks of volume regulation will continue if the period available for volume regulation is increased to 22 weeks. With the trend being more small sizes available later in a season, having the ability to regulate volume during the middle of the season will be a valuable asset. The purpose of this change is to provide a tool to prevent a surplus of small-sized red seedless grapefruit from damaging the overall grapefruit market during the middle part of the season. A tool that will help stabilize price and returns benefits both small and large producers and handlers. </P>
                <P>
                    This rule also finalizes the percentages that limited the volume of sizes 48 and 56 red seedless grapefruit entering the fresh market during the first 11 weeks of the 2001-02 season, beginning September 17, 2001. The weekly percentages were 45 percent for 
                    <PRTPAGE P="40843"/>
                    the first two weeks, 35 percent for week 3, 30 percent for weeks 4 through 10, and 40 percent for week 11. 
                </P>
                <P>This rule also finalizes weekly percentages established for 6 of the 11 weeks added to the regulatory period for the 2001-02 season. The Committee recommended weekly percentages of 40 percent for the first three weeks (December 3 through December 23) and 30 percent for the eight remaining weeks (December 24 through February 17) of the second 11-week period. However, because of available timeframes, weekly percentages were established for just the last 6 weeks of the second 11-week regulatory period at 30 percent (January 7, 2002, through February 17, 2002). </P>
                <P>While the establishment of volume regulation may necessitate spot picking, which could entail slightly higher harvesting costs, many producers are already using the practice. However, with spot picking, the persons harvesting the fruit are more selective and pick only the desired sizes and qualities. This reduces the amount of time and effort needed in sorting fruit, because undersize fruit is not harvested. This practice may also result in reduced processing and packing costs. In addition, because this regulation is only in effect for part of the season, the overall effect on costs is minimal. This rule is not expected to appreciably increase costs to producers. </P>
                <P>If a 25 percent restriction on small sizes had been applied during the 11-week period at the start of the season for the three seasons prior to 1997-98, an average of 4.2 percent of overall shipments during that period would have been constrained by regulation. Similarly, if a 25 percent restriction on small sizes had been applied during the second 11-week period for the three prior seasons, an average of 4.9 percent of the overall shipments during that period would have been subject to regulation. A large percentage of this volume most likely could have been replaced by larger sizes for which there are no volume restrictions. Under percentage of size regulation, larger sizes have been substituted for smaller sizes with a nominal effect on overall shipments. </P>
                <P>In addition, handlers can transfer, borrow, or loan allotment based on their needs in a given week. Handlers also can overship their allotment by 10 percent in a week, provided any overshipments are deducted from the following week's shipments. Transfers and loans have been used very effectively during past seasons with percentage of size regulation. Therefore, the overall impact of this regulation on total shipments should not be substantial. </P>
                <P>Handlers and producers have received higher returns under the 11-week percentage of size regulations issued for the first 11 weeks of the last four seasons. In late October, during the four years with 11-week regulation, the average f.o.b. price for red seedless grapefruit was $7.99 per carton compared to $7.22 for the three years prior to regulation. F.o.b. prices also have remained higher, with an average price of $7.29 in mid-December during 11-week regulation compared to $6.02 for the three years prior to regulation. Season average prices were also higher under 11-week regulation averaging $7.14 per carton compared to $5.83 for the prior three years. On-tree earnings per box for fresh red seedless grapefruit also improved under regulation, providing better returns to growers. The on-tree price increased from $3.26 per box in 1996-97, to $3.42 for 1997-98, to $5.04 for 1998-99, to $5.62 for the 1999-2000 season. These increased returns offset any additional costs associated with the 11-week regulation. </P>
                <P>The Committee believes that if the 11-week regulation at the start of a season has been successful in controlling the volume of small sizes and increasing returns, applying similar volume regulation during the second 11 weeks of the season should also be effective. Even if this action was only successful in raising returns by $.10 per carton, this increase in combination with the substantial number of shipments generally made during this second 11-week period, would represent an increased return of nearly $1 million. Consequently, any increased returns generated by this action should more than offset any additional costs associated with this regulation. </P>
                <P>The purpose of this rule is to help stabilize the market and improve grower returns. This rule provides a supply of small-sized red seedless grapefruit sufficient to meet market demand, without saturating all markets with these small sizes. This action is not expected to decrease the overall consumption of red seedless grapefruit. It is expected to benefit all red seedless grapefruit growers and handlers regardless of their size of operation. This rule will likely help small under-capitalized growers who need additional weekly revenues to meet operating costs. </P>
                <P>The Committee considered alternatives to the actions taken in this rule. One alternative was to leave the established weekly percentages at 25 percent for weeks 4 through 11. The Committee thought this was too restrictive and wanted to provide individual handlers more flexibility in weeks 4 through 11; therefore this option was rejected. Two other alternatives considered were not increasing the number of weeks available, and increasing the regulation period to include all 33 weeks of a season. Committee members agreed producers and handlers would benefit from smaller-sized fruit being controlled for a greater portion of the season. They also noted that the majority of export shipments occur during the last 11 weeks of the season helping to alleviate problems with small sizes during that part of the season. Consequently, these alternatives were also rejected. </P>
                <P>Other alternatives considered focused on the length of the holiday season and percentages set for that period. The holiday season is the weeks before Christmas when a large volume of small sizes is used for gift fruit shipments and fundraisers. One alternative was to add an additional week to those weeks considered as the holiday season, and set higher percentages for the first four weeks rather than the first three. Another alternative discussed was setting percentages higher than 40 percent for the weeks covered that were considered part of the holiday season. The Committee reviewed and discussed the suggestions and agreed that the weeks included and the percentages recommended the second 11 weeks of the 2001-02 season were the best solutions based on the information available. Therefore, these alternates also were rejected. </P>
                <P>This action required two new handler reports, forms 301A and 302A. In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35), AMS obtained emergency approval for a new information collection request under OMB No. 0581-0200 for Oranges, Grapefruit, Tangerines, and Tangelos Grown in Florida, Marketing Order No. 905. The emergency request was necessary because insufficient time was available to follow normal clearance procedures. Subsequent to the emergency approval by OMB, this information collection has since been merged under OMB No. 0581-0189, Generic OMB Fruit Crops. As with all Federal marketing order programs, reports and forms are periodically reviewed to reduce information requirements and duplication by industry and public sector agencies. </P>
                <P>
                    As noted in the initial regulatory flexibility analyses, USDA has not identified any relevant Federal rules that duplicate, overlap or conflict with this rule. However, red seedless 
                    <PRTPAGE P="40844"/>
                    grapefruit must meet the requirements as specified in the U.S. Standards for Grades of Florida Grapefruit (7 CFR 51.760 through 51.784) issued under the Agricultural Marketing Act of 1946 (7 U.S.C. 1621 through 1627). 
                </P>
                <P>The Committee's meetings were widely publicized throughout the Florida citrus industry and all interested persons were invited to attend the meetings and participate in Committee deliberations on all issues. Like all Committee meetings, the May 22, and August 29, 2001, meetings were public meetings and all entities, both large and small, were able to express views on this issue. </P>
                <P>
                    The two interim final rules concerning these actions were published in the 
                    <E T="04">Federal Register</E>
                    , one on September 26, 2001 (66 FR 39459) and  one on January 8, 2002 (67 FR 801). Copies of the rules were mailed or sent via facsimile to all Committee members and citrus handlers. Finally, both rules were made available through the Internet by the Office of the Federal Register and USDA. The rule published on September 26, 2001, provided a 20-day comment period that ended October 9, 2001. The rule published on January 8, 2002, provided a 15-day comment period that ended January 23, 2002. No comments were received. 
                </P>
                <P>
                    A small business guide on complying with fruit, vegetable, and specialty crop marketing agreements and orders may be viewed at: 
                    <E T="03">http://www.ams.usda.gov/fv/moab.html.</E>
                     Any questions about the compliance guide should be sent to Jay Guerber at the previously mentioned address in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. 
                </P>
                <P>
                    After consideration of all relevant material presented, including the Committee's recommendation, and other information, it is found that finalizing the interim final rules, without change, as published in the 
                    <E T="04">Federal Register</E>
                     (66 FR 39459, September 26, 2001) and (67 FR 801, January 8, 2002) will tend to effectuate the declared policy of the Act. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 905 </HD>
                    <P>Grapefruit, Marketing agreements, Oranges, Reporting and recordkeeping requirements, Tangelos, Tangerines.</P>
                </LSTSUB>
                <REGTEXT TITLE="7" PART="905">
                    <PART>
                        <HD SOURCE="HED">PART 905—ORANGES, GRAPEFRUIT, TANGERINES, AND TANGELOS GROWN IN FLORIDA </HD>
                    </PART>
                    <AMDPAR>Accordingly, the interim final rules amending 7 CFR part 905 which were published at 66 FR 49088 on September 26, 2001 and at 67 FR 801 on January 8, 2002, are adopted as final rules without change. </AMDPAR>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>A.J. Yates, </NAME>
                    <TITLE>Administrator, Agricultural Marketing Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15063 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-02-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Agricultural Marketing Service </SUBAGY>
                <CFR>7 CFR Part 948 </CFR>
                <DEPDOC>[Docket No. FV02-948-1 FR] </DEPDOC>
                <SUBJECT>Irish Potatoes Grown in Colorado; Increase in the Minimum Size Requirement for Area No. 2 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This rule increases the minimum size requirement for all varieties of potatoes produced in Area No. 2 of Colorado, except for the round varieties and the Russet Burbank, Russet Norkotah, and Silverton Russet varieties. This rule raises the minimum size requirement from 1
                        <FR>7/8</FR>
                         inches to 2 inches in diameter or 4 ounces in weight. This size change is based on a recommendation of the Colorado Potato Administrative Committee (Committee), the agency responsible for local administration of the marketing order for potatoes grown in Colorado. This change is intended to improve the marketing of Colorado potatoes and increase returns to producers. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>This final rule becomes effective July 15, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Robert J. Curry, Northwest Marketing Field Office, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1220 SW., Third Avenue, suite 385, Portland, Oregon 97204-2807; telephone: (503) 326-2724, Fax: (503) 326-7440; or George Kelhart, Technical Advisor, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938. </P>
                    <P>
                        Small businesses may request information on complying with this regulation by contacting Jay Guerber, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938, or E-mail: 
                        <E T="03">Jay.Guerber@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This final rule is issued under Marketing Agreement No. 97 and Order No. 948, both as amended (7 CFR part 948), regulating the handling of Irish potatoes grown in Colorado, hereinafter referred to as the “order.” The order is effective under the Agricultural Marketing Agreement Act of 1937, as amended (7 U.S.C. 601-674), hereinafter referred to as the “Act.” </P>
                <P>The Department of Agriculture (USDA) is issuing this rule in conformance with Executive Order 12866. </P>
                <P>This final rule has been reviewed under Executive Order 12988, Civil Justice Reform. This rule is not intended to have retroactive effect. This rule will not preempt any State or local laws, regulations, or policies, unless they present an irreconcilable conflict with this rule. </P>
                <P>The Act provides that administrative proceedings must be exhausted before parties may file suit in court. Under section 608c(15)(A) of the Act, any handler subject to an order may file with USDA a petition stating that the order, any provision of the order, or any obligation imposed in connection with the order is not in accordance with law and request a modification of the order or to be exempted therefrom. Such handler is afforded the opportunity for a hearing on the petition. After the hearing USDA would rule on the petition. The Act provides that the district court of the United States in any district in which the handler is an inhabitant, or has his or her principal place of business, has jurisdiction to review USDA's ruling on the petition, provided an action is filed not later than 20 days after the date of the entry of the ruling. </P>
                <P>
                    This rule increases the minimum size requirement for all varieties of potatoes produced in Area No. 2 of Colorado, except for the round varieties and the Russet Burbank, Russet Norkotah, and Silverton Russet varieties. This rule raises the minimum size requirement from 1
                    <FR>7/8</FR>
                     inches in diameter to 2 inches in diameter or 4 ounces in weight. This action is based on a recommendation the Committee made on August 16, 2001. 
                </P>
                <P>
                    Section 948.4 of the order defines the counties included in Area No. 2, which is commonly known as the San Luis Valley. Section 948.22 of the order authorizes the issuance of regulations for grade, size, quality, maturity, and pack for any variety or varieties of potatoes grown in different portions of the production area during any period. Section 948.23 authorizes the issuance of regulations that modify, suspend, or 
                    <PRTPAGE P="40845"/>
                    terminate requirements issued under § 948.22. Section 948.386 contains handling regulations authorized in § 948.22 for potatoes grown in Area No. 2. The regulations in effect prior to this final rule prescribed minimum size requirements of 2 inches in diameter for round varieties and 1
                    <FR>7/8</FR>
                     inches in diameter for long varieties. 
                </P>
                <P>
                    As stated above, this rule raises the minimum size requirement from 1
                    <FR>7/8</FR>
                     inches in diameter to 2 inches in diameter or 4 ounces in weight for all varieties of potatoes produced in Area No. 2 of Colorado, except for the round varieties and the Russet Burbank, Russet Norkotah, and Silverton Russet varieties. This means that the potato varieties subject to the minimum size requirements under this rule will meet the size requirements if they are at least 2 inches in diameter or 4 ounces in weight. For example, long, thin potatoes smaller than 2 inches in diameter, but weighing 4 ounces or more will meet these size requirements. Similarly, potatoes weighing less than 4 ounces, but at least 2 inches in diameter will also meet the minimum size requirements effective in this rule. 
                </P>
                <P>According to the Committee, quality assurance is very important to the Colorado potato industry. Providing the public with acceptable quality produce that is appealing to the consumer on a consistent basis is necessary to maintain buyer confidence in the marketplace. The Committee reports that potato size is important to buyers and that providing the sizes desired is necessary to maintain buyer confidence in the marketplace. </P>
                <P>When the Committee made its recommendation, nine members voted in favor of the motion, two members voted in opposition to the motion and one member abstained from voting. The Committee made the recommendation to provide buyers with the sizes they prefer and to maintain buyer confidence. The Committee also believes that this rule will help improve the marketing of the potato varieties affected by the change and that it will help improve producer returns. </P>
                <P>For the purpose of obtaining additional information on the need for the change, the Committee conducted a producer survey prior to making the recommendation to the USDA. The survey indicated that 58 percent of the producers supported an increase in the minimum size to 2 inches in diameter or 4 ounces in weight for all varieties of potatoes, except for the round varieties and the Russet Burbank, Russet Norkotah, and Silverton Russet varieties. </P>
                <P>
                    The Committee did not recommend a change in the minimum size requirement for all round varieties because it believes that the minimum size requirement of 2 inches in diameter for these varieties of potatoes continues to be appropriate. The Russet Burbank, Russet Norkotah, and Silverton Russet are long, thin potato varieties that have a tendency to fall through the sizing screens on the potato grading equipment, even when the potatoes are of adequate size and weight (i.e., 4 ounces or larger). This is particularly a problem when the sizing screens are tooled for larger sized potatoes such as 2 or 2
                    <FR>1/4</FR>
                     inch minimum diameter. Because of this problem, the Committee believes that the minimum size requirement for these three Russet varieties of 1
                    <FR>7/8</FR>
                     inches in diameter is appropriate. Although one Committee member opposed the recommendation because he believed all Area No. 2 potato varieties should have a minimum size requirement of 2 inches in diameter or 4 ounces in weight, the Committee believes that handlers might lose a high percentage of acceptable potatoes of the long, thin varieties during the sizing and grading of the potatoes if the minimum size requirement on such potatoes was increased to 2 inches in diameter or 4 ounces in weight. Another Committee member opposing the motion did not believe that the results of the producer survey were a sufficient reason for the Committee to recommend an increase in the minimum size requirements. While the survey provided background information that assisted the Committee in making its recommendation, the primary purposes for the change are to better meet the needs of buyers and consumers, improve the image of Colorado potatoes, and improve sales and prices. 
                </P>
                <HD SOURCE="HD1">Final Regulatory Flexibility Analysis </HD>
                <P>Pursuant to requirements set forth in the Regulatory Flexibility Act (RFA), the Agricultural Marketing Service (AMS) has considered the economic impact of this rule on small entities. Accordingly, AMS has prepared this final regulatory flexibility analysis. </P>
                <P>The purpose of the RFA is to fit regulatory actions to the scale of business subject to such actions in order that small businesses will not be unduly or disproportionately burdened. Marketing orders issued pursuant to the Act, and rules issued thereunder, are unique in that they are brought about through group action of essentially small entities acting on their own behalf. Thus, both statutes have small entity orientation and compatibility. </P>
                <P>There are approximately 230 producers of Colorado Area No. 2 potatoes and approximately 80 handlers subject to regulation under the marketing order. Small agricultural producers are defined by the Small Business Administration (13 CFR 121.201) as those having annual receipts of less than $750,000, and small agricultural service firms are defined as those whose annual receipts are less than $5,000,000.</P>
                <P>Information provided by the National Agricultural Statistics Service (NASS) was considered in determining the number of large and small producers by acreage, production, and producer prices. According to the information provided, the recent average yield per acre was 335 hundredweight, the average farm size was 306 acres of potatoes, and the recent season average producer price was $4.20 per hundredweight. This equates to average gross annual producer receipts of approximately $430,542 each. In addition, based upon information provided by the Committee, all handlers of Area No. 2 potatoes have shipped under $5,000,000 worth of potatoes during the most recent season for which statistics are available. Based on the foregoing, it can be concluded that a majority of producers and handlers of Area No. 2 potatoes may be classified as small entities. </P>
                <P>The NASS estimated planted acreage for the 2001-02 crop in Area No. 2 at 68,100 acres, a decrease of 7,500 acres when compared with the 75,600 acres harvested in 2000-01. Approximately 90 percent of the potatoes harvested in 2001-02 entered the fresh market (including potatoes produced for seed). </P>
                <P>Russet varieties accounted for 81.4 percent of the acres planted for the 2001-02 crop year. Russet Norkotah, the most popular variety, was planted on 53.8 percent of the total potato acreage. Other Russet varieties, including Russet Burbank and Silverton Russet varieties, accounted for 27.6 percent of the total acres planted, with various other non-Russet varieties making up the remaining 18.6 percent. While exact acreage is not known, plantings of Russet Burbank and Silverton Russet varieties of potatoes are estimated to make up only a small percentage of the total potato acreage. </P>
                <P>
                    This rule increases the minimum size requirement for all varieties of potatoes produced in Area No. 2 of Colorado, except for the round varieties and the Russet Burbank, Russet Norkotah, and Silverton Russet varieties. This rule raises the minimum size requirement from 1
                    <FR>7/8</FR>
                     inches in diameter to 2 inches in diameter or 4 ounces in weight. Only 
                    <PRTPAGE P="40846"/>
                    a small portion of the crop (i.e., that portion smaller than 2 inches in diameter or 4 ounces in weight but larger than 1
                    <FR>7/8</FR>
                     inches in diameter) is expected to be affected by the size increase. The Committee believes that the expected benefits of improved quality, increased purchases and sales volume, and increased returns received by producers will greatly outweigh the costs related to the regulation. 
                </P>
                <P>
                    Alternatives considered by the Committee included increasing the minimum size requirement for all Russet varieties or not making any changes. The Committee does not believe it is desirable to increase the minimum size requirement for the Russet Burbank, Russet Norkotah, and Silverton Russet varieties because these long and thin varieties have a tendency, especially when sitting on end, to fall through the sizing screens on the potato grading equipment even when the potatoes are of good size. This is particularly a problem when the sizing screens are set at larger size settings such as 2 or 2
                    <FR>1/4</FR>
                     inches. Because of this problem, the Committee decided that the minimum size requirement of 1
                    <FR>7/8</FR>
                     inches in diameter for these three Russet varieties is appropriate. The Committee believes that handlers would have lost a high percentage of acceptable potatoes through the sizing screens if the minimum size requirement on such potatoes had been increased to 2 inches in diameter or 4 ounces in weight. Finally, the Committee determined that the alternative of not taking action would not have addressed the industry's marketing problems.
                </P>
                <P>This rule changes the size requirements prescribed under the handling regulations of the order. Accordingly, this action will not impose any additional reporting or recordkeeping requirements on either small or large potato handlers. As with all Federal marketing order programs, reports and forms are periodically reviewed to reduce information requirements and duplication by industry and public sector agencies. </P>
                <P>Furthermore, as noted in the initial regulatory flexibility analysis, USDA has not identified any relevant Federal rules that duplicate, overlap or conflict with this proposed rule. </P>
                <P>In addition, the Committee's meeting was widely publicized throughout the Colorado Area No. 2 potato industry and all interested persons were invited to attend the meeting and participate in Committee deliberations on all issues. Like all Committee meetings, the Committee meeting on August 16, 2001, was a public meeting and all entities, both large and small, were able to express views on this issue. Finally, interested persons were invited to submit information on the regulatory and informational impacts of this action on small businesses. </P>
                <P>
                    A proposed rule concerning this action was published in the 
                    <E T="04">Federal Register</E>
                     on March 1, 2002 (67 FR 9418). A copy of the rule was provided to the Committee's staff, who in turn notified Committee members, potato producers, and handlers, and other interested persons. In addition, the Office of the Federal Register and USDA also made a copy available through the Internet. Finally, a 60-day comment period, which ended on April 30, 2002, was provided to allow interested persons the opportunity to respond to the proposal. 
                </P>
                <P>Four comments were received during the comment period in response to the proposal. Each of the comments contained several questions and opinions regarding the proposed size change. We have separated the questions and opinions into the following four categories: (1) USDA's role in implementing the proposal; (2) the level of support potato producers in Colorado Area No. 2 have for the proposal; (3) the purpose of the proposed size change; and (4) the impact of the proposed size change on consumers. Since most of the individual commenter's opinions and questions were similar, their questions are addressed below within the context of these four categories. </P>
                <HD SOURCE="HD1">USDA's Role in Implementing the Proposal </HD>
                <P>Marketing orders are designed to help stabilize market conditions for fruit, vegetable, and specialty crops. The programs assist producers in allowing them to collectively work to solve marketing problems. Industries voluntarily enter into these programs and choose to have federal oversight of certain aspects of their operations. The Marketing Order Administration Branch of the Fruit and Vegetable Programs oversees the programs to make sure the orders operate in the public interest and in accordance with the authorizing Act, the order, and the regulations. The Colorado potato order is one of 36 active orders which collect assessment fees from handlers to cover the operational and administrative costs of the programs. </P>
                <P>
                    Marketing orders contain regulations authorized by the U.S. Congress through the Agricultural Marketing Agreement Act of 1937. Local administrative committees made up of producers and handlers from their particular growing areas administer programs for fruits, vegetables, and specialty crops. Some of the committees have members that represent the public. The Colorado Potato Administrative Committee for Area No. 2 works with USDA in providing potato buyers with the size and quality their customers desire. Additional information on these programs, including the Colorado potato order, may be found at 
                    <E T="03">http://www.usda.gov/fv/moab.html.</E>
                </P>
                <HD SOURCE="HD1">The Level of Support Potato Producers in Colorado Area No. 2 Have for the Proposal </HD>
                <P>Committee members are nominated by their peers and selected by USDA. Committee members make decisions and vote for regulations that are supported by their constituents—the producers or handlers that nominated them. When a decision is made by a committee to recommend the establishment of, or change in, a regulation, considerable effort and debate is expended to ensure that the proposal would be effective. </P>
                <P>In addition to relying on each of its members expertise in the production, handling, and marketing of the regulated crop, a committee compiles such other information as is available to help it make decisions. In that regard, as previously stated, the Colorado Area No. 2 Committee conducted a producer survey to help it determine what type of changes in the size regulations it should pursue. The survey established that 58 percent of the respondents supported the increase in minimum size from 1 7/8 inches to 2 inches. Although the Committee made its decision based on many factors including the desire to meet the needs of buyers, the survey was a useful tool in providing the Committee with feedback. </P>
                <P>
                    One of the commenters questioned whether producers in Area No. 2 would be disadvantaged relative to producers in Areas No. 1 and 3. Area No. 1 is not currently regulated and the handling of potatoes in Area No. 3 is regulated under different handling provisions than those in Area No. 2. The order was established with different administrative committees, production areas, and handling regulations in recognition of the distinct geographical and marketing differences between them. Although the two regulated areas meet once a year as a combined committee, marketing and regulatory decisions are made independently of each other by the respective area committees in recognition that their decisions do not directly impact the other area. It is important to note that this final rule only affects the handling of certain potatoes produced in Area No. 2 of the State of Colorado. 
                    <PRTPAGE P="40847"/>
                </P>
                <HD SOURCE="HD1">The Purpose of the Proposed Size Change </HD>
                <P>Most of the individuals submitting comments questioned the reasoning behind a rule that mandates and changes the minimum allowable size of potatoes for the fresh market. As previously stated, this regulation only regulates the minimum size of certain varieties of Colorado Area No. 2 potatoes that are handled for subsequent sale into the fresh market. This regulation does not regulate potato production. Only those potatoes of the varieties affected by this regulation that are sold into the fresh market must meet the revised minimum size of at least 2 inches minimum diameter or 4 ounces in weight. Potatoes of these varieties that do not meet this size may be sold into alternative markets, including processing (e.g., frozen and dehydrated). </P>
                <P>
                    As explained in the proposed rule, the change in size from 1
                    <FR>7/8</FR>
                     inches minimum diameter to 2 inches minimum diameter for the affected potato varieties was recommended by the Committee for the purpose of improving the marketing of certain Colorado Area No. 2 potatoes and for improving the income producers receives from the sale of such potatoes. The Committee believes that the marketing of Area No. 2 potatoes is improved when the demand for such potatoes improves. Based on the experience of its members and input from buyers, the Committee determined that demand for the varieties affected by this rule would be better if such potatoes were consistently sized and larger. In this regard, the Committee determined that an increase in the minimum size of the affected varieties by an eighth of an inch was the optimal size increase to best improve demand. The establishment of a larger minimum diameter, 2
                    <FR>1/2</FR>
                     inches for example, would not have met with the Committee's, nor the Colorado Area No. 2 potato industry's, objective of satisfying the buyers of their potatoes and thereby increasing the marketing of the affected potato varieties. In addition, a larger minimum size would have required producers and handlers to divert a larger quantity of potatoes to lower return processing outlets. 
                </P>
                <P>With regard to questions by some of the commenters pertaining to why the regulation affects only certain varieties, the Committee determined that a marketing problem does not exist for round varieties or potatoes of the Russet Burbank, Russet Norkotah, and Silverton Burbank varieties. Round potatoes, including various white, red, and yellow varieties, generally have a different fresh market niche than do Russet potato varieties, and as such, the Committee continues to believe that the minimum diameter of 2 inches is appropriate for that market. Moreover, the long, thin shape of the Russet Burbank, Russet Norkotah, and Silverton Russet varieties cause a significant quantity of these potatoes to fall through the sizing screens in the grading equipment, even when the potatoes are of adequate size and weight. When potatoes are being graded, sized, and otherwise prepared for market, they are run on conveyer belts that include sections with screens that allow potatoes of different sizes to fall through adjustable openings to other conveyer belts. This is the method generally used by the industry to ensure that specific sized potatoes are segregated and thus packaged with similar sized potatoes. If too many potatoes of a desired size and weight for the fresh market fall through the sizing screens to belts conveying the potatoes to bins destined for a processor, for example, the industry loses money on the potential high-value sales of those potatoes into the fresh market. </P>
                <HD SOURCE="HD1">The Impact of the Proposed Size Change on Consumers </HD>
                <P>Finally, most of the comments reflected concern as to how consumers would be affected by this rule and why they would want to support it. Consumers purchasing Colorado Area No. 2 potatoes will benefit from this rule by continuing to have available a stable supply that is of consistent quality and of good marketable size. Although prices to consumers for the slightly larger potatoes may be higher, prices at retail are affected by many variables. The economic impact of this rule, which affects only a small portion of the total number of potatoes available in the fresh market, would likely be insignificant to the consumer, while significantly beneficial to the producers of such potatoes. </P>
                <P>Based on the comments received, no changes will be made to the rule as proposed. </P>
                <P>
                    A small business guide on complying with fruit, vegetable, and specialty crop marketing agreements and orders may be viewed at: 
                    <E T="03">http://www.ams.usda.gov/fv/moab.html.</E>
                     Any questions about the compliance guide should be sent to Jay Guerber at the previously mentioned address in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. 
                </P>
                <P>After consideration of all relevant matter presented, including the information and recommendation submitted by the Committee and other available information, it is hereby found that this rule, as hereinafter set forth, will tend to effectuate the declared policy of the Act. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 948 </HD>
                    <P>Marketing Agreements, Potatoes, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <REGTEXT TITLE="7" PART="948">
                    <AMDPAR>For the reasons set forth in the preamble, 7 CFR part 948 is amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 948—IRISH POTATOES GROWN IN COLORADO </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 7 CFR part 948 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>7 U.S.C. 601-674. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="948">
                    <AMDPAR>2. Section 948.386 is amended by revising the introductory text and paragraph (a) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 948.386 </SECTNO>
                        <SUBJECT>Handling regulation. </SUBJECT>
                        <P>No person shall handle any lot of potatoes grown in Area No. 2 unless such potatoes meet the requirements of paragraphs (a), (b), and (c) of this section, or unless such potatoes are handled in accordance with paragraphs (d) and (e), or (f) of this section. </P>
                        <P>
                            (a) 
                            <E T="03">Minimum grade and size requirements.</E>
                             (1) 
                            <E T="03">Round varieties,</E>
                             U.S. No. 2, or better grade, 2 inches minimum diameter. 
                        </P>
                        <P>
                            (2) 
                            <E T="03">All other varieties.</E>
                             U.S. No. 2, or better grade, 2 inches minimum diameter or 4 ounces minimum weight: 
                            <E T="03">Provided,</E>
                             That the Russet Burbank, Russet Norkotah, and Silverton Russet varieties shall be 1
                            <FR>7/8</FR>
                             inches minimum diameter. 
                        </P>
                        <P>
                            (3) 
                            <E T="03">All varieties.</E>
                             Size B, if U.S. No. 1 grade. 
                        </P>
                        <P>
                            (4) 
                            <E T="03">All varieties.</E>
                             1-inch minimum diameter to 1
                            <FR>3/4</FR>
                             inches maximum diameter, if at least U.S. No. 1 grade. 
                        </P>
                        <P>(5) None of the above categories of potatoes identified in paragraphs (a)(1) through (a)(4) of this section may be commingled in the same bag or other container.</P>
                    </SECTION>
                </REGTEXT>
                <STARS/>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>A.J. Yates, </NAME>
                    <TITLE>Administrator, Agricultural Marketing Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15064 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-02-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="40848"/>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <CFR>21 CFR Part 884</CFR>
                <DEPDOC>[Docket No. 99N-0922]</DEPDOC>
                <SUBJECT>Obstetric and Gynecology Devices; Effective Date of Requirement for Premarket Approval for Glans Sheath Devices</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is issuing a final rule to require the filing of a premarket approval application (PMA) or a notice of completion of product development protocol (PDP) for glans sheath medical devices. The agency has previously published its findings regarding the degree of risk of illness or injury designed to be eliminated or reduced by requiring the devices to meet the statute's approval requirements and the benefits to the public from the use of the devices.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective June 14, 2002.</P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Colin M. Pollard, Center for Devices and Radiological Health (HFZ-470), Food and Drug Administration, 9200 Corporate Blvd., Rockville, MD  20850, 301-594-1180.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>
                    Section 513 of the Federal Food, Drug, and Cosmetic Act (the act) (21 U.S.C. 360c) requires the classification of medical devices into one of three regulatory classes: Class I (general controls), class II (special controls), and class III (premarket approval). In the 
                    <E T="04">Federal Register</E>
                     of December 29, 1994 (59 FR 67185), FDA issued a final rule classifying glans sheath devices into class III. Section 515(b)(1) of the act (21 U.S.C. 360e(b)(1)) establishes the requirement that the Secretary of Health and Human Services issue a regulation subjecting a preamendments device that FDA has classified into class III to premarket approval.
                </P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of May 10, 1999 (64 FR 24967), FDA issued a proposed rule to require the filing of a PMA or a notice of completion of a PDP for glans sheath devices. In accordance with section 515(b)(2)(A) of the act, FDA included in the preamble to the proposed rule the agency's proposed findings regarding the degree of risk of illness or injury intended to be eliminated or reduced by requiring the device to meet the statute's approval requirements as well as the benefits to the public from use of the device.
                </P>
                <P>The May 10, 1999, proposed rule also provided an opportunity for interested persons to submit comments on the proposed rule and the agency's proposed findings. In accordance with section 515(b)(2)(A) of the act, FDA also provided an opportunity for interested persons to request a change in the classification of the device based on new information relevant to its classification. Any petition requesting a change in the classification of the devices was required to be submitted by May 26, 1999. The comment period closed August 9, 1999.</P>
                <P>FDA received no petitions requesting a change in the classification of glans sheath devices. FDA received no comments on the proposed rule.</P>
                <HD SOURCE="HD1">II. Findings With Respect to Risks and Benefits</HD>
                <P>Under section 515(b)(3) of the act, FDA is adopting the findings as published in the proposed rule of May 10, 1999. As required by section 515(b) of the act, FDA published its findings regarding:  (1) The degree of risk of illness or injury designed to be eliminated or reduced by requiring that these devices have an approved PMA or a declared completed PDP, and (2) the benefits to the public from the use of the device.</P>
                <P>These findings are based on the reports and recommendations of the Obstetrics and Gynecology Devices Panel, an FDA advisory committee for the classification of the devices as referenced in the May 10, 1999, proposed rule.</P>
                <HD SOURCE="HD1">III. The Final Rule</HD>
                <P>Under section 515(b)(3) of the act, FDA adopts the findings as published in the preamble to the proposed rule and issues this final rule to require premarket approval of glans sheath devices. This final rule revises part 884 (21 CFR part 884).</P>
                <P>Under the final rule, a PMA or a notice of completion of a PDP is required to be filed on or before September 12, 2002, for any glans sheath device that was in commercial distribution before May 28, 1976, or that has been found by FDA to be substantially equivalent to such a device on or before September 12, 2002.  If a PMA or notice of completion of a PDP is filed for such devices within this time limit, the applicant will be permitted to continue marketing its glans sheath device during FDA's review of its submission. Any other glans sheath device that was not in commercial distribution before May 28, 1976, is required to have an approved PMA or a declared completed PDP in effect before it may be marketed.</P>
                <P>If a PMA or a notice of completion of a PDP for a glans sheath device is not filed on or before September 12, 2002, that device is deemed adulterated under section 501(f)(1)(A) of the act (21 U.S.C. 351(f)(1)(A)), and commercial distribution of the device must cease immediately. The device may, however, be distributed for investigational use, if the requirements of the investigational device exemption (IDE) regulations (part 812 (21 CFR part 812)) are met.  Because the intended use of a glans sheath device is contraception, FDA considers it to be a significant risk device as defined in the IDE regulations (§ 812.3(m)(4)).</P>
                <P>As of September 12, 2002, the exemptions in § 812.2(c)(1) and (c)(2) from the requirements of the IDE regulations for preamendments class III devices cease to apply to any glans sheath device that is: (1) Not legally on the market on or before September 12, 2002; or (2) legally on the market by September 12, 2002, but for which a PMA or notice of completion of a PDP is not filed by September 12, 2002, or for which PMA approval has been denied or withdrawn.  FDA cautions that manufacturers who are not immediately planning to submit a PMA or notice of completion of a PDP should submit IDE applications to FDA by August 13, 2002, to minimize the possibility of interrupting shipment of the device. At this time, FDA is not aware of any firm that is marketing this device.</P>
                <HD SOURCE="HD1">IV. Environmental Impact</HD>
                <P>The agency has determined under 21 CFR 25.30(h) that this action is of a type that does not individually or cumulatively have a significant effect on the human environment. Therefore, neither an environmental assessment nor an environmental impact statement is required.</P>
                <HD SOURCE="HD1">V. Analysis of Impacts</HD>
                <P>
                    FDA has examined the impacts of the final rule under Executive Order 12866 and the Regulatory Flexibility Act (5 U.S.C. 601-612), and the Unfunded Mandates Reform Act of 1995 (Public Law 104-4). Executive Order 12866 directs agencies to assess all costs and benefits of available regulatory alternatives and, when regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety, 
                    <PRTPAGE P="40849"/>
                    and other advantages; distributive impacts; and equity). The agency believes that this final rule is consistent with the regulatory philosophy and principles identified in the Executive order. In addition, the final rule is not a significant regulatory action as defined by the Executive order and so is not subject to review under the Executive order.
                </P>
                <P>If a rule has a significant economic impact on a substantial number of small entities, the Regulatory Flexibility Act requires agencies to analyze regulatory options that would minimize any significant impact of a rule on small entities. FDA has reviewed the situation and believes that no PMAs will be submitted under this final rule.  FDA is not aware of any marketing of these devices at present. FDA has not received any premarket submissions for glans sheath devices in more than 15 years.  Consequently, the agency certifies that the final rule will not have a significant economic impact on a substantial number of small entities.  Therefore, under the Regulatory Flexibility Act, no further analysis is required.</P>
                <P>Section 202(a) of the Unfunded Mandates Reform Act of 1995 (Public Law 104-4) requires that agencies prepare a written statement of anticipated costs and benefits before proposing any rule that may result in an expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million in any one year (adjusted annually for inflation). The Unfunded Mandates Reform Act does not require FDA to prepare a statement of costs and benefits for the final rule, because the final rule is not expected to result in any 1-year expenditure that would exceed $100 million adjusted for inflation.</P>
                <HD SOURCE="HD1">VI. Paperwork Reduction Act of 1995</HD>
                <P>This final rule contains information collection provisions that are subject to review by the Office of Management and Budget (OMB) under the Paperwork Reduction Act of 1995 (the PRA). The burden hours required for § 884.5320(c), included in the collection entitled “Premarket Approval of Medical Devices—21 CFR Part 814,”  (64 FR 4112, January 27, 1999) are reported and approved under OMB control number 0910-0231. Therefore, clearance by OMB under the PRA is not required.</P>
                <HD SOURCE="HD1">VII. Federalism</HD>
                <P>FDA has analyzed this final rule in accordance with the principles set forth in Executive Order 13132. FDA has determined that the rule does not contain policies that have substantial direct effects on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government. Accordingly, the agency has concluded that the rule does not contain policies that have federalism implications as defined in the Executive order and, consequently, a federalism summary impact statement is not required.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 21 CFR Part 884</HD>
                    <P>Medical devices.</P>
                </LSTSUB>
                <REGTEXT TITLE="21" PART="884">
                    <AMDPAR>Therefore, under the Federal Food, Drug, and Cosmetic Act and under authority delegated to the Commissioner of Food and Drugs, 21 CFR part 884 is amended as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 884—OBSTETRICAL AND GYNECOLOGICAL DEVICES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 21 CFR part 884 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>21 U.S.C. 351, 360, 360c, 360e, 360j, 371.</P>
                    </AUTH>
                    <AMDPAR>2. Section 884.5320 is amended by revising paragraph (c) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 884.5320</SECTNO>
                        <SUBJECT>Glans sheath.</SUBJECT>
                    </SECTION>
                    <STARS/>
                    <P>
                        (c) 
                        <E T="03">Date premarket approval application (PMA) or notice of completion of a product development protocol (PDP) is required</E>
                        . A PMA or a notice of completion of a PDP is required to be filed with the Food and Drug Administration on or before September 12, 2002, for any glans sheath that was in commercial distribution before May 28, 1976, or that has, on or before September 12, 2002, been found to be substantially equivalent to a glans sheath that was in commercial distribution before May 28, 1976. Any other glans sheath shall have an approved PMA or declared completed PDP in effect before being placed in commercial distribution.
                    </P>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: May 14, 2002.</DATED>
                    <NAME>Linda S. Kahan,</NAME>
                    <TITLE>Deputy Director, Center for Devices and Radiological Health.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15042 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE </AGENCY>
                <CFR>22 CFR Parts 41 and 42 </CFR>
                <DEPDOC>[Public Notice 4028] </DEPDOC>
                <SUBJECT>Documentation of Immigrants and Nonimmigrants Under the Immigration and Nationality Act, as Amended—Visa Fees: Interim Rule With Request for Comments; Correction </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of State. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim rule with request for comments; Correction. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The document, published on June 6, 2002, in the 
                        <E T="04">Federal Register</E>
                        (67 FR 38892) inadvertently omitted the effective date of the interim rule. This document correctly establishes the effective date as set forth in the 
                        <E T="02">DATES</E>
                         section below. This document also corrects references in the preamble that mistakenly referred to the interim rule as a proposed rule. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The interim rule, published on June 6, 2002 (67 FR 38892), became effective on June 6, 2002. Written comments may be submitted on or before July 8, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments may be submitted, in duplicate, to the Legislation and Regulations Division, Visa Services, Department of State, Washington, DC 20520-0106 or by e-mail to 
                        <E T="03">visaregs@state.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Elizabeth J. Harper, Legislation and Regulations Division, Visa Services, Department of State, Washington, DC 20520-0106, by tel. (202) 663-1221, e-mail 
                        <E T="03">harperb@state.gov,</E>
                         or by fax (202) 663-3898. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Department of State published a document in the 
                    <E T="04">Federal Register</E>
                     on June 6, 2002, (67 FR 38892), which inadvertently omitted its effective date and mistakenly referred to the interim rule as a proposed rule. This document establishes the effective date as set forth in the DATES section and makes the following correction: 
                </P>
                <P>
                    In interim rule FR DOC 02-13001 published on June 6, 2002 (67 FR 38892), on page 38893, in the first column the section entitled 
                    <E T="03">“Administrative Procedure Act”</E>
                     should read as follows: 
                </P>
                <HD SOURCE="HD1">Administrative Procedure Act </HD>
                <P>The Department of State is publishing this rule as an interim rule, with a 30-day provision for public comments. </P>
                <SIG>
                    <PRTPAGE P="40850"/>
                    <DATED>Dated: June 11, 2002. </DATED>
                    <NAME>Timothy Egert, </NAME>
                    <TITLE>Federal Register Liaison, Department of State. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15096 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4710-06-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">PENSION BENEFIT GUARANTY CORPORATION </AGENCY>
                <CFR>29 CFR Parts 4022 and 4044 </CFR>
                <SUBJECT>Benefits Payable in Terminated Single-Employer Plans; Allocation of Assets in Single-Employer Plans; Interest Assumptions for Valuing and Paying Benefits </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pension Benefit Guaranty Corporation. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Pension Benefit Guaranty Corporation's regulations on Benefits Payable in Terminated Single-Employer Plans and Allocation of Assets in Single-Employer Plans prescribe interest assumptions for valuing and paying benefits under terminating single-employer plans. This final rule amends the regulations to adopt interest assumptions for plans with valuation dates in July 2002. Interest assumptions are also published on the PBGC's Web site (
                        <E T="03">http://www.pbgc.gov</E>
                        ). 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>July 1, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Harold J. Ashner, Assistant General Counsel, Office of the General Counsel, Pension Benefit Guaranty Corporation, 1200 K Street, NW., Washington, DC 20005, 202-326-4024. (TTY/TDD users may call the Federal relay service toll-free at 1-800-877-8339 and ask to be connected to 202-326-4024.) </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The PBGC's regulations prescribe actuarial assumptions—including interest assumptions—for valuing and paying plan benefits of terminating single-employer plans covered by title IV of the Employee Retirement Income Security Act of 1974. The interest assumptions are intended to reflect current conditions in the financial and annuity markets. </P>
                <P>Three sets of interest assumptions are prescribed: (1) A set for the valuation of benefits for allocation purposes under section 4044 (found in appendix B to part 4044), (2) a set for the PBGC to use to determine whether a benefit is payable as a lump sum and to determine lump-sum amounts to be paid by the PBGC (found in appendix B to part 4022), and (3) a set for private-sector pension practitioners to refer to if they wish to use lump-sum interest rates determined using the PBGC's historical methodology (found in Appendix C to Part 4022). </P>
                <P>Accordingly, this amendment (1) adds to appendix B to part 4044 the interest assumptions for valuing benefits for allocation purposes in plans with valuation dates during July 2002, (2) adds to appendix B to part 4022 the interest assumptions for the PBGC to use for its own lump-sum payments in plans with valuation dates during July 2002, and (3) adds to appendix C to part 4022 the interest assumptions for private-sector pension practitioners to refer to if they wish to use lump-sum interest rates determined using the PBGC's historical methodology for valuation dates during July 2002. </P>
                <P>For valuation of benefits for allocation purposes, the interest assumptions that the PBGC will use (set forth in appendix B to part 4044) will be 5.70 percent for the first 25 years following the valuation date and 4.25 percent thereafter. These interest assumptions are unchanged from those in effect for June 2002. </P>
                <P>The interest assumptions that the PBGC will use for its own lump-sum payments (set forth in appendix B to part 4022) will be 4.50 percent for the period during which a benefit is in pay status and 4.00 percent during any years preceding the benefit's placement in pay status. These interest assumptions are unchanged from those in effect for June 2002. </P>
                <P>For private-sector payments, the interest assumptions (set forth in appendix C to part 4022) will be the same as those used by the PBGC for determining and paying lump sums (set forth in appendix B to part 4022). </P>
                <P>The PBGC has determined that notice and public comment on this amendment are impracticable and contrary to the public interest. This finding is based on the need to determine and issue new interest assumptions promptly so that the assumptions can reflect, as accurately as possible, current market conditions. </P>
                <P>Because of the need to provide immediate guidance for the valuation and payment of benefits in plans with valuation dates during July 2002, the PBGC finds that good cause exists for making the assumptions set forth in this amendment effective less than 30 days after publication. </P>
                <P>The PBGC has determined that this action is not a “significant regulatory action” under the criteria set forth in Executive Order 12866. </P>
                <P>
                    Because no general notice of proposed rulemaking is required for this amendment, the Regulatory Flexibility Act of 1980 does not apply. 
                    <E T="03">See</E>
                     5 U.S.C. 601(2). 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>29 CFR Part 4022 </CFR>
                    <P>Employee benefit plans, Pension insurance, Pensions, Reporting and recordkeeping requirements. </P>
                    <CFR>29 CFR Part 4044 </CFR>
                    <P>Employee benefit plans, Pension insurance, Pensions. </P>
                </LSTSUB>
                <AMDPAR>In consideration of the foregoing, 29 CFR parts 4022 and 4044 are amended as follows: </AMDPAR>
                <REGTEXT TITLE="29" PART="4022">
                    <PART>
                        <HD SOURCE="HED">PART 4022—BENEFITS PAYABLE IN TERMINATED SINGLE-EMPLOYER PLANS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 4022 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>29 U.S.C. 1302, 1322, 1322b, 1341(c)(3)(D), and 1344. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4022">
                    <AMDPAR>2. In appendix B to part 4022, Rate Set 105, as set forth below, is added to the table. (The introductory text of the table is omitted.) </AMDPAR>
                    <HD SOURCE="HD1">Appendix B to Part 4022—Lump Sum Interest Rates for PBGC Payments </HD>
                    <STARS/>
                    <GPOTABLE COLS="9" OPTS="L1,tp0,i1" CDEF="10C,10C,10C,10C,10C,10C,10C,10C,10C">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Rate set </CHED>
                            <CHED H="1">For plans with a valuation date </CHED>
                            <CHED H="2">On or after </CHED>
                            <CHED H="2">Before </CHED>
                            <CHED H="1">
                                Immediate annuity rate 
                                <LI>(percent) </LI>
                            </CHED>
                            <CHED H="1">Deferred annuities (percent) </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">1</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">2</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">3</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">n</E>
                                <E T="54">1</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">n</E>
                                <E T="54">2</E>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">  </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         * </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">105 </ENT>
                            <ENT>7-1-02 </ENT>
                            <ENT>8-1-02 </ENT>
                            <ENT>4.50 </ENT>
                            <ENT>4.00 </ENT>
                            <ENT>4.00 </ENT>
                            <ENT>4.00 </ENT>
                            <ENT>7 </ENT>
                            <ENT>8 </ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4022">
                    <PRTPAGE P="40851"/>
                    <AMDPAR>3. In appendix C to part 4022, Rate Set 105, as set forth below, is added to the table. (The introductory text of the table is omitted.) </AMDPAR>
                    <HD SOURCE="HD1">Appendix C to Part 4022—Lump Sum Interest Rates For Private-Sector Payments </HD>
                    <STARS/>
                    <GPOTABLE COLS="9" OPTS="L1,tp0,i1" CDEF="10C,10C,10C,10C,10C,10C,10C,10C,10C">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Rate set </CHED>
                            <CHED H="1">For plans with a valuation date </CHED>
                            <CHED H="2">On or after </CHED>
                            <CHED H="2">Before </CHED>
                            <CHED H="1">
                                Immediate annuity rate 
                                <LI>(percent) </LI>
                            </CHED>
                            <CHED H="1">Deferred annuities (percent) </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">1</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">2</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">3</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">n</E>
                                <E T="54">1</E>
                            </CHED>
                            <CHED H="2">
                                <E T="03">n</E>
                                <E T="54">2</E>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">  </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         * </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">105 </ENT>
                            <ENT>7-1-02 </ENT>
                            <ENT>8-1-02 </ENT>
                            <ENT>4.50 </ENT>
                            <ENT>4.00 </ENT>
                            <ENT>4.00 </ENT>
                            <ENT>4.00 </ENT>
                            <ENT>7 </ENT>
                            <ENT>8 </ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4044">
                    <PART>
                        <HD SOURCE="HED">PART 4044—ALLOCATION OF ASSETS IN SINGLE-EMPLOYER PLANS </HD>
                    </PART>
                    <AMDPAR>4. The authority citation for part 4044 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>29 U.S.C. 1301(a), 1302(b)(3), 1341, 1344, 1362. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="29" PART="4044">
                    <AMDPAR>5. In appendix B to part 4044, a new entry, as set forth below, is added to the table. (The introductory text of the table is omitted.) </AMDPAR>
                    <HD SOURCE="HD1">Appendix B to Part 4044—Interest Rates Used to Value Benefits </HD>
                    <STARS/>
                    <GPOTABLE COLS="7" OPTS="L1,tp0,i1" CDEF="s25,10,10,10,10,xls40,xls40">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">For valuation dates occurring in the month— </CHED>
                            <CHED H="1">
                                The values of 
                                <E T="03">i</E>
                                <E T="54">t</E>
                                 are: 
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">t</E>
                            </CHED>
                            <CHED H="2">
                                for 
                                <E T="03">t</E>
                                 = 
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">t</E>
                            </CHED>
                            <CHED H="2">
                                for 
                                <E T="03">t</E>
                                 = 
                            </CHED>
                            <CHED H="2">
                                <E T="03">i</E>
                                <E T="54">t</E>
                            </CHED>
                            <CHED H="2">for t = </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">  </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         * </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">July 2002 </ENT>
                            <ENT>.0570 </ENT>
                            <ENT>1-25 </ENT>
                            <ENT>.0425 </ENT>
                            <ENT>&gt;25 </ENT>
                            <ENT>N/A </ENT>
                            <ENT>N/A </ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <SIG>
                    <DATED>Issued in Washington, DC, on this 10th day of June, 2002. </DATED>
                    <NAME>Steven A. Kandarian, </NAME>
                    <TITLE>Executive Director, Pension Benefit Guaranty Corporation. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15038 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7708-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[CGD09-01-124] </DEPDOC>
                <RIN>RIN 2115-AA97 </RIN>
                <SUBJECT>Security Zone: Lake Ontario, Oswego, NY </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule; change in effective period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is revising the effective period for a temporary security zone in the Captain of the Port Buffalo zone for the Nine Mile Point and Fitzpatrick Nuclear Power Plants. This security zone is necessary to protect the Nine Mile Point and Fitzpatrick Nuclear Power Plants from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. This security zone is intended to restrict vessel traffic from a portion of Lake Ontario. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The amendment to § 165.T09-999(b) in this rule is effective on June 14, 2002. Section 165.T09-999, added at 66 FR 49286, September 27, 2001, effective from September 12, 2001, through June 15, 2002 as amended in this rule, is extended in effect through August 15, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of docket CGD09-01-124 and are available for inspection or copying at U.S. Coast Guard Marine Safety Buffalo, 1 Fuhrmann Blvd., Buffalo, NY 14203 between 8 a.m. and 4 p.m., Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lieutenant Commander David Flaherty, U.S. Coast Guard Marine Safety Office Buffalo, 1 Fuhrmann Blvd., Buffalo, NY 14203. The telephone number is (716) 843-9574. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    On September 27, 2001, we published a temporary final rule entitled Security Zone: Lake Ontario, Oswego, NY in the 
                    <E T="04">Federal Register</E>
                     (66 FR 49285). The temporary final rule established a temporary security zone in the Captain of the Port Buffalo zone for the Nine Mile Point and Fitzpatrick Nuclear Power Plants. This security zone is necessary to protect this nuclear power plant from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. 
                </P>
                <P>We are extending the effective period of the temporary final rule so that we can complete a rulemaking CGD09-02-005 Security Zones; Captain of the Port Buffalo Zone to permanently establish four permanent security zones on the navigable waters of Lake Ontario and the St. Lawrence River in the Captain of the Port Buffalo Zone. These security zones are necessary to protect the Nuclear Power Plants and the St. Lawrence Seaway system from possible acts of terrorism. Extending the effective date until August 15, 2002 should provide us enough time to complete the rulemaking. </P>
                <P>
                    We did not publish a notice of proposed rulemaking (NPRM) for this rule and it is being made effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . When we promulgated the September 12, 2001 rule, we intended to either allow it to expire on June 15, 2002, or to cancel it if we made permanent changes before that date. We published an NPRM on May 30, 2002 to propose permanent security zones for this and other power plants (67 FR 37748). That rulemaking will follow normal notice and comment procedures, and a final rule should be published before August 15, 2002. Continuing the temporary final rule in effect while the permanent rulemaking is in progress will help ensure the safety of critical infrastructure that may be the subject of subversive activity. Nuclear power plants are an important means of 
                    <PRTPAGE P="40852"/>
                    electrical energy in the region. In addition, they could be a source of severe radiological contamination throughout the region. Therefore, the Coast Guard finds good cause under 5 U.S.C. 553(b)(B) and (d)(3) for why a notice of proposed rulemaking and opportunity for comment is not required and why this rule will be made effective fewer than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>A temporary security zone is necessary to ensure the security of the Nine Mile Point and Fitzpatrick nuclear power plants, as a result of the terrorist attacks on the United States on September 11, 2001. The security zone consists of all navigable waters of Lake Ontario bounded by the following area, starting at 43°30.8′ N, 076°25.7′ W; then north to 43°31.2′ N, 076°25.7′ W; then east-northeast to 43°31.6′ N, 076°24.9′ W; then east to 43°31.8′ N, 076°23.2′ W; then south to 43°31.5′ N, 076°23.2′ W; and then following the shoreline back to the point of origin. Entry into, transit through or anchoring within this security zone is prohibited unless authorized by the Captain of the Port Buffalo or his designated on-scene representative. The designated on-scene representative will be the Patrol Commander and may be contacted via VHF/FM Marine Channel 16. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040, February 26, 1979). </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. </P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we offered to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact Marine Safety Office Buffalo (see 
                    <E T="02">ADDRESSES.</E>
                    ) 
                </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble. </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Indian Tribal Governments </HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. </P>
                <HD SOURCE="HD1">Energy Effects </HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211. </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>
                    The Coast Guard considered the environmental impact of this regulation and concluded that, under figure 2-1, paragraph (34)(g) of Commandant Instruction M16475.1C, it is categorically excluded from further environmental documentation. A “Categorical Exclusion Determination” is available in the docket for inspection or copying where indicated under 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subject in 33 CFR Part 165 </HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and record keeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <REGTEXT TITLE="33" PART="165">
                    <PRTPAGE P="40853"/>
                    <AMDPAR>For the reasons set out in the preamble, the Coast Guard amends 33 CFR part 165 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <P>2. In § 165.T09-999, paragraph (b) is revised to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 165.T09-999 </SECTNO>
                        <SUBJECT>Security Zone; Lake Ontario, Oswego, NY. </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Effective time and date.</E>
                             This section is effective from September 12, 2001 through August 15, 2002. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>S.D. Hardy, </NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Buffalo. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15127 Filed 6-12-02; 12:37 pm] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[CGD09-01-125] </DEPDOC>
                <RIN>RIN 2115-AA97 </RIN>
                <SUBJECT>Security Zone; Lake Ontario, Rochester, NY </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule; change in effective period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is revising the effective period for a temporary security zone in the Captain of the Port Buffalo zone for the Ginna Nuclear Power Plant. This security zone is necessary to protect this nuclear power plant from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. This security zone is intended to restrict vessel traffic from a portion of Lake Ontario. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The amendment to § 165.T09-101(b) in this rule is effective on June 14, 2002. Section 165.T09-101, added at 66 FR 49285, September 27, 2001, effective September 12, 2001, through June 15, 2002, as amended in this rule, is extended in effect through August 15, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of docket CGD09-01-125 and are available for inspection or copying at U.S. Coast Guard Marine Safety Buffalo, 1 Fuhrmann Blvd., Buffalo, NY 14203 between 8 a.m. and 4 p.m., Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lieutenant Commander David Flaherty, U.S. Coast Guard Marine Safety Office Buffalo, 1 Fuhrmann Blvd., Buffalo, NY 14203. The telephone number is (716) 843-9574. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    On September 27, 2001, we published a temporary final rule entitled Security Zone: Lake Ontario, Rochester, NY in the 
                    <E T="04">Federal Register</E>
                     (66 FR 49284). The temporary final rule established a temporary security zone in the Captain of the Port Buffalo zone for the Ginna Nuclear Power Plant. This security zone is necessary to protect this nuclear power plant from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. 
                </P>
                <P>We are extending the effective period of the temporary final rule so that we can complete a rulemaking entitled “Security Zones; Captain of the Port Buffalo Zone” (67 FR 37748, May 30, 2002; docket number CGD09-02-005) to permanently establish four security zones on the navigable waters of Lake Ontario and the St. Lawrence River in the Captain of the Port Buffalo Zone. These security zones are necessary to protect the nuclear power plants and the St. Lawrence Seaway system from possible acts of terrorism. Extending the effective date until August 15, 2002 should provide us enough time to complete the rulemaking. </P>
                <P>
                    We did not publish a notice of proposed rulemaking (NPRM) for this rule and it is being made effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . When we promulgated the September 12, 2001 rule, we intended to either allow it to expire on June 15, 2002, or to cancel it if we made permanent changes before that date. We published an NPRM on May 30, 2002 to propose permanent security zones for this and other power plants (67 FR 37748). That rulemaking will follow normal notice and comment procedures, and a final rule should be published before August 15, 2002. Continuing the temporary final rule in effect while the permanent rulemaking is in progress will help ensure the safety of critical infrastructure that may be the subject of subversive activity. Nuclear power plants are important means of electrical energy in the region. In addition, they could be a source of severe radiological contamination throughout the region. Therefore, the Coast Guard finds good cause under 5 U.S.C. 553(b)(B) and (d)(3) for why a notice of proposed rulemaking and opportunity for comment is not required and why this rule will be made for comment is not required and why this rule will be made effective fewer than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>A temporary security zone is necessary to ensure the security of the security of the Ginna nuclear power plant, as a result of the terrorist attacks on the United States on 11 September 2001. The security zone consists of all navigable waters of Lake Ontario bounded by the following area, starting at 43°16.9′ N, 077°18.9′ W; then north to 43°17.3′ N, 077°18.9′ W; then east to 43°17.3′ N, 077°18.3′ W; then south to 43°16.7′ N, 077°18.3′ W; then following the shoreline back to starting point (NAD 83). Entry into, transit through or anchoring within this security zone is prohibited unless authorized by the Captain of the Port Buffalo or his designated on-scene representative. The designated on-scene representative will be the Patrol Commander and may be contacted via VHF/FM Marine Channel 16.</P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040, February 26, 1979). </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. </P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement 
                    <PRTPAGE P="40854"/>
                    Fairness Act of 1996 (Public Law 104-121), we offered to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact Marine Safety Office Buffalo (see 
                    <E T="02">ADDRESSES</E>
                    .) 
                </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble. </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Indian Tribal Governments </HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. </P>
                <HD SOURCE="HD1">Energy Effects </HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211. </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>
                    The Coast Guard considered the environmental impact of this regulation and concluded that, under figure 2-1, paragraph (34)(g) of Commandant Instruction M16475.1C, it is categorically excluded from further environmental documentation. A “Categorical Exclusion Determination” is available in the docket for inspection or copying where indicated under 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subject in 33 CFR Part 165 </HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and record keeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>For the reasons set out in the preamble, the Coast Guard amends 33 CFR Part 165 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for Part 165 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. In § 165.T09-101, paragraph (b) is revised to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T09-101 </SECTNO>
                        <SUBJECT>Security Zone; Lake Ontario, Rochester, NY. </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Effective time and date.</E>
                             This section is effective from September 12, 2001, through August 15, 2002. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>S.D. Hardy, </NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Buffalo. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15128 Filed 6-12-02; 12:37 pm] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[CGD09-01-128] </DEPDOC>
                <RIN>RIN 2115-AA97 </RIN>
                <SUBJECT>Security Zone; Saint Lawrence River, Massena, NY </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule; change in effective period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is revising the effective period for a temporary security zone in the Captain of the Port Buffalo zone for the Moses-Saunders Power Dam. This security zone is necessary to protect this power dam from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. This security zone is intended to restrict vessel traffic from a portion of the Saint Lawrence River. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The amendment to § 165.T09-103(b) in this rule is effective on June 14, 2002. Section 165.T09-103, added at 66 FR 49290, September 27, 2001, effective September 12, 2001, through June 15, 2002, as amended in this rule, is extended in effect through August 15, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of 
                        <PRTPAGE P="40855"/>
                        docket CGD09-01-128 and are available for inspection or copying at U.S. Coast Guard Marine Safety Buffalo, 1 Fuhrmann Blvd., Buffalo, NY 14203 between 8 a.m. and 4 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lieutenant Commander David Flaherty, U.S. Coast Guard Marine Safety Office Buffalo, (716) 843-9574. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION: </HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    On September 27, 2001, we published a temporary final rule entitled Security Zone: Saint Lawrence River, Massena, NY in the 
                    <E T="04">Federal Register</E>
                     (66 FR 49288). The temporary final rule established a temporary security zone in the Captain of the Port Buffalo zone for the Moses-Saunders Power Dam. This security zone is necessary to protect this power dam from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. 
                </P>
                <P>We are extending the effective period of the temporary final rule so that we can complete a rulemaking entitled Security Zones; Captain of the Port Buffalo Zone (67 FR 37748, May 30, 2002; docket number CGD09-02-005) to permanently establish four permanent security zones on the navigable waters of Lake Ontario and the St. Lawrence River in the Captain of the Port Buffalo Zone. These security zones are necessary to protect the Nuclear Power Plants and the St. Lawrence Seaway system from possible acts of terrorism. Extending the effective date until August 15, 2002 should provide us enough time to complete the rulemaking. </P>
                <P>
                    We did not publish a notice of proposed rulemaking (NPRM) for this rule and it is being made effective less than thirty days after publication in the 
                    <E T="04">Federal Register</E>
                    . When we promulgated the September 12, 2001 rule, we intended to either allow it to expire on June 15, 2002, or to cancel it if we made permanent changes before that date. We published an NPRM on May 30, 2002 to propose permanent security zones for this and other power plants (67 FR 37748). That rulemaking will follow normal notice and comment procedures, and a final rule should be published before August 15, 2002. Continuing the temporary final rule in effect while the permanent rulemaking is in progress will help ensure the safety of critical infrastructure that may be the subject of subversive activity. The power dam is an important means of electrical energy in the region. In addition, subversive acts could pose a serious threat to the movement of commercial shipping through the Saint Lawrence Seaway system. Therefore, the Coast Guard finds good cause under 5 U.S.C. 553(b)(B) and (d)(3) for why a notice of proposed rulemaking and opportunity for comment is not required and why this rule will be made effective fewer than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>A temporary security zone is necessary to ensure the security of the Moses-Saunders Power Dam, as a result of the terrorist attacks on the United States on September 11, 2001. The security zone consists of all navigable waters of the St. Lawrence River bounded by the following area, starting at 45°00.73′ N, 074°47.85′ W; southeast following the international border to 45°00.25′ N, 074°47.56′ W; then southwest to 45°00.16′ N, 074°47.76′ W; then east to the shoreline at 45°00.16′ N, 074°47.93′ W; then northwest to 45°00.36′ N, 074°48.16′ W; then northeast back to the starting point. These coordinates are based upon North American Datum 1983 (NAD 83). Persons desiring to transit the area of the Moses-Saunders Power Dam security zone must contact the Supervisor, Marine Safety Detachment Massena at telephone number (315) 764-3284, or on VHF/FM channel 16 to seek permission to transit the area. If permission is granted, all persons and vessels shall comply with the instructions of the Captain of the Port or his or her designated representative. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040, February 26, 1979). </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. </P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we offered to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact Marine Safety Office Buffalo (
                    <E T="03">see</E>
                      
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>
                    The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble. 
                    <PRTPAGE P="40856"/>
                </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Indian Tribal Governments </HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. </P>
                <HD SOURCE="HD1">Energy Effects </HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211. </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>
                    The Coast Guard considered the environmental impact of this regulation and concluded that, under figure 2-1, paragraph (34)(g) of Commandant Instruction M16475.1C, it is categorically excluded from further environmental documentation. A “Categorical Exclusion Determination” is available in the docket for inspection or copying where indicated under 
                    <E T="02">ADDRESSES</E>
                    . 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subject in 33 CFR Part 165 </HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and record keeping requirements, Security measures, Waterways. </P>
                </LSTSUB>
                  
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>For the reasons set out in the preamble, the Coast Guard amends 33 CFR Part 165 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for Part 165 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. In § 165.T09-103, paragraph (b) is revised to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T09-103</SECTNO>
                        <SUBJECT>Security Zone; Saint Lawrence River, Massena, NY. </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Effective time and date.</E>
                             This section is effective from September 12, 2001, through August 15, 2002. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>S.D. Hardy, </NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port Buffalo. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15129 Filed 6-12-02; 12:37 pm] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[CGD09-01-137]</DEPDOC>
                <RIN>RIN 2115-AA97</RIN>
                <SUBJECT>Security Zone; Lake Michigan, Point Beach Nuclear Power Plant</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule; change in effective period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is revising the effective period for a temporary security zone in the Captain of the Port Milwaukee zone for the Point Beach Nuclear Power Plant. This security zone is necessary to protect this nuclear power plant from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. This security zone is intended to restrict vessel traffic from a portion of Lake Michigan.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The amendment to § 165.T09-110(b) in this rule is effective on June 14, 2002. Section 165.T09-110, added at 66 FR 52042, October 12, 2001, effective from September 28, 2001, through June 15, 2002, as amended in this rule, is extended in effect through August 1, 2002.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of docket CGD09-01-137 and are available for inspection or copying at U.S. Coast Guard Marine Safety Milwaukee, 2420 South Lincoln Memorial Drive, Milwaukee, Wisconsin 53207 between 7 a.m. and 3:30 p.m., Monday through Friday, except Federal holidays.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Marine Science Technician, Chief David McClintock, U.S. Coast Guard Marine Safety Office Milwaukee, at (414) 747-7155.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information</HD>
                <P>
                    On October 12, 2001, we published a temporary final rule entitled “Security Zone: Lake Michigan, Point Beach Nuclear Power Plant, WI” in the 
                    <E T="04">Federal Register</E>
                     (66 FR 52041). The temporary final rule established a temporary security zone in the Captain of the Port Milwaukee zone for the Point Beach Nuclear Power Plant. This security zone is necessary to protect this nuclear power plant from possible sabotage or other subversive acts, accidents, or possible acts of terrorism.
                </P>
                <P>We are extending the effective period of the temporary final rule so that we can complete rulemaking entitled “Security Zone; Captain of the Port Milwaukee Zone, Lake Michigan” (docket number CGD09-02-007; 67 FR 19142, April 18, 2002) to establish a permanent security zone for Point Beach Nuclear Power Plant. Extending the effective date until August 1, 2002 should provide us enough time to complete the rulemaking.</P>
                <P>
                    We did not publish a notice of proposed rulemaking (NPRM) for this rule and it is being made effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . When we promulgated the September 28th, 2001 rule, we intended to either allow it to expire on June 15, 2002, or to cancel it if we made permanent changes before that date. We published an NPRM on April 18, 2002 to propose permanent security zones for this and another power plant (67 FR 19142). That rulemaking will follow normal notice and comment procedures, and a final rule should be published before August 1, 2002. Continuing the temporary final rule in effect while the permanent rulemaking is in progress will help ensure the safety of critical infrastructure that may be the subject of subversive activity.
                    <PRTPAGE P="40857"/>
                </P>
                <P>
                    Nuclear power plants are an important means of electrical energy in the region. In addition, they could be a source of severe radiological contamination throughout the region. Therefore, the Coast Guard finds good cause under 5 U.S.C. 553(b)(B) and (d)(3) for why a notice of proposed rulemaking and opportunity for comment is not required and why this rule will be made effective fewer than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">Background and Purpose</HD>
                <P>A temporary security zone is necessary to ensure the security of the Point Beach nuclear power plant, as a result of the terrorist attacks on the United States on September 11, 2001. The security zone consists of all navigable waters of Western Lake Michigan commencing from a point on the shoreline at 44°17.1′ N, 087°32.3′ W; then northeasterly to 44°17.4′ N, 087°31.6′ W; then southeasterly to 44°16.8′ N, 087°31.3′ W; then southwesterly 44°16.9′ N, 087°32.3′ W; then northwesterly along the shoreline to the point of origin. These coordinates are based upon North American Datum 1983 (NAD 83). Entry into, transit through or anchoring within this security zone is prohibited unless authorized by the Captain of the Port Milwaukee or his designated on-scene representative. The designated on-scene representative will be the Patrol Commander and may be contacted via VHF/FM Marine Channel 16.</P>
                <HD SOURCE="HD1">Regulatory Evaluation</HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040, February 26, 1979).</P>
                <HD SOURCE="HD1">Small Entities</HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities.</P>
                <HD SOURCE="HD1">Assistance for Small Entities</HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we offered to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact Marine Safety Office Milwaukee (
                    <E T="03">see</E>
                      
                    <E T="02">ADDRESSES.</E>
                    )
                </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247).</P>
                <HD SOURCE="HD1">Collection of Information</HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD1">Federalism</HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism.</P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
                <HD SOURCE="HD1">Taking of Private Property</HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
                <HD SOURCE="HD1">Civil Justice Reform</HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
                <HD SOURCE="HD1">Protection of Children</HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children.</P>
                <HD SOURCE="HD1">Indian Tribal Governments</HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD1">Energy Effects</HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
                <HD SOURCE="HD1">Environment</HD>
                <P>
                    The Coast Guard considered the environmental impact of this regulation and concluded that, under figure 2-1, paragraph (34)(g) of Commandant Instruction M16475.1C, it is categorically excluded from further environmental documentation. A “Categorical Exclusion Determination” is available in the docket for inspection or copying where indicated under 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <PRTPAGE P="40858"/>
                    <HD SOURCE="HED">List of Subject in 33 CFR Part 165</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and record keeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>For the reasons set out in the preamble, the Coast Guard amends 33 CFR Part 165 as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. In § 165.T09-110, paragraph (b) is revised to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T09-110 </SECTNO>
                        <SUBJECT>Security Zone; Lake Michigan, Point Beach, WI.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Effective time and date.</E>
                             This section is effective from September 28, 2001, through August 1, 2002.
                        </P>
                    </SECTION>
                </REGTEXT>
                <STARS/>
                <SIG>
                    <DATED>Dated: May 31, 2002.</DATED>
                    <NAME>M.R. DeVries,</NAME>
                    <TITLE>Commander, U.S. Coast Guard, Captain of the Port Milwaukee.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15130 Filed 6-12-02; 12:40 pm]</FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[CGD09-01-138] </DEPDOC>
                <RIN>RIN 2115-AA97 </RIN>
                <SUBJECT>Security Zone; Lake Michigan, Kewaunee Nuclear Power Plant </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule; change in effective period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is revising the effective period for a temporary security zone in the Captain of the Port Milwaukee zone for the Kewaunee Nuclear Power Plant. This security zone is necessary to protect the Kewaunee Nuclear Power Plant from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. This security zone is intended to restrict vessel traffic from a portion of Lake Michigan. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The amendment to § 165.T09-109 (b) in this rule is effective on June 14, 2002. Section 165.T09-109, added at 66 FR 52038, October 12, 2001, effective from September 28, 2001, through June 15, 2002, as amended in this rule, is extended in effect through August 1, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of docket CGD09-01-138 and are available for inspection or copying at U.S. Coast Guard Marine Safety Milwaukee, 2420 South Lincoln Memorial Drive, Milwaukee, Wisconsin 53207 between 7 a.m. and 3:30 p.m., Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Marine Science Technician, Chief David McClintock, U.S. Coast Guard Marine Safety Office Milwaukee, 2420 South Lincoln Memorial Drive, Milwaukee, Wisconsin 53402. The telephone number is (414) 747-7155. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    On October 12, 2001, we published a temporary final rule entitled “Security Zone: Lake Michigan, Kewaunee Nuclear Power Plant, WI” in the 
                    <E T="04">Federal Register</E>
                     (66 FR 52036). The temporary final rule established a temporary security zone in the Captain of the Port Milwaukee zone for the Kewaunee Nuclear Power Plant. This security zone is necessary to protect this nuclear power plant from possible sabotage or other subversive acts, accidents, or possible acts of terrorism. 
                </P>
                <P>We are extending the effective period of the temporary final rule so that we can complete a rulemaking entitled “Security Zone; Captain of the Port Milwaukee Zone, Lake Michigan” (docket number CGD09-02-007; 67 FR 19142, April 18, 2002) to establish a permanent security zone for Kewaunee Nuclear Power Plant. Extending the effective date until August 1, 2002 will provide enough time to complete the entire public notice and comment rulemaking prior to establishing permanent security zones in place of the temporary security zones. </P>
                <P>
                    We did not publish a notice of proposed rulemaking (NPRM) for this rule and it is being made effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . When we promulgated the September 28th, 2001 rule, we intended to either allow it to expire on June 15, 2002, or to cancel it if we made permanent changes before that date. We published an NPRM on April 18, 2002 to propose permanent security zones for this and another power plant (67 FR 19142). That rulemaking will follow normal notice and comment procedures, and a final rule should be published before August 1, 2002. Continuing the temporary final rule in effect while the permanent rulemaking is in progress will help ensure the safety of critical infrastructure that may be the subject of subversive activity. 
                </P>
                <P>
                    Nuclear power plants are an important means of electrical energy in the region. In addition, they could be a source of severe radiological contamination throughout the region. Therefore, the Coast Guard finds good cause under 5 U.S.C. 553 (b)(B) and (d)(3) for why a notice of proposed rulemaking and opportunity for comment is not required and why this rule will be made effective fewer than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>A temporary security zone is necessary to ensure the security of the Kewaunee nuclear power plant, as a result of the terrorist attacks on the United States on 11 September 2001. The security zone consists of all navigable waters of Western Lake Michigan commencing from a point on the shoreline at 44°20.85′ N, 087°32.1′ W; then easterly to 44°20.85′ N, 087°31.4′ W; then southerly to 44°20.35′ N, 087°31.4′ W; then westerly to 44°20.35′ N, 087°32.1′ W; then northerly following the shoreline to the point of origin. These coordinates are based upon North American Datum 1983 (NAD 83). Entry into, transit through or anchoring within this security zone is prohibited unless authorized by the Captain of the Port Milwaukee or his designated on-scene representative. The designated on-scene representative will be the Patrol Commander and may be contacted via VHF/FM Marine Channel 16. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040, February 26, 1979). </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>
                    Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently 
                    <PRTPAGE P="40859"/>
                    owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. 
                </P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we offered to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact Marine Safety Office Milwaukee (see 
                    <E T="02">ADDRESSES).</E>
                </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble. </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Indian Tribal Governments </HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. </P>
                <HD SOURCE="HD1">Energy Effects </HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211. </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>
                    The Coast Guard considered the environmental impact of this regulation and concluded that, under figure 2-1, paragraph (34)(g) of Commandant Instruction M16475.1C, it is categorically excluded from further environmental documentation. A “Categorical Exclusion Determination” is available in the docket for inspection or copying where indicated under 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subject in 33 CFR Part 165 </HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and record keeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>For the reasons set out in the preamble, the Coast Guard amends 33 CFR Part 165 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for Part 165 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. In § 165.T09-109, paragraph (b) is revised to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T09-109 </SECTNO>
                        <SUBJECT>Security Zone; Lake Michigan, Kewaunee, WI. </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Effective time and date.</E>
                             This section is effective from September 28, 2001, through August 1, 2002. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 6, 2002. </DATED>
                    <NAME>M.R. DeVries, </NAME>
                    <TITLE>Commander, U.S. Coast Guard, Captain of the Port Milwaukee. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15131 Filed 6-12-02; 12:40 pm] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[CGD01-01-187] </DEPDOC>
                <RIN>RIN 2115-AA97 </RIN>
                <SUBJECT>Regulated Navigation Area, Safety and Security Zones; Long Island Sound Marine Inspection and Captain of the Port Zone </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule; change in effective period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Coast Guard is extending the effective period of a regulated navigation area (RNA) and certain safety and security zones published January 4, 2002. This change will extend the effective period of the temporary final rule until November 15, 2002, allowing adequate time for informal rulemaking to develop a permanent rule. This rule will continue to regulate the circumstances under which certain vessels may enter, transit or operate 
                        <PRTPAGE P="40860"/>
                        within the regulated navigation area and will exclude all vessels from operating within 700 yards of the Millstone Nuclear Power Plant or 100 yards of anchored Coast Guard vessels. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The amendments of §§ 165.T01-153 and 165.T01-154 in this rule are effective June 15, 2002. Sections 165.T01-153 and 165.T01-154, added at 67 FR 519 and 520, January 4, 2002, effective December 10, 2001 until June 15, 2002, as amended in this rule, are extended in effect until November 15, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Documents indicated in this preamble are available for inspection and copying at Waterways Management, Coast Guard Group/Marine Safety Office Long Island Sound, 120 Woodward Ave., New Haven, CT 06512, between 8 a.m. and 3 p.m., Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lieutenant Pamela Garcia, Waterways Management, Coast Guard GP/MSO Long Island Sound at (203) 468-4429. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    On January 4, 2002, we published a temporary final rule (TFR) entitled “Regulated Navigation Areas, Safety And Security Zones: Long Island Sound Marine Inspection Zone and Captain of the Port Zone” in the 
                    <E T="04">Federal Register</E>
                     (67 FR 517). The effective period for this rule was from December 10, 2001 until June 15, 2002. 
                </P>
                <P>We did not publish a notice of proposed rulemaking (NPRM) for this regulation. Under 5 U.S.C. 553(b)(3), the Coast Guard finds that good cause exists for not publishing an NPRM. The original TFR was urgently required to prevent terrorist strikes within and adjacent to waters within the Long Island Sound Marine Inspection Zone and Captain of the Port Zone. It was anticipated that we would assess the security environment at the end of the effective period to determine whether continuing security precautions were required and, if so, propose regulations responsive to existing conditions. We have determined that the need for continued security regulations exists. The Coast Guard will utilize the extended effective period of this TFR to engage in notice and comment rulemaking to develop permanent regulations tailored to the present and foreseeable security environment within the Ports of Long Island Sound. </P>
                <P>
                    Under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . The measures contemplated by the rule were intended to prevent future terrorist attacks. The delay inherent in the NPRM process for developing a permanent rule is contrary to the public interest insofar as it may render individuals, vessels and facilities within and adjacent to the Long Island Sound Marine Inspection Zone and Captain of the Port Zone vulnerable to subversive activity, sabotage or terrorist attack. The Coast Guard will be publishing a NPRM to establish permanent safety and security zones that are temporarily effective under this rule. This revision preserves the status quo within the Port while permanent rules are developed. The present TFR has not been burdensome on the maritime public. The Coast Guard has not received written comments or suggestion to modify the scope of the existing TFR. 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>On September 11, 2001, two commercial aircraft were hijacked from Logan Airport in Boston, MA and flown into the World Trade Center in New York, NY inflicting catastrophic human casualties and property damage. A similar attack was conducted on the Pentagon with a plane launched from Newark, NJ on the same day. National security and intelligence officials warn that future terrorist attacks against civilian targets may be anticipated. The Coast Guard established RNA's and safety and security zones within defined areas of water as part of a comprehensive, port security regime designed to safeguard human life, vessels and waterfront facilities from sabotage or terrorist acts. As mentioned in the original TFR, these regulations were designed to provide the Captain of the Port of Long Island Sound with maximum flexibility to respond to emergent threats and dangerous conditions. When less stringent security measures are required, the Captain of the Port communicates relaxed enforcement policies to the public. As a result, the full scope of these regulations is rarely imposed. Nevertheless, the flexibility to utilize those measures permitted by the TFR and required by the circumstances is vital to ensure port security in the present environment. </P>
                <P>The current temporary rule is only effective until June 15, 2002. The Coast Guard is extending the effective date of this rule until November 15, 2002, to allow the establishment of permanent safety and security zones by notice and comment rulemaking. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12886, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040, February 26, 1979). </P>
                <P>The Coast Guard expects the economic impact of this final rule to be so minimal that a full Regulatory Evaluation under paragraph 10(e) of the regulatory policies and procedures of DOT is unnecessary. This finding is based on that the sizes of the zones are the minimum necessary to provide adequate protection for the public, vessels, and vessel crews. Any vessels seeking entry into or movement within the safety and security zones must request permission from the Captain of the Port or his authorized patrol representative. Any hardships experienced by persons or vessels are considered minimal compared to the national interest protecting the public, vessels, and vessel crews from the further devastating consequences of the aforementioned acts of terrorism, and from potential future sabotage or other subversive acts, accidents, or other causes of a similar nature. </P>
                <P>The Coast Guard will be publishing a NPRM to establish permanent safety and security zones that are temporarily effective under this rule. </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. </P>
                <P>
                    For the reasons addressed under the 
                    <E T="03">Regulatory Evaluation</E>
                     above, the Coast Guard expects the impact of this regulation to be minimal and certifies under section 605(b) of the Regulatory Flexibility Act (5 U.S.C. 601-612) that this final rule will not have a significant economic impact on a substantial number of small entities. Maritime advisories will be initiated by normal methods and means and be widely available to users of the area. 
                </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we offered to assist small entities 
                    <PRTPAGE P="40861"/>
                    in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact Lieutenant Pamela Garcia, Waterways Management, Coast Guard GP/MSO Long Island Sound (203) 468-4429. 
                </P>
                <P>Small Businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule calls for no new collection of information requirements under the Paperwork Reduction Act (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism. </P>
                <HD SOURCE="HD1">Unfunded Mandates </HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble. </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Indian Tribal Governments </HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>
                    We have considered the environmental impact of this rule and concluded that under figure 2-1, paragraph 34(g), of Commandant Instruction M16475.1D, this rule is categorically excluded from further environmental documentation. A “Categorical Exclusion Determination” is available in the docket for inspection or copying where indicated under 
                    <E T="02">ADDRESSES.</E>
                </P>
                <HD SOURCE="HD1">Energy Effects </HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that Order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165 </HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                  
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. Revise temporary § 165.T01-153(c) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T01-153 </SECTNO>
                        <SUBJECT>Regulated Navigation Area; Long Island Sound Marine Inspection Zone and Captain of the Port Zone </SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Effective dates.</E>
                             This section is effective from June 15, 2002 through November 15, 2002. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>3. Revise temporary § 165.T01-154(b) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T01-154 </SECTNO>
                        <SUBJECT>Safety and Security Zones; Long Island Sound Inspection Zone and Captain of the Port Zone </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Effective dates.</E>
                             This section is effective from June 15, 2002 through November 15, 2002. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>V.S. Crea, </NAME>
                    <TITLE>Rear Admiral, U.S. Coast Guard Commander, First Coast Guard District. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15132 Filed 6-12-02; 12:40 pm] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-P </BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[COTP TAMPA 02-046] </DEPDOC>
                <RIN>RIN 2115-AA97 </RIN>
                <SUBJECT>Security Zone; Port of Tampa, Tampa, FL </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Coast Guard is establishing temporary security zones within the Port of Tampa extending 50 yards from the shore or seawall and encompassing all piers around facilities in the following locations: Port Sutton, East Bay, Hooker's Point, Sparkman Channel, Ybor Channel and portions of Garrison Channel. Also, all recreational vessels and commercial fishing vessels are prohibited from operating in the Port Sutton Terminal Channel area. The 
                        <PRTPAGE P="40862"/>
                        purpose of these security zones is to safeguard the public and ports from destruction, loss, or injury from sabotage or other subversive acts. No person or vessel may enter a security zone without permission from the Captain of the Port, Tampa, Florida or his designated representative. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This regulation is effective from 6 p.m. on May 1, 2002 until 6 p.m. on June 15, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of COTP Tampa 02-046 and are available for inspection or copying at Marine Safety Office Tampa, 155 Columbia Drive, Tampa, Florida 33606-3598 between 7:30 a.m. and 3 p.m. Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>LT David McClellan, Coast Guard Marine Safety Office Tampa, at (813) 228-2189. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>We did not publish a notice of proposed rulemaking (NPRM) for this regulation. Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing a NPRM. Publishing a NPRM and delaying the rule's effective date would be contrary to the public interest since immediate action is needed to protect the public, ports and waterways of the United States. The Coast Guard will issue a broadcast notice to mariners and place Coast Guard vessels in the vicinity of these zones to advise mariners of the restriction. </P>
                <P>
                    For the same reasons, under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>Based on the September 11, 2001 terrorist attacks on the World Trade Center buildings in New York and the Pentagon in Arlington, Virginia, there is an increased risk that subversive activity could be launched by vessels or persons in close proximity to certain facilities within Tampa Bay. These facilities include but are not limited to; Cruise Ship Terminals, Liquefied Petroleum Gas (LPG), Anhydrous Ammonia (NH3) and/or flammable liquid cargo facilities. Due to the close proximity of several facilities in the Port Sutton area, it is necessary to restrict all recreational vessels and commercial fishing vessels from operating in this area. The zones will be 50 yards from shoreline or seawall and encompassing all piers around facilities commencing at: </P>
                <P>
                    <E T="03">Zone One:</E>
                     27° 54.16′N 082°26.11′W, eastnortheast to 27°54.19′N 082°26.00′W, then northeast to 27°54.37′N 082°25.72′W Closing off all of Port Sutton Channel to commercial and recreational fisherman, then northerly to 27°54.48′N 082°25.72′W, then northeasterly and terminating at point 27°55.27′N 082°25.17′W. 
                </P>
                <P>
                    <E T="03">Zone Two:</E>
                     27°56.05′N 082°25.95′W southwesterly to 27°56.00′N 082°26.08′W then southerly 27°55.83′N 082°26.07′W then southeasterly to 27°55.66′N 082°25.73′W the south to 27°54.75′N 082°25.74′W then southwesterly and terminating at point 27°54.57′N 082°25.86′W. 
                </P>
                <P>
                    <E T="03">Zone Three:</E>
                     27°54.74′N 082°26.47′W, northwest to 27°55.25′N 082°26.73′W, then north-northwest to 27°55.60′N 082°26.80′W, then north-northeast to 27°56.00′N 082°26.74′W, then northeast 27°56.56′N 082°26.55′W, and north to 27°56.84′N 082°26.55′W, west to 27°56.84′N 082°26.66′W, then southerly to 27°56.65′N 082°26.66′W, southwesterly to 27°56.7′N 082°26.7′W then southwesterly and terminating at 27°56.53′N 082°26.96′W. 
                </P>
                <P>All positions noted are fixed using the North American Datum of 1983 (World Geodetic System 1984). Coast Guard and local law enforcement patrol vessels will be on scene to enforce these zones. Entry into a security zone is prohibited, unless specifically authorized by the Captain of the Port, Tampa, Florida. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a significant regulatory action under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that order. The rule would prevent recreational fishing next to piers and seawalls of specified facilities in Port Tampa and entry into Port Sutton. There remain ample fishing locations for recreational fisherman to make use of in the local area. The Office of Management and Budget has not reviewed it under that order. It is not significant under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040; February 26, 1979). </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), the Coast Guard considered whether this rule would have a significant economic effect upon a substantial number of small entities. “Small entities” include small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. </P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities because small entities may be allowed to enter on a case by case basis with the authorization of the Captain of the Port. </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process. If the rule will affect your small business, organization, or government jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     for assistance in understanding this rule. 
                </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule calls for no new information collection requirements under the Paperwork Reduction Act (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>
                    The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of 
                    <PRTPAGE P="40863"/>
                    $100,000,000 or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble. 
                </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule will not effect a taking of private property or otherwise have taking Implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Environmental </HD>
                <P>The Coast Guard considered the environmental impact of this rule and concluded under Figure 2-1, paragraph 34(g) of Commandant Instruction M16475.1D, this rule is categorically excluded from further environmental documentation. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not concern an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Indian Tribal Governments </HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationships between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. </P>
                <HD SOURCE="HD1">Energy Effects </HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or use. We have Determined that it is not a “significant energy action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165 </HD>
                    <P>Harbors, Marine safety, Navigation (water), Reports and record keeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <AMDPAR>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165, as follows: </AMDPAR>
                <PART>
                    <HD SOURCE="HED">PART 165—[AMENDED] REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS </HD>
                </PART>
                <AMDPAR>1. The authority citation for part 165 continues to read as follows: </AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 6.04-11, 160.5; 49 CFR 1.46.</P>
                </AUTH>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. A new temporary § 165.T07-046 is added to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T07-046 </SECTNO>
                        <SUBJECT>Security Zone; Port of Tampa, Tampa Bay, Florida. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Regulated areas:</E>
                             Temporary security zones are established 50 yards from shoreline or seawall and encompassing all piers around facilities commencing at: 
                        </P>
                        <P>
                            (1) 
                            <E T="03">Zone One:</E>
                             27°54.16′ N 082°26.11′ W, eastnortheast to 27°54.19′ N 082°26.00′ W, then northeast to 27°54.37′ N 082°25.72′ W Closing off all of Port Sutton Channel to commercial and recreational fisherman, then northerly to 27°54.48′ N 082°25.72′ W, then northeasterly and terminating at point 27°55.27′ N 082°25.17′ W. (NAD 83) 
                        </P>
                        <P>
                            (2) 
                            <E T="03">Zone Two:</E>
                             27°56.05′ N 082°25.95′ W southwesterly to 27°56.00′ N 082°26.08′ W then southerly 27°55.83′ N 082°26.07′ W then southeasterly to 27°55.66′ N 082°25.73′ W the south to 27°54.75′ N 082°25.74′ W then southwesterly and terminating at point 27°54.57′ N 082°25.86′ W. (NAD 83) 
                        </P>
                        <P>
                            (3) 
                            <E T="03">Zone Three:</E>
                             27°54.74′ N 082°26.47′ W, northwest to 27°55.25′ N 082°26.73′ W, then north-northwest to 27°55.60′ N 082°26.80′ W, then north-northeast to 27°56.00′ N 082°26.74′ W, then northeast 27°56.56′ N 082°26.55′ W, and north to 27°56.84′ N 082°26.55′ W, west to 27°56.84′ N 082°26.66′ W, then southerly to 27°56.65′ N 082°26.66′ W, southwesterly to 27°56.7′ N 082°26.7′ W then southwesterly and terminating at 27°56.53′ N 082°26.96′ W. (NAD 83) 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Regulations:</E>
                             In accordance with the general regulations in § 165.33 of this part, entry into these zones is prohibited except as authorized by the Captain of the Port, or his designated representative. The Captain of the Port will notify the public via Marine Safety Radio Broadcast on VHF Marine Band Radio, Channel 13 and 16 (157.1 MHz). 
                        </P>
                        <P>
                            (c) 
                            <E T="03">Dates.</E>
                             This section is effective from 6 p.m. on May 1, 2002 until 6 p.m. on June 15, 2002.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: April 16, 2002. </DATED>
                    <NAME>A.L. Thompson, Jr., </NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15185 Filed 6-12-02; 2:26 pm] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[CGD13-02-007] </DEPDOC>
                <RIN>RIN 2115-AA97 </RIN>
                <SUBJECT>Safety Zone; Silver Dollar Casino Cup Hydroplane Races, Lake Washington, WA </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a temporary safety zone on the waters of Lake Washington. The Captain of the Port Puget Sound, Seattle, Washington, is taking this action to safeguard participants and spectators from the safety hazards associated with high performance watercraft operating at high speeds. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 11 a.m. (PDT) on June 15, 2002 until 5 p.m. (PDT) on June 16, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Documents indicated in this preamble as being available in the docket are part of docket CGD13-02-007 and are available for inspection or copying at the U.S. Coast Guard Marine Safety Office Puget Sound, 1519 Alaskan Way South, Building 1, Seattle, Washington 98134. Normal office hours are between 8 a.m. and 4 p.m., Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>LT A. L. Praskovich, c/o Captain of the Port Puget Sound, at (206) 217-6232. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    We did not publish a notice of proposed rulemaking (NPRM) for this regulation. Under 5 U.S.C. 553(b)(B) and 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for not publishing an NPRM and for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . Publishing a NPRM would be contrary to the public interest since immediate action is necessary to ensure the safety of vessels and persons that may be transiting in the vicinity of the Silver 
                    <PRTPAGE P="40864"/>
                    Dollar Casino Cup races. Specifically, the zone is needed to protect participant and spectator watercraft and their occupants from safety hazards associated with high performance vessels conducting complex maneuvers at high speed. Many onlookers may attempt to view the races at close range, thereby increasing their exposure to these hazards. In turn, participant craft maneuvering at high speed are extremely susceptible to the effects of stray wakes entering the race course. If normal notice and comment procedures were followed, this rule would not become effective until after the date of the event. 
                </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>The Coast Guard is establishing a temporary safety zone for the Silver Dollar Casino Cup Regatta Hydroplane races sponsored by the Northwest Power Boat Association. The zone is needed to protect participant and spectator watercraft and their occupants from safety hazards associated with high performance vessels conducting complex maneuvers at high speed. Many onlookers may attempt to view the races at close range, thereby increasing their exposure to these hazards. In turn, participant craft maneuvering at high speed are extremely susceptible to the effects of stray wakes entering the racecourse. Entry into the race course portion of the safety zone will be prohibited. Entry into the spectator portion of the safety zone will be authorized at a slow no-wake speed. A buoy line will mark the perimeter of the race course portion of the safety zone beyond which spectator vessels may not proceed. This safety zone will be enforced by representatives of the Captain of the Port Puget Sound, Seattle, Washington. The Captain of the Port may be assisted by other federal, state, or local agencies. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT) (44 FR 11040, February 26, 1979). </P>
                <P>We expect the economic impact of this rule to be so minimal that a full Regulatory Evaluation under paragraph 10(e) of the regulatory policies and procedures of DOT is unnecessary. This expectation is based on the fact that the regulated area established by the rule would encompass a small area that should not significantly impact commercial or recreational traffic. Recreational vessels are the primary users of this area, and the event is being held for the benefit of recreational boaters. For the above reasons, the Coast Guard does not anticipate any significant economic impact. </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we considered whether this rule would have a significant economic impact on a substantial number of small entities. “Small entities” include small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. This rule will affect the following entities, some of which may be small entities: the owners or operators of vessels intending to transit this portion of Lake Washington when this rule is in effect. The rule will not have a significant economic impact due to its short duration and small area. Because the impacts of this proposal are expected to be so minimal, the Coast Guard certifies under 605(b) of the Regulatory Flexibility Act (5 U.S.C. 601-612) that this final rule will not have a significant economic impact on a substantial number of small entities. </P>
                <P>
                    If you think that your business, organization, or governmental jurisdiction qualifies as a small entity and that this rule would have a significant economic impact on it, please submit a comment (see 
                    <E T="02">ADDRESSES</E>
                    ) explaining why you think it qualifies and how and to what degree this rule would economically affect it. 
                </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we want to assist small entities in understanding this rule so that they can better evaluate its effects on them and participate in the rulemaking. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact the person listed in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. 
                </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule would call for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>We have analyzed this rule under Executive Order 13132, Federalism, and have determined that this rule does not have implications for federalism under that Order. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) governs the issuance of Federal regulations that require unfunded mandates. An unfunded mandate is a regulation that requires a State, local, or tribal government or the private sector to incur direct costs without the Federal Government's having first provided the funds to pay those costs. This rule would not impose an unfunded mandate. </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule would not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not concern an environmental risk to health or risk to safety that may disproportionately affect children. </P>
                <HD SOURCE="HD1">Indian Tribal Governments </HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. </P>
                <HD SOURCE="HD1">Energy Effects </HD>
                <P>
                    We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that Order because it is not a “significant regulatory action” under Executive Order 12866 and is not 
                    <PRTPAGE P="40865"/>
                    likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211. 
                </P>
                <HD SOURCE="HD1">Environment </HD>
                <P>We considered the environmental impact of this proposed rule and concluded that, under figure 2-1, paragraph(34)(g) of Commandant Instruction M16475.lC, this rule is categorically excluded from further environmental documentation. A “Categorical Exclusion” is provided for temporary safety zones of less than one week in duration. This rule establishes a temporary safety zone of limited duration which will be within the one-week timeframe. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165 </HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>For the reasons set out in the preamble, the Coast Guard amends 33 part 165 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46. </P>
                    </AUTH>
                </REGTEXT>
                  
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. From 11 a.m. (PDT) on July 15, 2002, until 5 p.m. (PDT) on July 16, 2002, a temporary § 165.T13-004 is added to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T13-004 </SECTNO>
                        <SUBJECT>Safety Zone; Silver Dollar Casino Cup hydroplane races, Lake Washington, WA. </SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             The following area is a safety zone: all waters of Lake Washington, Renton, Washington, bounded by a line commencing at Coleman Point in position 47°31′07″ N, 122°12′42″ W; thence 1500 feet due west to 47°31′07″ N, 122°13′05″ W; thence due south to the Renton Municipal Airport Runway at 47°30′02″ N, 122°13′05″ W; thence returning along the shoreline to point of origin. (Datum: NAD 83) 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Regulations.</E>
                             In accordance with the general regulations in § 165.23 of this part, no person or vessel may enter or remain in the race course portion of this zone, except for: participants in the event, supporting personnel, vessels registered with the event organizer, or other vessels authorized by the Captain of the Port or his designated representatives. Vessels entering the spectator portion of the safety zone must proceed at a slow no-wake speed and, upon notice, shall obey the lawful order or direction of the Captain of the Port or his designated representatives. 
                        </P>
                        <P>
                            (c) 
                            <E T="03">Enforcement period.</E>
                             This section will be enforced from 11 a.m. (PDT) to 5 p.m. (PDT) on June 15 and 16, 2002. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: May 28, 2002. </DATED>
                    <NAME>M.R. Moore, </NAME>
                    <TITLE>Captain, U.S. Coast Guard, Captain of the Port, Puget Sound. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15183 Filed 6-12-02; 2:26 pm] </FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 165</CFR>
                <DEPDOC>[CGD09-02-010]</DEPDOC>
                <RIN>RIN 2115-AA97</RIN>
                <SUBJECT>Safety Zone; Racine Harbor, Lake Michigan, Racine, WI</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing a temporary safety zone outside Racine Harbor just south of Reef Point Marina in Racine, Wisconsin for the Racine Harbor Fest 2002 fireworks display. This safety zone is necessary to protect spectators and vessels from the hazards associated with the storage, preparation, and launching of fireworks. This safety zone is intended to restrict vessel traffic from a portion of Lake Michigan and in particular, the southern outer harbor, Racine, Wisconsin.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from 9:20 p.m. (CST) on June 14, 2002 until 9:55 p.m. (CST) on June 15, 2002.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments and material received from the public, as well as documents indicated in this preamble as being available in the docket, are part of docket [CGD09-02-010] and are available for inspection or copying at U.S. Coast Guard Marine Safety Office Milwaukee, 2420 South Lincoln Memorial Drive, Milwaukee, WI 53207 between 7 a.m. and 3:30 p.m., Monday through Friday, except Federal holidays.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>LCDR Timothy Sickler, Port Operations Chief, Marine Safety Office Milwaukee, at (414) 747-7155.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information</HD>
                <P>On May 14, 2002 we published a notice of proposed rulemaking (NPRM) for this regulation (67 FR 34420). The permit application was received such that we could receive public comment on the proposed rule. However, under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days from the date of publication. The permit application did not allow sufficient time for publication of an NPRM followed by a temporary final rule effective 30 days after publication. Any delay of the effective date of this rule would be contrary to the public interest by exposing the public to the known dangers associated with fireworks displays and the possible loss of life, injury, and damage to property.</P>
                <HD SOURCE="HD1">Background and Purpose</HD>
                <P>This safety zone is established to safeguard the public from the hazards associated with launching of fireworks from outside Racine Harbor south of Reef Point Marina. The size of the zone was determined by using previous experiences with fireworks displays in the Captain of the Port Milwaukee zone and local knowledge about wind, waves, and currents in this particular area.</P>
                <P>The safety zone will be enforced on June 14 and again on 15 from 9:20 p.m. (CST) until 9:55 p.m.(CST). The safety zone will encompass all waters and adjacent shoreline bounded by the arc of the circle with a 140-foot radius with its center in approximate position 42°43.447′ N, 087°46.41′ W (south of Racine Harbor). These coordinates are based upon North American Datum 1983 (NAD 83).</P>
                <P>All persons and vessels shall comply with the instructions of the Captain of the Port Milwaukee or his designated on scene patrol personnel. Entry into, transiting, or anchoring within the safety zone is prohibited unless authorized by the Captain of the Port Milwaukee or his designated on scene representative. The Captain of the Port Milwaukee may be contacted via VHF Channel 16.</P>
                <HD SOURCE="HD1">Regulatory Evaluation</HD>
                <P>
                    This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Transportation (DOT)(44 FR 11040, February 26, l979).
                    <PRTPAGE P="40866"/>
                </P>
                <HD SOURCE="HD1">Small Entities</HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities.</P>
                <P>This rule will affect the following entities: the owners or operators of vessels intending to transit or anchor in the vicinity of outside Racine Harbor south of Reef Point Marina from 9:20 p.m. (CST) until 9:55 p.m. (CST) on June 14 and June 15, 2002.</P>
                <P>This safety zone will not have a significant economic impact on a substantial number of small entities for the following reasons: This rule will be in effect for only one hour on one day and late in the day when vessel traffic is minimal. Vessel traffic may enter or transit through the safety zone with the permission of the Captain of the Port Milwaukee or his designated on scene representative. Before the effective period, we will issue maritime advisories widely available to users of the Port of Milwaukee.</P>
                <HD SOURCE="HD1">Assistance for Small Entities</HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Public Law 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process. If the rule would affect your small business, organization, or governmental jurisdiction and you have questions concerning its provisions or options for compliance, please contact Marine Safety Office Milwaukee (
                    <E T="03">See</E>
                      
                    <E T="02">ADDRESSES</E>
                    ).
                </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247).</P>
                <HD SOURCE="HD1">Collection of Information</HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD1">Federalism</HD>
                <P>We have analyzed this rule under Executive Order 13132, Federalism, and have determined that this rule does not have implications for federalism under that Order.</P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this proposed rule would not result in such an expenditure, we do discuss the effects of this rule elsewhere in this preamble.</P>
                <HD SOURCE="HD1">Taking of Private Property</HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
                <HD SOURCE="HD1">Civil Justice Reform</HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
                <HD SOURCE="HD1">Protection of Children</HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not concern an environmental risk to health or risk to safety that may disproportionately affect children.</P>
                <HD SOURCE="HD1">Environment</HD>
                <P>The Coast Guard considered the environmental impact of this rule and concluded that under figure 2-1, paragraph (34) (g), of Commandant Instruction M16475.lC, this rule is categorically excluded from further environmental documentation.</P>
                <HD SOURCE="HD1">Indian Tribal Governments</HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD1">Energy Effects</HD>
                <P>We have analyzed this proposed rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that Order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. It has not been designated by the Administrator of the Office of Information and Regulatory Affairs as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, and Waterways.</P>
                </LSTSUB>
                  
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR part 165 as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1231; 50 U.S.C. 191, 33 CFR 1.05-1(g), 6.04-1, 6.04-6, 160.5; 49 CFR 1.46. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. From 9:20 p.m. on June 14, 2002, until 9:55 p.m. on June 15, 2002, a new temporary § 165.T09-003 is added to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T09-003 </SECTNO>
                        <SUBJECT>Safety Zone; Racine Harbor, Lake Michigan, Racine, WI.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             The following area is a safety zone: all waters and adjacent shoreline of Lake Michigan bounded by the arc of a circle with a 140-foot radius with its center in approximate position 42°43.44′ N, 087°46.41′ W (located south of Racine Harbor) NAD 83. 
                        </P>
                        <P>
                            (b) 
                            <E T="03">Enforcement periods.</E>
                             This section is effective from 9:20 p.m. (CST) on June 14, 2002, until 9:55 p.m. (CST) on June 15, 2002. The section will be enforced from 9:20 p.m. until 9:55 p.m. on June 14, 2002 and again during these same times on June 15, 2002.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             (1) The general regulations contained in 33 CFR 165.23 apply.
                        </P>
                        <P>
                            (2) All persons and vessels shall comply with the instructions of the Coast Guard Captain of the Port 
                            <PRTPAGE P="40867"/>
                            Milwaukee or the designated on scene patrol personnel. Coast Guard patrol personnel include commissioned, warrant or petty officers of the U.S. Coast Guard. Upon being hailed by a U.S. Coast Guard vessel via siren, radio, flashing light, or other means, the operator shall proceed as directed.
                        </P>
                        <P>(3) This safety zone should not adversely effect shipping. However, commercial vessels may request permission from the Captain of the Port Milwaukee to enter or transit the safety zone. Approval will be made on a case-by-case basis. Requests must be in advance and approved by the Captain of the Port Milwaukee before transits will be authorized. The Captain of the Port Milwaukee may be contacted via U.S. Coast Guard Group Milwaukee on Channel 16, VHF-FM. </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: June 10, 2002.</DATED>
                    <NAME>M.R. DeVries,</NAME>
                    <TITLE>Commander, U.S. Coast Guard, Captain of the Port, Milwaukee, Milwaukee, Wisconsin.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15184 Filed 6-12-02; 2:26 pm]</FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS </AGENCY>
                <CFR>38 CFR Part 3 </CFR>
                <RIN>RIN 2900-AL19 </RIN>
                <SUBJECT>Cross Reference Change in Forms To Be Furnished </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Veterans Affairs. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document amends the Department of Veterans Affairs (VA) adjudication regulations regarding forms to be furnished by VA to update a cross-reference listed at the end of a regulation. This amendment is necessary to ensure the regulation's cross-reference accurately cites the new title of the cross-referenced regulation. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective Date:</E>
                         June 14, 2002. 
                    </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Randy A. McKevitt, Consultant, Regulations Staff, Compensation and Pension Service, Veterans Benefits Administration, 810 Vermont Avenue, NW., Washington, DC 20420, telephone (202) 273-7138. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    VA's regulation 38 CFR 3.150, “Forms to be furnished,” has at the end of the regulation a cross-reference to “Failure to furnish claim form or notice of time limit. 
                    <E T="03">See</E>
                     § 3.109(b).” In a previous VA amendment to § 3.109, we changed the title of subparagraph § 3.109(b) to “Extension of time limit.” This amendment changes the cross-reference in § 3.150 to “Extension of time limit.” 
                </P>
                <P>This document only makes a technical correction to the regulation, which under the provisions of 5 U.S.C. 553, is exempt from the prior notice and public comment and delayed effective date provisions. </P>
                <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                <P>This document contains no provisions constituting a collection of information under the Paperwork Reduction Act (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Unfunded Mandates </HD>
                <P>The Unfunded Mandates Reform Act requires (in section 202) that agencies prepare an assessment of anticipated costs and benefits before developing any rule that may result in an expenditure by State, local, or tribal governments, in the aggregate, or by the private sector of $100 million or more in any given year. This rule would have no consequential effect on State, local, or tribal governments. </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                <P>The Secretary hereby certifies that this regulatory amendment will not have a significant economic impact on a substantial number of small entities as they are defined in the Regulatory Flexibility Act, 5 U.S.C. 601-612. The reason for this certification is that this regulatory amendment would not directly affect any small entities. Only VA beneficiaries could be directly affected. Therefore, pursuant to 5 U.S.C. 605(b), this amendment is exempt from the initial and final regulatory flexibility analysis requirements of sections 603 and 604. </P>
                <HD SOURCE="HD1">Catalog of Federal Domestic Assistance Numbers </HD>
                <P>The Catalog of Federal Domestic Assistance program numbers are 64.100, 64.101, 64.102, 64.104, 64.105, 64.106, 64.109, 64.110, 64.115, 64.116, and 64.127. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 38 CFR part 3 </HD>
                    <P>Administrative practice and procedure, Claims, Disability benefits, Health Care, Pensions, Veterans, Vietnam.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Approved: June 6, 2002. </DATED>
                    <NAME>Anthony J. Principi, </NAME>
                    <TITLE>Secretary of Veterans Affairs.</TITLE>
                </SIG>
                <REGTEXT TITLE="38" PART="3">
                    <AMDPAR>For the reasons set forth in the preamble, 38 CFR part 3 is amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 3—ADJUDICATION </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—Pension, Compensation, and Dependency and Indemnity Compensation </HD>
                        </SUBPART>
                    </PART>
                    <AMDPAR>1. The authority citation for part 3, subpart A, continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>38 U.S.C. 501(a), unless otherwise noted. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="38" PART="3">
                    <AMDPAR>2. The Cross reference at the end of § 3.150 is revised to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 3.150</SECTNO>
                        <SUBJECT>Forms to be furnished. </SUBJECT>
                        <STARS/>
                        <P>
                            <E T="03">Cross Reference:</E>
                             Extension of time limit. 
                            <E T="03">See</E>
                             § 3.109(b). 
                        </P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15075 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 52 </CFR>
                <DEPDOC>[CA 250-0331a; FRL-7165-4] </DEPDOC>
                <SUBJECT>Revisions to the California State Implementation Plan, Lake County Air Quality Management District </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Direct final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>EPA is taking direct final action to approve a revision to the Lake County Air Quality Management District (LCAQMD) portion of the California State Implementation Plan (SIP). This revision concerns the emission of particulate matter (PM-10) from open fires and prescribed burning. We are approving local rules that regulate these emission sources under the Clean Air Act as amended in 1990 (CAA or the Act). </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        This rule is effective on August 13, 2002 without further notice, unless EPA receives adverse comments by July 15, 2002. If we receive such comments, we will publish a timely withdrawal in the 
                        <E T="04">Federal Register</E>
                         to notify the public that this rule will not take effect. 
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Mail comments to Andy Steckel, Rulemaking Office Chief (AIR-4), U.S. Environmental Protection Agency, Region IX, 75 Hawthorne Street, San Francisco, CA 94105. </P>
                    <P>You can inspect copies of the submitted rule revisions and EPA's technical support document (TSD) at our Region IX office during normal business hours. You may also see copies of the submitted rule revisions and TSD at the following locations: </P>
                    <P>
                        Environmental Protection Agency, Air Docket (6102), Ariel Rios Building, 1200 
                        <PRTPAGE P="40868"/>
                        Pennsylvania Avenue, NW., Washington DC 20460. 
                    </P>
                    <P>California Air Resources Board, Stationary Source Division, Rule Evaluation Section, 1001 “I” Street, Sacramento, CA 95814. </P>
                    <P>Lake County Air Quality Management District, 885 Lakeport Boulevard, Lakeport, CA 95453. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Al Petersen, Rulemaking Office (AIR-4), U.S. Environmental Protection Agency, Region IX; (415) 947-4118. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Throughout this document, “we,” “us” and “our” refer to EPA. </P>
                <HD SOURCE="HD1">Table of Contents </HD>
                <EXTRACT>
                    <FP SOURCE="FP-2">I. The State's Submittal </FP>
                    <FP SOURCE="FP1-2">A. What rules did the State submit? </FP>
                    <FP SOURCE="FP1-2">B. Are there other versions of these rules? </FP>
                    <FP SOURCE="FP1-2">C. What is the purpose of the submitted rule revisions? </FP>
                    <FP SOURCE="FP-2">II. EPA's Evaluation and Action </FP>
                    <FP SOURCE="FP1-2">A. How is EPA evaluating the rules? </FP>
                    <FP SOURCE="FP1-2">B. Do the rules meet the evaluation criteria? </FP>
                    <FP SOURCE="FP1-2">C. Public comment and final action </FP>
                    <FP SOURCE="FP-2">III. Background Information </FP>
                    <FP SOURCE="FP1-2">A. Why were these rules submitted? </FP>
                    <FP SOURCE="FP-2">IV. Administrative Requirements </FP>
                </EXTRACT>
                <HD SOURCE="HD1">I. The State's Submittal </HD>
                <HD SOURCE="HD2">A. What Rules Did the State Submit? </HD>
                <P>Table 1 lists the rules we are approving with the date that they were adopted by the local air agency and submitted by the California Air Resources Board (CARB). </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="xs75,8.1,r100,9,9">
                    <TTITLE>Table 1.—Submitted Rules </TTITLE>
                    <BOXHD>
                        <CHED H="1">Local agency </CHED>
                        <CHED H="1">Section No. [Rule No.] </CHED>
                        <CHED H="1">Rule title </CHED>
                        <CHED H="1">Adopted </CHED>
                        <CHED H="1">Submitted </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>203 </ENT>
                        <ENT>Agricultural Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>204.5 </ENT>
                        <ENT>Air Quality </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>208.3 </ENT>
                        <ENT>Burn Plan or Smoke Management Plan </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>208.8 </ENT>
                        <ENT>Burn Day or Permissive Burn Day </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>226.4 </ENT>
                        <ENT>Fire Protection Agency </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>226.5 </ENT>
                        <ENT>Fire Season—Burn Ban </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>240.8 </ENT>
                        <ENT>No Burn Day </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>246 </ENT>
                        <ENT>Particulate Matter</ENT>
                        <ENT> 06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>248.3 </ENT>
                        <ENT>Pre-Fire Fuel Treatment </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>248.5 </ENT>
                        <ENT>Prescribed Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>249.5 </ENT>
                        <ENT>Range Improvement Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>251.7 </ENT>
                        <ENT>Smoke Sensitive Areas </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>270 </ENT>
                        <ENT>Wildland Vegetation Management Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>431 </ENT>
                        <ENT>Non-Agricultural Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>431.5 </ENT>
                        <ENT>[Non-Agricultural Open Burning] </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>433 </ENT>
                        <ENT>[Single and Two-Family Dwellings] </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>434 </ENT>
                        <ENT>[Levee, Reservoir, and Ditch Maintenance] </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1000 </ENT>
                        <ENT>Agricultural and Prescribed Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1001 </ENT>
                        <ENT>[Agricultural Burning Permit] </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1003 </ENT>
                        <ENT>Special No-Burn Day Permit </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1105 </ENT>
                        <ENT>Burning Hours </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1107 </ENT>
                        <ENT>Agricultural Burning During Fire Season </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1130 </ENT>
                        <ENT>Open Burning in Agricultural Operations in the Growing of Crops or Raising of Animals </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1140 </ENT>
                        <ENT>Range Improvement Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1145 </ENT>
                        <ENT>Forest Management Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1150 </ENT>
                        <ENT>Burning of Standing Tule </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1160 </ENT>
                        <ENT>Prescribed Burning, Habitat Improvement Burning, Wildland Vegetation Burning and Forest Management Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">LCAQMD </ENT>
                        <ENT>1170 </ENT>
                        <ENT>Wood Waste Burning </ENT>
                        <ENT>06/19/01 </ENT>
                        <ENT>10/30/01 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>On January 18, 2002, this submittal was found to meet the completeness criteria in 40 CFR Part 51 Appendix V, which must be met before formal EPA review. </P>
                <HD SOURCE="HD2">B. Are There Other Versions of These Rules? </HD>
                <P>We approved a version of Sections 203, 246, 431, 1000, 1001, 1140 (as SIP Section 1100), 1145 (as SIP Section 1200), and 1130 (as SIP Section 1300) into the SIP on August 4, 1978 (43 FR 34463). We approved a version of Section 434 into the SIP on October 23, 1989 (54 FR 43173). We approved a version of Sections 248.5 and 270 into the SIP on May 18, 1999 (64 FR 26876). We approved a version of Sections 226.5, 431.5, 433, and 1160 (as SIP Section 1150) into the SIP on April 21, 2000 (65 FR 21347). </P>
                <P>The LCAQMD adopted Section 1003 on June 13, 1989 and CARB submitted it to us on March 26, 1990. While we can act on only the most recently submitted version, we have reviewed materials provided with this previous submittal. </P>
                <HD SOURCE="HD2">C. What Is the Purpose of the Submitted Rule Revisions? </HD>
                <P>The purpose of the submitted rule revisions is to improve the SIP and make the rules consistent with California Smoke Management Guidelines. </P>
                <HD SOURCE="HD1">II. EPA's Evaluation and Action </HD>
                <HD SOURCE="HD2">A. How Is EPA Evaluating the Rules? </HD>
                <P>Generally, SIP rules must be enforceable (see section 110(a) of the CAA) and must not relax existing requirements (see sections 110(l) and 193). BACM/BACT and RACM/RACT are not required for PM-10 attainment areas (see section 189(a) and 189(b)). LCAQMD is a PM-10 attainment area. </P>
                <P>The following guidance documents were used for reference: </P>
                <P>
                    • 
                    <E T="03">Requirements for Preparation, Adoption, and Submittal of Implementation Plans, U.S. EPA,</E>
                     40 CFR Part 51. 
                </P>
                <P>
                    • 
                    <E T="03">General Preamble Appendix C3—Prescribed Burning Control Measures</E>
                     (57 FR 18072, April 28, 1992). 
                    <PRTPAGE P="40869"/>
                </P>
                <P>
                    • 
                    <E T="03">General Preamble for the Implementation of Title I of the Clean Air Act Amendments of 1990,</E>
                     57 FR 13498, 13540 (April 16, 1992). 
                </P>
                <P>
                    • 
                    <E T="03">Addendum to the General Preamble for the Implementation of Title I of the Clean Air Act Amendments of 1990,</E>
                     59 FR 41998 (August 16, 1994). 
                </P>
                <P>
                    • 
                    <E T="03">PM-10 Guideline Document,</E>
                     EPA-452/R-93-008. 
                </P>
                <HD SOURCE="HD2">B. Do the Rules Meet the Evaluation Criteria? </HD>
                <P>We believe the rules are consistent with the relevant policy and guidance regarding enforceability and SIP relaxations. The TSD has more information on our evaluation. </P>
                <HD SOURCE="HD2">C. Public Comment and Final Action </HD>
                <P>
                    As authorized in section 110(k)(3) of the CAA, EPA is fully approving the submitted rules because we believe they fulfill all relevant requirements. We do not think anyone will object to this, so we are finalizing the approval without proposing it in advance. However, in the Proposed Rules section of this 
                    <E T="04">Federal Register</E>
                    , we are simultaneously proposing approval of the same submitted rules. If we receive adverse comments by July 15, 2002, we will publish a timely withdrawal in the 
                    <E T="04">Federal Register</E>
                     to notify the public that the direct final approval will not take effect and we will address the comments in a subsequent final action based on the proposal. If we do not receive timely adverse comments, the direct final approval will be effective without further notice on August 13, 2002. This will incorporate these rules into the federally-enforceable SIP. 
                </P>
                <P>Please note that if EPA receives adverse comment on an amendment, paragraph, or section of this direct final rule and if that provision may be severed from the remainder of the rule, EPA may adopt as final those provisions of the rule that are not the subject of an adverse comment. </P>
                <HD SOURCE="HD1">III. Background Information </HD>
                <HD SOURCE="HD2">A. Why Was This Rule Submitted? </HD>
                <P>PM-10 harms human health and the environment. Section 110(a) of the CAA requires states to submit regulations that control PM-10 emissions. Table 2 lists some of the national milestones leading to the submittal of local agency PM-10 rules. </P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s100,r300">
                    <TTITLE>Table 2.—PM-10 Nonattainment Milestones </TTITLE>
                    <BOXHD>
                        <CHED H="1">Date </CHED>
                        <CHED H="1">Event </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">March 3, 1978</ENT>
                        <ENT>EPA promulgated a list of total suspended particulate (TSP) nonattainment areas under the Clean Air Act, as amended in 1977. 43 FR 8964; 40 CFR 81.305. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">July 1, 1987</ENT>
                        <ENT>EPA replaced the TSP standards with new PM standards applying only up to 10 microns in diameter (PM-10). 52 FR 24672. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November 15, 1990</ENT>
                        <ENT>
                            Clean Air Act Amendments of 1990 were enacted, Pub. L. 101-549, 104 Stat. 2399, codified at 42 U.S.C. 7401-7671
                            <E T="03">q.</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November 15, 1990</ENT>
                        <ENT>PM-10 areas meeting the qualifications of section 107(d)(4)(B) of the CAA were designated nonattainment by operation of law and classified as moderate pursuant to section 188(a). States are required by section 110(a) to submit rules regulating PM-10 emissions in order to achieve the attainment dates specified in section 188(c). </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">IV. Administrative Requirements </HD>
                <P>
                    Under Executive Order 12866 (58 FR 51735, October 4, 1993), this action is not a “significant regulatory action” and therefore is not subject to review by the Office of Management and Budget. For this reason, this action is also not subject to Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001). This action merely approves state law as meeting federal requirements and imposes no additional requirements beyond those imposed by state law. Accordingly, the Administrator certifies that this rule will not have a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ). Because this rule approves pre-existing requirements under state law and does not impose any additional enforceable duty beyond that required by state law, it does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Public Law 104-4). 
                </P>
                <P>This rule also does not have tribal implications because it will not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes, as specified by Executive Order 13175 (65 FR 67249, November 9, 2000). This action also does not have Federalism implications because it does not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132 (64 FR 43255, August 10, 1999). This action merely approves a state rule implementing a Federal standard, and does not alter the relationship or the distribution of power and responsibilities established in the CAA. This rule also is not subject to Executive Order 13045, “Protection of Children from Environmental Health Risks and Safety Risks” (62 FR 19885, April 23, 1997), because it is not economically significant. </P>
                <P>
                    In reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the CAA. In this context, in the absence of a prior existing requirement for the State to use voluntary consensus standards (VCS), EPA has no authority to disapprove a SIP submission for failure to use VCS. It would thus be inconsistent with applicable law for EPA, when it reviews a SIP submission, to use VCS in place of a SIP submission that otherwise satisfies the provisions of the CAA. Thus, the requirements of section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) do not apply. This rule does not impose an information collection burden under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ). 
                </P>
                <P>
                    The Congressional Review Act, 5 U.S.C. section 801 
                    <E T="03">et seq.</E>
                    , as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the 
                    <PRTPAGE P="40870"/>
                    United States. EPA will submit a report containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the 
                    <E T="04">Federal Register</E>
                    . A major rule cannot take effect until 60 days after it is published in the 
                    <E T="04">Federal Register</E>
                    . This action is not a “major rule” as defined by 5 U.S.C. section 804(2). 
                </P>
                <P>Under section 307(b)(1) of the CAA, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by August 13, 2002. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this rule for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. This action may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).) </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 52 </HD>
                    <P>Environmental protection, Air pollution control, Incorporation by reference, Intergovernmental relations, Particulate matter, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: March 14, 2002. </DATED>
                    <NAME>Laura Yoshii, </NAME>
                    <TITLE>Acting Regional Administrator, Region IX. </TITLE>
                </SIG>
                <REGTEXT TITLE="40" PART="52">
                    <AMDPAR>Part 52, chapter I, title 40 of the Code of Federal Regulations is amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 52—[AMENDED] </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for Part 52 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority: </HD>
                        <P>
                            42 U.S.C. 7401 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="52">
                    <SUBPART>
                        <HD SOURCE="HED">Subpart F—California </HD>
                    </SUBPART>
                    <AMDPAR>2. Section 52.220 is amended by adding paragraph (c)(288)(i)(B) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 52.220 </SECTNO>
                        <SUBJECT>Identification of plan. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(288) * * * </P>
                        <P>(i) * * * </P>
                        <P>(B) Lake County Air Quality Management District. </P>
                        <P>
                            (
                            <E T="03">1</E>
                            ) Sections [Rules] 203, 204.5, 208.3, 208.8, 226.4, 226.5, 240.8, 246, 248.3, 248.5, 249.5, 251.7, 270, 431, 431.5, 433, 434, 1000, 1001, 1003, 1105, 1107, 1130, 1140, 1145, 1150, 1160, and 1170, adopted on June 19, 2001. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14512 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 76 </CFR>
                <DEPDOC>[CS Docket No. 96-85, FCC 02-117] </DEPDOC>
                <SUBJECT>Implementation of Cable Act Reform Provisions of the Telecommunications Act of 1996 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In this document, the Commission addresses petitions for reconsideration or clarification regarding certain decisions in this proceeding. It affirms its earlier decisions and denies the petitions. This action by the Commission implements the cable reform provisions of the Telecommunications Act of 1996. </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Thomas L. Horan, Media Bureau, 202-418-7200. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of the Commission's Order on Reconsideration, FCC 02-117, adopted on April 16, 2002 and released on April 22, 2002. The full text of this Order on Reconsideration is available for inspection and copying during normal business hours in the FCC Reference Center, Room CY-A257, 445 12th Street, SW., Washington, DC 20554 or may be downloaded at www.fcc.gov. The Order may be purchased from the Commission's copy contractor, Qualex International, 445 12th Street, SW., Room CY-B402, Washington, DC, 20554, telephone 202-863-2893, facsimile 202-863-2898, or via e-mail 
                    <E T="03">qualexint@aol.com.</E>
                </P>
                <P>In the Report and Order (“R&amp;O”), 64 FR 35948, July 2, 1999, in this proceeding, the Commission adopted rules to implement the cable reform provisions of the Telecommunications Act of 1996. This Order on Reconsideration addresses and subsequently denies petitions for reconsideration or clarification regarding certain of our decisions in the R&amp;O. The major decisions in the Order on Reconsideration are as follows: </P>
                <P>• The Commission reiterates that a Local Franchising Authority (“LFA”) may establish and enforce requirements for facilities and equipment pursuant to the franchising and renewal provisions of the statute consistent with the statutory directive that forbids an LFA from directing the use of particular transmission technologies. </P>
                <P>• The Commission reaffirms that bulk discounts should not be premised on a cable operator's exclusive access to all residents. </P>
                <P>• The Commission reaffirms its prior decision that truly passive investments should be excluded when determining whether an entity is affiliated with a cable operator for purposes of the small cable operator rate rules </P>
                <P>• The Commission reiterates that when determining if there is effective competition by a local exchange carrier, the Commission will make a fact-specific finding in each case. </P>
                <HD SOURCE="HD1">Ordering Clause </HD>
                <P>
                    <E T="03">It is ordered</E>
                     that, pursuant to section 405 of the Communications Act of 1934, as amended, 47 U.S.C. 405, and section 1.106 of the Commission's rules, 47 CFR 1.106, the petitions for reconsideration or clarification are 
                    <E T="03">denied.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 76 </HD>
                    <P>Cable television.</P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>Marlene H. Dortch, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15082 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6412-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Parts 600 and 660</CFR>
                <DEPDOC>[Docket No. 011231309-2090-03 ;I.D. 121301A]</DEPDOC>
                <RIN>RIN 0648-AO69</RIN>
                <SUBJECT>Magnuson-Stevens Act Provisions; Fisheries off the West Coast States and in the Western Pacific; Pacific Coast Groundfish Fishery; Groundfish Fishery Management Measures; Corrections</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Corrections to the 2002 specifications and management measures and the limited entry trawl trip limit table.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document contains corrections to the trawl trip limits and management measures for flatfish north and south of 40°10′ N. lat. published in the March 7, 2002, final rule 
                        <PRTPAGE P="40871"/>
                        implementing the 2002 Pacific Coast groundfish fishery specifications and management measures (March 7, 2002) and to the inseason action published May 7, 2002.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Effective June 14, 2002, through the effective date of the 2003 specifications and management measures for the Pacific Coast groundfish fishery, unless modified, superceded, or rescinded, in which case it will be announced in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jamie Goen (Northwest Region, NMFS), 206-526-6140.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    The specifications and management measures for the current fishing year (January 1 - December 31, 2002) were initially published in the 
                    <E T="04">Federal Register</E>
                     as an emergency rule for January 1-February 28, 2002 (67 FR 1540, January 11, 2002), and  as a proposed rule for all of 2002 (67 FR 1555, January 11, 2002)  that was finalized effective March 1, 2002 (67 FR 10490, March 7, 2002).  In the meantime, the emergency rule was amended at 67 FR 3820 (January 28, 2002) and at 67 FR 7289 (February 19, 2002).  The final rule was subsequently amended at 67 FR 15338 (April 1, 2002) and, at 67 FR 30604 (May 7, 2002).
                </P>
                <P>The final rule (67 FR 10490, March 7, 2002) and the subsequent inseason action (67 FR 30604, May 7, 2002) contained errors that need correction.  More specifically, corrections to the limited entry trawl regulatory language on large footrope restrictions in the final rule and to the trip limit table (Table 3) in the inseason action are needed to clarify the Council’s intent for limited entry trawl, large footrope flatfish limits north and south of 40°10′ N. lat.</P>
                <HD SOURCE="HD1">Corrections</HD>
                <P>In the final rule, FR Doc. 02-5302, in the issue of Thursday, March 7, 2002 (67 FR 10490) make the following correction:</P>
                <P>1.  On page 10512, in the third column, under section IV. NMFS Actions(A)(14), the second sentence of paragraph (b)(i) is corrected to read as follows:</P>
                <STARS/>
                <P>(b) * * *</P>
                <P>
                    (i) 
                    <E T="03">Large footrope trawl.</E>
                    * * *  It is unlawful to take and retain, possess or land petrale sole, rex sole, or arrowtooth flounder from a fishing trip if large footrope gear is onboard and the trip is conducted at least in part between May 1 and October 31; cumulative limits for “all other flatfish” (all flatfish except those with cumulative trip limits in Table 3 to section IV) and arrowtooth flounder (during January-April and September-December) are lower for vessels with large footrope gear on board throughout the year (See Table 3).
                </P>
                <STARS/>
                <P>In the inseason action rule, FR Doc. 02-11218, in the issue of Tuesday, May 7, 2002 (67 FR 30604) make the following correction:</P>
                <P>1.  On page 30609, in line 34 (All other flatfish-North and South: large footrope) in Table 3 is removed and the large footrope information previously contained in line 34 is added under the headers “Flatfish-North” and “Flatfish-South” to read as follows:</P>
                <BILCOD>BILLING CODE  3510-22-S</BILCOD>
                <GPH SPAN="3" DEEP="605">
                    <PRTPAGE P="40872"/>
                    <GID>ER14JN02.001</GID>
                </GPH>
                <GPH SPAN="3" DEEP="334">
                    <PRTPAGE P="40873"/>
                    <GID>ER14JN02.002</GID>
                </GPH>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq</E>
                        .
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 7, 2002.</DATED>
                    <NAME>William T. Hogarth,</NAME>
                    <TITLE>Assistant Administrator for Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14961 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE  3510-22-C</BILCOD>
        </RULE>
    </RULES>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="40874"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service </SUBAGY>
                <CFR>7 CFR Part 319 </CFR>
                <DEPDOC>[Docket No. 01-132-1] </DEPDOC>
                <SUBJECT>Gypsy Moth Host Material From Canada; Removal of Infested Areas in British Columbia, Canada </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are proposing to amend the regulations concerning gypsy moth host material from Canada by removing the areas in British Columbia from the list of gypsy moth infested areas. Surveys have shown that those areas in British Columbia have been free of gypsy moth for the past 2 years. This proposed action would remove restrictions on the importation of regulated articles from British Columbia that no longer appear necessary. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments we receive that are postmarked, delivered, or e-mailed by August 13, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by postal mail/commercial delivery or by e-mail. If you use postal mail/commercial delivery, please send four copies of your comment (an original and three copies) to: Docket No. 01-132-1, Regulatory Analysis and Development, PPD, APHIS, Station 3C71, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. 01-132-1. If you use e-mail, address your comment to 
                        <E T="03">regulations@aphis.usda.gov.</E>
                         Your comment must be contained in the body of your message; do not send attached files. Please include your name and address in your message and “Docket No. 01-132-1” on the subject line. 
                    </P>
                    <P>You may read any comments that we receive on this docket in our reading room. The reading room is located in room 1141 of the USDA South Building, 14th Street and Independence Avenue SW., Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming. </P>
                    <P>
                        APHIS documents published in the 
                        <E T="04">Federal Register</E>
                        , and related information, including the names of organizations and individuals who have commented on APHIS dockets, are available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/rad/webrepor.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Frederick A. Thomas, Export Operations Officer, Phytosanitary Issues Management, PPQ, APHIS, 4700 River Road Unit 140, Riverdale, MD 20737-1236; (301) 734-8367. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>
                    The gypsy moth, 
                    <E T="03">Lymantria dispar</E>
                     (Linnaeus), is a destructive pest of forest and shade trees. The regulations in “Subpart—Gypsy Moth Host Material from Canada” (7 CFR 319.77-1 through 319.77-5, referred to below as the regulations) restrict the importation of certain gypsy moth host material (regulated articles) from Canada to prevent the spread of gypsy moth from Canada into noninfested areas of the United States. The regulations in § 319.77-2 identify the following as regulated articles: Trees without roots (e.g., Christmas trees), unless greenhouse-grown throughout the year; trees with roots, unless greenhouse-grown throughout the year; shrubs with roots and persistent woody stems, unless greenhouse-grown throughout the year; logs with bark attached; pulpwood with bark attached; outdoor household articles; and mobile homes and their associated equipment. Regulated articles must meet specific certification or destination requirements if they are intended to be moved into or through areas of the United States that are not infested with gypsy moth. Section 319.77-3 lists those areas of Canada known to be infested with gypsy moth. The descriptions of those infested areas, which are in British Columbia, New Brunswick, Nova Scotia, Ontario, and Quebec, were provided by the Canadian Food Inspection Agency (CFIA). Section 319.77-4 contains the conditions for the importation into the United States of regulated articles from Canada. 
                </P>
                <P>It has been our policy, agreed upon by CFIA, that an area must be free from gypsy moth for a period of 2 consecutive years before it will be removed from the list of gypsy moth infested areas. This is consistent with our practice under the provisions of our domestic quarantine regulations on gypsy moth in 7 CFR 301.45 through 301.45-12. Those areas in British Columbia that have been listed in the regulations as gypsy moth infested areas have been surveyed and found free of gypsy moth for the past 2 years, and have thus met our standard for removal from the list of gypsy moth infested areas. </P>
                <P>Therefore, we are proposing to amend the regulations by removing those areas in British Columbia from the list of gypsy moth infested areas in Canada. This proposed action would remove restrictions on the importation of regulated articles from British Columbia that no longer appear necessary. </P>
                <HD SOURCE="HD1">Executive Order 12866 and Regulatory Flexibility Act </HD>
                <P>This proposed rule has been reviewed under Executive Order 12866. For this action, the Office of Management and Budget has waived its review under Executive Order 12866. </P>
                <P>We are proposing to amend the regulations concerning gypsy moth host material from Canada by removing areas in British Columbia from the list of gypsy moth infested areas. Surveys have shown that those areas in British Columbia have been free of gypsy moth for the past 2 years. This proposed action would relieve the specific certification and destination requirements of the regulations for certain gypsy moth host material imported into the United States from British Columbia. </P>
                <P>
                    The articles that would be affected by this proposed rule are trees without roots (e.g., Christmas trees), unless greenhouse-grown throughout the year; trees with roots, unless greenhouse-grown throughout the year; shrubs with roots and persistent woody stems, unless greenhouse-grown throughout the year; logs with bark attached; pulpwood with bark attached; outdoor household articles; and mobile homes and their associated equipment. In 2000, the United States imported nearly $282 million in live plants and trees, about $64 million in Christmas trees and 
                    <PRTPAGE P="40875"/>
                    foliage, and more than $253 million in wood in the rough (i.e., logs with bark and pulpwood). Table 1 shows the total values of these imported products in 2000 and the percentage coming from Canada. Canada ranks first among the sources of U.S. imports of these products. 
                </P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s40,10,10">
                    <TTITLE>Table 1.—U.S. Imports of Live Trees, Plants, and Rough Wood in 2000 </TTITLE>
                    <BOXHD>
                        <CHED H="1">Commodity group </CHED>
                        <CHED H="1">Total value of imports ($ million) </CHED>
                        <CHED H="1">
                            Percentage from 
                            <LI>Canada</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">0602 </ENT>
                        <ENT>$281.9 </ENT>
                        <ENT>72 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">060491 </ENT>
                        <ENT>64.2 </ENT>
                        <ENT>71 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">44010 </ENT>
                        <ENT>4.0 </ENT>
                        <ENT>85 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4403 </ENT>
                        <ENT>249.4 </ENT>
                        <ENT>92 </ENT>
                    </ROW>
                </GPOTABLE>
                <NOTE>
                    <HD SOURCE="HED">Note: </HD>
                    <P>The numbers identifying the commodities denote the harmonized system for classifying commodities in trade. These digits denote the general classes of live trees, plants, and rough wood traded. The first group, 0602, includes live roses, live fruit or nut trees, rhododendrons and azaleas, live orchid plants, chrysanthemums with soil attached, poinsettias with soil attached, herbaceous perennials, and trees and shrubs with soil attached. The second category, 060491, includes fir, northern Douglas, and other evergreen Christmas trees (also included in this category is foliage). The third group, 44010, includes fuel wood in logs, billets, and twigs. The fourth group, 4403, is wood in the rough. </P>
                    <P>
                        <E T="03">Source:</E>
                         World Trade Atlas, Global Trade Information Services: Calendar Year 2000. 
                    </P>
                </NOTE>
                <P>Canada is the major source of all U.S. imports of the regulated articles covered by the regulations, and British Columbia supplies a large portion of those Canadian exports. Table 2 shows U.S. imports of regulated articles from British Columbia during period 1996-2000. </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s25,10,10,10,10,10">
                    <TTITLE>Table 2.—U.S. Imports of Live Trees, Plants, and Rough Wood From British Columbia, 1996-2000 </TTITLE>
                    <BOXHD>
                        <CHED H="1">Commodity group </CHED>
                        <CHED H="1">
                            1996 
                            <LI>($ million) </LI>
                        </CHED>
                        <CHED H="1">
                            1997 
                            <LI>($ million) </LI>
                        </CHED>
                        <CHED H="1">
                            1998 
                            <LI>($ million) </LI>
                        </CHED>
                        <CHED H="1">
                            1999 
                            <LI>($ million) </LI>
                        </CHED>
                        <CHED H="1">
                            2000 
                            <LI>($ million) </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">0602 </ENT>
                        <ENT>$14.2 </ENT>
                        <ENT>$18.3 </ENT>
                        <ENT>$23.2 </ENT>
                        <ENT>$31.9 </ENT>
                        <ENT>$42.4 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">060491 </ENT>
                        <ENT>3.1 </ENT>
                        <ENT>2.8 </ENT>
                        <ENT>2.5 </ENT>
                        <ENT>2.7 </ENT>
                        <ENT>2.1 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">440110 </ENT>
                        <ENT>1.1 </ENT>
                        <ENT>1.2 </ENT>
                        <ENT>1.4 </ENT>
                        <ENT>1.5 </ENT>
                        <ENT>1.7 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">4403 </ENT>
                        <ENT>45.4 </ENT>
                        <ENT>43.0 </ENT>
                        <ENT>60.9 </ENT>
                        <ENT>110.8 </ENT>
                        <ENT>155.2 </ENT>
                    </ROW>
                    <TNOTE>
                        <E T="03">Source:</E>
                         Statistics Canada. 
                    </TNOTE>
                </GPOTABLE>
                <P>With the exception of outdoor household articles and mobile homes and their associated equipment, regulated articles originating in a Canadian infested area that are to be moved into or through U.S. noninfested areas must be accompanied by an officially endorsed Canadian phytosanitary certificate that includes an additional declaration confirming that the regulated articles have been inspected and found free of gypsy moth or that the regulated articles have been treated for gypsy moth in accordance with the Plant Protection and Quarantine Treatment Manual. Logs or pulpwood originating in a Canadian infested area may also be moved into or through U.S. noninfested areas if they are moved to a specified U.S. processing plant or mill under compliance agreement with the Animal and Plant Health Inspection Service for specified handling or processing that will mitigate the risk of gypsy moth. Outdoor household articles and mobile homes and their associated equipment that are being moved from a Canadian infested area into or through U.S. noninfested areas may be imported into the United States only if they are accompanied by a statement, signed by their owner, stating that they have been inspected and found free of gypsy moth. </P>
                <P>Under the regulations, logs or pulpwood with bark attached, trees, and shrubs originating in a Canadian noninfested area that are to be moved into or through a U.S. noninfested area must be accompanied by a certification of origin stating that they were produced in an area of Canada where gypsy moth is not known to occur. (As defined in § 319.77-1, a certification of origin is a signed, accurate statement certifying the area in which a regulated article was produced or grown that may be provided directly on the shipping documents accompanying shipments of commercial wood products from Canada, or may be provided on a separate certificate.) Outdoor household articles and mobile homes and their associated equipment that are being moved from a Canadian noninfested area may be imported into any area of the United States without restriction. </P>
                <P>Our proposed removal of areas in British Columbia from the list of Canadian infested areas would eliminate the costs associated with the phytosanitary certificates required by our Canadian gypsy moth regulations for most regulated articles moved from British Columbia into or through U.S. noninfested areas. Some regulated articles, i.e., trees with roots and shrubs with roots and persistent woody stems, would still require a Canadian phytosanitary certificate under our nursery stock regulations in 7 CFR 319.37-4. For most affected entities, therefore, the costs associated with phytosanitary certifications would be replaced with the costs associated with certifications of origin. The cost of a Canadian phytosanitary certificate is $7 or $17 (Canadian), depending on the value of the shipment; the fee for an associated pre-export inspection ranges from $15 to $50 (Canadian) per lot, depending on the type of article presented for inspection. The costs associated with certifications of origin, which are prepared and signed by the exporter, are minimal, given that those certifications require little processing time and no inspection costs or administrative fees. </P>
                <P>While we do not have information on the number and size of entities in British Columbia that might be affected by this proposed rule, the areas within British Columbia that we are proposing to remove from the list of gypsy moth infested areas represent a small portion of the province as a whole, so few entities are likely to be affected. Therefore, we expect this proposed rule would have little economic effect on affected entities, whether small or large. </P>
                <P>In addition, Canada has been and is by far the largest source of U.S. imports of the regulated products, and British Columbia is a large source within Canada. This continued to be the case even after our regulations concerning gypsy moth host material from Canada were established in 1999. Therefore, the decrease in costs is not expected to have a significant effect on this pattern. Thus, the overall effect upon price and competitiveness is expected to be positive but relatively insignificant. </P>
                <P>
                    Under these circumstances, the Administrator of the Animal and Plant 
                    <PRTPAGE P="40876"/>
                    Health Inspection Service has determined that this action would not have a significant economic impact on a substantial number of small entities. 
                </P>
                <HD SOURCE="HD1">Executive Order 12988 </HD>
                <P>This proposed rule has been reviewed under Executive Order 12988, Civil Justice Reform. If this proposed rule is adopted: (1) All State and local laws and regulations that are inconsistent with this rule will be preempted; (2) no retroactive effect will be given to this rule; and (3) administrative proceedings will not be required before parties may file suit in court challenging this rule. </P>
                <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                <P>
                    This proposed rule contains no information collection or recordkeeping requirements under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ). 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 319 </HD>
                    <P>Bees, Coffee, Cotton, Fruits, Honey, Imports, Logs, Nursery Stock, Plant diseases and pests, Quarantine, Reporting and recordkeeping requirements, Rice, Vegetables.</P>
                </LSTSUB>
                  
                <P>Accordingly, we propose to amend 7 CFR part 319 as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 319—FOREIGN QUARANTINE NOTICES </HD>
                    <P>1. The authority citation for part 319 would continue to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>7 U.S.C. 166, 450, 7711-7714, 7718, 7731, 7732, and 7751-7754; 21 U.S.C. 136 and 136a; 7 CFR 2.22, 2.80, and 371.3. </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 319.77-3 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. In § 319.77-3, paragraph (a) would be removed and paragraphs (b) through (e) would be redesignated as paragraphs (a) through (d), respectively. </P>
                    </SECTION>
                    <SIG>
                        <DATED>Done in Washington, DC, this 11th day of June, 2002 . </DATED>
                        <NAME>Peter Fernandez, </NAME>
                        <TITLE>Acting Administrator, Animal and Plant Health Inspection Service. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15074 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Agricultural Marketing Service </SUBAGY>
                <CFR>7 CFR Part 911 </CFR>
                <DEPDOC>[Docket No. FV97-911-1 PR] </DEPDOC>
                <SUBJECT>Limes Grown in Florida and Imported Limes; Withdrawal of a Proposed Rule </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Withdrawal of proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This action withdraws a portion of a proposed rule published in the 
                        <E T="04">Federal Register</E>
                         on April 29, 1997 (62 FR 23185), which would have increased the minimum size requirement prescribed under the lime marketing order and the lime import regulations for the month of June. The order regulates the handling of limes grown in Florida and is administered locally by the Florida Lime Administrative Committee (Committee). The spread of citrus canker in South Florida has decreased production and regulations have been suspended under the marketing order through February 24, 2003. Under section 8e of the Agricultural Marketing Agreement Act of 1937, the lime import regulations also have been suspended through February 24, 2003. Thus, an increase in the size requirements for Florida and imported limes would not be appropriate at this time. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The proposed rule published on April 29, 1997 (62 FR 23185) is partially withdrawn as of June 15, 2002. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Doris Jamieson, Marketing Specialist, Southeast Marketing Field Office, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 799 Overlook Drive, Suite A, Winter Haven, Florida 33884; telephone: (863) 324-3375, Fax: (863) 325-8793; or George Kelhart, Technical Advisor, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue, SW STOP 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938. </P>
                    <P>
                        Small businesses may request information on complying with this regulation by contacting Jay Guerber, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue, SW STOP 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938, or E-mail: 
                        <E T="03">Jay.Guerber@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Marketing Agreement No. 126 and Marketing Order No. 911, both as amended (7 CFR part 911), regulate the handling of limes grown in Florida, hereinafter referred to as the “order.” The order is effective under the Agricultural Marketing Agreement Act of 1937, as amended (7 U.S.C. 601-674), hereinafter referred to as the “Act.” </P>
                <P>
                    This action withdraws a portion of a proposed rule published in the 
                    <E T="04">Federal Register</E>
                     on April 29, 1997, (62 FR 23185), which would have increased the minimum size requirement for limes and limes imported into the United States (7 CFR 911.344 and 944.209). Specifically, the Committee recommended increasing the minimum size requirement from 1
                    <FR>7/8</FR>
                     inches to 2 inches in diameter for the month of June. Under section 8e of the Act, the same change had to be considered for imported limes. Since that proposal was issued, citrus canker has spread throughout South Florida. This outbreak has significantly reduced lime production and all regulations under the lime marketing order and the lime import regulation have been suspended through February 24, 2003 (67 FR 6837). The suspension is intended to reduce industry costs and help the industry recover from the effects of citrus canker. As a consequence, a size increase for June is not necessary at this time, and that portion of the April 1997 proposal is being withdrawn. The other portions of the proposed rule were finalized in a rule published in the 
                    <E T="04">Federal Register</E>
                     on August 26, 1997 (62 FR 45142). 
                </P>
                <P>
                    Therefore, the portion of the proposed rule regarding a size increase for South Florida and imported limes during the month of June published in the 
                    <E T="04">Federal Register</E>
                     April 29, 1997, (62 FR 23185) is hereby withdrawn. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 911 </HD>
                    <P>Limes, Marketing agreements, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>7 U.S.C. 601-674. </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>A.J. Yates, </NAME>
                    <TITLE>Administrator, Agricultural Marketing Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15057 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-02-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Agricultural Marketing Service </SUBAGY>
                <CFR>7 CFR Part 987 </CFR>
                <DEPDOC>[Docket No. FV02-987-1 PR] </DEPDOC>
                <SUBJECT>Domestic Dates Produced or Packed in Riverside County, CA; Increased Assessment Rate </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This rule would increase the assessment rate established for the California Date Administrative Committee (Committee) for the 2002-03 and subsequent crop years from $0.25 to $0.90 per hundredweight of dates handled. The Committee locally administers the marketing order that 
                        <PRTPAGE P="40877"/>
                        regulates the handling of dates produced or packed in Riverside County, California. Authorization to assess date handlers enables the Committee to incur expenses that are reasonable and necessary to administer the program. The crop year begins October 1 and ends September 30. The assessment rate would remain in effect indefinitely unless modified, suspended, or terminated. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by July 15, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit written comments concerning this rule. Comments must be sent to the Docket Clerk, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue, SW., STOP 0237, Washington, DC 20250-0237; Fax: (202) 720-8938, or E-mail: moab.docketclerk@usda.gov. Comments should reference the docket number and the date and page number of this issue of the 
                        <E T="04">Federal Register</E>
                         and will be available for public inspection in the Office of the Docket Clerk during regular business hours, or can be viewed at: 
                        <E T="03">http://www.ams.usda.gov/fv/moab.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Toni Sasselli, Marketing Assistant, or Richard P. Van Diest, Marketing Specialist, California Marketing Field Office, Fruit and Vegetable Programs, AMS, USDA, 2202 Monterey St., suite 102B, Fresno, CA 93721; telephone: (559) 487-5901, Fax: (559) 487-5906; or George Kelhart, Technical Advisor, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue, SW., STOP 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938. </P>
                    <P>
                        Small businesses may request information on compliance with this regulation by contacting Jay Guerber, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue, SW., STOP 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938, or E-mail: 
                        <E T="03">Jay.Guerber@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This rule is issued under Marketing Agreement and Order No. 987, both as amended (7 CFR part 987), regulating the handling of domestic dates produced or packed in Riverside County, California, hereinafter referred to as the “order.” The marketing agreement and order are effective under the Agricultural Marketing Agreement Act of 1937, as amended (7 U.S.C. 601-674), hereinafter referred to as the “Act.” </P>
                <P>The Department of Agriculture (USDA) is issuing this rule in conformance with Executive Order 12866. </P>
                <P>This rule has been reviewed under Executive Order 12988, Civil Justice Reform. Under the marketing order now in effect, California date handlers are subject to assessments. Funds to administer the order are derived from such assessments. It is intended that the assessment rate as proposed herein will be applicable to all assessable dates beginning on October 1, 2002, and continue until amended, suspended, or terminated. This rule will not preempt any State or local laws, regulations, or policies, unless they present an irreconcilable conflict with this rule. </P>
                <P>The Act provides that administrative proceedings must be exhausted before parties may file suit in court. Under section 608c(15)(A) of the Act, any handler subject to an order may file with USDA a petition stating that the order, any provision of the order, or any obligation imposed in connection with the order is not in accordance with law and request a modification of the order or to be exempted therefrom. Such handler is afforded the opportunity for a hearing on the petition. After the hearing USDA would rule on the petition. The Act provides that the district court of the United States in any district in which the handler is an inhabitant, or has his or her principal place of business, has jurisdiction to review USDA's ruling on the petition, provided an action is filed not later than 20 days after the date of the entry of the ruling. </P>
                <P>This rule would increase the assessment rate established for the Committee for the 2002-03 and subsequent crop years from $0.25 to $0.90 per hundredweight of assessable dates handled. </P>
                <P>The California date marketing order provides authority for the Committee, with the approval of USDA, to formulate an annual budget of expenses and collect assessments from handlers to administer the program. The members of the Committee are producers and producer-handlers of California dates. They are familiar with the Committee's needs and with the costs for goods and services in their local area and are thus in a position to formulate an appropriate budget and assessment rate. The assessment rate is formulated and discussed at a public meeting. Thus, all directly affected persons have an opportunity to participate and provide input. </P>
                <P>For the 2001-02 and subsequent crop years, the Committee recommended, and USDA approved, an assessment rate that would continue in effect from crop year to crop year unless modified, suspended, or terminated by USDA upon recommendation and information submitted by the Committee or other information available to USDA. </P>
                <P>The Committee met on April 8, 2002, and unanimously recommended 2002-03 expenditures of $273,450 and an assessment rate of $0.90 per hundredweight of dates handled. In comparison, last year's budgeted expenditures were $90,800. The recommended assessment rate of $0.90 is $0.65 higher than the rate currently in effect. The higher assessment rate is needed to fund the industry's marketing and promotion programs under the Committee budget. These programs have been implemented under a State marketing order. However, the date industry concluded that it was in its best interest to implement the programs under the Federal marketing order because recent court actions have been filed against several California State marketing orders under which similar programs have been implemented. </P>
                <P>Proceeds from the sales of cull dates are usually deposited in a surplus account for subsequent use by the Committee in covering the surplus pool share of the Committee's expenses. Handlers may also dispose of cull dates of their own production within their own livestock-feeding operation; otherwise, such cull dates must be shipped or delivered to the Committee for sale to non-human food product outlets. </P>
                <P>Last year, the Committee applied $5,000 of surplus account monies to cover surplus pool expenses. Based on a recent trend of declining sales of cull dates over the past few years and reduced surplus pool costs, the Committee decided not to apply any of the surplus pool funds toward the 2002-03 Committee budget. The Committee, instead, recommended assessing handlers for the full amount of the increased budget that includes marketing and promotion programs. </P>
                <P>The budgeted administrative expenses for the 2002-03 year include $123,450 for labor and office expenses. This compares to $90,800 in budgeted expenses in 2000-01. In addition, $150,000 has been budgeted for marketing and promotion under the program for the 2002-03 crop year. </P>
                <P>The assessment rate of $0.90 per hundredweight of assessable dates was derived by applying the following formula where: </P>
                <FP SOURCE="FP-1">
                    A=Administrative Reserve ($39,450 of the anticipated $50,000 Administrative Reserve) 
                    <PRTPAGE P="40878"/>
                </FP>
                <FP SOURCE="FP-1">B=2002-03 expected shipments (260,000 hundredweight in pounds) </FP>
                <FP SOURCE="FP-1">C=2002-03 expenses ($273,450); (C−A) ÷ B=$0.90 per hundredweight. </FP>
                <P>Estimated shipments should provide $234,000 in assessment income. Income derived from handler assessments and the administrative reserves would be adequate to cover budgeted expenses. Funds in the reserve are expected to total about $10,550 by September 30, 2003, and therefore would be less than the maximum permitted by the order (not to exceed 50 percent of the average of expenses incurred during the most recent five preceding crop years; § 987.72(c)). </P>
                <P>The proposed assessment rate would continue in effect indefinitely unless modified, suspended, or terminated by the Secretary upon recommendation and information submitted by the Committee or other available information. </P>
                <P>Although this assessment rate would be in effect for an indefinite period, the Committee would continue to meet prior to or during each crop year to recommend a budget of expenses and consider recommendations for modification of the assessment rate. The dates and times of Committee meetings are available from the Committee or USDA. Committee meetings are open to the public and interested persons may express their views at these meetings. USDA would evaluate Committee recommendations and other available information to determine whether modification of the assessment rate is needed. Further rulemaking would be undertaken as necessary. The Committee's 2002-03 budget and those for subsequent crop years would be reviewed and, as appropriate, approved by the USDA. </P>
                <HD SOURCE="HD1">Initial Regulatory Flexibility Analysis</HD>
                <P>Pursuant to requirements set forth in the Regulatory Flexibility Act (RFA), the Agricultural Marketing Service (AMS) has considered the economic impact of this rule on small entities. Accordingly, AMS has prepared this initial regulatory flexibility analysis. </P>
                <P>The purpose of the RFA is to fit regulatory actions to the scale of business subject to such actions in order that small businesses will not be unduly or disproportionately burdened. Marketing orders issued pursuant to the Act, and the rules issued thereunder, are unique in that they are brought about through group action of essentially small entities acting on their own behalf. Thus, both statutes have small entity orientation and compatibility. </P>
                <P>There are approximately 100 producers of dates in the production area and approximately 9 handlers subject to regulation under the marketing order. Small agricultural producers are defined by the Small Business Administration (13 CFR 121.201) as those having annual receipts of less than $750,000, and small agricultural service firms are defined as those having annual receipts are less than $5,000,000. Five of the 9 handlers (55 percent) shipped over $5,000,000 of dates and could be considered large handlers by the Small Business Administration. Four of the 9 handlers (45 percent) shipped under $5,000,000 of dates and could be considered small handlers. The majority of California date producers may be classified as small entities. </P>
                <P>This rule would increase the assessment rate established for the Committee and collected from handlers for the 2002-03 and subsequent crop years from $0.25 to $0.90 per hundredweight of assessable dates handled. The Committee unanimously recommended 2002-03 expenditures of $273,450 and the $0.90 per hundredweight assessment rate. The proposed assessment rate of $0.90 is $0.65 higher than the rate currently in effect. The quantity of assessable dates for the 2002-03-crop year is estimated at 260,000 hundredweight. Thus, the $0.90 per hundredweight rate should provide $234,000 in assessment income and, together with the administrative reserve funds available to the Committee, be adequate to meet this year's expenses. </P>
                <P>The higher assessment rate is needed to fund marketing and promotion programs under the Committee budget. The programs have been implemented under a State marketing order for several years. However, because of legal challenges recently brought against several State marketing order programs implementing marketing and promotion programs, the date industry has decided to implement these programs under the Federal marketing order. </P>
                <P>In addition, proceeds from the sales of cull dates are usually deposited in a surplus account for subsequent use by the Committee in covering the surplus pool share of the Committee's expenses. Handlers may also dispose of cull dates of their own production within their own livestock-feeding operation; otherwise, such cull dates must be shipped or delivered to the Committee for sale to non-human food product outlets. The Committee anticipates a reduction in surplus funds available to the Committee from the sale of cull dates. As a consequence, it decided to fund all of the Committee's expenses with assessment funds during 2002-03. </P>
                <P>The budgeted administrative expenses for the 2002-03 year include $123,450 for labor and office expenses. This compares to $90,800 in budgeted expenses in 2000-01. In addition, $150,000 has been budgeted for marketing and promotion under the marketing order for the 2002-03 crop year. </P>
                <P>The Committee reviewed and unanimously recommended 2002-03 expenditures of $273,450, which include marketing and promotion programs. Prior to arriving at this budget, the Committee considered alternative expenditure levels, including a proposal to not have a budget. The assessment rate of $0.90 per hundredweight of assessable dates was then determined by applying the following formula where: </P>
                <FP SOURCE="FP-1">A=Administrative Reserve ($39,450 of the anticipated $50,000 Administrative Reserve) </FP>
                <FP SOURCE="FP-1">B=2002-03 expected shipments (260,000 hundredweight in pounds) </FP>
                <FP SOURCE="FP-1">C=2002-03 expenses ($273,450); (C − A) ÷ B=$0.90 per hundredweight. </FP>
                <P>Estimated shipments should provide $234,000 in assessment income. Income derived from handler assessments and the administrative reserves would be adequate to cover budgeted expenses. Funds in the administrative reserve are expected to total about $10,550 by September 30, 2003, and therefore would be less than the maximum permitted by the order (not to exceed 50 percent of the average of expenses incurred during the most recent five preceding crop years; § 987.72(c)). </P>
                <P>A review of historical information and preliminary information pertaining to the upcoming crop year indicates that the grower price for the 2002-03 season could range between $30 and $75 per hundredweight of dates. Therefore, the estimated assessment revenue for the 2002-03 crop year as a percentage of total grower revenue could range between 1 and 3 percent. </P>
                <P>
                    This action would increase the assessment obligation imposed on handlers under the Federal marketing order. While assessments impose some additional costs on handlers under the Federal marketing order, the costs are minimal and uniform on all handlers. Some of the additional costs may be passed on to producers. However, these costs would be offset by the benefits derived by the operation of the marketing order. In addition, the Committee's meeting was widely publicized throughout the California date industry, and all interested persons were invited to attend the meeting and participate in Committee deliberations 
                    <PRTPAGE P="40879"/>
                    on all issues. Like all Committee meetings, the April 8, 2002 meeting was a public meeting and all entities, both large and small, were able to express views on this issue. Finally, interested persons are invited to submit information on the regulatory and informational impacts of this action on small businesses. 
                </P>
                <P>This proposed rule would impose no additional reporting or recordkeeping requirements on either small or large California date handlers. As with all Federal marketing order programs, reports and forms are periodically reviewed to reduce information requirements and duplication by industry and public sector agencies. </P>
                <P>USDA has not identified any relevant Federal rules that duplicate, overlap, or conflict with this rule. </P>
                <P>
                    A small business guide on complying with fruit, vegetable, and specialty crop marketing agreements and orders may be viewed at: 
                    <E T="03">http//www.ams.usda.gov/fv/moab.html.</E>
                     Any questions about the compliance guide should be sent to Jay Guerber at the previously mentioned address in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. 
                </P>
                <P>Interested persons may comment on this proposed rule through July 15, 2002. The date of July 15, 2002, is deemed appropriate because: (1) The 2002-03 crop year begins on October 1, 2002, and the marketing order requires that the rate of assessment for each crop year apply to all assessable dates handled during such crop year; (2) the Committee needs to have sufficient funds to pay its expenses which are incurred on a continuous basis; and (3) handlers are aware of this action which was unanimously recommended by the Committee at a public meeting and is similar to other assessment rate actions issued in past years. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 987 </HD>
                    <P>Dates, Marketing agreements, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For the reasons set forth in the preamble, 7 CFR part 987 is proposed to be amended as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 987—DOMESTIC DATES PRODUCED OR PACKED IN RIVERSIDE COUNTY, CALIFORNIA </HD>
                    <P>1. The authority citation for 7 CFR part 987 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>7 U.S.C. 601-674.</P>
                    </AUTH>
                    <P>2. Section 987.339 is revised to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 987.339 </SECTNO>
                        <SUBJECT>Assessment rate. </SUBJECT>
                        <P>On and after October 1, 2002, an assessment rate of $0.90 per hundredweight is established for California dates. </P>
                    </SECTION>
                    <SIG>
                        <DATED>Dated: June 10, 2002. </DATED>
                        <NAME>A.J. Yates, </NAME>
                        <TITLE>Administrator, Agricultural Marketing Service. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15058 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-02-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Agricultural Marketing Service </SUBAGY>
                <CFR>7 CFR Part 999 </CFR>
                <DEPDOC>[Docket No. FV02-999-1 PR] </DEPDOC>
                <SUBJECT>Specialty Crops, Import Regulations; Addition of a New Varietal Type to the Raisin Import Regulation </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule would add Other-Seedless Sulfured raisins, along with quality requirements, to the raisin import regulation. The import regulation is authorized under section 8e of the Agricultural Marketing Agreement Act of 1937 (Act) and requires imports of raisins to meet the same or comparable grade and size requirements as those in effect under Federal Marketing Order No. 989 (order). The order regulates the handling of raisins produced from grapes grown in California. The regulations authorized under the domestic order were recently changed to add Other-Seedless Sulfured raisins, along with quality requirements for this varietal type. This is a new type of raisin being produced by some California industry members. This rule would bring the import regulation into conformity with the regulations for California raisins under the marketing Order. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by August 13, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit written comments concerning this proposal. Comments must be sent to the Docket Clerk, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; Fax (202) 720-8938, or E-mail: 
                        <E T="03">moab.docketclerk@usda.gov.</E>
                         All comments should reference the docket number and the date and page number of this issue of the 
                        <E T="04">Federal Register</E>
                         and will be made available for public inspection in the Office of the Docket Clerk during regular business hours, or can be viewed at: 
                        <E T="03">http://www.ams.usda.gov/fv/moab.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Maureen T. Pello, Senior Marketing Specialist, California Marketing Field Office, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 2202 Monterey Street, suite 102B, Fresno, California 93721; telephone: (559) 487-5901, Fax: (559) 487-5906; or George Kelhart, Technical Advisor, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington, DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938. </P>
                    <P>
                        Small businesses may request information on complying with this regulation by contacting Jay Guerber, Marketing Order Administration Branch, Fruit and Vegetable Programs, AMS, USDA, 1400 Independence Avenue SW., STOP 0237, Washington DC 20250-0237; telephone: (202) 720-2491, Fax: (202) 720-8938, or E-mail: 
                        <E T="03">Jay.Guerber@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This proposed rule is issued under section 8e of the Agricultural Marketing Agreement Act of 1937, as amended (7 U.S.C. 601-674), hereinafter referred to as the “Act,” which provides that whenever certain specified commodities, including raisins, are regulated under a Federal marketing order, imports of these commodities into the United States are prohibited unless they meet the same or comparable grade, size, quality, or maturity requirements as those in effect for the domestically produced commodity. </P>
                <P>The Department of Agriculture (USDA) is issuing this rule in conformance with Executive Order 12866. </P>
                <P>This rule has been reviewed under Executive Order 12988, Civil Justice Reform. This rule is not intended to have retroactive effect. This rule will not preempt any State or local laws, regulations, or policies, unless they present an irreconcilable conflict with this rule. </P>
                <P>There are no administrative procedures which must be exhausted prior to any judicial challenge to the provisions of import regulations issued under section 8e of the Act. </P>
                <P>
                    This rule would add a new varietal type to the raisin import regulation. This action would add Other Seedless-Sulfured raisins, along with quality requirements, to the import regulation. This action is necessary to bring the import regulation in line with the domestic marketing order. The order 
                    <PRTPAGE P="40880"/>
                    regulates the handling of raisins produced from grapes grown in California. 
                </P>
                <P>The domestic order provides authority for volume and quality regulations that are imposed by varietal type. Section 989.10 of the order defines the term “varietal type” to mean raisins generally recognized as possessing characteristics differing from other raisins in a degree sufficient to make necessary or desirable separate identification and classification. That section includes a list of varietal types, and provides authority for the Raisin Administrative Committee (RAC), with the approval of USDA, to change this list. A description of these varietal types, along with additional varietal types, is specified in § 989.110 of the order's administrative rules and regulations. </P>
                <P>
                    In August 2001, the RAC, which locally administers the order, recommended changing the domestic regulation to add a new varietal type of raisin. Some California industry members are marketing a new type of raisin that is made by dehydrating sulfured red seedless grapes. These raisins did not fit into any of the existing varietal types specified under the order prior to the issuance of the rulemaking action mentioned below. Such raisins are similar to the Other Seedless varietal type, except they have been sulfured. Such raisins are also similar to the Golden Seedless varietal type, but may not meet the color requirements for Golden Seedless raisins. Golden Seedless raisins are made from green seedless grapes and are mostly yellowish green to green amber in color when sulfured. Red seedless grapes typically vary in color when sulfured. Thus, the RAC recommended establishing a new varietal type, along with quality requirements, for Other Seedless-Sulfured raisins. This action was published in the 
                    <E T="04">Federal Register</E>
                     on May 28, 2002 (67 FR 36789) and became effective on May 29, 2002. 
                </P>
                <P>This rule would bring the raisin import regulation into conformity with the domestic order. This action would add Other Seedless-Sulfured raisins to the list of varietal types specified in § 999.300(a)(2) of the raisin import regulation. This rule would also add Other Seedless-Sulfured raisins to § 999.300(b)(1); thus, imports of such raisins would have to meet the same quality requirements in effect for such raisins domestically produced. USDA is not aware of any imports of this type of raisin at this time. </P>
                <P>Accordingly, imported lots of Other Seedless-Sulfured raisins would have to meet the requirements of U.S. Grade C as defined in the United States Standards for Grades of Processed Raisins (§§ 52.1841 through 52.1858) issued under the Agricultural Marketing Act of 1946 (7 U.S.C. 1622 through 1624). At least 70 percent, by weight, of the raisins in a lot would have to be well-matured or reasonably well-matured. With respect to select-sized and mixed-sized lots, the raisins would have to at least meet the U.S. Grade B tolerances for pieces of stem and undeveloped and substandard raisins, and small (midget) sized raisins would have to meet the U.S. Grade C tolerances for those factors. Raisin importers would continue to be charged $47 per hour by USDA for inspecting the raisins. </P>
                <HD SOURCE="HD1">Initial Regulatory Flexibility Analysis </HD>
                <P>Pursuant to requirements set forth in the Regulatory Flexibility Act (RFA), the Agricultural Marketing Service (AMS) has considered the economic impact of this action on small entities. Accordingly, AMS has prepared this initial regulatory flexibility analysis. </P>
                <P>The purpose of the RFA is to fit regulatory actions to the scale of business subject to such actions in order that small businesses will not be unduly or disproportionately burdened. Marketing orders issued pursuant to the Act, and rules issued thereunder, are unique in that they are brought about through group action of essentially small entities acting on their own behalf. Thus, both statutes have small entity orientation and compatibility. Import regulations issued under the Act are based on those established under Federal marketing orders. </P>
                <P>There are approximately 75 importers of raisins. During the 2000-01 season (August 2000 through September 2001), the dollar value of U.S. raisin imports totaled $12.2 million. During the 1999-2000 season, the value was $21.7 million. During the 1996-97 through 2000-01 seasons, the value of imports ranged from a low of $11.8 million in 1997-98 to a high of $29.6 million in 1998-99. Small agricultural service firms, which includes raisin importers, are defined by the Small Business Administration (13 CFR 121.201) as those having annual receipts of less than $5,000,000. A majority of importers may be classified as small entities. </P>
                <P>Mexico, Chile, Argentina, and the Republic of South Africa are the major raisin-producing countries exporting raisins to the United States. During the 2000-01 season, 11,631 metric tons of raisins were imported into the United States. Chile accounted for 4,841 metric tons, 3,811 metric tons arrive for Mexico, 1,245 metric tons were imported from Argentina, and 1,245 metric tons arrived from the Republic of South Africa. Most of the remaining balance came from Iran, Turkey, and Pakistan. During the 1999-2000 season, 17,538 metric tons of raisins were imported. Of the tonnage, 6,076 metric tons came from Mexico, 6,134 metric tons came from Chile, 2,436 tons arrived from Argentina, and 1,400 metric tons were from the Republic of South Africa. Most the remaining tonnage was imported from Afghanistan, Turkey, and Pakistan. During the 1996-97 through 2000-01 seasons, raisins imports ranged from a low of 10,390 metric tons in 1997-98 to a high of 25,337 metric tons in 1998-99. </P>
                <P>This rule would add Other Seedless-Sulfured raisins to the list of varietal types specified in § 999.300(a)(2) of the raisin import regulation. This rule would also add Other Seedless-Sulfured raisins to § 999.300(b)(1); thus, imports of such raisins would have to meet the same quality requirements in effect for such domestically produced raisins. Authority for these changes is provided in section 8e of the Act. </P>
                <P>Regarding the impact of this action on affected entities, this rule would bring the import regulation into conformity with the domestic regulation. The domestic regulation was changed on May 29, 2002 (67 FR 36789) to add a varietal type, along with quality requirements, for Other Seedless-Sulfured raisins. This is a new type of raisin being produced by some members of the California raisin industry. Accordingly, under section 8e of the Act, imports of Other Seedless-Sulfured raisins would have to meet the same quality requirements as the domestic product. Raisin importers would continue to be charged $47 per ton by USDA for inspecting the raisins. As previously stated, USDA is not aware at this time of any imports of this type of raisin. </P>
                <P>With regards to alternatives, as previously stated, the Act requires that raisin imports meet the same or comparable grade and size requirements as those in effect under Federal Marketing Order No. 989. </P>
                <P>
                    This rule would impose no additional reporting or recordkeeping requirements on either small or large raisin importers. Reports and forms required under the raisin import regulation are periodically reviewed to reduce information requirements and duplication by industry and public sector agencies. There are currently two forms required under the raisin import regulation. Forms 1 and 2 must be completed only for lots of raisins that do not meet applicable grade and size requirements and are going to be used in the 
                    <PRTPAGE P="40881"/>
                    production of other products besides raisins. In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35), the information collection requirements referenced herein have been approved by the Office of Management and Budget (OMB) under OMB. NO. 0581-0178. It is estimated that it takes importers of raisins about 15 minutes to complete Raisin Form No. 1, and processors of failing imported raisins about 15 minutes to complete Raisin Form No. 2. The total annual burden for Raisin Form Nos. 1 and 2, respectively, is 24 hours. 
                </P>
                <P>Additionally, except for applicable domestic regulations, USDA has not identified any relevant Federal rules that duplicate, overlap, or conflict with this rule. However, as previously stated, imports of Other Seedless-Sulfured raisins must meet a modified U.S. Grade C as defined in the United States Standards for Grades of Processed Raisins (§§ 52.1841 through 52.1858) issued under the Agricultural Marketing Act of 1946 (7 U.S.C. 1622 through 1624). Finally, all interested persons are invited to submit information on the regulatory and information impact of this action on small businesses. </P>
                <P>
                    A small business guide on complying with fruit, vegetable, and specialty crop marketing agreements and orders may be viewed at: 
                    <E T="03">http://www.ams.usda.gov/fv/moab.html.</E>
                     Any questions about the compliance guide should be sent to Jay Guerber at the previously mentioned address in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. 
                </P>
                <P>In accordance with section 8e of the Act, the United States Trade Representative has concurred with the issuance of this proposed rule. </P>
                <P>This rule invites comments on adding Other Seedless-Sulfured raisins, along with quality requirements, to the raisin import regulation. A 60-day comment period is provided to allow interested persons to respond to this rule. All comments received will be considered prior to finalization of this rule. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 999 </HD>
                    <P>Dates, Filberts, Food grades and standards, Imports, Nuts, Prunes, Raisins, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                  
                <P>For the reasons set forth in the preamble, 7 CFR part 999 is proposed to be amended to read as followed: </P>
                <PART>
                    <HD SOURCE="HED">PART 999—SPECIALITY CROPS; IMPORT REGULATIONS </HD>
                    <P>1. The authority citation for 7 CFR part 999 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>7 U.S.C. 601-674. </P>
                    </AUTH>
                    <P>2. In § 999.300, paragraph (a)(2) and (b)(1) are revised to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 999.300 </SECTNO>
                        <SUBJECT>Regulation governing importation of raisin. </SUBJECT>
                        <P>(a) * * * </P>
                        <P>
                            (2) 
                            <E T="03">Varietal type</E>
                             means the applicable one of the following: Thompson Seedless raisins, Muscat raisins, Layer Muscat raisins, Currant raisins, Monukka raisins, Other Seedless raisins, Golden Seedless raisins, and Other Seedless-Sulfured raisins. 
                        </P>
                        <STARS/>
                        <P>(b) * * * </P>
                        <P>
                            (1) With respect to Thompson Seedless and Other Seedless-Sulfured raisins —the requirements of U.S. Grade C as defined in the effective United States Standards of Grades of Processed Raisins (§§ 52.1841 through 52.1858 of this title): 
                            <E T="03">Provided,</E>
                             That, at least 70 percent, by weight, of the raisins shall be well-matured or reasonably well-matured. With respect to select-sized and mixed-sized lots, the raisins shall at least meet the U.S. Grade B tolerances for pieces of stem and undeveloped and substandard raisins, and small (midget) sized raisins shall meet the U.S. Grade C tolerances for those factors; 
                        </P>
                        <STARS/>
                    </SECTION>
                    <SIG>
                        <DATED>Dated: June 10, 2002. </DATED>
                        <NAME>A.J. Yates, </NAME>
                        <TITLE>Administrator, Agricultural Marketing Service. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15059 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-02-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL ELECTION COMMISSION </AGENCY>
                <CFR>11 CFR Part 100 </CFR>
                <DEPDOC>[Notice 2002-9] </DEPDOC>
                <SUBJECT>Reorganization of Regulations on “Contribution” and “Expenditure” </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Election Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The recently enacted Bipartisan Campaign Reform Act (“BCRA”) substantially amended the Federal Election Campaign Act (“FECA”). Among its amendments is the deletion of the office facility exception in the definition of “contribution” in section 431(8)(B) of the FECA. The Federal Election Commission (“Commission”) is proposing to amend the regulations to reflect this statutory change. As part of this effort, the Commission is also proposing to reorganize the sections defining “contribution” and “expenditure” in its regulations. The Commission is issuing this notice of proposed rulemaking (“NPRM”) to solicit comments on its proposal to redefine “contribution” and “expenditure” and to reorganize the regulations. Please note that the draft rules that follow do not represent a final decision by the Commission on the issues presented by this rulemaking. Further information is provided in the supplementary information that follows. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received on or before July 12, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>All comments should be addressed to Ms. Rosemary C. Smith, Acting Associate General Counsel, and must be submitted in either electronic or written form. Electronic mail comments should be sent to reorganization@fec.gov and must include the full name, electronic mail address and postal service address of the commenter. Electronic mail comments that do not contain the full name, electronic mail address and postal service address of the commenter will not be considered. Faxed comments should be sent to (202) 219-3923, with printed copy follow-up to ensure legibility. Written comments and printed copies of faxed comments should be sent to the Federal Election Commission, 999 E Street, NW., Washington, DC 20463. Commenters are strongly encouraged to submit comments electronically to ensure timely receipt and consideration. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Rosemary C. Smith, Acting Associate General Counsel, or Ms. Mai T. Dinh, Attorney, 999 E Street, NW., Washington, DC 20463, (202) 694-1650 or (800) 424-9530. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The Bipartisan Campaign Reform Act, Pub. L. 107-155, 116 Stat. 81 (March 27, 2000), significantly amends the Federal Election Campaign Act, 2 U.S.C. 431 
                    <E T="03">et seq.</E>
                    , and directs the Commission to promulgate regulations implementing Title I of the BCRA within 90 days of enactment and to promulgate regulations implementing the other titles of BCRA that are under the Commission's jurisdiction within 270 days of enactment. 
                    <E T="03">See</E>
                     BCRA, section 402(c). The amendment to the definition of “contribution” is in Title I, section 103(b)(1). Section 103(b)(1) deletes current 2 U.S.C. 431(8)(B)(viii), thus eliminating the office facility exception for national party committees from the definition of “contribution.” The Commission's proposal to amend the definitions of “contribution” and “expenditure” to comply with this amendment is contained in this notice of proposed rulemaking (“NPRM”). The Commission has published a separate NPRM to address the impact of this 
                    <PRTPAGE P="40882"/>
                    statutory change on State and local party committees. 
                    <E T="03">See</E>
                     “Prohibited and Excessive Contributions: Non-Federal Funds or Soft Money” (“Soft Money NPRM”). 67 FR 35654 (May 20, 2002). The Soft Money NPRM also addresses the other sections of Title I of BCRA. 
                </P>
                <HD SOURCE="HD1">Proposed Rules </HD>
                <HD SOURCE="HD2">Reorganization of Current 11 CFR 100.7 and 100.8 </HD>
                <P>As part of this NPRM, the Commission is also proposing to reorganize current 11 CFR 100.7 and 100.8. This reorganization would make it easier to locate and read the definitions of “contribution” and “expenditure” and the detailed exceptions to those definitions. The proposed rules would create four new subparts, B through E, within 11 CFR part 100. The definitions of “contribution” and “expenditure” would be moved into these new subparts. Subpart B would describe items that are contributions; subpart C would describe items that are not contributions; subpart D would describe items that are expenditures; and subpart E would describe items that are not expenditures. </P>
                <HD SOURCE="HD2">Inclusion of “Brokerage Loans and Lines of Credit” </HD>
                <P>
                    The proposed rule would incorporate another recent change to the FECA—the inclusion of a loan of money derived from an advance on a candidate's brokerage account, credit card, home equity line of credit, or other line of credit available to the candidate as an item that is not a contribution. The Commission published the final rules, entitled “Brokerage Loans and Lines of Credit,” to amend current 11 CFR 100.7(b) and 100.8(b) to include these types of loans. 
                    <E T="03">See</E>
                     67 FR 38353 (June 4, 2002). The language in this NPRM at proposed 11 CFR 100.73 and 100.114 reflects the language in the “Brokerage Loans and Lines of Credit” final rules. 
                </P>
                <HD SOURCE="HD2">Proposed Amendments to the Office Facility Exception </HD>
                <P>
                    Current 11 CFR 100.7(b)(12) and 100.8(b)(13), designate that the construction or purchase of an office facility is an exception to the definition of contribution and expenditure. The proposed rules would make clear that this exception no longer applies to national party committees by adding a new section, proposed 11 CFR 100.56, that would state that contributions to national party committees for the purchase of an office building or facility is a contribution. In addition, proposed 11 CFR 100.84 would state that donations, made to a non-Federal account of a State, local, or district party committee or organization to purchase or construct an office building, are not contribution. The expenditure subparts would include similar proposed sections pertaining to expenditures for the purchase or construction of an office building or facility. 
                    <E T="03">See</E>
                     proposed 11 CFR 100.114 for national party committees and proposed 11 CFR 100.144 for State, local, or district party committees or organizations. 
                </P>
                <HD SOURCE="HD2">Proposal To Amend “Allocation” to “Attribution” </HD>
                <P>Other than deleting the office facility section, this NPRM would not amend any other provisions in a substantive manner. The Commission is considering making a clarifying amendment in several proposed sections that is not reflected in the proposed rules. In sections that describe the “exempt activities,” the current regulations require that certain contributions or expenditures be allocated to Federal activities. In these sections, however, the contributions or expenditures are not being allocated to Federal candidates in the sense that contributions and expenditures are being allocated under current 11 CFR part 106. Rather, these contributions and expenditures are being attributed to the Federal candidates. Changing the words in the proposed sections may eliminate any confusion that these contributions and expenditures would need to be allocated in a manner similar to the allocations that are required under current 11 CFR part 106. The Commission seeks comment on whether the word “allocation” or any of its derivatives should be changed to “attribution” or one of its derivatives in the following proposed sections: </P>
                <FP SOURCE="FP-2">Proposed section 100.80 Slate cards and sample ballots. </FP>
                <FP SOURCE="FP-2">Proposed section 100.87 Volunteer activity for party committees. </FP>
                <FP SOURCE="FP-2">Proposed section 100.88 Volunteer activity for candidates. </FP>
                <FP SOURCE="FP-2">Proposed section 100.89 Voter registration and get-out-the-vote activities for Presidential candidates (“coattails” exception). </FP>
                <FP SOURCE="FP-2">Proposed section 100.140 Slate cards and sample ballots. </FP>
                <FP SOURCE="FP-2">Proposed section 100.147 Volunteer activity for party committees. </FP>
                <FP SOURCE="FP-2">Proposed section 100.148 Volunteer activity for candidates. </FP>
                <FP SOURCE="FP-2">Proposed section 100.149 Voter registration and get-out-the-vote activities for Presidential candidates (“coattails” exception). </FP>
                <HD SOURCE="HD2">Potential Impact of Soft Money NPRM </HD>
                <P>
                    In addition to the deletion of current 11 CFR 100.7(b)(12) and 100.8(b)(13), the Soft Money NPRM may affect the substance in the definitions of “contribution” and “expenditure”. The Soft Money NPRM identified several issues and alternative approaches on which the Commission sought comment. The issues concerning “exempt activity” by State and local parties and the definition of “Federal election activity” may directly impact on the definitions of “contribution” and “expenditure”.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         For discussion of these issues, 
                        <E T="03">see</E>
                         Soft Money NPRM at 35655-35657, and 35662-35672. 
                    </P>
                </FTNT>
                <P>The resolution of these issues will occur in the final rules arising from the Soft Money NPRM. If these decisions, however, require substantively amending the current definitions of “contribution” or “expenditure”, the amendment to the text of the regulations will be incorporated in the final rules arising from this reorganization rulemaking. This is ensure that there is no confusion, duplication, or inconsistency between this rulemaking that the Soft Money rulemaking. Although the Commission does not anticipate that any of proposed sections in this NPRM would be affected by the Soft Money NPRM, it is possible that any of the following proposed sections would need to be amended in the final rules as a result of the final rules arising from the Soft Money NPRM: </P>
                <FP SOURCE="FP-2">Proposed section 100.80 Slate cards and sample ballots. </FP>
                <FP SOURCE="FP-2">Proposed section 100.87 Volunteer activity for party committees. </FP>
                <FP SOURCE="FP-2">Proposed section 100.88 Volunteer activity for candidates. </FP>
                <FP SOURCE="FP-2">Proposed section 100.89 Voter registration and get-out-the-vote activities for Presidential candidates (“coattails” exception). </FP>
                <FP SOURCE="FP-2">Proposed section 100.140 Slate cards and sample ballots. </FP>
                <FP SOURCE="FP-2">Proposed section 100.147 Volunteer activity for party committees. </FP>
                <FP SOURCE="FP-2">Proposed section 100.148 Volunteer activity for candidates. </FP>
                <FP SOURCE="FP-2">Proposed section 100.149 Voter registration and get-out-the-vote activities for Presidential Candidates (“coattails” exception). </FP>
                <HD SOURCE="HD2">Grammatical and Technical Revisions </HD>
                <P>
                    In addition to non-substantive grammatical corrections, minor technical revisions would be made to reflect the reorganized structure. Other than changes resulting from the Soft Money NPRM, any substantive changes to other provisions or definitions would 
                    <PRTPAGE P="40883"/>
                    be addressed in separate rulemaking projects. The Commission seeks comments on this proposed implementation of section 103(b)(1) of BCRA and the structural reorganization of current 11 CFR 100.7 and 100.8. If the Commission decides to reorganize these sections, the final rules will include a distribution table and a derivative table to cross-reference the current sections to the new sections. 
                </P>
                <HD SOURCE="HD1">Certification of No Effect Pursuant to 5 U.S.C. 605(b) (Regulatory Flexibility Act) </HD>
                <P>The attached proposed rules will not, if promulgated, have a significant economic impact on a substantial number of small entities. The proposed rules would not substantively change the current regulations other than to amend the office facility provision to reflect the amendment to 2 U.S.C. 431(8)(B) as mandated by BCRA and to make minor clarifying changes to current definitions. Therefore, the attached proposed rules, if promulgated, will not have a significant economic impact on a substantial number of small entities. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 11 CFR Part 100 </HD>
                    <P>Elections.</P>
                </LSTSUB>
                <P>
                    For the reasons set out in the preamble, it is proposed to amend Chapter I of title 11 of the 
                    <E T="03">Code of Federal Regulations</E>
                     as follows: 
                </P>
                <PART>
                    <HD SOURCE="HED">PART 100—SCOPE AND DEFINITIONS (2 U.S.C. 431) </HD>
                    <P>1. The authority citation for part 100 would continue to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>2 U.S.C. 431, 434(a)(11), 438(a)(8). </P>
                    </AUTH>
                    <P>2. Section 100.7 would be removed and reserved. </P>
                    <P>3. Section 100.8 would be removed and reserved. </P>
                    <P>4. Part 100 would be amended by adding new subparts B, C, D, and E to read as follows: </P>
                    <CONTENTS>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart B—Definition of Contribution (2 U.S.C. 431(8)) </HD>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>100.51 </SECTNO>
                            <SUBJECT>Scope. </SUBJECT>
                            <SECTNO>100.52 </SECTNO>
                            <SUBJECT>Gift, subscription, loan, advance or deposit of money. </SUBJECT>
                            <SECTNO>100.53 </SECTNO>
                            <SUBJECT>Attendance at a fundraiser or political event. </SUBJECT>
                            <SECTNO>100.54 </SECTNO>
                            <SUBJECT>Compensation for personal services. </SUBJECT>
                            <SECTNO>100.55 </SECTNO>
                            <SUBJECT>Extension of credit. </SUBJECT>
                            <SECTNO>100.56 </SECTNO>
                            <SUBJECT>Office building or facility for national party committees. </SUBJECT>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart C—Exceptions to Contributions </HD>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>100.71 </SECTNO>
                            <SUBJECT>Scope. </SUBJECT>
                            <SECTNO>100.72 </SECTNO>
                            <SUBJECT>Testing the waters. </SUBJECT>
                            <SECTNO>100.73 </SECTNO>
                            <SUBJECT>News story, commentary, or editorial by the media. </SUBJECT>
                            <SECTNO>100.74 </SECTNO>
                            <SUBJECT>Uncompensated services by volunteers. </SUBJECT>
                            <SECTNO>100.75 </SECTNO>
                            <SUBJECT>Use of a volunteer's real or personal property. </SUBJECT>
                            <SECTNO>100.76 </SECTNO>
                            <SUBJECT>Use of church or community room. </SUBJECT>
                            <SECTNO>100.77 </SECTNO>
                            <SUBJECT>Invitations, food, and beverages. </SUBJECT>
                            <SECTNO>100.78 </SECTNO>
                            <SUBJECT>Sale of food or beverages by vendor. </SUBJECT>
                            <SECTNO>100.79 </SECTNO>
                            <SUBJECT>Unreimbursed payment for transportation and subsistence expenses. </SUBJECT>
                            <SECTNO>100.80 </SECTNO>
                            <SUBJECT>Slate cards and sample ballots. </SUBJECT>
                            <SECTNO>100.81 </SECTNO>
                            <SUBJECT>Payment by corporations and labor organizations. </SUBJECT>
                            <SECTNO>100.82 </SECTNO>
                            <SUBJECT>Bank loans. </SUBJECT>
                            <SECTNO>100.83 </SECTNO>
                            <SUBJECT>Brokerage loans and lines of credit to candidates. </SUBJECT>
                            <SECTNO>100.84 </SECTNO>
                            <SUBJECT>Office building for State, local, or district party committees or organizations. </SUBJECT>
                            <SECTNO>100.85 </SECTNO>
                            <SUBJECT>Legal or accounting services to political party committees. </SUBJECT>
                            <SECTNO>100.86 </SECTNO>
                            <SUBJECT>Legal or accounting services to other political committees. </SUBJECT>
                            <SECTNO>100.87 </SECTNO>
                            <SUBJECT>Volunteer activity for party committees. </SUBJECT>
                            <SECTNO>100.88 </SECTNO>
                            <SUBJECT>Volunteer activity for candidates. </SUBJECT>
                            <SECTNO>100.89 </SECTNO>
                            <SUBJECT>Voter registration and get-out-the-vote activities for Presidential candidates (“coattails” exception). </SUBJECT>
                            <SECTNO>100.90 </SECTNO>
                            <SUBJECT>Ballot access fees. </SUBJECT>
                            <SECTNO>100.91 </SECTNO>
                            <SUBJECT>Recounts. </SUBJECT>
                            <SECTNO>100.92 </SECTNO>
                            <SUBJECT>Candidate debates. </SUBJECT>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart D—Definition of Expenditure (2 U.S.C. 431(9)) </HD>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>100.110 </SECTNO>
                            <SUBJECT>Scope. </SUBJECT>
                            <SECTNO>100.111 </SECTNO>
                            <SUBJECT>Gift, subscription, loan, advance or deposit of money. </SUBJECT>
                            <SECTNO>100.112 </SECTNO>
                            <SUBJECT>Contracts, promises, and agreements to make expenditures. </SUBJECT>
                            <SECTNO>100.113 </SECTNO>
                            <SUBJECT>Independent expenditures. </SUBJECT>
                            <SECTNO>100.114 </SECTNO>
                            <SUBJECT>Office building or facility for national party committees. </SUBJECT>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart E—Exceptions to Expenditures </HD>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>100.130 </SECTNO>
                            <SUBJECT>Scope. </SUBJECT>
                            <SECTNO>100.131 </SECTNO>
                            <SUBJECT>Testing the waters. </SUBJECT>
                            <SECTNO>100.132 </SECTNO>
                            <SUBJECT>News story, commentary, or editorial by the media. </SUBJECT>
                            <SECTNO>100.133 </SECTNO>
                            <SUBJECT>Voter registration and get-out-the-vote activities. </SUBJECT>
                            <SECTNO>100.134 </SECTNO>
                            <SUBJECT>Internal communication by corporations, labor organizations, and membership organizations. </SUBJECT>
                            <SECTNO>100.135 </SECTNO>
                            <SUBJECT>Use of a volunteer's real or personal property. </SUBJECT>
                            <SECTNO>100.136 </SECTNO>
                            <SUBJECT>Use of church or community room. </SUBJECT>
                            <SECTNO>100.137 </SECTNO>
                            <SUBJECT>Invitations, food, and beverages. </SUBJECT>
                            <SECTNO>100.138 </SECTNO>
                            <SUBJECT>Sale of food or beverages by vendor. </SUBJECT>
                            <SECTNO>100.139 </SECTNO>
                            <SUBJECT>Unreimbursed payment for transportation and subsistence expenses. </SUBJECT>
                            <SECTNO>100.140 </SECTNO>
                            <SUBJECT>Slate cards and sample ballots. </SUBJECT>
                            <SECTNO>100.141 </SECTNO>
                            <SUBJECT>Payment by corporations and labor organizations. </SUBJECT>
                            <SECTNO>100.142 </SECTNO>
                            <SUBJECT>Bank loans. </SUBJECT>
                            <SECTNO>100.143 </SECTNO>
                            <SUBJECT>Brokerage loans and lines of credit to candidates. </SUBJECT>
                            <SECTNO>100.144 </SECTNO>
                            <SUBJECT>Office building for State, local, or district party committees or organizations. </SUBJECT>
                            <SECTNO>100.145 </SECTNO>
                            <SUBJECT>Legal or accounting services to political party committees. </SUBJECT>
                            <SECTNO>100.146 </SECTNO>
                            <SUBJECT>Legal or accounting services to other political committees. </SUBJECT>
                            <SECTNO>100.147 </SECTNO>
                            <SUBJECT>Volunteer activity for party committees. </SUBJECT>
                            <SECTNO>100.148 </SECTNO>
                            <SUBJECT>Volunteer activity for candidate. </SUBJECT>
                            <SECTNO>100.149 </SECTNO>
                            <SUBJECT>Voter registration and get-out-the-vote activities for Presidential candidates (“coattails” exception). </SUBJECT>
                            <SECTNO>100.150 </SECTNO>
                            <SUBJECT>Ballot access fees. </SUBJECT>
                            <SECTNO>100.151 </SECTNO>
                            <SUBJECT>Recounts. </SUBJECT>
                            <SECTNO>100.152 </SECTNO>
                            <SUBJECT>Fundraising costs for Presidential candidates. </SUBJECT>
                            <SECTNO>100.153 </SECTNO>
                            <SUBJECT>Routine living expenses. </SUBJECT>
                            <SECTNO>100.154 </SECTNO>
                            <SUBJECT>Candidate debates. </SUBJECT>
                        </SUBPART>
                    </CONTENTS>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart B—Definition of Contribution (2 U.S.C. 431(8)) </HD>
                        <SECTION>
                            <SECTNO>§ 100.51 </SECTNO>
                            <SUBJECT>Scope. </SUBJECT>
                            <P>
                                (a) The term 
                                <E T="03">contribution</E>
                                 includes the payments, services, or other things of value described in this subpart. 
                            </P>
                            <P>(b) For the purpose of this subpart, a contribution or payment made by an individual shall not be attributed to any other individual, unless otherwise specified by that other individual in accordance with 11 CFR 110.1(k). </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.52 </SECTNO>
                            <SUBJECT>Gift, subscription, loan, advance or deposit of money. </SUBJECT>
                            <P>(a) A gift, subscription, loan (except for a loan made in accordance with 11 CFR 100.72 and 100.73), advance, or deposit of money or anything of value made by any person for the purpose of influencing any election for Federal office is a contribution. </P>
                            <P>
                                (b) For purposes of this section, the term 
                                <E T="03">loan</E>
                                 includes a guarantee, endorsement, and any other form of security. 
                            </P>
                            <P>(1) A loan that exceeds the contribution limitations of 2 U.S.C. 441a and 11 CFR part 110 shall be unlawful whether or not it is repaid. </P>
                            <P>(2) A loan is a contribution at the time it is made and is a contribution to the extent that it remains unpaid. The aggregate amount loaned to a candidate or committee by a contributor, when added to other contributions from that individual to that candidate or committee, shall not exceed the contribution limitations set forth at 11 CFR part 110. A loan, to the extent it is repaid, is no longer a contribution. </P>
                            <P>
                                (3) Except as provided in paragraph (b)(4) of this section, a loan is a contribution by each endorser or guarantor. Each endorser or guarantor shall be deemed to have contributed that portion of the total amount of the loan for which he or she agreed to be liable in a written agreement. Any reduction in the unpaid balance of the loan shall reduce proportionately the amount endorsed or guaranteed by each endorser or guarantor in such written agreement. In the event that such agreement does not stipulate the portion 
                                <PRTPAGE P="40884"/>
                                of the loan for which each endorser or guarantor is liable, the loan shall be considered a loan by each endorser or guarantor in the same proportion to the unpaid balance that each endorser or guarantor bears to the total number of endorsers or guarantors. 
                            </P>
                            <P>(4) A candidate may obtain a loan on which his or her spouse's signature is required when jointly owned assets are used as collateral or security for the loan. The spouse shall not be considered a contributor to the candidate's campaign if the value of the candidate's share of the property used as collateral equals or exceeds the amount of the loan that is used for the candidate's campaign. </P>
                            <P>(5) If a political committee makes a loan to any person, such loan shall be subject to the limitations of 11 CFR part 110. Repayment of the principal amount of such loan to such political committee shall not be a contribution by the debtor to the lender committee. Such repayment shall be made with funds that are subject to the prohibitions of 11 CFR 110.4(a) and part 114. The payment of interest to such committee by the debtor shall be a contribution only to the extent that the interest paid exceeds a commercially reasonable rate prevailing at the time the loan is made. All payments of interest shall be made from funds subject to the prohibitions of 11 CFR 110.4(a) and part 114. </P>
                            <P>
                                (c) For purposes of this section, the term 
                                <E T="03">money</E>
                                 includes currency of the United States or of any foreign nation, checks, money orders, or any other negotiable instruments payable on demand. 
                            </P>
                            <P>
                                (d)(1) For purposes of this section, the term 
                                <E T="03">anything of value</E>
                                 includes all in-kind contributions. Unless specifically exempted under 11 CFR part 100, subpart C, the provision of any goods or services without charge or at a charge that is less than the usual and normal charge for such goods or services is a contribution. Examples of such goods or services include, but are not limited to: Securities, facilities, equipment, supplies, personnel, advertising services, membership lists, and mailing lists. If goods or services are provided at less than the usual and normal charge, the amount of the in-kind contribution is the difference between the usual and normal charge for the goods or services at the time of the contribution and the amount charged the political committee. 
                            </P>
                            <P>
                                (2) For purposes of paragraph (d)(1) of this section, 
                                <E T="03">usual and normal charge for goods</E>
                                 means the price of those goods in the market from which they ordinarily would have been purchased at the time of the contribution; and usual and normal charge for any services, other than those provided by an unpaid volunteer, means the hourly or piecework charge for the services at a commercially reasonable rate prevailing at the time the services were rendered. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.53 </SECTNO>
                            <SUBJECT>Attendance at a fundraiser or political event. </SUBJECT>
                            <P>The entire amount paid to attend a fundraiser or other political event and the entire amount paid as the purchase price for a fundraising item sold by a political committee is a contribution. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.54 </SECTNO>
                            <SUBJECT>Compensation for personal services. </SUBJECT>
                            <P>The payment by any person of compensation for the personal services of another person if those services are rendered without charge to a political committee for any purpose, except for legal and accounting services provided under 11 CFR 100.74 and 100.75, is a contribution. No compensation is considered paid to any employee under any of the following conditions: </P>
                            <P>
                                (a) 
                                <E T="03">Paid on an hourly or salaried basis.</E>
                                 If an employee is paid on an hourly or salaried basis and is expected to work a particular number of hours per period, no contribution results if the employee engages in political activity during what would otherwise be a regular work period, provided that the taken or released time is made up or completed by the employee within a reasonable time. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Paid on commission or piecework basis.</E>
                                 No contribution results where an employee engages in political activity during what would otherwise be normal working hours if the employee is paid on a commission or piecework basis, or is paid only for work actually performed and the employee's time is considered his or her own to use as he or she sees fit. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Vacation or earned leave time.</E>
                                 No contribution results where the time used by the employee to engage in political activity is bona fide, although compensable, vacation time or other earned leave time. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.55 </SECTNO>
                            <SUBJECT>Extension of credit. </SUBJECT>
                            <P>The extension of credit by any person is a contribution unless the credit is extended in the ordinary course of the person's business and the terms are substantially similar to extensions of credit to nonpolitical debtors that are of similar risk and size of obligation. If a creditor fails to make a commercially reasonable attempt to collect the debt, a contribution will result. (See 11 CFR 116.3 and 116.4.) If a debt owed by a political committee is forgiven or settled for less than the amount owed, a contribution results unless such debt is settled in accordance with the standards set forth at 11 CFR 116.3 and 116.4. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.56 </SECTNO>
                            <SUBJECT>Office building or facility for national party committees. </SUBJECT>
                            <P>A gift, subscription, loan, advance, or deposit of money or anything of value to a national party committee for the purchase or construction of an office building or facility is a contribution. </P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart C—Exceptions to Contributions </HD>
                        <SECTION>
                            <SECTNO>§ 100.71 </SECTNO>
                            <SUBJECT>Scope. </SUBJECT>
                            <P>
                                (a) The term 
                                <E T="03">contribution</E>
                                 does not include payments, services or other things of value described in this subpart. 
                            </P>
                            <P>(b) For the purpose of this subpart, a contribution or payment made by an individual shall not be attributed to any other individual, unless otherwise specified by that other individual in accordance with 11 CFR 110.1(k). </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.72 </SECTNO>
                            <SUBJECT>Testing the waters. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General exemption.</E>
                                 Funds received solely for the purpose of determining whether an individual should become a candidate are not contributions. Examples of activities permissible under this exemption if they are conducted to determine whether an individual should become a candidate include, but are not limited to, conducting a poll, telephone calls, and travel. Only funds permissible under the Act may be used for such activities. The individual shall keep records of all such funds received. See 11 CFR 101.3. If the individual subsequently becomes a candidate, the funds received are contributions subject to the reporting requirements of the Act. Such contributions must be reported with the first report filed by the principal campaign committee of the candidate, regardless of the date the funds were received. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Exemption not applicable to individuals who have decided to become candidates.</E>
                                 This exemption does not apply to funds received for activities indicating that an individual has decided to become a candidate for a particular office or for activities relevant to conducting a campaign. Examples of activities that indicate that an individual has decided to become a candidate include, but are not limited to: 
                            </P>
                            <P>(1) The individual uses general public political advertising to publicize his or her intention to campaign for Federal office. </P>
                            <P>
                                (2) The individual raises funds in excess of what could reasonably be expected to be used for exploratory 
                                <PRTPAGE P="40885"/>
                                activities or undertakes activities designed to amass campaign funds that would be spent after he or she becomes a candidate. 
                            </P>
                            <P>(3) The individual makes or authorizes written or oral statements that refer to him or her as a candidate for a particular office. </P>
                            <P>(4) The individual conducts activities in close proximity to the election or over a protracted period of time. </P>
                            <P>(5) The individual has taken action to qualify for the ballot under State law. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.73 </SECTNO>
                            <SUBJECT>News story, commentary, or editorial by the media. </SUBJECT>
                            <P>Any cost incurred in covering or carrying a news story, commentary, or editorial by any broadcasting station (including a cable television operator, programmer or producer), newspaper, magazine, or other periodical publication is not a contribution unless the facility is owned or controlled by any political party, political committee, or candidate, in which case the costs for a news story: </P>
                            <P>
                                (a) That represents a 
                                <E T="03">bona fide</E>
                                 news account communicated in a publication of general circulation or on a licensed broadcasting facility; and 
                            </P>
                            <P>(b) That is part of a general pattern of campaign-related news accounts that give reasonably equal coverage to all opposing candidates in the circulation or listening area, is not a contribution. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.74 </SECTNO>
                            <SUBJECT>Uncompensated services by volunteers. </SUBJECT>
                            <P>The value of services provided without compensation by any individual who volunteers on behalf of a candidate or political committee is not a contribution. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.75 </SECTNO>
                            <SUBJECT>Use of a volunteer's real or personal property. </SUBJECT>
                            <P>No contribution results where an individual, in the course of volunteering personal services on his or her residential premises to any candidate or to any political committee of a political party, provides the use of his or her real or personal property to such candidate for candidate-related activity or to such political committee of a political party for party-related activity. For the purposes of this section, an individual's residential premises, shall include a recreation room in a residential complex where the individual volunteering services resides, provided that the room is available for use without regard to political affiliation. A nominal fee paid by such individual for the use of such room is not a contribution. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.76 </SECTNO>
                            <SUBJECT>Use of church or community room. </SUBJECT>
                            <P>No contribution results where an individual, in the course of volunteering personal services to any candidate or political committee of a political party, obtains the use of a church or community room and provides such room to any candidate for candidate-related activity or to any political committee of a political party for party-related activity, provided that the room is used on a regular basis by members of the community for noncommercial purposes and the room is available for use by members of the community without regard to political affiliation. A nominal fee paid by such individual for the use of such room is not a contribution. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.77 </SECTNO>
                            <SUBJECT>Invitations, food, and beverages. </SUBJECT>
                            <P>The cost of invitations, food and beverages is not a contribution where such items are voluntarily provided by an individual volunteering personal services on the individual's residential premises or in a church or community room as specified at 11 CFR 100.65 and 100.66 to a candidate for candidate-related activity or to any political committee of a political party for party-related activity, to the extent that: The aggregate value of such invitations, food and beverages provided by the individual on behalf of the candidate does not exceed $1,000 with respect to any single election; and on behalf of all political committees of each political party does not exceed $2,000 in any calendar year. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.78 </SECTNO>
                            <SUBJECT>Sale of food or beverages by vendor. </SUBJECT>
                            <P>The sale of any food or beverage by a vendor (whether incorporated or not) for use in a candidate's campaign, or for use by a political committee of a political party, at a charge less than the normal or comparable commercial rate, is not a contribution, provided that the charge is at least equal to the cost of such food or beverage to the vendor, to the extent that: The aggregate value of such discount given by the vendor on behalf of any single candidate does not exceed $1,000 with respect to any single election; and on behalf of all political committees of each political party does not exceed $2,000 in a calendar year. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.79 </SECTNO>
                            <SUBJECT>Unreimbursed payment for transportation and subsistence expenses. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Transportation expenses.</E>
                                 Any unreimbursed payment for transportation expenses incurred by any individual on behalf of any candidate or any political committee of a political party is not a contribution to the extent that: 
                            </P>
                            <P>(1) The aggregate value of the payments made by such individual on behalf of a candidate does not exceed $1,000 with respect to a single election; and </P>
                            <P>(2) The aggregate value of the payments made by such individual on behalf of all political committees of each political party does not exceed $2,000 in a calendar year. </P>
                            <P>
                                (b) 
                                <E T="03">Subsistence expenses.</E>
                                 Any unreimbursed payment from a volunteer's personal funds for usual and normal subsistence expenses incidental to volunteer activity is not a contribution. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.80 </SECTNO>
                            <SUBJECT>Slate cards and sample ballots. </SUBJECT>
                            <P>The payment by a State or local committee of a political party of the costs of preparation, display, or mailing or other distribution incurred by such committee with respect to a printed slate card, sample ballot, palm card, or other printed listing(s) of three or more candidates for any public office for which an election is held in the State in which the committee is organized is not a contribution. The payment of the portion of such costs allocable to Federal candidates must be made from funds subject to the limitations and prohibitions of the Act. If made by a political committee, such payments shall be reported by that committee as disbursements, but need not be allocated in committee reports to specific candidates. This exemption shall not apply to costs incurred by such a committee with respect to the preparation and display of listings made on broadcasting stations, or in newspapers, magazines, and similar types of general public political advertising such as billboards. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.81 </SECTNO>
                            <SUBJECT>Payments by corporations and labor organizations. </SUBJECT>
                            <P>Any payment made or obligation incurred by a corporation or a labor organization is not a contribution, if under the provisions of 11 CFR part 114 such payment or obligation would not constitute an expenditure by the corporation or labor organization. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.82 </SECTNO>
                            <SUBJECT>Bank loans. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General provisions.</E>
                                 A loan of money to a political committee or a candidate by a State bank, a federally chartered depository institution (including a national bank) or a depository institution whose deposits and accounts are insured by the Federal Deposit Insurance Corporation or the National Credit Union Administration is not a contribution by the lending 
                                <PRTPAGE P="40886"/>
                                institution if such loan is made in accordance with applicable banking laws and regulations and is made in the ordinary course of business. A loan will be deemed to be made in the ordinary course of business if it: 
                            </P>
                            <P>(1) Bears the usual and customary interest rate of the lending institution for the category of loan involved; </P>
                            <P>(2) Is made on a basis that assures repayment; </P>
                            <P>(3) Is evidenced by a written instrument; and </P>
                            <P>(4) Is subject to a due date or amortization schedule. </P>
                            <P>
                                (b) 
                                <E T="03">Reporting.</E>
                                 Such loans shall be reported by the political committee in accordance with 11 CFR 104.3(a) and (d). 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Endorsers and guarantors.</E>
                                 Each endorser or guarantor shall be deemed to have contributed that portion of the total amount of the loan for which he or she agreed to be liable in a written agreement, except that, in the event of a signature by the candidate's spouse, the provisions of 11 CFR 100.52(b)(4) shall apply. Any reduction in the unpaid balance of the loan shall reduce proportionately the amount endorsed or guaranteed by each endorser or guarantor in such written agreement. In the event that such agreement does not stipulate the portion of the loan for which each endorser or guarantor is liable, the loan shall be considered a contribution by each endorser or guarantor in the same proportion to the unpaid balance that each endorser or guarantor bears to the total number of endorsers or guarantors. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Overdrafts.</E>
                                 For purposes of this section, an overdraft made on a checking or savings account of a political committee shall be considered a contribution by the bank or institution unless: 
                            </P>
                            <P>(1)The overdraft is made on an account that is subject to automatic overdraft protection; </P>
                            <P>(2)The overdraft is subject to a definite interest rate that is usual and customary; and </P>
                            <P>(3)There is a definite repayment schedule. </P>
                            <P>
                                (e) 
                                <E T="03">Made on a basis that assures repayment.</E>
                                 A loan, including a line of credit, shall be considered made on a basis that assures repayment if it is obtained using either of the sources of repayment described in paragraphs (e)(1) or (2) of this section, or a combination of paragraphs (e)(1) and (2) of this section: 
                            </P>
                            <P>(1)(i) The lending institution making the loan has perfected a security interest in collateral owned by the candidate or political committee receiving the loan, the fair market value of the collateral is equal to or greater than the loan amount and any senior liens as determined on the date of the loan, and the candidate or political committee provides documentation to show that the lending institution has a perfected security interest in the collateral. Sources of collateral include, but are not limited to, ownership in real estate, personal property, goods, negotiable instruments, certificates of deposit, chattel papers, stocks, accounts receivable and cash on deposit. </P>
                            <P>(ii) Amounts guaranteed by secondary sources of repayment, such as guarantors and cosigners, shall not exceed the contribution limits of 11 CFR part 110 or contravene the prohibitions of 11 CFR 110.4, part 114 and part 115; or </P>
                            <P>(2) The lending institution making the loan has obtained a written agreement whereby the candidate or political committee receiving the loan has pledged future receipts, such as public financing payments under 11 CFR part 9001 through part 9012 or part 9031 through part 9039 contributions, or interest income, provided that: </P>
                            <P>(i) The amount of the loan or loans obtained on the basis of such funds does not exceed the amount of pledged funds; </P>
                            <P>(ii) Loan amounts are based on a reasonable expectation of the receipt of pledged funds. To that end, the candidate or political committee must furnish the lending institution documentation, i.e., cash flow charts or other financial plans, that reasonably establish that such future funds will be available; </P>
                            <P>(iii) A separate depository account is established at the lending institution or the lender obtains an assignment from the candidate or political committee to access funds in a committee account at another depository institution that meets the requirements of 11 CFR 103.2, and the committee has notified the other institution of this assignment; </P>
                            <P>(iv) The loan agreement requires the deposit of the public financing payments, contributions and interest income pledged as collateral into the separate depository account for the purpose of retiring the debt according to the repayment requirements of the loan agreement; and </P>
                            <P>(v) In the case of public financing payments, the borrower authorizes the Secretary of the Treasury to directly deposit the payments into the depository account for the purpose of retiring the debt. </P>
                            <P>(3) If the requirements set forth in this paragraph are not met, the Commission will consider the totality of the circumstances on a case-by-case basis in determining whether a loan was made on a basis that assures repayment. </P>
                            <P>(f) This section shall not apply to loans described in 11 CFR 100.73. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.83</SECTNO>
                            <SUBJECT>Brokerage loans and lines of credit to candidates. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General provisions.</E>
                                 Any loan of money derived from an advance on a candidate's brokerage account, credit card, home equity line of credit, or other line of credit available to the candidate, including an overdraft made on a personal checking or savings account of a candidate, provided that: 
                            </P>
                            <P>(1) Such loan is made in accordance with applicable law and under commercially reasonable terms; and </P>
                            <P>(2) The person making such loan makes loans derived from an advance on a candidate's brokerage account, credit card, home equity line of credit, or other line of credit in the normal course of the person's business. </P>
                            <P>
                                (b) 
                                <E T="03">Endorsers and guarantors.</E>
                                 Each endorser, guarantor, or co-signer shall be deemed to have contributed that portion of the total amount of the loan derived from an advance on a candidate's brokerage account, credit card, home equity line of credit, or other line of credit available to the candidate, for which he or she agreed to be liable in a written agreement, including a loan used for the candidate's routine living expenses. Any reduction in the unpaid balance of the loan, advance, or line of credit shall reduce proportionately the amount endorsed or guaranteed by each endorser or guarantor in such written agreement. In the event that such agreement does not stipulate the portion of the loan, advance, or line of credit for which each endorser, guarantor, or co-signer is liable, the loan shall be considered a contribution by each endorser or guarantor in the same proportion to the unpaid balance that each endorser, guarantor, or co-signer bears to the total number of endorsers or guarantors. However, if the spouse of the candidate is the endorser, guarantor, or co-signer, the spouse shall not be deemed to make a contribution if: 
                            </P>
                            <P>(1) For a secured loan, the value of the candidate's share of the property used as collateral equals or exceeds the amount of the loan that is used for the candidate's campaign; or </P>
                            <P>(2) For an unsecured loan, the amount of the loan used for in connection with the candidate's campaign does not exceed one-half of the available credit extended by the unsecured loan. </P>
                            <P>
                                (c) 
                                <E T="03">Routine living expenses.</E>
                                 (1) A loan derived from an advance on a candidate's brokerage account, credit card, home equity line of credit, or other line of credit available to the candidate, 
                                <PRTPAGE P="40887"/>
                                that is used by the candidate solely for routine living expenses, as described in 11 CFR 100.153, does not need to be reported under 11 CFR part 104 provided that the loan, advance, or line of credit is repaid exclusively from the personal funds of the candidate or payments that would have been made irrespective of the candidacy pursuant to 11 CFR 113.1(g)(6). 
                            </P>
                            <P>(2) Any repayment, in part or in whole, of the loan, advance, or line of credit described in paragraph (c)(1) of this section by the candidate's authorized committee constitutes the personal use of campaign funds and is prohibited by 11 CFR 113.2. </P>
                            <P>(3) Any repayment or forgiveness, in part or in whole, of the loan, advance, or line of credit described in paragraph (c)(1) of this section by a third party (other than a third party whose payments are permissible under 11 CFR 113.1(g)(6)) or the lending institution is a contribution, subject to the limitations and prohibitions of 11 CFR parts 110 and 114, and shall be reported under 11 CFR part 104. </P>
                            <P>(4) Notwithstanding paragraph (c)(1) of this section, the portion of any loan or advance from a candidate's brokerage account, credit card account, home equity line of credit, or other line of credit that is used for the purpose of influencing the candidate's election for Federal office shall be reported under 11 CFR part 104. </P>
                            <P>
                                (d) 
                                <E T="03">Repayment.</E>
                                 The candidate's authorized committee may repay a loan from the candidate that is derived from an advance on a candidate's brokerage account, credit card, home equity line of credit, or other line of credit available to the candidate, directly to the candidate or the original lender. The amount of the repayment shall not exceed the amount of the principal used for the purpose of influencing the candidate's election for Federal office and interest that has accrued on that principal. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Reporting.</E>
                                 Loans derived from an advance on a candidate's brokerage account, credit card, home equity line of credit, or other line of credit available to the candidate shall be reported by the candidate's principal campaign committee in accordance with 11 CFR part 104. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.84</SECTNO>
                            <SUBJECT>Office building for State, local, or district party committees or organizations. </SUBJECT>
                            <P>A donation made to a non-Federal account of a State, local, or district party committee or organization in accordance with 11 CFR 300.35 for the purchase or construction of an office building is not a contribution. A donation includes a gift, subscription, loan, advance, or deposit of money or anything of value. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.85</SECTNO>
                            <SUBJECT>Legal or accounting services to political party committees. </SUBJECT>
                            <P>Legal or accounting services rendered to or on behalf of any political committee of a political party are not contributions if the person paying for such services is the regular employer of the individual rendering the services and such services are not attributable to activities that directly further the election of any designated candidate for Federal office. For purposes of this section, a partnership shall be deemed to be the regular employer of a partner. Amounts paid by the regular employer for such services shall be reported by the committee receiving such services in accordance with 11 CFR 104.3(h). </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.86</SECTNO>
                            <SUBJECT>Legal or accounting services to other political committees. </SUBJECT>
                            <P>
                                Legal or accounting services rendered to or on behalf of an authorized committee of a candidate or any other political committee are not contributions if the person paying for such services is the regular employer of the individual rendering the services and if such services are solely to ensure compliance with the Act or 26 U.S.C. 9001 
                                <E T="03">et seq.</E>
                                 and 9031 
                                <E T="03">et seq.</E>
                                 For purposes of this section, a partnership shall be deemed to be the regular employer of a partner. Amounts paid by the regular employer for these services shall be reported by the committee receiving such services in accordance with 11 CFR 104.3(h). 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.87</SECTNO>
                            <SUBJECT>Volunteer activity for party committees. </SUBJECT>
                            <P>The payment by a state or local committee of a political party of the costs of campaign materials (such as pins, bumper stickers, handbills, brochures, posters, party tabloids or newsletters, and yard signs) used by such committee in connection with volunteer activities on behalf of any nominee(s) of such party is not a contribution, provided that the following conditions are met: </P>
                            <P>
                                (a) 
                                <E T="03">Exemption not applicable to general public communication or political advertising.</E>
                                 Such payment is not for cost incurred in connection with any broadcasting, newspaper, magazine, bill board, direct mail, or similar type of general public communication or political advertising. For purposes of this paragraph, the term 
                                <E T="03">direct mail</E>
                                 means any mailing(s) by a commercial vendor or any mailing(s) made from commercial lists. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Allocation.</E>
                                 The portion of the cost of such materials allocable to Federal candidates must be paid from contributions subject to the limitations and prohibitions of the Act. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Contributions designated for particular Federal candidates.</E>
                                 Such payment is not made from contributions designated by the donor to be spent on behalf of a particular candidate or candidates for Federal office. For purposes of this paragraph, a contribution shall not be considered a designated contribution if the party committee disbursing the funds makes the final decision regarding which candidate(s) shall receive the benefit of such disbursement. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Distribution of materials by volunteers.</E>
                                 Such materials are distributed by volunteers and not by commercial or for-profit operations. For the purposes of this paragraph, payments by the party organization for travel and subsistence or customary token payments to volunteers do not remove such individuals from the volunteer category. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Reporting.</E>
                                 If made by a political committee such payments shall be reported by the political committee as disbursements in accordance with 11 CFR 104.3 but need not be allocated to specific candidates in committee reports. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">State candidates and their campaign committees.</E>
                                 Payments by a State candidate or his or her campaign committee to a State or local political party committee for the State candidate's share of expenses for such campaign materials are not contributions, provided the amount paid by the State candidate or his or her committee does not exceed his or her proportionate share of the expenses. 
                            </P>
                            <P>
                                (g) 
                                <E T="03">Exemption not applicable to campaign materials purchased by national party committees.</E>
                                 Campaign materials purchased by the national committee of a political party and delivered to a State or local party committee, or materials purchased with funds donated by the national committee to such State or local committee for the purchase of such materials, shall not qualify under this exemption. Rather, the cost of such materials shall be subject to the limitations of 2 U.S.C. 441a(d) and 11 CFR 110.7. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.88</SECTNO>
                            <SUBJECT>Volunteer activity for candidates. </SUBJECT>
                            <P>
                                (a) The payment by a candidate for any public office (including State or local office), or by such candidate's authorized committee, of the costs of that candidate's campaign materials that include information on or any reference to a candidate for Federal office and that are used in connection with volunteer activities (such as pins, bumper stickers, 
                                <PRTPAGE P="40888"/>
                                handbills, brochures, posters, and yard signs) is not a contribution to such candidate for Federal office, provided that the payment is not for the use of broadcasting, newspapers, magazines, billboards, direct mail or similar types of general public communication or political advertising. 
                            </P>
                            <P>
                                (b) The payment of the portion of the cost of such materials allocable to Federal candidates shall be made from contributions subject to the limitations and prohibitions of the Act. For purposes of this section, the term 
                                <E T="03">direct mail</E>
                                 means any mailing(s) by commercial vendors or mailing(s) made from lists that were not developed by the candidate. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.89</SECTNO>
                            <SUBJECT>Voter registration and get-out-the-vote activities for Presidential candidates (“coattails” exception). </SUBJECT>
                            <P>The payment by a State or local committee of a political party of the costs of voter registration and get-out-the-vote activities conducted by such committee on behalf of the Presidential and Vice Presidential nominee(s) of that party, is not a contribution to such candidate(s) provided that the following conditions are met: </P>
                            <P>
                                (a) 
                                <E T="03">Exemption not applicable to general public communication or political advertising.</E>
                                 Such payment is not for the costs incurred in connection with any broadcasting, newspaper, magazine, billboard, direct mail, or similar type of general public communication or political advertising. For purposes of this paragraph, the term 
                                <E T="03">direct mail</E>
                                 means any mailing(s) by a commercial vendor or any mailing(s) made from commercial lists. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Allocation.</E>
                                 The portion of the costs of such activities allocable to Federal candidates is paid from contributions subject to the limitations and prohibitions of the Act. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Contributions designated for particular Federal candidates.</E>
                                 Such payment is not made from contributions designated to be spent on behalf of a particular candidate or candidates for Federal office. For purposes of this paragraph, a contribution shall not be considered a designated contribution if the party committee disbursing the funds makes the final decision regarding which candidate(s) shall receive the benefit of such disbursement. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">References to House or Senate candidates.</E>
                                 For purposes of this section, if such activities include references to any candidate(s) for the House or Senate, the costs of such activities that are allocable to that candidate(s) shall be a contribution to such candidate(s) unless the mention of such candidate(s) is merely incidental to the overall activity. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Phone banks.</E>
                                 For purposes of this section, payment of the costs incurred in the use of phone banks in connection with voter registration and get-out-the-vote activities is not a contribution when such phone banks are operated by volunteer workers. The use of paid professionals to design the phone bank system, develop calling instructions and train supervisors is permissible. The payment of the costs of such professional services is not an expenditure but shall be reported as a disbursement in accordance with 11 CFR 104.3 if made by a political committee. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">Reporting of payments for voter registration and get-out-the-vote activities.</E>
                                 If made by a political committee, such payments for voter registration and get-out-the-vote activities shall be reported by that committee as disbursements in accordance with 11 CFR 104.3, but such payments need not be allocated to specific candidates in committee reports except as provided in 11 CFR 100.78(d). 
                            </P>
                            <P>
                                (g) 
                                <E T="03">Exemption not applicable to donations by a national committee of a political party to a State or local party committee for voter registration and get-out-the-vote activities.</E>
                                 Payments made from funds donated by a national committee of a political party to a State or local party committee for voter registration and get-out-the-vote activities shall not qualify under this exemption. Rather, such funds shall be subject to the limitations of 2 U.S.C. 441a(d) and 11 CFR 110.7. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.90</SECTNO>
                            <SUBJECT>Ballot access fees. </SUBJECT>
                            <P>Payments made to any party committee by a candidate or the authorized committee of a candidate as a condition of ballot access are not contributions. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.91</SECTNO>
                            <SUBJECT>Recounts. </SUBJECT>
                            <P>A gift, subscription, loan, advance, or deposit of money or anything of value made with respect to a recount of the results of a Federal election, or an election contest concerning a Federal election, is not a contribution except that the prohibitions of 11 CFR 110.4(a) and part 114 apply. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.92</SECTNO>
                            <SUBJECT>Candidate debates. </SUBJECT>
                            <P>Funds provided to defray costs incurred in staging candidate debates in accordance with the provisions of 11 CFR 110.13 and 114.4(f) are not contributions. </P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart D—Definition of Expenditure (2 U.S.C. 431(9)) </HD>
                        <SECTION>
                            <SECTNO>§ 100.110 </SECTNO>
                            <SUBJECT>Scope. </SUBJECT>
                            <P>
                                (a) The term 
                                <E T="03">expenditure</E>
                                 includes payments, gifts or other things of value described in this subpart. 
                            </P>
                            <P>(b) For the purpose of this subpart, a payment made by an individual shall not be attributed to any other individual, unless otherwise specified by that other individual. To the extent that a payment made by an individual qualifies as a contribution, the provisions of 11 CFR 110.1(k) shall apply. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.111 </SECTNO>
                            <SUBJECT>Gift, subscription, loan, advance or deposit of money. </SUBJECT>
                            <P>(a) A purchase, payment, distribution, loan (except for a loan made in accordance with 11 CFR 100.113 and 100.114), advance, deposit, or gift of money or anything of value, made by any person for the purpose of influencing any election for Federal office is an expenditure. </P>
                            <P>
                                (b) For purposes of this section, the term 
                                <E T="03">payment</E>
                                 includes payment of any interest on an obligation and any guarantee or endorsement of a loan by a candidate or a political committee. 
                            </P>
                            <P>
                                (c) For purposes of this section, the term 
                                <E T="03">payment</E>
                                 does not include the repayment by a political committee of the principal of an outstanding obligation that is owed by such committee, except that the repayment shall be reported as disbursements in accordance with 11 CFR 104.3(b). 
                            </P>
                            <P>
                                (d) For purposes of this section, the term 
                                <E T="03">money</E>
                                 includes currency of the United States or of any foreign nation, checks, money orders, or any other negotiable instrument payable on demand. 
                            </P>
                            <P>
                                (e)(1) For purposes of this section, the term 
                                <E T="03">anything of value</E>
                                 includes all in-kind contributions. Unless specifically exempted under 11 CFR part 100, subpart E, the provision of any goods or services without charge or at a charge that is less than the usual and normal charge for the goods or services is an expenditure. Examples of such goods or services include, but are not limited to: Securities, facilities, equipment, supplies, personnel, advertising services, membership lists, and mailing lists. If goods or services are provided at less than the usual and normal charge, the amount of the expenditure is the difference between the usual and normal charge for the goods or services at the time of the expenditure and the amount charged the candidate or political committee. 
                            </P>
                            <P>
                                (2) For the purposes of paragraph (e)(1) of this section, 
                                <E T="03">
                                    usual and normal 
                                    <PRTPAGE P="40889"/>
                                    charge for goods
                                </E>
                                 means the price of those goods in the market from which they ordinarily would have been purchased at the time of the expenditure; and usual and normal charge for services, other than those provided by an unpaid volunteer, means the hourly or piecework charge for the services at a commercially reasonable rate prevailing at the time the services were rendered. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.112 </SECTNO>
                            <SUBJECT>Contracts, promises, and agreements to make expenditures. </SUBJECT>
                            <P>A written contract, including a media contract, promise, or agreement to make an expenditure is an expenditure as of the date such contract, promise or obligation is made. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.113 </SECTNO>
                            <SUBJECT>Independent expenditures. </SUBJECT>
                            <P>An independent expenditure that meets the requirements of 11 CFR 104.4 or part 109 is an expenditure, and such independent expenditure is to be reported by the person making the expenditure in accordance with 11 CFR 104.4 and part 109. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.114 </SECTNO>
                            <SUBJECT>Office building or facility for national party committees. </SUBJECT>
                            <P>A payment, distribution, loan, advance, or deposit of money or anything of value made by, or on behalf of, a national party committee for the purchase or construction of an office building or facility is an expenditure. </P>
                        </SECTION>
                    </SUBPART>
                    <SUBPART>
                        <HD SOURCE="HED">Subpart E—Exceptions to Expenditures </HD>
                        <SECTION>
                            <SECTNO>§ 100.130 </SECTNO>
                            <SUBJECT>Scope </SUBJECT>
                            <P>
                                (a) The term 
                                <E T="03">expenditure</E>
                                 does not include payments, gifts, or other things of value described in this subpart. 
                            </P>
                            <P>(b) For the purpose of this subpart, a payment made by an individual shall not be attributed to any other individual, unless otherwise specified by that other individual. To the extent that a payment made by an individual qualifies as a contribution, the provisions of 11 CFR 110.1(k) shall apply. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.131 </SECTNO>
                            <SUBJECT>Testing the waters. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General exemption.</E>
                                 Payments made solely for the purpose of determining whether an individual should become a candidate are not expenditures. Examples of activities permissible under this exemption if they are conducted to determine whether an individual should become a candidate include, but are not limited to, conducting a poll, telephone calls, and travel. Only funds permissible under the Act may be used for such activities. The individual shall keep records of all such payments. 
                                <E T="03">See</E>
                                 11 CFR 101.3. If the individual subsequently becomes a candidate, the payments made are subject to the reporting requirements of the Act. Such expenditures must be reported with the first report filed by the principal campaign committee of the candidate, regardless of the date the payments were made. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Exemption not applicable to individuals who have decided to become candidates.</E>
                                 This exemption does not apply to payments made for activities indicating that an individual has decided to become a candidate for a particular office or for activities relevant to conducting a campaign. Examples of activities that indicate that an individual has decided to become a candidate include, but are not limited to: 
                            </P>
                            <P>(1) The individual uses general public political advertising to publicize his or her intention to campaign for Federal office. </P>
                            <P>(2) The individual raises funds in excess of what could reasonably be expected to be used for exploratory activities or undertakes activities designed to amass campaign funds that would be spent after he or she becomes a candidate. </P>
                            <P>(3) The individual makes or authorizes written or oral statements that refer to him or her as a candidate for a particular office. </P>
                            <P>(4) The individual conducts activities in close proximity to the election or over a protracted period of time. </P>
                            <P>(5) The individual has taken action to qualify for the ballot under State law. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.132 </SECTNO>
                            <SUBJECT>Newsstory, commentary, or editorial by the media. </SUBJECT>
                            <P>Any cost incurred in covering or carrying a new story, commentary, or editorial by any broadcasting station (including a cable television operator, programmer or producer), newspaper, magazine, or other periodical publication is not an expenditure unless the facility is owned or controlled by any political party, political committee, or candidate, in which case the costs for a news story: </P>
                            <P>
                                (a) That represents a 
                                <E T="03">bona fide</E>
                                 news account communicated in a publication of general circulation or on a licensed broadcasting facility; and 
                            </P>
                            <P>(b) That is part of a general pattern of campaign-related news account that give reasonably equal coverage to all opposing candidates in the circulation or listening area, is not an expenditure. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.133 </SECTNO>
                            <SUBJECT>Voter registration and get-out-the-vote activities. </SUBJECT>
                            <P>
                                Any cost incurred for activity designed to encourage individuals to register to vote or to vote is not an expenditure if no effort is or has been made to determine the party or candidate preference of individuals before encouraging them to register to vote or to vote, except that corporations and labor organizations shall engage in such activity in accordance with 11 CFR 114.4 (c) and (d). 
                                <E T="03">See also</E>
                                 11 CFR 114.3(c)(4). 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.134 </SECTNO>
                            <SUBJECT>Internal communications by corporations, labor organizations, and membership organizations. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General provision.</E>
                                 Any cost incurred for any communication by a membership organization, including a labor organization, to its members, or any cost incurred for any communication by a corporation to its stockholders or executive or administrative personnel, is not an expenditure, except that the costs directly attributable to such a communication that expressly advocates the election or defeat of a clearly identified candidate (other than a communication primarily devoted to subjects other than the express advocacy of the election or defeat of a clearly identified candidate) shall, if those costs exceed $2,000 per election, be reported to the Commission on FEC Form 7 in accordance with 11 CFR 104.6. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Definition of labor organization.</E>
                                 For purposes of this section, 
                                <E T="03">labor organization</E>
                                 means an organization of any kind (any local, national, or international union, or any local or State central body of a federation of unions is each considered a separate labor organization for purposes of this section) or any agency or employee representative committee or plan, in which employees participate and that exists for the purpose, in whole or in part, of dealing with employers concerning grievances, labor disputes, wages, rates of pay, hours of employment, or conditions of work. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Definition of stockholder.</E>
                                 For purposes of this section, 
                                <E T="03">stockholder</E>
                                 means a person who has a vested beneficial interest in stock, has the power to direct how that stock shall be voted, if it is voting stock, and has the right to receive dividends. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Definition of executive or administrative personnel.</E>
                                 For purposes of this section, 
                                <E T="03">executive or administrative personnel</E>
                                 means individuals employed by a corporation who are paid on a salary rather than hourly basis and who have policymaking, managerial, professional, or supervisory responsibilities. 
                            </P>
                            <P>(1) This definition includes— </P>
                            <P>
                                (i) Individuals who run the corporation's business, such as officers, 
                                <PRTPAGE P="40890"/>
                                other executives, and plant, division, and section managers; and 
                            </P>
                            <P>(ii) Individuals following the recognized professions, such as lawyers and engineers. </P>
                            <P>(2) This definition does not include— </P>
                            <P>(i) Professionals who are represented by a labor organization; </P>
                            <P>(ii) Salaried foremen and other salaried lower level supervisors having direct supervision over hourly employees; </P>
                            <P>(iii) Former or retired personnel who are not stockholders; or </P>
                            <P>(iv) Individuals who may be paid by the corporation, such as consultants, but who are not employees, within the meaning of 26 CFR 31.3401(c)-(1), of the corporation for the purpose of the collection of, and liability for, employee tax under 26 CFR 1.3402(a)-(1). </P>
                            <P>(3) Individuals on commission may be considered executive or administrative personnel if they have policymaking, managerial, professional, or supervisory responsibility and if the individuals are employees, within the meaning of 26 CFR 31.3401(c)-(1), of the corporation for the purpose of the collection of, and liability for, employee tax under 26 CFR 31.3402(a)-(1). </P>
                            <P>
                                (4) The Fair Labor Standards Act, 29 U.S.C. 201, 
                                <E T="03">et seq.</E>
                                 and the regulations issued pursuant to such Act, 29 CFR part 541, may serve as a guideline in determining whether individuals have policymaking, managerial, professional, or supervisory responsibilities. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Definition of membership organization.</E>
                                 For purposes of this section 
                                <E T="03">membership organization</E>
                                 means an unincorporated association, trade association, cooperative, corporation without capital stock, or a local, national, or international labor organization that: 
                            </P>
                            <P>(1) Is composed of members, some or all of whom are vested with the power and authority to operate or administer the organization, pursuant to the organization's articles, bylaws, constitution or other formal organizational documents; </P>
                            <P>(2) Expressly states the qualifications and requirements for membership in its articles, bylaws, constitution or other formal organizational documents; </P>
                            <P>(3) Makes its articles, bylaws, constitution or other formal organizational documents available to its members; </P>
                            <P>(4) Expressly solicits persons to become members; </P>
                            <P>(5) Expressly acknowledges the acceptance of membership, such as by sending a membership card or including the member's name on a membership newsletter list; and </P>
                            <P>(6) Is not organized primarily for the purpose of influencing the nomination for election, or election, of any individual for Federal office. </P>
                            <P>
                                (f) 
                                <E T="03">Definition of members.</E>
                                 For purposes of this section, the term 
                                <E T="03">members</E>
                                 includes all persons who are currently satisfying the requirements for membership in a membership organization, affirmatively accept the membership organization's invitation to become a member, and either: 
                            </P>
                            <P>(1) Have some significant financial attachment to the membership organization, such as a significant investment or ownership stake; or </P>
                            <P>(2) Pay membership dues at least annually, of a specific amount predetermined by the organization; or </P>
                            <P>(3) Have a significant organizational attachment to the membership organization that includes: Affirmation of membership on at least an annual basis and direct participatory rights in the governance of the organization. For example, such rights could include the right to vote directly or indirectly for at least one individual on the membership organization's highest governing board; the right to vote on policy questions where the highest governing body of the membership organization is obligated to abide by the results; the right to approve the organization's annual budget; or the right to participate directly in similar aspects of the organization's governance. </P>
                            <P>
                                (g) 
                                <E T="03">Additional considerations in determining membership.</E>
                                 Notwithstanding the requirements of paragraph (f) of this section, the Commission may determine, on a case-by-case basis, that persons who do not precisely meet the requirements of the general rule, but have a relatively enduring and independently significant financial or organizational attachment to the organization, may be considered members for purposes of this section. For example, student members who pay a lower amount of dues while in school, long term dues paying members who qualify for lifetime membership status with little or no dues obligation, and retired members may be considered members of the organization. 
                            </P>
                            <P>
                                (h) 
                                <E T="03">Members of local unions.</E>
                                 Notwithstanding the requirements of paragraph (f) of this section, members of a local union are considered to be members of any national or international union of which the local union is a part and of any federation with which the local, national, or international union is affiliated. 
                            </P>
                            <P>
                                (i) 
                                <E T="03">National federation structures.</E>
                                 In the case of a membership organization that has a national federation structure or has several levels, including, for example, national, state, regional and/or local affiliates, a person who qualifies as a member of any entity within the federation or of any affiliate by meeting the requirements of paragraphs (f)(1), (2), or (3) of this section shall also qualify as a member of all affiliates for purposes of paragraphs (d) through (h) of this section. The factors set forth at 11 CFR 100.5(g)(2), (3) and (4) shall be used to determine whether entities are affiliated for purposes of this paragraph. 
                            </P>
                            <P>
                                (j) 
                                <E T="03">Non-applicability of state law in determining status of membership organizations.</E>
                                 The status of a membership organization, and of members, for purposes of this section, shall be determined pursuant to paragraphs (d) through (i) of this section and not by provisions of state law governing unincorporated associations, trade associations, cooperatives, corporations without capital stock, or labor organizations. 
                            </P>
                            <P>
                                (k) 
                                <E T="03">Definition of election.</E>
                                 For purposes of this section, 
                                <E T="03">election</E>
                                 means two separate processes in a calendar year, to each of which the $2,000 threshold described above applies separately. The first process is comprised of all primary elections for Federal office, whenever and wherever held; the second process is comprised of all general elections for Federal office, whenever and wherever held. The term election shall also include each special election held to fill a vacancy in a Federal office (11 CFR 100.2(f)) or each runoff election (11 CFR 100.2(d)). 
                            </P>
                            <P>
                                (l) 
                                <E T="03">Definition of corporation.</E>
                                 For purposes of this section, 
                                <E T="03">corporation</E>
                                 means any separately incorporated entity, whether or not affiliated. 
                            </P>
                            <P>
                                (m) 
                                <E T="03">Reporting.</E>
                                 When the aggregate costs under this section exceed $2,000 per election, all costs of the communication(s) shall be reported on the filing dates specified in 11 CFR 104.6, and shall include the total amount expended for each candidate supported. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.135 </SECTNO>
                            <SUBJECT>Use of a volunteer's real or personal property. </SUBJECT>
                            <P>
                                No expenditure results where an individual, in the course of volunteering personal services on his or her residential premises to any candidate or political committee of a political party, provides the use of his or her real or personal property to such candidate for candidate-related activity or to such political committee of a political party for party-related activity. For the purposes of this section, an individual's residential premises shall include a recreation room in a residential complex where the individual volunteering services resides, provided that the room 
                                <PRTPAGE P="40891"/>
                                is available for use without regard to political affiliation. A nominal fee paid by such individual for the use of such room is not an expenditure. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.136 </SECTNO>
                            <SUBJECT>Use of a church or a community room. </SUBJECT>
                            <P>No expenditure results where an individual, in the course of volunteering personal services to any candidate or political committee of a political party, obtains the use of a church or community room and provides such room to any candidate for candidate-related activity or to any political committee of a political party for party-related activity, provided that the room is used on a regular basis by members of the community for noncommercial purposes and the room is available for use by members of the community without regard to political affiliation. A nominal fee paid by such individual for the use of such room is not an expenditure. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.137 </SECTNO>
                            <SUBJECT>Invitations, food, and beverages. </SUBJECT>
                            <P>The cost of invitations, food, and beverages is not an expenditure where such items are voluntarily provided by an individual in rendering voluntary personal services on the individual's residential premises or in a church or community room as specified at 11 CFR 100.106 and 100.107 to a candidate for candidate-related activity or to a political committee of a political party for party-related activity, to the extent that: The aggregate value of such invitations, food and beverages provided by the individual on behalf of the candidate does not exceed $1,000 with respect to any single election; and on behalf of all political committees of each political party does not exceed $2,000 in any calendar year. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.138 </SECTNO>
                            <SUBJECT>Sale of food and beverages by vendor. </SUBJECT>
                            <P>The sale of any food or beverage by a vendor (whether incorporated or not) for use in a candidate's campaign, or for use by a political committee of a political party, at a charge less than the normal or comparable commercial charge, is not an expenditure, provided that the charge is at least equal to the cost of such food or beverage to the vendor, to the extent that: The aggregate value of such discount given by the vendor on behalf of any single candidate does not exceed $1,000 with respect to any single election; and on behalf of all political committees of each political party does not exceed $2,000 in a calendar year. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.139 </SECTNO>
                            <SUBJECT>Unreimbursed payment for transportation and subsistence expenses. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Transportation expenses.</E>
                                 Any unreimbursed payment for transportation expenses incurred by any individual on behalf of any candidate or political committee of a political party is not an expenditure to the extent that: 
                            </P>
                            <P>(1) The aggregate value of the payments made by such individual on behalf of a candidate does not exceed $1,000 with respect to a single election; and </P>
                            <P>(2) On behalf of all political committees of each political party does not exceed $2,000 in a calendar year. </P>
                            <P>
                                (b) 
                                <E T="03">Subsistence expenses.</E>
                                 Any unreimbursed payment from a volunteer's personal funds for usual and normal subsistence expenses incident to volunteer activity is not an expenditure. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.140 </SECTNO>
                            <SUBJECT>Slate cards and sample ballots. </SUBJECT>
                            <P>The payment by a State or local committee of a political party of the costs of preparation, display, or mailing or other distribution incurred by such committee with respect to a printed slate card, sample ballot, palm card, or other printed listing(s) of three or more candidates for any public office for which an election is held in the State in which the committee is organized is not an expenditure. The payment of the portion of such costs allocable to Federal candidates must be made from funds subject to the limitations and prohibitions of the Act. If made by a political party committee, such payments shall be reported by that committee as disbursements, but need not be allocated in committee reports to specific candidates. This exemption shall not apply to costs incurred by such a committee with respect to the preparation and display of listings made on broadcasting stations, or in newspapers, magazines, and similar types of general public political advertising such as billboards. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.141 </SECTNO>
                            <SUBJECT>Payment by corporations and labor organizations. </SUBJECT>
                            <P>Any payment made or obligation incurred by a corporation or labor organization is not an expenditure if under the provisions of 11 CFR part 114 such payment or obligation would not constitute an expenditure by the corporation or labor organization. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.142 </SECTNO>
                            <SUBJECT>Bank loans. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General provisions.</E>
                                 Repayment of a loan of money to a candidate or a political committee by a State bank, a federally chartered depository institution (including a national bank) or a depository institution whose deposits and accounts are insured by the Federal Deposit Insurance Corporation or the National Credit Union Administration is not an expenditure by the lending institution if such loan is made in accordance with applicable banking laws and regulations and is made in the ordinary course of business. A loan will be deemed to be made in the ordinary course of business if it: 
                            </P>
                            <P>(1) Bears the usual and customary interest rate of the lending institution for the category of loan involved; </P>
                            <P>(2) Is made on a basis that assures repayment; </P>
                            <P>(3) Is evidenced by a written instrument; and </P>
                            <P>(4) Is subject to a due date or amortization schedule. </P>
                            <P>
                                (b) 
                                <E T="03">Reporting.</E>
                                 Such loans shall be reported by the political committee in accordance with 11 CFR 104.3(a) and (d). 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Endorsers and guarantors.</E>
                                 Each endorser or guarantor shall be deemed to have contributed that portion of the total amount of the loan for which he or she agreed to be liable in a written agreement, except that, in the event of a signature by the candidate's spouse, the provisions of 11 CFR 100.52(b)(4) shall apply. Any reduction in the unpaid balance of the loan shall reduce proportionately the amount endorsed or guaranteed by each endorser or guarantor in such written agreement. In the event that the loan agreement does not stipulate the portion of the loan for which each endorser or guarantor is liable, the loan shall be considered an expenditure by each endorser or guarantor in the same proportion to the unpaid balance that each endorser or guarantor bears to the total number of endorsers or guarantors. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Overdrafts.</E>
                                 For the purpose of this section, repayment of an overdraft made on a checking or savings account of a political committee shall be considered an expenditure unless: 
                            </P>
                            <P>(1) The overdraft is made on an account that is subject to automatic overdraft protection; and </P>
                            <P>(2) The overdraft is subject to a definite interest rate and a definite repayment schedule. </P>
                            <P>
                                (e) 
                                <E T="03">Made on a basis that assures repayment.</E>
                                 A loan, including a line of credit, shall be considered made on a basis that assures repayment if it is obtained using either of the sources of repayment described in paragraphs (e)(1) or (2) of this section, or a combination of paragraphs (e)(1) or (2) of this section: 
                            </P>
                            <P>
                                (1)(i) The lending institution making the loan has perfected a security interest in collateral owned by the candidate or political committee receiving the loan; 
                                <PRTPAGE P="40892"/>
                                the fair market value of the collateral is equal to or greater than the loan amount and any senior liens as determined on the date of the loan; and the candidate or political committee provides documentation to show that the lending institution has a perfected security interest in the collateral. Sources of collateral include, but are not limited to, ownership in real estate, personal property, goods, negotiable instruments, certificates of deposit, chattel papers, stocks, accounts receivable and cash on deposit. 
                            </P>
                            <P>(ii) Amounts guaranteed by secondary sources of repayment, such as guarantors and cosigners, shall not exceed the contribution limits of 11 CFR part 110 or contravene the prohibitions of 11 CFR 110.4, part 114 and part 115; or </P>
                            <P>(2) The lending institution making the loan has obtained a written agreement whereby the candidate or political committee receiving the loan has pledged future receipts, such as public financing payments under 11 CFR part 9001 through part 9012 or part 9031 through part 9039, contributions, or interest income, provided that: </P>
                            <P>(i) The amount of the loan(s) obtained the basis of such funds does not exceed the amount of pledged funds; </P>
                            <P>(ii) Loan amounts are based on a reasonable expectation of the receipt of pledged funds. To that end, the candidate or political committee must furnish the lending institution documentation, i.e., cash flow charts or other financial plans, that reasonably establish that such future funds will be available; </P>
                            <P>(iii) A separate depository account is established at the lending institution or the lender obtains an assignment from the candidate or political committee to access funds in a committee account at another depository institution that meets the requirements of 11 CFR 103.2, and the committee has notified the other institution of this assignment; </P>
                            <P>(iv) The loan agreement requires the deposit of the public financing payments, contributions, interest or other income pledged as collateral into the separate depository account for the purpose of retiring the debt according to the repayment requirements of the loan; and </P>
                            <P>(v) In the case of public financing payments, the borrower authorizes the Secretary of the Treasury to directly deposit the payments into the depository account for the purpose of retiring the debt. </P>
                            <P>(3) If the requirements set forth in paragraph (e) of this section are not met, the Commission will consider the totality of circumstances on a case-by-case basis in determining whether a loan was made on a basis that assures repayment. </P>
                            <P>(f) This section shall not apply to loans described in 11 CFR 100.73 and 100.114. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.143 </SECTNO>
                            <SUBJECT>Brokerage loans and lines of credit to candidates. </SUBJECT>
                            <P>Repayment of a loan of money derived from an advance on a candidate's brokerage account, credit card, home equity line of credit, or other line of credit available to the candidate, as described in 11 CFR 100.73, is not an expenditure. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.144 </SECTNO>
                            <SUBJECT>Office building for State, local, or district party committees or organizations. </SUBJECT>
                            <P>A payment, distribution, loan, advance, or deposit of money or anything of value, made by, or on behalf of, a State, local, or district party committee or organization for the purchase or construction of an office building in accordance with 11 CFR 300.35 is not an expenditure. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.145 </SECTNO>
                            <SUBJECT>Legal or accounting services to political party committees. </SUBJECT>
                            <P>Legal or accounting services rendered to or on behalf of any political committee of a political party are not expenditures if the person paying for such services is the regular employer of the individual rendering the services and such services are not attributable to activities that directly further the election of any designated candidate for Federal office. For purposes of this section, a partnership shall be deemed to be the regular employer of a partner. Amounts paid by the regular employer for such services shall be reported by the committee receiving such services in accordance with 11 CFR 104.3(h). </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.146 </SECTNO>
                            <SUBJECT>Legal or accounting services to other political committees. </SUBJECT>
                            <P>Legal or accounting services rendered to or on behalf of an authorized committee of a candidate or any other political committee are not expenditures if the person paying for such services is the regular employer of the individual rendering such services and if the services are solely to ensure compliance with the Act or 26 U.S.C. 9001 et seq. and 9032 et seq. For purposes of this section, a partnership shall be deemed to be the regular employer of a partner. Amounts paid by the regular employer for these services shall be reported by the committee receiving such services in accordance with 11 CFR 104.3(h). Expenditures for these services by a candidate certified to receive Primary Matching Funds under 11 CFR part 9034 do not count against such candidate's expenditure limitations under 11 CFR part 9035 or 11 CFR 110.8. Unless paid for with federal funds received pursuant to 11 CFR part 9005, disbursements for these services by a candidate who is certified to receive payments from the Presidential Election Campaign Fund under 11 CFR part 9005 do not count against that candidate's expenditure limitations under 11 CFR 110.8. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.147 </SECTNO>
                            <SUBJECT>Volunteer activity for party committees. </SUBJECT>
                            <P>The payment by a state or local committee of a political party of the costs of campaign materials (such as pins, bumper stickers, handbills, brochures, posters, party tabloids or newsletters, and yard signs) used by such committee in connection with volunteer activities on behalf of any nominee(s) of such party is not an expenditure, provided that the following conditions are met: </P>
                            <P>
                                (a) 
                                <E T="03">Exemption does not apply to general public communications or political advertising.</E>
                                 Such payment is not for costs incurred in connection with any broadcasting, newspaper, magazine, billboard, direct mail, or similar type of general public communication or political advertising. For the purposes of this paragraph, the term 
                                <E T="03">direct mail</E>
                                 means any mailing(s) by a commercial vendor or any mailing(s) made from commercial lists. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Allocation.</E>
                                 The portion of the cost of such materials allocable to Federal candidates is paid from contributions subject to the limitations and prohibitions of the Act. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Contributions designated for Federal candidates.</E>
                                 Such payment is not made from contributions designated by the donor to be spent on behalf of a particular candidate or candidates for Federal office. For purposes of this paragraph, a contribution shall not be considered a designated contribution if the party committee disbursing the funds makes the final decision regarding which candidate(s) shall receive the benefit of such disbursement. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Distribution of materials by volunteers.</E>
                                 Such materials are distributed by volunteers and not by commercial or for-profit operations. For the purposes of this paragraph, payments by the party organization for travel and subsistence or customary token payments to volunteers do not remove such individuals from the volunteer category. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Reporting.</E>
                                 If made by a political party committee, such payments shall be reported by that committee as disbursements, in accordance with 11 CFR 104.3, but need not be allocated to 
                                <PRTPAGE P="40893"/>
                                specific candidates in committee reports. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">State candidates and their campaign committees.</E>
                                 Payments by a State candidate or his or her campaign committee to a State or local political party committee for the State candidate's share of expenses for such campaign materials are not expenditures, provided the amount paid by the State candidate or his or her committee does not exceed his or her proportionate share of the expenses. 
                            </P>
                            <P>
                                (g) 
                                <E T="03">Exemption not applicable to campaign materials purchased by national party committees.</E>
                                 Campaign materials purchased by the national committee of a political party and delivered to a State or local party committee, or materials purchased with funds donated by the national committee to such State or local committee for the purchase of such materials, shall not qualify under this exemption. Rather, the cost of such materials shall be subject to the limitations of 2 U.S.C. 441a(d) and 11 CFR 110.7. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.148 </SECTNO>
                            <SUBJECT>Volunteer activity for candidate. </SUBJECT>
                            <P>The payment by a candidate for any public office (including State or local office), or by such candidate's authorized committee, of the costs of that candidate's campaign materials that include information on or any reference to a candidate for Federal office and that are used in connection with volunteer activities (such as pins, bumper stickers, handbills, brochures, posters, and yard signs) is not an expenditure on behalf of such candidate for Federal office, provided that the payment is not for the use of broadcasting, newspapers, magazines, billboards, direct mail or similar types of general public communication or political advertising. The payment of the portion of the cost of such materials allocable to Federal candidates shall be made from contributions subject to the limitations and prohibitions of the Act. For purposes of this section, the term direct mail means mailings by commercial vendors or mailings made from lists that were not developed by the candidate. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.149 </SECTNO>
                            <SUBJECT>Voter registration and get-out-the-vote activities for Presidential candidates (“coattails” exception). </SUBJECT>
                            <P>The payment by a State or local committee of a political party of the costs of voter registration and get-out-the-vote activities conducted by such committee on behalf of the Presidential and Vice Presidential nominee(s) of that party is not an expenditure for the purpose of influencing the election of such candidates provided that the following conditions are met: </P>
                            <P>
                                (a) 
                                <E T="03">Exemption not applicable to general public communication or political advertising.</E>
                                 Such payment is not for the costs incurred in connection with any broadcasting, newspaper, magazine, billboard, direct mail, or similar type of general public communication or political advertising. For purposes of this paragraph, the term direct mail means any mailing(s) by a commercial vendor or any mailing(s) made from commercial lists. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Allocation.</E>
                                 The portion of the costs of such activities allocable to Federal candidates is paid from contributions subject to the limitations and prohibitions of the Act. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Contributions designated for Federal candidates.</E>
                                 Such payment is not made from contributions designated to be spent on behalf of a particular candidate or candidates for Federal office. For the purposes of this paragraph, a contribution shall not be considered a designated contribution if the party committee disbursing the funds makes the final decision regarding which candidate(s) shall receive the benefit of such disbursement. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">References to House or Senate candidates.</E>
                                 For purposes of this section, if such activities include references to any candidate(s) for the House or Senate, the costs of such activities that are allocable to that candidate(s) shall be an expenditure on behalf of such candidate(s) unless the mention of such candidate(s) is merely incidental to the overall activity. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Phone banks.</E>
                                 For purposes of this section, payment of the costs incurred in the use of phone banks in connection with voter registration and get-out-the-vote activities is not an expenditure when such phone banks are operated by volunteer workers. The use of paid professionals to design the phone bank system, develop calling instructions and train supervisors is permissible. The payment of the costs of such professional services is not an expenditure but shall be reported as a disbursement in accordance with 11 CFR 104.3 if made by a political committee. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">Reporting of payments for voter registration and get-out-the-vote activities.</E>
                                 If made by a political committee, such payments for voter registration and get-out-the-vote activities shall be reported by that committee as disbursements, in accordance with 11 CFR 104.3 but such payments need not be allocated to specific candidates in committee reports except as provided in paragraph (d) of this section. 
                            </P>
                            <P>
                                (g) 
                                <E T="03">Exemption not applicable to donations by a national committee of a political party to a State or local party committee for voter registration and get-out-the-vote activities.</E>
                                 Payments made from funds donated by a national committee of a political party to a State or local party committee for voter registration and get-out-the-vote activities shall not qualify under this exemption. Rather, such funds shall be subject to the limitations of 2 U.S.C. 441a(d) and 11 CFR 110.7. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.150 </SECTNO>
                            <SUBJECT>Ballot access fees. </SUBJECT>
                            <P>Amounts transferred by a party committee to another party committee or payments made to the appropriate State official of fees collected from candidates or their authorized committees as a condition of ballot access are not expenditures. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.151 </SECTNO>
                            <SUBJECT>Recounts. </SUBJECT>
                            <P>A purchase, payment, distribution, loan, advance, or deposit of money or anything of value made with respect to a recount of the results of a Federal election, or an election contest concerning a Federal election, is not an expenditure except that the prohibitions of 11 CFR 110.4(a) and part 114 apply. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.152 </SECTNO>
                            <SUBJECT>Fundraising costs for Presidential candidates. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Costs incurred in connection with the solicitation of contributions.</E>
                                 Any costs incurred by a candidate or his or her authorized committee(s) in connection with the solicitation of contributions are not expenditures if incurred by a candidate who has been certified to receive Presidential Primary Matching Fund Payments, or by a candidate who has been certified to receive general election public financing under 26 U.S.C. 9004 and who is soliciting contributions in accordance with 26 U.S.C. 9003(b)(2) or 9003(c)(2) to the extent that the aggregate of such costs does not exceed 20 percent of the expenditure limitation applicable to the candidate. These costs shall, however, be reported as disbursements pursuant to 11 CFR part 104. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Definition of in connection with the solicitation of contributions.</E>
                                 For a candidate who has been certified to receive general election public financing under 26 U.S.C. 9004 and who is soliciting contributions in accordance with 26 U.S.C. 9003(b)(2) or 9003(c)(2), 
                                <E T="03">in connection with the solicitation of contributions</E>
                                 means any cost reasonably related to fundraising activity, including the costs of printing and postage, the production of and space or air time for, advertisements used for fundraising, and the costs of meals, beverages, and 
                                <PRTPAGE P="40894"/>
                                other costs associated with a fundraising reception or dinner. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Limitation on costs that may be exempted.</E>
                                 For a candidate who has been certified to receive Presidential Primary Matching Fund Payments, the costs that may be exempted as fundraising expenses under this section shall not exceed 20% of the overall expenditure limitation under 11 CFR 9035.1, and shall equal the total of: 
                            </P>
                            <P>(1) All amounts excluded from the state expenditure limitations for exempt fundraising activities under 11 CFR 110.8(c)(2), plus </P>
                            <P>(2) An amount of costs that would otherwise be chargeable to the overall expenditure limitation but that are not chargeable to any state expenditure limitation, such as salary and travel expenses. See 11 CFR 106.2. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.153 </SECTNO>
                            <SUBJECT>Routine living expenses. </SUBJECT>
                            <P>Payments by a candidate from his or her personal funds, as defined at 11 CFR 110.10(b), for the candidate's routine living expenses that would have been incurred without candidacy, including the cost of food and residence, are not expenditures. Payments for such expenses by a member of the candidate's family as defined in 11 CFR 113.1(g)(7), are not expenditures if the payments are made from an account jointly held with the candidate, or if the expenses were paid by the family member before the candidate became a candidate. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 100.154 </SECTNO>
                            <SUBJECT>Candidate debates. </SUBJECT>
                            <P>Funds used to defray costs incurred in staging candidate debates in accordance with the provisions of 11 CFR 110.13 and 114.4(f) are not expenditures. </P>
                        </SECTION>
                    </SUBPART>
                    <SIG>
                        <DATED>Dated: June 10, 2002. </DATED>
                        <NAME>David M. Mason, </NAME>
                        <TITLE>Chairman, Federal Election Commission. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14902 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6715-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. 2001-NM-74-AD] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; Boeing Model 757-200, -200PF, -200CB, and -300 Series Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes the adoption of a new airworthiness directive (AD) that is applicable to certain Boeing Model 757-200, -200PF, -200CB, and -300 series airplanes. This proposal would require inspection for damage of the W2800 wire bundle insulation, wire conductor, the wire bundle clamp bracket, and the BACC10GU( ) clamp, and repair or replacement with new or serviceable parts, if necessary. This proposal also would require installation of spacers between the clamp and the bracket. This action is necessary to prevent contact between the power feeder wires of the auxiliary power unit (APU) and the clamp bracket aft of the STA 1720 bulkhead due to chafing damage of the Adel clamp and “L” shaped bracket, which could result in electrical arcing and fire, or loss of electrical power in the airplane. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by July 29, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2001-NM-74-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 
                        <E T="03">9-anm-nprmcomment@faa.gov.</E>
                         Comments sent via fax or the Internet must contain “Docket No. 2001-NM-74-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 for Windows or ASCII text. 
                    </P>
                    <P>The service information referenced in the proposed rule may be obtained from Boeing Commercial Airplane Group, P.O. Box 3707, Seattle, Washington 98124-2207. This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Elias Nastiopoulos, Aerospace Engineer, Systems and Equipment Branch, ANM-130S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue, SW., Renton, Washington 98055-4056; telephone (425) 227-1279; fax (425) 227-1181. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited </HD>
                <P>Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received. </P>
                <P>Submit comments using the following format: </P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues. </P>
                <P>• For each issue, state what specific change to the proposed AD is being requested. </P>
                <P>• Include justification (e.g., reasons or data) for each request. </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket. </P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2001-NM-74-AD.” The postcard will be date stamped and returned to the commenter. </P>
                <HD SOURCE="HD1">Availability of NPRMs </HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2001-NM-74-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. </P>
                <HD SOURCE="HD1">Discussion </HD>
                <P>
                    The FAA has received a report regarding a Boeing 757-200 series airplane indicating that, during a structural inspection of the generator power feeder (GPF) wires for the auxiliary power unit (APU), chafing damage was detected on the Adel clamp and the “L” shaped bracket. The clamp and bracket support the wires that are located just aft of the pressure seal fitting at the STA 1720 bulkhead. As a result of that finding, the operator that submitted the report inspected seven additional Model 757 series airplanes in its fleet for chafing damage. The report 
                    <PRTPAGE P="40895"/>
                    also indicated that the GPF wires of four of the seven airplanes had been either repaired or repositioned. Electrical contact between the power feeder wires of the APU and the clamp bracket aft of the STA 1720 bulkhead due to chafing damage of the Adel clamp and “L” shaped bracket, if not corrected, could result in electrical arcing and fire or loss of electrical power in the airplane. 
                </P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information </HD>
                <P>The FAA has reviewed and approved Boeing Service Bulletin 757-24-0089 (for Model 757-200 series airplanes) and Boeing Service Bulletin 757-24-0090 (for Model 757-300 series airplanes), both dated March 15, 2001. The service bulletins describe procedures for a general visual inspection for damage of the W2800 wire bundle insulation, wire conductor, the wire bundle clamp bracket, and the BACC10GU( ) clamp, and repair or replacement with new or serviceable parts, if necessary. The service bulletins also describe procedures for installing spacers between the clamp and the bracket and ensuring that there is 0.25-inch minimum clearance between the wire bundle and the aft edge of the bracket. Accomplishment of the actions specified in the service bulletins is intended to adequately address the identified unsafe condition. </P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed Rule </HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other products of this same type design, the proposed AD would require accomplishment of the actions specified in the service bulletins described previously. </P>
                <HD SOURCE="HD1">Similar Models </HD>
                <P>The installation of the GPF wires for the APU on certain Boeing Model 757-200PF series airplanes is similar to that installed on certain Boeing Model 757-200, -200CB, and certain Model 757-300 series airplanes. Therefore, all of these models may be subject to the same unsafe condition. </P>
                <HD SOURCE="HD1">Cost Impact </HD>
                <P>There are approximately 934 Boeing Model 757-200, -200PF, -200CB, and -300 series airplanes of the affected design in the worldwide fleet. The FAA estimates that 595 airplanes of U.S. registry would be affected by this proposed AD, that it would take approximately 1 work hour per airplane to accomplish the proposed inspection and installation of spacers, and that the average labor rate is $60 per work hour. Based on these figures, the cost impact of the proposed AD on U.S. operators is estimated to be $35,700, or $60 per airplane. </P>
                <P>The cost impact figure discussed above is based on assumptions that no operator has yet accomplished any of the proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this proposed AD were not adopted. The cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions. </P>
                <HD SOURCE="HD1">Regulatory Impact </HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132. </P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39 </HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment </HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES </HD>
                    <P>1. The authority citation for part 39 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701. </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. Section 39.13 is amended by adding the following new airworthiness directive:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Boeing:</E>
                                 Docket 2001-NM-74-AD.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model 757-200, -200PF, -200CB, and -300 series airplanes, as listed in Boeing Service Bulletin 757-24-0089 and Boeing Service Bulletin 757-24-0090, both dated March 15, 2001, as applicable; certificated in any category. 
                            </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>This AD applies to each airplane identified in the preceding applicability provision, regardless of whether it has been modified, altered, or repaired in the area subject to the requirements of this AD. For airplanes that have been modified, altered, or repaired so that the performance of the requirements of this AD is affected, the owner/operator must request approval for an alternative method of compliance in accordance with paragraph (b) of this AD. The request should include an assessment of the effect of the modification, alteration, or repair on the unsafe condition addressed by this AD; and, if the unsafe condition has not been eliminated, the request should include specific proposed actions to address it.</P>
                            </NOTE>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously. 
                            </P>
                            <P>To prevent electrical contact between the power feeder wires of the auxiliary power unit (APU) and the clamp bracket aft of STA 1720 bulkhead due to chafing damage of the Adel clamp and “L” shaped bracket, which could result in electrical arcing and fire or loss of electrical power in the airplane; accomplish the following: </P>
                            <HD SOURCE="HD1">Inspection and Repair of Any Damage </HD>
                            <P>(a) Within 15 months after the effective date of this AD, perform a general visual inspection for damage of the W2800 wire bundle insulation, wire conductor, the wire bundle clamp bracket, and the BACC10GU( ) clamp; per Boeing Service Bulletin 757-24-0089 (for Boeing Model 757-200 series airplanes) or Boeing Service Bulletin 757-24-0090 (for Boeing Model 757-300 series airplanes), both dated March 15, 2001, as applicable. If no damage is detected: Before further flight, install spacers and ensure that there is 0.25-inch minimum clearance between the wire bundle and aft edge of the bracket, per the applicable service bulletin. </P>
                            <P>(1) If any damage to the wire bundle insulation or the wire conductor is detected: Before further flight, repair the damage per the applicable service bulletin, install spacers, and ensure that there is 0.25-inch minimum clearance between the wire bundle and aft edge of the bracket; per the applicable service bulletin. </P>
                            <P>(2) If any damage to the wire bundle clamp bracket or the BACC10GU( ) clamp is detected: Before further flight, replace the clamp bracket and the clamp with new or serviceable parts, install spacers, and ensure that there is 0.25-inch minimum clearance between the wires bundle and aft edge of the bracket; per the applicable service bulletin. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>
                                    For the purposes of this AD, a general visual inspection is defined as: “A 
                                    <PRTPAGE P="40896"/>
                                    visual examination of an interior or exterior area, installation, or assembly to detect obvious damage, failure, or irregularity. This level of inspection is made from within touching distance unless otherwise specified. A mirror may be necessary to enhance visual access to all exposed surfaces in the inspection area. This level of inspection is made under normally available lighting conditions such as daylight, hangar lighting, flashlight, or droplight and may require removal or opening of access panels or doors. Stands, ladders, or platforms may be required to gain proximity to the area being checked.”
                                </P>
                            </NOTE>
                            <HD SOURCE="HD1">Alternative Methods of Compliance </HD>
                            <P>(b) An alternative method of compliance or adjustment of the compliance time that provides an acceptable level of safety may be used if approved by the Manager, Seattle Aircraft Certification Office (ACO), FAA. Operators shall submit their requests through an appropriate FAA Principal Maintenance Inspector, who may add comments and then send it to the Manager, Seattle ACO. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 3:</HD>
                                <P>Information concerning the existence of approved alternative methods of compliance with this AD, if any, may be obtained from the Seattle ACO.</P>
                            </NOTE>
                            <HD SOURCE="HD1">Special Flight Permits </HD>
                            <P>(c) Special flight permits may be issued in accordance with sections 21.197 and 21.199 of the Federal Aviation Regulations (14 CFR 21.197 and 21.199) to operate the airplane to a location where the requirements of this AD can be accomplished.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on June 7, 2002. </DATED>
                        <NAME>Ali Bahrami, </NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15106 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 71 </CFR>
                <SUBAGY>Airspace Docket No. 00-AAL-03 </SUBAGY>
                <RIN>RIN 2120-AA66 </RIN>
                <SUBJECT>Proposed Modification and Revocation of Federal Airways; Alaska</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; withdrawal. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This action withdraws the proposed rule published in the 
                        <E T="04">Federal Register</E>
                         on June 28, 2000. In that action, the FAA proposed to modify two jet routes (J-115 and J-125); two Very High Frequency Omnidirectional Range (VOR) Federal airways (V-447 and V-436); and one Colored Federal Airway (A-15) in Alaska. The FAA has determined that withdrawal of the proposed rule is warranted since the FAA is no longer planning on decommissioning the Chandalar Lake Nondirectional Radio Beacon. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The proposed rule is withdrawn as of June 14, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ken McElroy, Airspace and Rules Division, ATA-400, Office of Air Traffic Airspace Management, Federal Aviation Administration, 800 Independence Avenue, SW., Washington, DC 20591; telephone: (202) 267-8783. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On June 28, 2000, a notice of proposed rulemaking (NPRM) was published in the 
                    <E T="04">Federal Register</E>
                     proposing to amend 14 CFR part 71 by modifying two jet routes (J-115 and J-125); two Very High Frequency Omnidirectional Range (VOR) Federal airways (V-447 and V-436); and one Colored Federal Airway (A-15) in Alaska (65 FR 39833). Interested parties were invited to participate in the rulemaking process by submitting written data, views, or arguments regarding the proposal. No comments were received on the proposal. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 71 </HD>
                    <P>Airspace, Incorporation by reference, Navigation (air).</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Withdrawal </HD>
                <P>
                    In consideration of the foregoing, the Notice of Proposed Rulemaking, Airspace Docket No. 00-AAL-03, as published in the 
                    <E T="04">Federal Register</E>
                     on June 28, 2000 (65 FR 39833), is hereby withdrawn. 
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>49 U.S.C. 106(g), 40103, 40113, 40120; E.O. 10854; 24 FR 9565, 3 CFR, 1959-1963 Comp., p. 389. </P>
                </AUTH>
                <SIG>
                    <DATED>Issued in Washington, DC, on June 4, 2002. </DATED>
                    <NAME>Reginald C. Matthews, </NAME>
                    <TITLE>Manager, Airspace and Rules Division. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14688 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <CFR>26 CFR Part 1 </CFR>
                <DEPDOC>[REG-209114-90] </DEPDOC>
                <RIN>RIN 1545-AH49 </RIN>
                <SUBJECT>Golden Parachute Payments; Hearing Cancellation </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Cancellation of notice of public hearing on proposed rulemaking. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document cancels the public hearing on proposed regulations that relates to golden parachute payments to provide guidance to taxpayers who must comply with section 280G. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The public hearing originally scheduled for Wednesday, June 26, 2002, at 10 a.m., is cancelled. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>LaNita Van Dyke of the Regulations Unit, Associate Chief Counsel (Income Tax and Accounting), (202) 622-7190 (not a toll-free number). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    A notice of proposed rulemaking and notice of public hearing that appeared in the 
                    <E T="04">Federal Register</E>
                     on Wednesday, February 20, 2001 (67 FR 7630), announced that a public hearing was scheduled for Wednesday, June 26, 2002, at 10 a.m., in the IRS Auditorium, Internal Revenue Building, 1111 Constitution Avenue, NW., Washington, DC. The subject of the public hearing is proposed regulations under section 280G of the Internal Revenue Code. The public comment period for these proposed regulations expired on Wednesday, June 5, 2002. 
                </P>
                <P>The notice of proposed rulemaking and notice of public hearing, instructed those interested in testifying at the public hearing to submit a request to speak and an outline of the topics to be addressed. As of Tuesday, June 11, 2002, no one has requested to speak. Therefore, the public hearing scheduled for Wednesday, June 25, 2002, is cancelled. </P>
                <SIG>
                    <NAME>Cynthia E. Grigsby,</NAME>
                    <TITLE>Chief, Regulations Unit, Associate Chief Counsel, (Income Tax and Accounting). </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15108 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Internal Revenue Service </SUBAGY>
                <CFR>26 CFR Part 1 </CFR>
                <DEPDOC>[REG-107100-00] </DEPDOC>
                <RIN>RIN 1545-AY26 </RIN>
                <SUBJECT>Disallowance of Deductions and Credits for Failure To File Timely Return; Correction </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Internal Revenue Service (IRS), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Correction of a cancellation of notice of public hearing on proposed regulations.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document contains corrections to a cancellation notice of 
                        <PRTPAGE P="40897"/>
                        public hearing on proposed rulemaking which was published in the 
                        <E T="04">Federal Register</E>
                         on Wednesday, May 29, 2002 (67 FR 37369), relating to the disallowance of deduction and credits for nonresident alien individuals and foreign corporations that fail to file a timely U.S. income tax return. 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nina E. Chowdhry, (202) 622-3880 (not a toll-free number). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">Background </HD>
                <P>The notice of cancellation of public hearing on proposed rulemaking that is subject to this correction is under sections 874 and 882 of the Internal Revenue Code. </P>
                <HD SOURCE="HD1">Need for Correction </HD>
                <P>As published, the notice of cancellation of public hearing on proposed rulemaking contained errors which may prove misleading and are in need of correction. </P>
                <HD SOURCE="HD1">Correction of Publication </HD>
                <P>Accordingly, the publication of the cancellation of notice of public hearing on proposed rulemaking which is the subject of FR Doc. 02-13397, is corrected as follows: </P>
                <P>
                    1. On page 37369, in the preamble, following the caption 
                    <E T="02">ACTION:</E>
                    , the language “Cancellation of notice of proposed rulemaking by cross-reference to temporary regulations and notice of public hearing.” is corrected to read “Cancellation of notice of public hearing on proposed rulemaking.”.
                </P>
                <P>
                    2. On page 37369, in the preamble, following the caption 
                    <E T="02">SUMMARY:</E>
                    , the language “This document provides notice of cancellation of proposed regulations and notice of public hearing relating to the disallowance of deductions and credits for nonresident alien individuals and foreign corporations that fail to file a timely U.S. income tax return.” is corrected to read “This document provides notice of cancellation of a public hearing on proposed regulations relating to the disallowance of deductions and credits for nonresident alien individuals and foreign corporations that fail to file a timely U.S. income tax return.”. 
                </P>
                <SIG>
                    <NAME>Cynthia E. Grigsby, </NAME>
                    <TITLE>Chief, Regulations Unit, Associate Chief Counsel, (Income Tax &amp; Accounting).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15107 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 52 </CFR>
                <DEPDOC>[CA 250-0331b; FRL-7165-5] </DEPDOC>
                <SUBJECT>Revisions to the California State Implementation Plan, Lake County Air Quality Management District </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>EPA is proposing to approve a revision to the Lake County Air Quality Management District (LCAQMD) portion of the California State Implementation Plan (SIP). This revision concerns particulate matter (PM-10) emissions from open fires and prescribed burning. We are proposing to approve local rules that regulate this emission source under the Clean Air Act as amended in 1990 (CAA or the Act). </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Any comments on this proposal must arrive by July 15, 2002. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Mail comments to Andy Steckel, Rulemaking Office Chief (AIR-4), U.S. Environmental Protection Agency, Region IX, 75 Hawthorne Street, San Francisco, CA 94105. </P>
                    <P>You can inspect copies of the submitted rule revisions and EPA's technical support document (TSD) at our Region IX office during normal business hours. You may also see copies of the submitted rule revisions and TSD at the following locations: </P>
                    <FP SOURCE="FP-1">Environmental Protection Agency, Air Docket (6102), Ariel Rios Building, 1200 Pennsylvania Avenue, NW., Washington DC 20460. </FP>
                    <FP SOURCE="FP-1">California Air Resources Board, Stationary Source Division, Rule Evaluation Section, 1001 “I” Street, Sacramento, CA 95814. </FP>
                    <FP SOURCE="FP-1">Lake County Air Quality Management District, 885 Lakeport Boulevard, Lakeport, CA 95453. </FP>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Al Petersen, Rulemaking Office (AIR-4), U.S. Environmental Protection Agency, Region IX; (415) 947-4118. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This proposal addresses the approval of the local LCAQMD Sections [Rules] 203, 204.5, 208.3, 208.8, 226.4, 226.5, 240.8, 246, 248.3, 248.5, 249.5, 251.7, 270, 431, 431.5, 433, 434, 1000, 1001, 1003, 1105, 1107, 1130, 1140, 1145, 1150, 1160, and 1170. In the Rules section of this 
                    <E T="04">Federal Register</E>
                    , we are approving these local rules in a direct final action without prior proposal because we believe this SIP revision is not controversial. If we receive adverse comments, however, we will publish a timely withdrawal of the direct final rule and address the comments in subsequent action based on this proposed rule. We do not plan to open a second comment period, so anyone interested in commenting should do so at this time. If we do not receive adverse comments, no further activity is planned. For further information, please see the direct final action. 
                </P>
                <SIG>
                    <DATED>Dated: March 14, 2002. </DATED>
                    <NAME>Laura Yoshii, </NAME>
                    <TITLE>Acting Regional Administrator, Region IX. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14511 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 52 </CFR>
                <DEPDOC>[MT-001-00010; MT-001-0028; FRL-7231-4] </DEPDOC>
                <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; Montana; Billings/Laurel Sulfur Dioxide State Implementation Plan; Correction </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; correction. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On May 2, 2002, EPA proposed to partially and limitedly approve and limitedly disapprove revisions to the Billings/Laurel sulfur dioxide (SO2) State Implementation Plan (SIP). EPA noticed an error in the May 2, 2002 document and is correcting it with this document. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments on the May 2, 2002 proposed rule must be received on or before July 1, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Laurie Ostrand, EPA, Region VIII, (303) 312-6437. </P>
                    <HD SOURCE="HD1">Correction </HD>
                    <P>Our May 2, 2002 document, in which we proposed partial and limited approval and limited disapproval of the Billings/Laurel SO2 SIP (67 FR 22242) (FR Doc. 02-10333), is corrected as follows: </P>
                    <P>On page 22246, first column, Section IV. Request for Public Comment, the last sentence should read as follows: “We will consider your comments in deciding our final action if your letter is received on or before July 1, 2002.” </P>
                    <P>
                        As published on May 2, 2002, the sentence incorrectly listed the comment deadline as “[W]e will consider your comments in deciding our final action if your letter is received before [insert date, 30 days from publication].” The correct deadline for submitting 
                        <PRTPAGE P="40898"/>
                        comments appeared in the 
                        <E T="02">Dates</E>
                         section of the May 2, 2002 notice, first column of 67 FR 22242. 
                    </P>
                    <SIG>
                        <DATED>Dated: June 6, 2002. </DATED>
                        <NAME>Robert E. Roberts, </NAME>
                        <TITLE>Regional Administrator, Region 8. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15091 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Parts 2 and 97 </CFR>
                <DEPDOC>[ET Docket No. 02-98 ; FCC 02-136] </DEPDOC>
                <SUBJECT>Amateur Radio Service Rules </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes to amend the Commission's Rules to add a new secondary allocation to the 135.7-137.8 kHz band for the amateur service for experimentation in the low frequency (“LF”) region of the spectrum; add a new secondary allocation to the 5250-5400 kHz band for the amateur service to facilitate high frequency (“HF”) amateur service operations; and to upgrade the amateur service allocation from secondary status to primary status and add a primary allocation for the amateur-satellite service in the 2400-2402 MHz band. The proposed changes to the Rules would enhance the ability of the amateur service to conduct technical experiments with LF propagation and antenna design; allow amateurs to communicate at 5250 kHz when propagation conditions do not permit communication at 3500 kHz or 7000 kHz; and provide protected status for the amateur-satellite service now using the 2400-2402 MHz band. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments are due July 29, 2002, and reply comments are due August 13, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kathyrn Medley, Office of Engineering and Technology, (202) 418-1211, TTY (202) 418-2989, e-mail: 
                        <E T="03">kmedley@fcc.gov.</E>
                    </P>
                </FURINF>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>All filings must be addressed to the Commission's Secretary, Office of the Secretary, Federal Communications Commission. Filings can be sent by hand or messenger delivery, by commercial overnight courier, or by first-class or overnight U.S. Postal Service mail (although we continue to experience delays in receiving U.S. Postal Service mail). The Commission's contractor, Vistronix, Inc., will receive hand-delivered or messenger-delivered paper filings for the Commission's Secretary at 236 Massachusetts Avenue, NE., Suite 110, Washington, DC 20002. The filing hours at this location are 8:00 a.m. to 7:00 p.m. All hand deliveries must be held together with rubber bands or fasteners. Any envelopes must be disposed of before entering the building. Commercial overnight mail (other than U.S. Postal Service Express Mail and Priority Mail) must be sent to 9300 East Hampton Drive, Capitol Heights, MD 20743. U.S. Postal Service first-class mail, Express Mail, and Priority Mail should be addressed to 445 12th Street, SW, Washington, DC 20554. </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a summary of the Commission's 
                    <E T="03">Notice of Proposed Rulemaking,</E>
                     ET Docket 02-98, FCC 02-136, adopted May 2, 2002, and released May 15, 2002. The full text of this document is available for inspection and copying during regular business hours in the FCC Reference Center (Room CY-A257), 445 12th Street, SW., Washington, DC 20554. The complete text of this document also may be purchased from the Commission's copy contractor, Qualex International, 445 12th Street, SW., Room, CY-B402, Washington, DC 20554. The full text may also be downloaded at: 
                    <E T="03">www.fcc.gov.</E>
                     Alternative formats are available to persons with disabilities by contacting Brian Millin at (202) 418-7426 or TTY (202) 418-7365. 
                </P>
                <P>
                    Pursuant to Sections 1.415 and 1.419 of the Commission's rules, 47 CFR 1.415, 1.419, interested parties may file comments on or before July 29, 2002, and reply comments on or before August 13, 2002. Comments may be filed using the Commission's Electronic Comment Filing System (ECFS) or by filing paper copies. 
                    <E T="03">See Electronic Filing of Documents in Rulemaking Proceedings,</E>
                     63 FR 24121 (1998). Comments filed through the ECFS can be sent as an electronic file via the Internet to 
                    <E T="03">http://www.fcc.gov/e-file/ecfs.html.</E>
                     Generally, only one copy of an electronic submission must be filed. If multiple docket or rulemaking numbers appear in the caption of this proceeding, however, commenters must transmit one electronic copy of the comments to each docket or rulemaking number referenced in the caption. In completing the transmittal screen, commenters should include their full name, U.S. Postal Service mailing address, and the applicable docket or rulemaking number. Parties may also submit an electronic comment by Internet e-mail. To get filing instructions for e-mail comments, commenters should send an e-mail to 
                    <E T="03">ecfs@fcc.gov,</E>
                     and should include the following words in the body of the message, “get form &lt;your e-mail address.” A sample form and directions will be sent in reply. Parties who choose to file by paper must file an original and four copies of each filing. If more than one docket or rulemaking number appear in the caption of this proceeding, commenters must submit two additional copies for each additional docket or rulemaking number. 
                </P>
                <HD SOURCE="HD1">Summary of Notice of Proposed Rule Making </HD>
                <P>
                    1. 
                    <E T="03">The Notice of Proposed Rulemaking</E>
                     (
                    <E T="03">“NPRM”</E>
                    ) proposes to amend parts 2 and 97 of the Commission's rules to: (1) Add a new secondary allocation to the 135.7-137.8 kHz band for the amateur service for experimentation in the low frequency (“LF”) region of the spectrum; (2) add a new secondary allocation to the 5250-5400 kHz band for the amateur service to facilitate high frequency (“HF”) amateur service operations; and (3) upgrade the amateur service allocation from secondary status to primary status and add a primary allocation for the amateur-satellite service in the 2400-2402 MHz band. These proposed changes to the rules would enhance the ability of the amateur service to conduct technical experiments with LF propagation and antenna design; allow amateurs to communicate at 5250 kHz when propagation conditions do not permit communication in the amateur allocated spectrum at 3500 kHz or 7000 kHz; and provide protected status for the amateur-satellite service now using the 2400-2402 MHz band. 
                </P>
                <P>
                    2. 
                    <E T="03">An Allocation in the Low Frequency (“LF”) range.</E>
                     The American Radio Relay League filed a 
                    <E T="03">Petition for Rulemaking</E>
                     with the Commission requesting a secondary allocation to the amateur service in the LF spectrum range (specifically the 135.7-137.8 kHz and the 160-190 kHz bands). The Commission was persuaded by ARRL's arguments to consider a secondary amateur service allocation in the LF range of the spectrum to serve the public interest because amateur experimentation could lead to a better understanding of communication techniques in this frequency range. 
                </P>
                <P>
                    3. Incumbent use of the 135.7-137.8 kHz band is relatively light and thus a secondary amateur service allocation in this band raises few concerns. An analysis of a portion of the UTC database of power line carrier (“PLC”) systems by Commission staff shows that PLC system density is significantly less in the 135.7-137.8 kHz band than in the 
                    <PRTPAGE P="40899"/>
                    160-190 kHz band. Consequently, there should be many areas where PLC systems would not be in close proximity to any future amateur operations. Further, domestic primary services in this band would be minimally affected by an amateur service allocation. The Government Master File (“GMF”) and Commission's databases identify only one Federal Government assignment in the 135.7-137.8 kHz band. The amateur service has extensive experience in operating on a secondary basis with primary status services in frequency bands with long range capabilities and the Commission stated the same should apply here. The NPRM stated that interference would be rare because amateur radio operators have demonstrated their effective use of the “listen-before-transmit” protocol, which also can be utilized with the primary users of this band. Regarding the radio-frequency identification devices uses in the lower adjacent band and the PLC use in-band, the NPRM proposed technical rules that are intended to minimize any impact from these amateur station operations on unlicensed equipment use. The NPRM sought comment on this assessment. 
                </P>
                <P>4. While there is no international allocation to the amateur service at 135.7-137.8 kHz in the International Table of Allocations, the NPRM noted that the European Posts and Telecommunications Commission (“CEPT”) has allocated this band to the amateur service on a secondary basis and individual administrations are granting amateur radio operators additional technical flexibility for their LF operations. The Commission also noted that Canada has recently proposed a secondary allocation of the 135.7-137.8 kHz band for the amateur service in Region 2, which may be considered at the 2003 World Radio Conference (“WRC-03”). The NPRM stated that a domestic secondary amateur service allocation in the 135.7-137.8 kHz band would provide a chance to harmonize amateur LF allocations and promote international exploration of a common band. In the absence of an international allocation, however, the NPRM proposed to adopt certain technical limitations on amateur radio operations in this band so that they would not cause interference to primary services outside of the United States. The NPRM requested comment on whether there are any specific spectrum sharing concerns between amateur station operations and domestic or international primary allocation operations in the 135.7-137.8 kHz band.</P>
                <P>5. The NPRM proposed to require that amateur stations in the 135.7-137.8 kHz band meet the technical limits suggested by Canada in the WRC-03 preparatory process. As noted in the Canadian proposal, sharing of this spectrum would be facilitated if the amateur station is limited to an EIRP of 1 W and the transmission bandwidth is limited to 100 Hz. Because of possible difficulty in measuring the EIRP of the amateur station in this frequency range, the NPRM also proposed to limit amateur output power in this band to 100 W PEP. It also sought comment on whether these limits on EIRP and PEP are appropriate. No restrictions on antenna size or design for amateur stations were proposed because such restrictions would inhibit experimentation, and interference to other users can be adequately addressed by the proposed power limitations. The NPRM also proposed to limit access to this band to amateur operators holding a General, Advanced, or Amateur Extra Class license, as requested by ARRL, as a way to insure amateur operations would be conducted in a manner that minimizes the interference potential to other users. It was noted that with an allocation of only 2.1 kilohertz of spectrum in this band, amateur radio operations may be limited to propagation experiments, telegraphy and low speed data applications. Nonetheless, this allocation would benefit amateur experimentation of the LF range. Comment was sought on all of these proposals for a secondary amateur service allocation in the 135.7-137.8 kHz band. </P>
                <P>6. In declining to propose a secondary amateur service allocation for the 160-190 kHz band, the NPRM observed that while the number of incumbent primary users in this band has decreased over the years, the record and Commission staff analysis shows that significant PLC use continues in this band in many locations. The wider bandwidth in the 160-190 kHz band increases the number of PLC systems potentially impacted. Further, while newer technologies may be implemented where possible, PLC systems are not being replaced or retrofitted with these new technologies in many areas. Therefore, the Commission was concerned about the interference potential that a secondary amateur service allocation would have on PLC systems. The Commission also observed that, unlike the situation with the 135.7-137.8 kHz band, there does not appear to be interest internationally in adding amateur services in the 160-190 kHz band. </P>
                <P>7. Amateur radio operations in the 160-190 kHz band under the Commission's part 15 rules would not be affected. Under these rules, amateur operations must meet certain power and antenna length requirements, but they also are allowed to build and operate some equipment of their own design. The NPRM noted that amateurs do have some flexibility to achieve wideband communications and thus, the need to provide a secondary amateur service allocation in the 160-190 kHz band is reduced. Comment was sought on the tentative decision to not provide the allocation in this band that ARRL requested. </P>
                <P>8. Finally, the Commission recognized that spectrum in both the 135.7-137.8 kHz and 160-190 kHz bands could be used more efficiently if potential operators knew where other users of the spectrum were located and could avoid them. UTC has maintained a database of PLC locations in order to notify primary Federal Government users of PLC operations. The NPRM requested comment on whether this database provides sufficient information for use by amateur operators and how such access could be provided. </P>
                <P>
                    9. 
                    <E T="03">An allocation in the 5250-5400 kHz band</E>
                    . The American Radio Relay League filed a 
                    <E T="03">Petition for Rulemaking</E>
                     with the Commission requesting a secondary allocation to the amateur service in the 5250-5400 kHz band. ARRL argued that propagation and interference conditions in the 3500 kHz and 7000 kHz bands could hinder effective amateur HF communications. In particular, the nature of the ionosphere prevents communications during certain portions of the day because of increased atmospheric noise levels at certain times on certain frequencies, or decreased ionization allows the transmission to penetrate the ionosphere at other times and frequencies. ARRL's experimentation appears to support its contention that the 5000 kHz frequency range can be effective in supporting communication when the 3500 kHz and 7000 kHz ranges are not. A new allocation in the 5000 kHz frequency range would permit amateur service operations when other bands cannot be used. Therefore, the Commission tentatively concluded that the amateur service would benefit from a secondary allocation in the 5250-5400 kHz band and proposed to establish such an allocation. Comment was sought on this proposal. 
                </P>
                <P>
                    10. The NPRM indicates that amateur radio operators should be able to avoid interference to primary operations in this band due to the limited numbers of primary assignments which are authorized for operation in the 5250-5400 kHz band, and their experience in sharing HF frequencies in other bands. The operational protocol of “listen 
                    <PRTPAGE P="40900"/>
                    before transmit” employed by amateur radio operators should further minimize interference. Currently this technique is not explicitly required by the Commission's rules and comment was requested on whether it should be explicitly stated in the rules in order to protect the primary operators in the 5250-5400 kHz band. The NPRM proposed to limit the output power of the amateur stations to 1500 W PEP as requested by ARRL. Further, the NPRM invited comments as to whether the 5250-5400 kHz band should be restricted to Amateur radio operators with an Amateur Extra Class license to better ensure compatible sharing with the Federal Government operations, or could the band also be made available to operators with a General or Advanced Class license just as in the 10,100-10,150 kHz band (30 meter band). Comment was invited on whether the power limit and operator license requirement are sufficient to prevent interference to primary users, and whether an EIRP limit would also be appropriate for this frequency band. The NPRM also invited comment on other means that will reduce potential interference. 
                </P>
                <P>
                    11. The 
                    <E T="03">5000 kHz Petition</E>
                     does not discuss sub-banding and ARRL's suggested rules would allow all emission types to use the entire band. Section 97.305 of the Commission's rules segregates digital modes from other amateur station emission modes in the 3500 kHz and 7000 kHz bands to protect narrow band emissions like data from wider emissions like single-side band voice. Therefore, the NPRM requested comment on whether sub-banding is necessary and/or appropriate for the 5250 kHz band as well. 
                </P>
                <P>
                    12. 
                    <E T="03">An allocation in the 2400-2402 MHz band</E>
                    . The American Radio Relay League also filed a 
                    <E T="03">Petition for Rulemaking</E>
                     with the Commission requesting primary allocations to the amateur and the amateur-satellite services in the 2400-2402 MHz band. The Commission placed this spectrum into a reserve for future development because existing ISM and unlicensed operations created a spectral environment that would be difficult to share with other operations. Nevertheless, the amateur radio community has succeeded in sharing this spectrum. Further, the amateur radio community has invested time, effort and money in the development of the amateur and amateur satellite services and primary allocations in this band would protect this investment from future allocation requests in the band. Accordingly, the NPRM proposed to upgrade the allocation for the amateur service from secondary status to primary status and to add a primary allocation to the amateur-satellite service in the 2400-2402 MHz band in parts 2 and 97 of the Commission's rules. It was also noted that footnote 5.282 of the International Table of Allocations states that “the amateur-satellite service may operate subject to not causing harmful interference to other services operating in accordance with the Table [of Allocations].” Therefore, amateur-satellite operators would not be exempted from this requirement to protect operations of other services outside of the United States. 
                </P>
                <P>13. While primary allocations for the amateur and amateur-satellite services may guard against introducing other incompatible users in the band, this allocation change would not alter the status of amateur and amateur'satellite services use vis-à-vis incumbent uses of the band. Either a primary or secondary allocation in ISM bands must accept interference from, and not hinder the use of, ISM equipment. Similarly, this band is extensively used by unlicensed operations, which have been able to share with amateur radio station use to this point. Because this band is important to unlicensed applications and there is widespread deployment, the removal of such devices would not be feasible. The NPRM requested comment on whether the proposed primary amateur and amateur-satellite service allocations would conflict with unlicensed use of the band. </P>
                <P>14. The NPRM merely proposed to change the allocation status of the amateur service operations in the 2400-2402 MHz band. Modification of the service rules or operational requirements of the services in this band is not needed. Comment on this proposal was requested. </P>
                <HD SOURCE="HD1">Initial Regulatory Flexibility Certification </HD>
                <P>
                    15. The Regulatory Flexibility Act of 1980, as amended (RFA),
                    <SU>1</SU>
                    <FTREF/>
                     requires that an initial regulatory flexibility analysis be prepared for notice and comment rule making proceedings, unless the agency certifies that “the rule will not, if promulgated, have a significant economic impact on a substantial number of small entities.”
                    <SU>2</SU>
                    <FTREF/>
                     The RFA generally defines the term “small entity” as having the same meaning as the terms “small business,” “small organization,” and “small governmental jurisdiction.”
                    <SU>3</SU>
                    <FTREF/>
                     In addition, the term “small business” has the same meaning as the term “small business concern” under the Small Business Act.
                    <SU>4</SU>
                    <FTREF/>
                     A “small business concern” is one which: (1) Is independently owned and operated; (2) is not dominant in its field of operation; and (3) satisfies any additional criteria established by the Small Business Administration (SBA).
                    <SU>5</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See</E>
                         5 U.S.C. 603. The RFA, see 5 U.S.C. § 601-612, has been amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), Public Law 104-121, Title II, 110 Stat. 857 (1996). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         5 U.S.C. 605(b). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         5 U.S.C. 601(6). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         5 U.S.C. 601(3) (incorporating by reference the definition of “small business concern” in the Small Business Act, 15 U.S.C. 632). Pursuant to 5 U.S.C. 601(3), the statutory definition of a small business applies “unless an agency, after consultation with the Office of Advocacy of the Small Business Administration and after opportunity for public comment, establishes one or more definitions of such term which are appropriate to the activities of the agency and publishes such definition(s) in the 
                        <E T="04">Federal Register</E>
                        .” 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         15 U.S.C. 632. 
                    </P>
                </FTNT>
                <P>
                    16. In this NPRM, the Commission proposed to make available two additional frequency bands on a secondary basis and upgrade the allocation of a third frequency band to the amateur service. The amateur radio service is a voluntary non-commercial communication service comprised of individuals or groups of individuals holding amateur radio licenses issued by the Commission.
                    <SU>6</SU>
                    <FTREF/>
                     These individuals are prohibited from using spectrum allocated to the amateur service for communications for hire or for material compensation, or for communications in which the amateur radio operator has a pecuniary interest.
                    <SU>7</SU>
                    <FTREF/>
                     Therefore, amateur radio operators do not fit any part of the definition of “small entities” described above, and thus are not classified as such. 
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         47 CFR 97.1 and 97.3(a).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         
                        <E T="03">See</E>
                         47 CFR 97.113(a)(2).
                    </P>
                </FTNT>
                <P>17. In addition, even if the amateur radio licensees were hypothetically considered as “small entities,” the rule changes proposed in this NPRM simply make spectrum available for the amateur radio operations and impose no additional fees, costs, or compliance burdens on an operator. Since the amateur radio service is a voluntary service, it would be up to each individual amateur to purchase or modify equipment to use the new bands. There is no cost associated with the upgrade of the allocation. On the contrary, the amateur radio service receives the positive benefits of access to additional spectrum. </P>
                <P>
                    18. Therefore, the Commission certified that the proposals in this NPRM, if adopted, will not have a significant economic impact on a substantial number of small entities. The Commission will send a copy of the 
                    <PRTPAGE P="40901"/>
                    NPRM, including a copy of this Initial Regulatory Flexibility Certification, to the Chief Counsel for Advocacy of the SBA.
                    <SU>8</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         5 U.S.C. 605(b).
                    </P>
                </FTNT>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>47 CFR Part 2 </CFR>
                    <P>Radio.</P>
                    <CFR>47 CFR Part 97 </CFR>
                    <P>Radio, Satellites. </P>
                </LSTSUB>
                <SIG>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>Marlene H. Dortch, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
                <HD SOURCE="HD1">Proposed Rules </HD>
                <P>For the reasons discussed in the preamble, the Federal Communications Commission proposes to amend 47 CFR parts 2 and 97 as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 2—FREQUENCY ALLOCATIONS AND RADIO TREATY MATTERS; GENERAL RULES AND REGULATIONS </HD>
                    <P>1. The authority citation for part 2 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>47 U.S.C. 154, 302a, 303, and 336, unless otherwise noted. </P>
                    </AUTH>
                    <P>2. Section 2.106, is amended as follows: </P>
                    <P>a. Revise pages 3, 11, and 51 of the Table. </P>
                    <P>b. In the list of United States footnotes, add footnote USxxx. </P>
                    <P>The additions and revisions read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 2.106 </SECTNO>
                        <SUBJECT>Table of Frequency Allocations. </SUBJECT>
                        <STARS/>
                        <BILCOD>BILLING CODE 6712-01-P</BILCOD>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="40902"/>
                            <GID>EP14JN02.003</GID>
                        </GPH>
                        <GPH SPAN="3" DEEP="640">
                            <PRTPAGE P="40903"/>
                            <GID>EP14JN02.004</GID>
                        </GPH>
                        <PRTPAGE P="40904"/>
                        <GPH SPAN="3" DEEP="640">
                            <GID>EP14JN02.005</GID>
                        </GPH>
                        <BILCOD>
                            BILLING CODE 6712-01-C
                            <PRTPAGE P="40905"/>
                        </BILCOD>
                        <STARS/>
                        <HD SOURCE="HD3">UNITED STATES (US) FOOTNOTES </HD>
                        <STARS/>
                        <P>USxxx In the bands 135.7-137.8 kHz and 5250-5400 kHz, the amateur service is allocated on a secondary basis. </P>
                    </SECTION>
                </PART>
                <PART>
                    <HD SOURCE="HED">PART 97—AMATEUR RADIO SERVICE </HD>
                    <P>3. The authority citation for part 97 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>48 Stat. 1066, 1082, as amended: 47 U.S.C. 154, 303. Interpret or apply 48 Stat. 1064-1068, 1081-1105, as amended; 47 U.S.C. 151-155, 301-609, unless otherwise noted.</P>
                    </AUTH>
                    <P>4. Section 97.3 is amended by redesignating paragraphs (b)(4) through (b)(11) as (b)(5) through (b)(12) and by adding a new paragraph (b)(4) to read as follows: </P>
                    <SECTION>
                        <SECTNO>§ 97.3 </SECTNO>
                        <SUBJECT>Definitions. </SUBJECT>
                        <STARS/>
                        <P>(b) * * * </P>
                        <P>
                            (4) 
                            <E T="03">LF (low frequency).</E>
                             The frequency range between 30 kHz and 300 kHz. 
                        </P>
                        <STARS/>
                        <P>5. Section 97.301 is amended by revising the tables in paragraphs (b), (c), and (d) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 97.301 </SECTNO>
                        <SUBJECT>Authorized frequency bands. </SUBJECT>
                        <STARS/>
                        <P>(b) * * * </P>
                        <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,r50,r50,r50,r50">
                            <TTITLE>  </TTITLE>
                            <BOXHD>
                                <CHED H="1">Wavelength band</CHED>
                                <CHED H="1">ITU—Region 1</CHED>
                                <CHED H="1">ITU—Region 2 </CHED>
                                <CHED H="1">ITU—Region 3 </CHED>
                                <CHED H="1">
                                    Sharing requirements see § 97.303 
                                    <LI>(Paragraph) </LI>
                                </CHED>
                            </BOXHD>
                            <ROW RUL="s">
                                <ENT I="25">LF </ENT>
                                <ENT>kHz </ENT>
                                <ENT>kHz </ENT>
                                <ENT>kHz </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">2200m</ENT>
                                <ENT/>
                                <ENT>135.7-137.8</ENT>
                                <ENT/>
                                <ENT>(s). </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="25">MF</ENT>
                                <ENT>kHz</ENT>
                                <ENT>kHz</ENT>
                                <ENT>kHz </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">160 m</ENT>
                                <ENT>1810-1850</ENT>
                                <ENT>1800-2000</ENT>
                                <ENT>1800-2000</ENT>
                                <ENT>(a), (b), (c). </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="25">HF</ENT>
                                <ENT>MHz</ENT>
                                <ENT>MHz</ENT>
                                <ENT>MHz </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">80 m</ENT>
                                <ENT>3.50-3.75</ENT>
                                <ENT>3.50-3.75</ENT>
                                <ENT>3.50-3.75</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">75 m</ENT>
                                <ENT>3.75-3.80</ENT>
                                <ENT>3.75-4.00</ENT>
                                <ENT>3.75-3.90</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">60 m</ENT>
                                <ENT/>
                                <ENT>5.25-5.40</ENT>
                                <ENT/>
                                <ENT>(t). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">40 m</ENT>
                                <ENT>7.0-7.1</ENT>
                                <ENT>7.0-7.3</ENT>
                                <ENT>7.0-7.1</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">30 m</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>(d). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">20 m</ENT>
                                <ENT>14.00-14.35</ENT>
                                <ENT>14.00-14.35</ENT>
                                <ENT>14.00-14.35 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">17 m</ENT>
                                <ENT>18.068-18.168</ENT>
                                <ENT>18.068-18.168</ENT>
                                <ENT>18.068-18.168 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15 m</ENT>
                                <ENT>21.00-21.45</ENT>
                                <ENT>21.00-21.45</ENT>
                                <ENT>21.00-21.45 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 m</ENT>
                                <ENT>24.890-24.99</ENT>
                                <ENT>24.89-24.99</ENT>
                                <ENT>24.89-24.99 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">10 m</ENT>
                                <ENT>28.0-29.7</ENT>
                                <ENT>28.0-29.7</ENT>
                                <ENT>28.0-29.7 </ENT>
                            </ROW>
                        </GPOTABLE>
                        <P> (c) * * *</P>
                        <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,r50,r50,r50,r50">
                            <TTITLE>  </TTITLE>
                            <BOXHD>
                                <CHED H="1">Wavelength band</CHED>
                                <CHED H="1">ITU—Region 1</CHED>
                                <CHED H="1">ITU—Region 2 </CHED>
                                <CHED H="1">ITU—Region 3 </CHED>
                                <CHED H="1">
                                    Sharing requirements see § 97.303 
                                    <LI>(Paragraph) </LI>
                                </CHED>
                            </BOXHD>
                            <ROW RUL="s">
                                <ENT I="25">LF </ENT>
                                <ENT>kHz </ENT>
                                <ENT>kHz </ENT>
                                <ENT>kHz </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">2200 m</ENT>
                                <ENT/>
                                <ENT>135.7-137.8</ENT>
                                <ENT/>
                                <ENT>(s). </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="25">MF</ENT>
                                <ENT>kHz</ENT>
                                <ENT>kHz</ENT>
                                <ENT>kHz </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">160 m</ENT>
                                <ENT>1810-1850</ENT>
                                <ENT>1800-2000</ENT>
                                <ENT>1800-2000</ENT>
                                <ENT>(a), (b), (c). </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="25">HF</ENT>
                                <ENT>MHz</ENT>
                                <ENT>MHz</ENT>
                                <ENT>MHz </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">80 m</ENT>
                                <ENT>3.525-3.750</ENT>
                                <ENT>3.525-3.750</ENT>
                                <ENT>3.525-3.750</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">75 m</ENT>
                                <ENT>3.775-3.800</ENT>
                                <ENT>3.775-4.000</ENT>
                                <ENT>3.775-3.900</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">60 m</ENT>
                                <ENT/>
                                <ENT>5.250-5.400</ENT>
                                <ENT/>
                                <ENT>(t). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">40 m</ENT>
                                <ENT>7.025-7.100</ENT>
                                <ENT>7.035-7.300</ENT>
                                <ENT>7.025-7.100</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">30 m</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>(d). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">20 m</ENT>
                                <ENT>14.025-14.150</ENT>
                                <ENT>14.025-14.150</ENT>
                                <ENT>14.025-14.150 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">  Do</ENT>
                                <ENT>14.175-14.350</ENT>
                                <ENT>14.175-14.350</ENT>
                                <ENT>14.175-14.350 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">17 m</ENT>
                                <ENT>18.068-18.168</ENT>
                                <ENT>18.068-18.168</ENT>
                                <ENT>18.068-18.168 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15 m</ENT>
                                <ENT>21.025-21.200</ENT>
                                <ENT>21.025-21.200</ENT>
                                <ENT>21.025-21.200 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">  Do</ENT>
                                <ENT>21.225-21.450</ENT>
                                <ENT>21.225-21.450</ENT>
                                <ENT>21.225-21.450 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 m</ENT>
                                <ENT>24.89-24.99</ENT>
                                <ENT>24.89-24.99</ENT>
                                <ENT>24.89-24.99 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">10 m</ENT>
                                <ENT>28.0-29.7</ENT>
                                <ENT>28.0-29.7</ENT>
                                <ENT>28.0-29.7 </ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>
                            (d) * * *
                            <PRTPAGE P="40906"/>
                        </P>
                        <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s50,r50,r50,r50,r50">
                            <TTITLE>  </TTITLE>
                            <BOXHD>
                                <CHED H="1">Wavelength band</CHED>
                                <CHED H="1">ITU—Region 1</CHED>
                                <CHED H="1">ITU—Region 2 </CHED>
                                <CHED H="1">ITU—Region 3 </CHED>
                                <CHED H="1">
                                    Sharing requirements see § 97.303 
                                    <LI>(Paragraph) </LI>
                                </CHED>
                            </BOXHD>
                            <ROW RUL="s">
                                <ENT I="25">LF</ENT>
                                <ENT>kHz</ENT>
                                <ENT>kHz</ENT>
                                <ENT>kHz</ENT>
                                <ENT/>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">2200 m</ENT>
                                <ENT/>
                                <ENT>135.7-137.8</ENT>
                                <ENT/>
                                <ENT>(s). </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="25">MF</ENT>
                                <ENT>kHz</ENT>
                                <ENT>kHz</ENT>
                                <ENT>kHz </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="01">160 m</ENT>
                                <ENT>1810-1850</ENT>
                                <ENT>1800-2000</ENT>
                                <ENT>1800-2000</ENT>
                                <ENT>(a), (b), (c). </ENT>
                            </ROW>
                            <ROW RUL="s">
                                <ENT I="25">HF</ENT>
                                <ENT>MHz</ENT>
                                <ENT>MHz</ENT>
                                <ENT>MHz </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">80 m</ENT>
                                <ENT>3.525-3.750</ENT>
                                <ENT>3.525-3.750</ENT>
                                <ENT>3.525-3.750</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">75 m</ENT>
                                <ENT/>
                                <ENT>3.85-4.00</ENT>
                                <ENT>3.85-3.90</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">60 m</ENT>
                                <ENT/>
                                <ENT>5.25-5.40</ENT>
                                <ENT/>
                                <ENT>(t). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">40 m </ENT>
                                <ENT>7.025-7.100</ENT>
                                <ENT>7.025-7.150</ENT>
                                <ENT>7.025-7.100</ENT>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">  Do</ENT>
                                <ENT/>
                                <ENT>7.225-7.300</ENT>
                                <ENT/>
                                <ENT>(a). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">30 m</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>10.10-10.15</ENT>
                                <ENT>(d). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">20 m</ENT>
                                <ENT>14.025-14.150</ENT>
                                <ENT>14.025-14.150</ENT>
                                <ENT>14.025-14.150 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">  Do</ENT>
                                <ENT>14.225-14.350</ENT>
                                <ENT>14.225-14.350</ENT>
                                <ENT>14.225-14.350 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">17 m</ENT>
                                <ENT>18.068-18.168</ENT>
                                <ENT>18.068-18.168</ENT>
                                <ENT>18.068-18.168 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">15 m</ENT>
                                <ENT>21.025-21.200</ENT>
                                <ENT>21.025-21.200</ENT>
                                <ENT>21.025-21.200 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">  Do</ENT>
                                <ENT>21.30-21.45</ENT>
                                <ENT>21.30-21.45</ENT>
                                <ENT>21.30-21.45 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">12 m</ENT>
                                <ENT>24.89-24.99</ENT>
                                <ENT>24.89-24.99</ENT>
                                <ENT>24.89-24.99 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">10 m</ENT>
                                <ENT>28.0-29.7</ENT>
                                <ENT>28.0-29.7</ENT>
                                <ENT>28.0-29.7 </ENT>
                            </ROW>
                        </GPOTABLE>
                        <STARS/>
                        <P>6. Section 97.303 is amended by revising paragraphs (j)(2)(iii) and (j)(2)(iv), and by adding paragraphs (s) and (t) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 97.303 </SECTNO>
                        <SUBJECT>Frequency sharing requirements. </SUBJECT>
                        <STARS/>
                        <P>(j) * * * </P>
                        <P>(2) * * * </P>
                        <P>(iii) The 2390-2417 MHz segment is allocated to the amateur service on a primary basis. </P>
                        <P>(iv) The 2417-2450 MHz segment is allocated to the amateur service on a co-secondary basis with the Federal Government radiolocation service. Amateur stations operating within the 2400-2450 MHz segment must accept harmful interference that may be caused by the proper operation of industrial, scientific, and medical devices operating within the band. </P>
                        <STARS/>
                        <P>(s) No amateur station transmitting in the 135.7-137.8 kHz segment shall cause harmful interference to any Federal fixed or maritime stations; any non-Federal Government fixed station; or, in the polar regions above 60 degrees North latitude, any aeronautical fixed station; nor is any amateur station protected from interference due to the operation of any such station. </P>
                        <P>(t) No amateur station transmitting in the 5.250-5.400 MHz band shall cause harmful interference to stations authorized in the mobile and fixed services; nor is any amateur station protected from interference due to the operation of any such station. </P>
                        <P>7. Section 97.305 is amended by adding an LF entry; and two HF entries in numerical order to the table in paragraph (c) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 97.305 </SECTNO>
                        <SUBJECT>Authorized emission types. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * </P>
                        <GPOTABLE COLS="4" OPTS="L1,tp0,i1" CDEF="s50,r50,r50,r50">
                            <TTITLE>  </TTITLE>
                            <BOXHD>
                                <CHED H="1">Wavelength band </CHED>
                                <CHED H="1">Frequencies </CHED>
                                <CHED H="1">Emission types authorized </CHED>
                                <CHED H="1">
                                    Standards see § 97.307(f), 
                                    <LI>paragraph: </LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="11">LF: </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">2200 m </ENT>
                                <ENT>Entire band </ENT>
                                <ENT>RTTY, data </ENT>
                                <ENT>(14). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22">  </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="11">HF: </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">60 m</ENT>
                                <ENT>Entire band</ENT>
                                <ENT>RTTY, data </ENT>
                                <ENT>(3), (9). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">60 m</ENT>
                                <ENT>Entire band </ENT>
                                <ENT>Phone, image</ENT>
                                <ENT>(1), (2). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22">  </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                        </GPOTABLE>
                        <PRTPAGE P="40907"/>
                        <P>8. Section 97.307 is amended by adding new paragraph (f)(14) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 97.307 </SECTNO>
                        <SUBJECT>Emission standards. </SUBJECT>
                        <STARS/>
                        <P>(f) * * * </P>
                        <P>(14) The bandwidth of the transmitted signal shall not exceed 100 hertz. </P>
                        <P>9. Section 97.313 is amended by adding paragraph (i) to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 97.313 </SECTNO>
                        <SUBJECT>Transmitter power standards. </SUBJECT>
                        <STARS/>
                        <P>(i) No station may transmit with a transmitter power exceeding 100 W PEP in the 135.7-137.8 kHz segment, and the total Effective Isotropic Radiated Power (EIRP) shall not exceed 1 watt. </P>
                    </SECTION>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14774 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <CFR>47 CFR Part 73 </CFR>
                <DEPDOC>[DA 02-1191; MM Docket Nos. 02-114, 02-115; RM-10426, RM-10427] </DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Meridianville, Tuscumbia, Carrollton, and Gurley, AL; Monroe and Luna Pier, MI </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Commission seeks comment on proposals in two separate docketed proceedings in a multiple docket 
                        <E T="03">Notice of Proposed Rule Making.</E>
                         The first, jointly filed by Capstar TX Limited Partnership and Clear Channel Broadcasting Licenses, Inc., proposes the reallotment of Channel 231A from Meridianville, Alabama to Gurley, Alabama, modification of the license of Station WXQX(FM) to reflect the change of community, the deletion of Channel 262C1 from Tuscumbia, Alabama, and allotment of Channel 262C2 at Meridianville, Alabama, and modification of the license of Station WLAY-FM to reflect the change of community. They also request the downgrade of Station WZBQ(FM), Carrollton, Alabama, from Channel 231C to Channel 231C0 to accommodate the modification at Gurley. Channel 231A can be allotted at Gurley at a site 12.8 kilometers (8.0 miles) northwest of the community. Channel 262C2 can be allotted at a site 15.6 kilometers (9.7 miles) west of the community. Channel 231C0 can be allotted at Carrollton at Station WZBQ's licensed site. Coordinates for Channel C0 at Carrollton are 33-13-6 NL and 88-5-46 WL. Coordinates for Channel 231A at Gurley are 34-44-29 NL and 86-30-26 NL. Coordinates for Channel 262C2 at Meridianville are 34-49-06 NL and 86-44-16 WL. The second, filed by Cumulus Licensing Corporation, proposes to reallot Channel 252A from Monroe, Michigan to Luna Pier, Michigan, as that community's first local aural transmission service, and modify the license of Station WTWR(FM) to reflect the change of community. Channel 252A can be reallotted from Monroe to Luna Pier at petitioner's licensed site 4.7 kilometers (2.9 miles) northwest of the community at coordinates 41-50-43 NL and 83-27-12 WL. See 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        . 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be filed on or before July 8, 2002, and reply comments must be filed on or before July 23, 2002. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Victoria M. McCauley, Media Bureau, (202) 418-2180. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a synopsis of the Commission's Notice of Proposed Rule Making, MM Docket Nos. 02-114, and 02-115, adopted May 1, 2002, and released May 17, 2002. The full text of this document is available for public inspection and copying during regular business hours at the FCC Reference Information Center, Portals II, 445 12th Street, SW., Room CY-A257, Washington, DC, 20554. This document may also be purchased from the Commission's duplicating contractor, Qualex International, Portals II, 445 12th Street, SW., Room CY-B402, Washington, DC, 20554, telephone 202-863-2893, facsimile 202-863-2898, or via e-mail 
                    <E T="03">qualexint@aol.com.</E>
                </P>
                <P>
                    The Provisions of the Regulatory Flexibility Act of 1980 do not apply to this proceeding. Members of the public should note that from the time a Notice of Proposed Rule Making is issued until the matter is no longer subject to Commission consideration or court review, all 
                    <E T="03">ex parte</E>
                     contacts are prohibited in Commission proceedings, such as this one, which involve channel allotments. 
                    <E T="03">See</E>
                     47 CFR 1.1204(b) for rules governing permissible 
                    <E T="03">ex parte</E>
                     contacts. 
                </P>
                <P>
                    On August 21, 2000, the Audio Services Division granted a minor change application (BPH-20000424ABJ) for Station WLAY-FM, downgrading its facilities to specify operation on Channel 262C1 in lieu of Channel 262C. 
                    <E T="03">See Report and Order</E>
                     adopted May 29, 2002, and released June 7, 2002 (DA 02-1341). 
                </P>
                <P>
                    For information regarding proper filing procedures for comments, 
                    <E T="03">see</E>
                     47 CFR 1.415 and 1.420. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 73 </HD>
                    <P>Radio broadcasting.</P>
                </LSTSUB>
                  
                <P>For the reasons discussed in the preamble, the Federal Communications Commission proposes to amend 47 CFR Part 73 as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 73—RADIO BROADCAST SERVICES </HD>
                    <P>1. The authority citation for Part 73 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>47 U.S.C. 154, 303, 334, 336. </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 73.202</SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. Section 73.202(b), the Table of FM Allotments under Alabama, is amended by adding Gurley, Channel 231A, by removing Channel 231C and adding Channel 231C0 at Carrollton, by removing Channel 231A and adding Channel 262C2 at Meridianville and by removing Tuscumbia, Channel 262C. </P>
                        <P>3. Section 73.202(b), the Table of FM Allotments under Michigan, is amended by adding Luna Pier, Channel 252A, and by removing Monroe, Channel 252A. </P>
                    </SECTION>
                    <SIG>
                        <FP>Federal Commuications Commission. </FP>
                        <NAME>John A. Karousos, </NAME>
                        <TITLE>Assistant Chief, Audio Division, Office of Broadcast License Policy, Media Bureau. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15098 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="40908"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Agricultural Marketing Service </SUBAGY>
                <DEPDOC>[DA-00-10A] </DEPDOC>
                <SUBJECT>Milk for Manufacturing Purposes and Its Production and Processing; Requirements Recommended for Adoption by State Regulatory Agencies </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Agricultural Marketing Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document amends the recommended manufacturing milk requirements (Recommended Requirements) by updating the existing drug residue monitoring program. The amendment provides State regulatory agencies and the dairy industry with updated guidance in carrying out sampling, testing, and monitoring activities relating to drug residues in manufacturing grade milk. The amendment to update the drug residue monitoring program was initiated at the request of the Dairy Division of the National Association of State Departments of Agriculture (NASDA) and developed in cooperation with NASDA, the Food and Drug Administration (FDA), dairy trade associations, and producer groups. This document also makes final certain other changes to the Recommended Requirements for clarity and consistency. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 17, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Duane R. Spomer, Associate Deputy Administrator for Standards and Grading, AMS/USDA/Dairy Programs, Room 2746 South Building, P.O. Box 96456, Washington, DC 20090-6456, telephone (202) 720-3171, email 
                        <E T="03">Duane.Spomer@usda.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Under the authority of the Agricultural Marketing Act of 1946, as amended (7 U.S.C. 1621-1627), the United States Department of Agriculture (USDA) maintains a set of model regulations relating to quality and sanitation requirements for the production and processing of manufacturing grade milk. These Recommended Requirements are developed by AMS and recommended for adoption and enforcement by the various States that regulate manufacturing grade milk. The purpose of the model requirements is to promote uniformity in State dairy laws and regulations relating to manufacturing grade milk. </P>
                <P>In consultation with representatives from NASDA, State regulatory agencies, FDA, and dairy industry trade associations, the Department prepared the Recommended Requirements to promote uniformity in State dairy laws and regulations for manufacturing grade milk. To accommodate changes that have occurred in the dairy industry, NASDA and various State officials have at times requested USDA to update the Recommended Requirements. </P>
                <P>On May 6, 1993, AMS updated the existing Recommended Requirements and incorporated an expanded drug residue monitoring program based on drug residue provisions for Grade A milk produced under the National Conference on Interstate Milk Shipments (NCIMS) cooperative program (58 FR 26950). Within the NCIMS program, FDA, State regulatory agencies, consumers, and the dairy industry cooperatively develop and modify model regulations that are used to regulate Grade A milk. Since 1993 several drug residue monitoring changes have occurred in the Grade A milk model program. </P>
                <P>
                    During its July 1999 annual meeting, the Dairy Division of NASDA passed a resolution requesting USDA to review the drug residue provisions of the Recommended Requirements and update this document to provide greater consistency with the drug residue requirements currently in place for Grade A milk. AMS reviewed these provisions and developed a draft that identified the changes associated with this request. This draft was provided to State regulatory officials and dairy trade association representatives for informal discussion prior to publication in the 
                    <E T="04">Federal Register</E>
                    . Subsequently, a Notice of Proposal to Change the document, “Milk for Manufacturing Purposes and Its Production and Processing; Requirements Recommended for Adoption by State Regulatory Agencies,” was published in the 
                    <E T="04">Federal Register</E>
                     on April 20, 2001 (66 FR 20226). The Notice of Proposal to Change the document provided for a 60-day comment period that ended on June 19, 2001. No comments were received. 
                </P>
                <P>Accordingly, the changes proposed in the Milk for Manufacturing Purposes and Its Production and Processing: Requirements Recommended for Adoption by State Regulatory Agencies are incorporated in the revised Recommended Requirements. </P>
                <P>
                    The Recommended Requirements (incorporating the changes herein adopted) are available either from the above address or by accessing the information on the Internet at the following address: 
                    <E T="03">http://www.ams.usda.gov/dairy/manufmlk.pdf.</E>
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>(7 U.S.C. 1621-1627) </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>A.J. Yates, </NAME>
                    <TITLE>Administrator, Agricultural Marketing Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15065 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-02-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>Ravalli County Resource Advisory Committee</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Ravalli County Resource Advisory Committee will be meeting to discuss projects to fund this fiscal year. Agenda topics will include Project review, evaluation and selection, and a public forum (question and answer session). The meeting is being held pursuant to the authorities in the Federal Advisory Committee Act (Public Law 92-463) and under the Secure Rural Schools and Community Self-Determination Act of 2000 (Public Law 106-393). The meeting is open to the public.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held on June 25, 2002, 6:30 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The meeting will be held at the Ravalli County Administration 
                        <PRTPAGE P="40909"/>
                        Building, 215 S. 4th Street, Hamilton, Montana. Send written comments to Jeanne Higgins, District Ranger, Stevensville Ranger District, 88 Main Street, Stevensville, MT 59870, by fascimile (406) 777-7423, or electronically to 
                        <E T="03">jmhiggins@fs.fed.us.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jeanne Higgins, Stevensville District Ranger and Designated Federal Officer, Phone: (406) 777-5461.</P>
                    <SIG>
                        <DATED>Dated: June 10, 2002.</DATED>
                        <NAME>Lesley Thompson,</NAME>
                        <TITLE>Acting Forest Supervisor.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15036 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-11-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>Eastern Idaho Resource Advisory Committee; Caribou-Targhee National Forest, Idaho Falls, ID</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to the authorities in the Federal Advisory Committee Act (Public Law 92-463) and under the Secure Rural Schools and Community Self-Determination Act of 2000 (Public Law 106-393) the Caribou-Targhee National Forests' Eastern Idaho Resource Advisory Committee will meet Tuesday, July 9, 2002 in Idaho Falls for a business meeting. The meeting is open to the pubic.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The business meeting will be held on July 9, 2002 from 10 a.m. to 3 p.m.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting location is the Caribou-Targhee National Forest Headquarters Office 1405 Hollipark Drive, Idaho Falls Idaho 83402.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jerry Reese, Caribou-Targhee National Forest Supervisor and Designated Federal Officer, at (208) 524-7500.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The business meeting on July 9, 2002, begins at 10 a.m., at the Caribou-Targhee National Forest Headquarters Office, 1405 Hollipark Drive, Idaho Falls, Idaho. Agenda topics will include project proposal presentations from those projects were invited to this meeting. At the end of meeting, Resource Advisory Committee will make a decision on projects to fund.</P>
                <SIG>
                    <DATED>Dated: June 10, 2002.</DATED>
                    <NAME>Jerry B. Reese,</NAME>
                    <TITLE>Caribou-Targhee Forest Supervisor.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15040  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-11-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE BLIND OR SEVERELY DISABLED </AGENCY>
                <SUBJECT>Procurement List; Proposed Additions </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Committee for Purchase from People Who Are Blind or Severely Disabled. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed additions to Procurement List. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Committee is proposing to add to the Procurement List products and services to be furnished by nonprofit agencies employing persons who are blind or have other severe disabilities. </P>
                    <P>
                        <E T="03">Comments Must be Received on or Before:</E>
                         July 15, 2002.
                    </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled, Jefferson Plaza 2, Suite 10800, 1421 Jefferson Davis Highway, Arlington, Virginia 22202-3259. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sheryl D. Kennerly, (703) 603-7740. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published pursuant to 41 U.S.C. 47(a)(2) and 41 CFR 51-2.3. Its purpose is to provide interested persons an opportunity to submit comments on the possible impact of the proposed actions. </P>
                <P>The U.S. Department of Agriculture's requirements for Bakery Mix are currently on the Procurement List with Advocacy and Resources Corp. (ARC), Cookeville, Tennessee as the producing nonprofit agency. The Committee is proposing to extend the scope of that mandate to include the Defense Supply Center—Philadelphia and to add three additional nonprofit agencies as producers. </P>
                <P>If the Committee approves the proposed additions, the entities of the Federal Government identified in the notice for each product or service will be required to procure the products and services listed below from nonprofit agencies employing persons who are blind or have other severe disabilities. </P>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were: </P>
                <P>1. If approved, the action will not result in any additional reporting, recordkeeping or other compliance requirements for small entities other than the small organizations that will furnish the products and services to the Government. </P>
                <P>2. If approved, the action will result in authorizing small entities to furnish the products and services to the Government. </P>
                <P>3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 46-48c) in connection with the products and services proposed for addition to the Procurement List. Comments on this certification are invited. Commenters should identify the statement(s) underlying the certification on which they are providing additional information. </P>
                <P>The following products and services are proposed for addition to Procurement List for production by the nonprofit agencies listed:</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Products </HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Product/NSN:</E>
                         Bakery Mix 
                    </FP>
                    <FP SOURCE="FP1-2">8920-00-NSH-0001</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Advocacy and Resources Corp. (ARC), Cookeville, Tennessee.
                    </FP>
                    <FP SOURCE="FP1-2">CW Resources, Inc. New Britain, Connecticut,</FP>
                    <FP SOURCE="FP1-2">Knox County Association for Retarded Citizens, Inc., Vincennes, Indiana.</FP>
                    <FP SOURCE="FP1-2">Transylvania Vocational Services, Inc., Brevard, North Carolina </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Defense Supply Center—Philadelphia, Philadelphia, Pennsylvania
                    </FP>
                    <FP SOURCE="FP1-2">This above product is currently on the Procurement List for U.S. Department of Agriculture.</FP>
                    <FP SOURCE="FP1-2">This proposal is to extend the scope of the mandate to include Defense Supply Center—Philadelphia, Pennsylvania and to add three additional producing nonprofit agencies.</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Product/NSN:</E>
                         Marker, Permanent Ink (Colossal)
                    </FP>
                    <FP SOURCE="FP1-2">7520-01-424-4849 (Black)</FP>
                    <FP SOURCE="FP1-2">7520-01-424-4855 (Red)</FP>
                    <FP SOURCE="FP1-2">7520-01-424-4870 (Green)</FP>
                    <FP SOURCE="FP1-2">7520-01-424-4880 (Blue)</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Dallas Lighthouse for the Blind, Inc., Dallas, Texas
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Office Supplies &amp; Paper Products Commodity Center, New York, NY
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Product/NSN:</E>
                         PRC Deck Recoating System
                    </FP>
                    <FP SOURCE="FP1-2">8010-00-NIB-0012</FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Alphapointe Association for the Blind, Kansas City, Missouri
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Fleet Industrial Supply Center, Bremerton, Washington
                    </FP>
                    <HD SOURCE="HD1">Services </HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type/Location:</E>
                         Embroidery of USAF Service Name Tapes &amp; Emboss of Plastic Name Tags, Lackland Air Force Base, Texas
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">NPA:</E>
                         Delaware Division for the Visually Impaired, New Castle, Delaware, Lions Industries for the Blind, Inc., Kinston, North Carolina
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Department of the Air Force  
                    </FP>
                </EXTRACT>
                <FP SOURCE="FP-2">
                    <E T="03">Service Type/Location:</E>
                     Installation Support Services, Fort Hunter Liggett, California
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">NPA:</E>
                     PRIDE Industries, Roseville, California
                    <PRTPAGE P="40910"/>
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Contract Activity:</E>
                     Headquarters Fort McCoy, Fort McCoy, Wisconsin
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Service Type/Location:</E>
                     Janitorial/Custodial, Hubert H. Humphrey Building, Washington, DC
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">NPA:</E>
                     Melwood Horticultural Training Center, Upper Marlboro, Maryland
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Contract Activity:</E>
                     Department of Health &amp; Human Services
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Service Type/Location:</E>
                     Laundry Service, Fort Carson, Colorado
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">NPA:</E>
                     Goodwill Industries of Colorado Springs, Colorado Springs, Colorado
                </FP>
                <FP SOURCE="FP-2">
                    <E T="03">Contract Activity:</E>
                     Department of the Air Force
                </FP>
                <SIG>
                    <NAME>Sheryl D. Kennerly, </NAME>
                    <TITLE>Director, Information Management. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15069 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6353-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>Bureau of Economic Analysis </SUBAGY>
                <SUBJECT>Submission for OMB Review; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce. </P>
                    <P>DOC has submitted to OMB for clearance the following proposal for collection of information under the provisions of the Paperwork Reduction Act of 1995 Public Law 104-13. </P>
                    <P>
                        <E T="03">Title:</E>
                         Institutional Remittances to Foreign Countries. 
                    </P>
                    <P>
                        <E T="03">Agency Form Number:</E>
                         BE-40. 
                    </P>
                    <P>
                        <E T="03">OMB Number:</E>
                         0608-0002. 
                    </P>
                    <P>
                        <E T="03">Type of Review:</E>
                         Renewal of an existing collection. 
                    </P>
                    <P>
                        <E T="03">Burden:</E>
                         3,273 reporting hours. 
                    </P>
                    <P>
                        <E T="03">Number of Respondents:</E>
                         1,336 respondents. 
                    </P>
                    <P>
                        <E T="03">Average Hours Per Response:</E>
                         1.5 hours per annual reporter, 6.0 hours per quarterly reporter. 
                    </P>
                    <P>
                        <E T="03">Needs and Uses:</E>
                         The survey is required in order to obtain comprehensive initial data concerning the transfer of cash grants to foreign countries and their expenditures in foreign countries by U.S. religious, charitable, educational, scientific, and similar organizations. The data are needed primarily to compile the U.S. international accounts. 
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         U.S. religious, charitable, educational, scientific, and similar organizations which transfer cash grants to foreign countries and their expenditures in foreign countries. 
                    </P>
                    <P>
                        <E T="03">Frequency:</E>
                         Quarterly for institutions transferring $1 million or more each year, annually for all others. 
                    </P>
                    <P>
                        <E T="03">Respondent's Obligation:</E>
                         Voluntary. 
                    </P>
                </AGY>
                <AUTH>
                    <HD SOURCE="HED">Legal Authority: </HD>
                    <P>Bretton Woods Agreement Act, Section 8, and E.O. 10033, as amended.</P>
                    <P>
                        <E T="03">OMB Desk Officer:</E>
                         Paul Bugg (202) 395-3093. 
                    </P>
                    <P>Copies of the above information collection proposal can be obtained by calling or writing Departmental Paperwork Clearance Officer, Madeleine Clayton (202) 482-3129, Department of Commerce, Room 6608, 14th Street and Constitution Avenue, NW., Washington, DC 20230. </P>
                    <P>Written comments and recommendations for the proposed information collection should be sent to Paul Bugg, OMB Desk Officer, Room 10201, New Executive Office Building, Washington, DC 20503. </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 11, 2002. </DATED>
                    <NAME>Madeleine Clayton, </NAME>
                    <TITLE>Departmental Paperwork Clearance Officer, Office of the Chief Information Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15077 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-EA-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>Bureau of Industry and Security </SUBAGY>
                <DEPDOC>[Docket No. 020607143-2143-01] </DEPDOC>
                <SUBJECT>List of Unverified Persons in Foreign Countries, Guidance to Exporters as to “Red Flags” </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Industry and Security, Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>As part of its preventive enforcement efforts, the Bureau of Industry and Security (“BIS”) conducts pre-license checks (“PLC”) and post-shipment verifications (“PSV”) on certain export transactions. This notice sets forth a list of persons in foreign countries who were parties in past transactions where PLCs or PSVs could not be conducted for reasons outside the control of the U.S. Government. This notice also advises exporters that the involvement of a listed person as a party to a proposed transaction constitutes a “red flag” as described in the guidance set forth in Supplement No. 3 to 15 CFR part 732. Under that guidance, the “red flag” requires heightened scrutiny by the exporter before proceeding with a transaction in which a listed person is a party. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This notice is effective June 14, 2002. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Thomas W. Andrukonis, Office of Enforcement Analysis, Bureau of Industry and Security, Telephone: (202) 482-4255. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>In administering export controls under the Export Administration Regulations (15 CFR parts 730 to 774) (EAR), BIS carries out a number of preventive enforcement activities with respect to individual export transactions. Such activities are intended to assess diversion risks, identify potential violations, verify end-uses, and determine the suitability of end-users to receive U.S. commodities or technology. In carrying out these activities, BIS officials, or officials of other federal agencies acting on BIS's behalf, selectively conduct pre-licence checks (“PLCs”) to verify the bona fides of the transaction and the suitability of the end-user or ultimate consignee. In addition, such officials sometimes carry out post-shipment verifications (“PSVs”) to ensure that U.S. exports have actually been delivered to the authorized end-user, are being used in a manner consistent with the terms of a license or license exception, and are otherwise consistent with the EAR. </P>
                <P>In certain instances BIS officials, or other federal officials acting on BIS's behalf, have been unable to perform a PLC or PSV with respect to certain export control transactions, for reasons outside the control of the U.S. Government (including a lack of cooperation by the host government authority, the end-user, or the ultimate consignee). This notice sets forth a list of certain foreign end-users and consignees involved in such transactions. The list is called the “Unverified List.” </P>
                <P>The inability of BIS to verify the nature of the activities, or suitability, of any end-user or consignee involved in an export transaction can raise concerns about the bona fides of such person, and that person's suitability for participation in future transactions subject to the EAR. Accordingly, this notice also advises exporters that the participation of a person on the Unverified List in any proposed transaction will be considered by BIS to raise a “red flag” for purposes of the “Know Your Customer” guidance set forth in Supplement No. 3 to 15 CFR part 732. Under that guidance, whenever there is a “red flag,” exporters have an affirmative duty to inquire, verify, or otherwise substantiate the proposed transaction to satisfy themselves that the transaction does not involve a proliferation activity prohibited by part 744, and does not violate other provisions of the EAR. </P>
                <P>
                    The listing of a person on the Unverified List does not equate to a licensing requirement such as that imposed on persons included on the 
                    <PRTPAGE P="40911"/>
                    Entities List in 15 CFR part 744. If an exporter can satisfy himself that the transaction does not involve a proliferation activity and does not violate any other provision of the EAR, the exporter may proceed with the transaction notwithstanding the inclusion of the person on the Unverified List. If an exporter continues to have reasons for concern after the inquiry, the exporter should refrain from such transaction or submit all relevant information to BIS in the form of an application for a license or a request for an advisory opinion. 
                </P>
                <P>Periodically, BIS will add persons to the Unverified List based on the criteria set forth above, and remove the names of persons from the Unverified List when warranted. Moreover, BIS may add to the Unverified List names of persons that BIS discovers are affiliated with a person on the Unverified List by virtue of ownership, control, position of responsibility, or other affiliation or connection in the conduct of trade or business. Any person on the Unverified List may request that BIS review its inclusion on the Unverified List by filing an appeal in accordance with 15 CFR part 756. </P>
                <P>The “Unverified List” is set forth below. </P>
                <SIG>
                    <DATED>Dated: June 11, 2002. </DATED>
                    <NAME>Kenneth I. Juster, </NAME>
                    <TITLE>Under Secretary for Industry and Security.</TITLE>
                </SIG>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s75,r75,r75">
                    <TTITLE>Unverified List </TTITLE>
                    <TDESC>[June 14, 2002] </TDESC>
                    <BOXHD>
                        <CHED H="1">Name </CHED>
                        <CHED H="1">Country </CHED>
                        <CHED H="1">Last known address </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Power Test &amp; Research Institute of Guangzhou</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>No. 38 East Huangshi Road, Guangzhou. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Civil Airport Construction Corporation</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>111 Bei Sihuan Str. East, Chao Yang District, Beijing. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Xian XR Aerocomponents Co., Ltd</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>Xujiawen Beijiao, Xian, Shaanxi. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shaanxi Telecom Measuring Station</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>39 Jixiang Road, Yanta District Xian, Shaanxi. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">S.B. Submarine Systems Co., Ltd</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>1591 Hongqiao Rd., Bldg. 15, Shanghai. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Beijing San Zhong Electronic Equipment Engineer Co., Ltd</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>Hai Dian Fu Yuau, Men Hao 1 Hao, Beijing. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Huabei Petroleum Administration Bureau Logging Company</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>South Yanshan Road, Ren Qiu City, Hebei. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Yunma Aircraft Mfg</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>Yaopu, Anshun, Guizhou. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Daqing Production Logging Institute</ENT>
                        <ENT>People's Republic of China</ENT>
                        <ENT>No. 3 Fengshou Village, Sartu District, Daqing City, Heilongjiang. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Dee Communications M SDN. BHD</ENT>
                        <ENT>Malaysia</ENT>
                        <ENT>G5/G6, Ground Floor, Jin Gereja, Johor Bahru. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arrow Electronics Industries</ENT>
                        <ENT>United Arab Emirates</ENT>
                        <ENT>204 Arbift Tower, Benyas Road, Dubai. </ENT>
                    </ROW>
                    <TNOTE>The Unverified List includes names and countries of foreign persons who in the past were parties to a transaction with respect to which BIS could not conduct a pre-license check (“PLC”) or a post-shipment verification (“PSV”) for reasons outside of the U.S. Government's control. Any transaction to which a listed person is a party will be deemed by BIS to raise a “red flag” with respect to such transaction within the meaning of the guidance set forth in Supplement No. 3 to 15 CFR part 732. The red flag applies to the person on the Unverified List regardless of where the person is located in the country included on the list. </TNOTE>
                </GPOTABLE>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15095 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-33-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-427-822]</DEPDOC>
                <SUBJECT>Notice of Postponement of Final Determination of Antidumping Duty Investigation: Certain Cold-Rolled Carbon Steel Flat Products from France</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Postponement of Final Determination of Antidumping Duty Investigation.</P>
                </ACT>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 14, 2002.)</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Angelica Mendoza, John Drury or Abdelali Elouaradia at (202) 482-3019, (202) 482-0195 and (202) 482-1374, respectively; AD/CVD Enforcement, Office 8, Group III, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW, Washington, DC 20230.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">The Applicable Statute and Regulations</HD>
                <P>Unless otherwise indicated, all citations to the statute are references to the provisions effective January 1, 1995, the effective date of the amendments made to the Tariff Act of 1930 (the Act) by the Uruguay Round Agreements Act (URAA).  In addition, unless otherwise indicated, all citations to the Department of Commerce (Department's) regulations are to the regulations at 19 CFR part 351 (April 2001).</P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On October 18, 2001, the Department initiated antidumping duty investigations of CRCS from a number of countries, including France. 
                    <E T="03">See Notice of Initiation of Antidumping Duty Investigations: Certain Cold-Rolled Carbon Steel Flat Products From Argentina, Australia, Belgium, Brazil, France, Germany, India, Japan, Korea, the Netherlands, New Zealand, the People's Republic of China, the Russian Federation, South Africa, Spain, Sweden, Taiwan, Thailand, Turkey, and Venezuela</E>
                    , 66 FR 54198, (October 26, 2001).  The period of investigation (POI) is July 1, 2000 through June 30, 2001.  On May 9, 2002, the Department published the notice of preliminary determination. 
                    <E T="03">See Notice of Preliminary Determination of Sales at Not Less Than Fair Value: Certain Cold-Rolled Carbon Steel Flat Products from France</E>
                    , 67 FR 31204 (
                    <E T="03">Preliminary Determination</E>
                    ).  On May 29, 2002, the Department published its amended preliminary determination in this investigation. 
                    <E T="03">See Notice of Amended Preliminary Determination of Sales at Less Than Fair Value: Certain Cold-Rolled Carbon Steel Flat Products from France</E>
                    , 67 FR 37387 (
                    <E T="03">Amended Preliminary Determination</E>
                    ).
                </P>
                <HD SOURCE="HD1">Postponement of Final Determination</HD>
                <P>
                    Section 735(a)(2) of the Act provides that a final determination may be postponed until no later than 135 days 
                    <PRTPAGE P="40912"/>
                    after the publication of the preliminary determination if, in the event of an affirmative determination, a request for such postponement is made by exporters who account for a significant proportion of exports of the subject merchandise, or in the event of a negative preliminary determination, a request for such postponement is made by petitioners.  The Department's regulations, at 19 CFR 351.210(e)(2), require that requests by respondents for postponement of a final determination be accompanied by a request for extension of provisional measures from a four-month period to not more than six months.
                </P>
                <P>
                    On May 23, 2002, Usinor Group (respondent) requested that the Department, pursuant to Section 735(a)(2) of the Act, postpone its final determination until not later than 135 days after the date of the publication of the preliminary determination in the 
                    <E T="04">Federal Register</E>
                     and requested extension of provisional measures to a period not to exceed six months.  In accordance with 19 CFR 351.210(b)(2)(ii), because the request was filed in proper form and because (1) our amended preliminary determination was affirmative, (2) the respondent requesting the postponement accounts for a significant proportion of exports of the subject merchandise, and (3) no compelling reasons for denial exist, we are granting the respondent's request and are postponing the final determination until no later than 135 days after the publication of the preliminary determination in the 
                    <E T="04">Federal Register</E>
                    .  Therefore, in accordance with section 735(a)(2) of the Act, the Department is postponing the final determination of the aforementioned investigation until September 23, 2002.  Suspension of liquidation will be extended accordingly.
                </P>
                <P>This notice is published in accordance with section 735(a)(2) of the Act.</P>
                <SIG>
                    <DATED>Dated:  June 6, 2002</DATED>
                    <NAME>Faryar Shirzad,</NAME>
                    <TITLE>Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15099  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT  OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-560-803]</DEPDOC>
                <SUBJECT>Notice of Final Results and Partial Recission of Antidumping Duty Administrative Review: Extruded Rubber Thread From Indonesia</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Final Results and Partial Rescission of Antidumping Duty Administrative Review.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We determine that sales of the subject merchandise have not been made below normal value (“NV”).</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 14, 2002.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>James Terpstra or Lyman Armstrong, AD/CVD Enforcement, Office VI, Group II, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, N.W., Washington, D.C. 20230; telephone: (202) 482-3965 or (202) 482-3601, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Applicable Statute and Regulations</HD>
                <P>Unless otherwise indicated, all citations to the Tariff Act of 1930, as amended (“the Act”), are references to the provisions effective January 1, 1995, the effective date of the amendments made to the Act by the Uruguay Round Agreements Act.  In addition, unless otherwise indicated, all citations to the Department of Commerce (“the Department”) regulations are to 19 CFR Part 351 (April 2001).</P>
                <HD SOURCE="HD1">Case History</HD>
                <P>
                    On February 7, 2002, the Department published the preliminary results of its administrative review of the antidumping duty order on extruded rubber thread from Indonesia. 
                    <E T="03">See Notice of Preliminary Results and Partial Rescission of Antidumping Duty Administrative Review: Extruded Rubber Thread from Indonesia</E>
                    , 67 FR 5786 (“
                    <E T="03">Preliminary Results</E>
                    ”).  As discussed in the preliminary results, this review covers shipments by P.T. Swasthi Parama Mulya (“Swasthi”), during the period of review (“POR”) May 1, 2000 through April 30, 2001.  We invited parties to comment on our preliminary results of review.  In response to the Department's invitation to comment on the preliminary results of this review, Swasthi, a respondent in the case, submitted a letter stating that it would not file any comments regarding the preliminary results unless in response to other comments filed by other interested parties. 
                    <E T="03">See</E>
                     Letter from Swasthi to the Department of Commerce (February 28, 2002).  Interested parties did not submit case briefs nor did they request a hearing.  There have been no changes since the preliminary results.
                </P>
                <HD SOURCE="HD1">Scope of the Review</HD>
                <P>For purposes of this review, the product covered is extruded rubber thread (“ERT”) from Indonesia.  ERT is defined as vulcanized rubber thread obtained by extrusion of stable or concentrated natural rubber latex of any cross sectional shape, measuring from 0.18 mm, which is 0.007 inches or 140 gauge, to 1.42 mm, which is 0.056 inch or 18 gauge, in diameter.</P>
                <P>
                    ERT is currently classified under subheading 4007.00.00 of the 
                    <E T="03">Harmonized Tariff Schedule</E>
                     (HTS).  Although the HTS subheading is provided for convenience and customs purposes, the written description of the scope of this review is dispositive.
                </P>
                <HD SOURCE="HD1">Partial Rescission</HD>
                <P>
                    We originally initiated a review of two companies: Swasthi and Filati Lastex Sdn. Bhd. (“Filati”), (
                    <E T="03">see Notice of Initiation of Antidumping Duty Administrative Review</E>
                    , 66 FR 32934 (June 19, 2001)).  However, as noted in the preliminary results, Filati withdrew its request and there were no additional requests for a review of Filati from any other interested party.  We received no comments concerning Filati for the final results.  Therefore, in accordance with 19 CFR 351.213(d)(3) and consistent with Department practice, we are rescinding our review of Filati (
                    <E T="03">see, e.g., Certain Welded Carbon Steel Pipe and Tube from Turkey: Final Results and Partial Rescission of Antidumping Administrative Review</E>
                    , 63 FR 35190, 35191, (June 29, 1998); 
                    <E T="03">see also, Certain Fresh Cut Flowers From Colombia; Final Results and Partial Rescission of Antidumping Duty Administrative Review</E>
                    , 62 FR 53287, 53288 (October 14, 1997)).
                </P>
                <HD SOURCE="HD1">Price Comparisons</HD>
                <P>
                    We calculated export price and NV based on the same methodology described in the 
                    <E T="03">Preliminary Results</E>
                    .
                </P>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    We gave interested parties an opportunity to comment on the 
                    <E T="03">Preliminary Results</E>
                    .  As noted above, we received no comments from any party.
                </P>
                <PRTPAGE P="40913"/>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>As a result of our review, we determine that Swasthi had a zero weighted-average margin for the period May 1, 2000 through April 30, 2001.</P>
                <HD SOURCE="HD1">Assessment Rate</HD>
                <P>
                    The Department shall determine, and Customs shall assess, antidumping duties on all appropriate entries.  Pursuant to 19 CFR 351.212(b), the Department calculated an assessment rate for each importer of the subject merchandise.  For assessment purposes, we calculated importer-specific assessment rates for the subject merchandise by aggregating the dumping margins for all U.S. sales to each importer and dividing the amount by the total entered value of the sales to that importer.   Where the importer-specific assessment rate is above 
                    <E T="03">de minimis</E>
                     we will instruct Customs to assess antidumping duties on that importer's entries of subject merchandise.
                </P>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>
                    The following deposit rates will be effective upon publication of the final results of this administrative review for all shipments of ERT from Indonesia entered, or withdrawn from warehouse, for consumption on or after the publication date, as provided by section 751(a)(2)(C) of the Act:  (1) The cash deposit rate for Swasthi will be zero; (2) for previously reviewed or investigated companies, the cash deposit rate will continue to be the company-specific rate published for the most recent final results in which that manufacturer or exporter participated; (3) if the exporter is not a firm covered in this review, a prior review, or the original less-than-fair-value (“LTFV”) investigation, but the manufacturer is, the cash deposit rate will be the rate established for the most recent final results for the manufacturer of the merchandise; and (4) if neither the exporter nor the manufacturer is a firm covered in this or any previous review conducted by the Department, the cash deposit rate will be 24.00 percent, the “All Others” rate established in the LTFV investigation. 
                    <E T="03">See Notice of Amended Final Determination of Sales at Less Than Fair Value and Antidumping Duty Order: Extruded Rubber Thread From Indonesia</E>
                    , 64 FR 27755 (May 21, 1999).
                </P>
                <P>These cash deposit requirements, when imposed, shall remain in effect until publication of the final results of the next administrative review.</P>
                <HD SOURCE="HD1">Notification to Importers</HD>
                <P>This notice serves as a  reminder to importers of their responsibility under 19 CFR 351.402 to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period.  Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                <P>This notice also serves as a reminder to parties subject to administrative protective order (“APO”) of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with 19 CFR 351.305.  Timely notification of return/destruction of APO materials or conversion to judicial protective order is hereby requested.  Failure to comply with the regulations and the terms of an APO is a sanctionable violation.</P>
                <P>This determination is issued and published pursuant to sections 751(a) and 777(i) of the Act.</P>
                <SIG>
                    <DATED>Dated:   June 3, 2002.</DATED>
                    <NAME>Faryar Shirzad,</NAME>
                    <TITLE>Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15102 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-351-605]</DEPDOC>
                <SUBJECT>Frozen Concentrated Orange Juice From Brazil; Final Results and Partial Rescission of Antidumping Duty Administrative Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of final results of antidumping duty administrative review.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On April 17, 2002, the Department of Commerce published the preliminary results of administrative review of the antidumping duty order on frozen concentrated orange juice from Brazil (67 FR 18859).  This review covers four manufacturers/exporters of the subject merchandise to the United States.  This review covers the period May 1, 2000, through April 30, 2001.  We have made no changes in the margin calculations.  Therefore, the final results do not differ from the preliminary results.</P>
                    <P>We have determined that no sales have been made below the normal value by Branco Peres Citrus S.A. in this review.  In addition, we have determined to rescind the review with respect to Citrovita Agro-Industrial Ltda., because the request for review was withdrawn, and with respect to CTM Citrus S.A., and Sucorrico S.A., because they had no shipments of subject merchandise to the United States during the period of review.  The final weighted-average dumping margin for the reviewed firm is listed below in the section entitled “Final Results of Review.”</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 14, 2002.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Irina Itkin or Elizabeth Eastwood, Office of AD/CVD Enforcement, Office 2, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW., Washington, DC 20230; telephone (202) 482-0656 or (202) 482-3874, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Applicable Statute and Regulations</HD>
                <P>Unless otherwise indicated, all citations to the Tariff Act of 1930, as amended (the Act), are references to the provisions effective January 1, 1995, the effective date of the amendments made to the Act by the Uruguay Round Agreements Act (URAA).  In addition, unless otherwise indicated, all citations are to the Department of Commerce's (“the Department's”) regulations codified at 19 CFR part 351 (2001).</P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    This review covers four manufacturers/exporters (
                    <E T="03">i.e.</E>
                    , Branco Peres Citrus S.A. (Branco Peres); Citrovita Agro Industrial Ltda. and its affiliated parties Cambuhy MC Industrial Ltda. and Cambuhy Citrus Comercial e Exportadora (collectively, “Citrovita”); CTM Citrus S.A. (CTM); and Sucorrico S.A. (Sucorrico)).
                </P>
                <P>
                    On April 17, 2002, the Department published in the 
                    <E T="04">Federal Register</E>
                     the preliminary results of administrative review of the antidumping duty order on frozen concentrated orange juice (FCOJ) from Brazil. 
                    <E T="03">See Frozen Concentrated Orange Juice from Brazil; Preliminary Results and Partial Recission of Antidumping Duty Administrative Review</E>
                    , 67 FR 18859 (Apr. 17, 2002) (
                    <E T="03">Preliminary Results</E>
                    ).
                </P>
                <P>
                    Sucorrico claimed that it did not have shipments of subject merchandise to the United States.  Because we were able to confirm this with the Customs Service, and because we were also able to confirm that CTM also had no shipments, in accordance with 19 CFR 351.213(d)(3) and consistent with our practice, we are rescinding our review for CTM and Sucorrico.  In January 2002, the petitioners withdrew their request 
                    <PRTPAGE P="40914"/>
                    for review for Citrovita.  Consequently, we are also rescinding our review for Citrovita.  For further discussion, see the “Partial Rescission of Review” section of this notice, below.
                </P>
                <P>We invited parties to comment on our preliminary results of review.  On May 20, 2002, Branco Peres submitted a case brief.  However, Branco Peres withdrew this submission on May 28, 2002, and, thus, we have not considered it for the final results.  The Department has conducted this administrative review in accordance with section 751 of the Act.</P>
                <HD SOURCE="HD1">Scope of the Order</HD>
                <P>The merchandise covered by this order is frozen concentrated orange juice from Brazil. The merchandise is currently classifiable under item 2009.11.00 of the Harmonized Tariff Schedule of the United States (HTSUS).  The HTSUS item number is provided for convenience and for customs purposes.  The written description of the scope of this proceeding is dispositive.</P>
                <HD SOURCE="HD1">Period of Review</HD>
                <P>The period of review (POR) is May 1, 2000, through April 30, 2001.</P>
                <HD SOURCE="HD1">Partial Rescission of Review</HD>
                <P>
                    As noted above, Sucorrico informed the Department that it had no shipments of subject merchandise to the United States during the POR.  We have confirmed with the Customs Service that neither Sucorrico nor CTM had shipments of subject merchandise during the POR.  Therefore, in accordance with 19 CFR 351.213(d)(3) and consistent with the Department's practice, we are rescinding our review with respect to CTM and Sucorrico.  (
                    <E T="03">See e.g., Certain Welded Carbon Steel Pipe and Tube from Turkey; Final Results and Partial Rescission of Antidumping Administrative Review</E>
                    , 63 FR 35190, 35191 (June 29, 1998); and 
                    <E T="03">Certain Fresh Cut Flowers from Colombia; Final Results and Partial Rescission of Antidumping Duty Administrative Review</E>
                    , 62 FR 53287, 53288 (Oct. 14, 1997).)
                </P>
                <P>In addition, on January 9, 2002, the petitioners withdrew their request for an administrative review of Citrovita.  Although the petitioners asked to withdraw their review request after the 90-day time limit specified in 19 CFR 351.213(d)(1), the review for this company had not yet progressed beyond a point where it would have been unreasonable to allow the petitioners to withdraw their request for review.  Therefore, in accordance with 19 CFR 351.213(d)(1) and consistent with our practice, we are also rescinding our review with respect to Citrovita.</P>
                <HD SOURCE="HD1">Cost of Production</HD>
                <P>
                    As discussed in the 
                    <E T="03">Preliminary Results</E>
                    , we conducted an investigation to determine whether Branco Peres made home market sales of the foreign like product during the POR at prices below its cost of production (COP) within the meaning of section 773(b)(1) of the Act.  We calculated the COP for these final results, and performed the cost test, following the same methodology as in the Preliminary Results.
                </P>
                <P>
                    Based on this analysis, we found that 100 percent of Branco Peres' home market sales were made at prices above the COP.  Therefore, we did not disregard any home market sales made by Branco Peres during the POR.  For further discussion, see the 
                    <E T="03">Preliminary Results</E>
                    , 67 FR at 18859.
                </P>
                <HD SOURCE="HD1">Changes Since the Preliminary Results</HD>
                <P>We have made no changes to the margin calculation since the Preliminary Results.</P>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>We determine that the following weighted-average margin percentage exists for the period May 1, 2000, through April 30, 2001:</P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s90,15">
                    <BOXHD>
                        <CHED H="1">Manufacturer/exporter</CHED>
                        <CHED H="1">Percent margin</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Branco Peres</ENT>
                        <ENT>0.00</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The Department shall determine, and the Customs Service shall assess, antidumping duties on all appropriate entries.  Accordingly, we have calculated importer-specific duty assessment rates for the merchandise in question by aggregating the dumping margins calculated for all U.S. sales to each importer and dividing this amount by the total quantity of those sales. The assessment rate will be assessed uniformly on all entries of that particular importer made during the POR.</P>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>The following deposit requirements will be effective upon publication of this notice of final results of administrative review for all shipments of FCOJ from Brazil entered, or withdrawn from warehouse, for consumption on or after the date of publication, as provided by section 751(a)(1) of the Act: (1) The cash deposit rate for the reviewed company will be the rate established in the final results of this review; (2) for previously investigated companies not listed above, the cash deposit rate will continue to be the company-specific rate published for the most recent period; (3) if the exporter is not a firm covered in this review, or the less-than-fair-value (LTFV) investigation, but the manufacturer is, the cash deposit rate will be the rate established for the most recent period for the manufacturer of the merchandise; and (4) the cash deposit rate for all other manufacturers or exporters will continue to be 1.96 percent, the “all others” rate established in the LTFV investigation.</P>
                <P>These deposit requirements, when imposed, shall remain in effect until publication of the final results of the next administrative review.</P>
                <P>This notice also serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period.  Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of doubled antidumping duties.</P>
                <P>This notice serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3).  Timely written notification of return/destruction of APO materials or conversion to judicial protective order is hereby requested.  Failure to comply with the regulations and the terms of an APO is a sanctionable violation.</P>
                <P>We are issuing and publishing this determination and notice in accordance with sections section 751(a)(1) and 777(i) of the Act.</P>
                <SIG>
                    <DATED>Dated:   June 7, 2002.</DATED>
                    <NAME>Faryar Shirzad,</NAME>
                    <TITLE>Assistant Secretary  For Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15100 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-583-830]</DEPDOC>
                <SUBJECT>Stainless Steel Plate in Coils From Taiwan: Final Results and Rescission in Part of Antidumping Duty Administrative Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <PRTPAGE P="40915"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Final Results and Rescission in Part of Antidumping Duty Administrative Review.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On June 19, 2001, the Department of Commerce (“Department”) published a notice of initiation of an antidumping duty administrative review on stainless steel plate in coils from Taiwan.  This review covers two manufacturers/exporters of the subject merchandise, Yieh United Steel Corporation (“YUSCO”), a Taiwanese producer and exporter of subject merchandise, and Ta Chen Stainless Pipe Co., Ltd. (“Ta Chen”), a Taiwanese exporter of subject merchandise. The period of review (“POR”) is May 1, 2000 through April 30, 2001.</P>
                    <P>
                        On February 7, 2002, the Department preliminarily determined that YUSCO's antidumping rate be based on total adverse facts available due to YUSCO's failure to participate in this proceeding.  Therefore, for YUSCO, we applied the highest margin rate applied to YUSCO determined in a prior segment of this proceeding.  With respect to Ta Chen, we preliminarily rescinded this review based on record evidence supporting the conclusion that there were no entries into the United States of subject merchandise during the POR. 
                        <E T="03">See Stainless Steel Plate in Coils From Taiwan; Preliminary Results and Rescission in Part of Antidumping Duty Administrative Review</E>
                        , 67 FR 5789 (February 7, 2002) (“
                        <E T="03">Preliminary Notice</E>
                        ”).  The Department is now publishing its final determination.
                    </P>
                    <P>Petitioners are Allegheny Ludlum, AK Steel Corporation, Butler Armco Independent Union, J&amp;L Specialty Steel, Inc., North American Stainless, United Steelworkers of America, AFL-CIO/CLC, and Zanesville Armco Independent Organization herein called (“Petitioners”).</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 14, 2002.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Stephen Bailey or Robert Bolling, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, N.W., Washington, DC 20230; telephone: (202) 482-1102 and (202) 482-3434 respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Applicable Statute and Regulations</HD>
                <P>Unless otherwise indicated, all citations to the Tariff Act of 1930, as amended (“the Act”), are references to the provisions effective January 1, 1995, the effective date of the amendments made to the Act by the Uruguay Round Agreements Act.  In addition, unless otherwise indicated, all citations to the Department of Commerce's regulations are to 19 CFR part 351 (2001).</P>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On May 21, 1999, the Department of Commerce (“Department”) published the antidumping duty order on stainless steel plate in coils from Taiwan. 
                    <E T="03">See Antidumping Duty Orders; Certain Stainless Steel Plate in Coils From Belgium, Canada, Italy, the Republic of Korea, South Africa, and Taiwan</E>
                    , 64 FR 27756 (May 21, 1999).  On May 1, 2001, the Department published a notice of opportunity to request an administrative review of this order for the period May 1, 2000 through April 30, 2001. 
                    <E T="03">See Antidumping or Countervailing Duty Order, Finding, or Suspended Investigation; Opportunity to Request Administrative Review</E>
                    , 66 FR 21740 (May 1, 2001).  Petitioners timely requested that the Department conduct an administrative review of sales by YUSCO, a Taiwanese producer and exporter of subject merchandise, and Ta Chen, a Taiwanese exporter of subject merchandise.  On June 19, 2001, in accordance with section 751(a) of the Act, the Department published in the Federal Register a notice of initiation of this antidumping duty administrative review of sales by YUSCO and Ta Chen for the period May 1, 2000 through April 30, 2001. 
                    <E T="03">See Initiation of Antidumping and Countervailing Duty Administrative Reviews and Requests for Revocations in Part</E>
                    , 66 FR 32934 (June 19, 2001).  On July 10, 2001, the Department issued its antidumping duty questionnaire to YUSCO and Ta Chen.  On August 2, 2001, Ta Chen reported to the Department that it did not have any U.S. sales, shipments or entries of subject merchandise during the POR, and requested that it not be required to answer the Department's questionnaire.  YUSCO did not respond to the Department's antidumping questionnaire.
                </P>
                <P>
                    On February 7, 2002, the Department preliminarily determined that YUSCO's antidumping rate be based on total adverse facts available due to YUSCO's failure to participate in this proceeding.  With respect to Ta Chen, we preliminarily rescinded this review based on  record evidence and a Customs inquiry, both of which support the conclusion that there were no entries into the United States of subject merchandise during the POR. 
                    <E T="03">See Preliminary Notice</E>
                    , 67 FR 5790.
                </P>
                <P>On March 11, 2002, Petitioners filed their case brief.  Respondents did not file case or rebuttal briefs.  Neither Petitioners nor respondents requested a hearing in the instant review.</P>
                <HD SOURCE="HD1">Scope of the Review</HD>
                <P>For purposes of this review, the product covered is certain stainless steel plate in coils. Stainless steel is an alloy steel containing, by weight, 1.2 percent or less of carbon and 10.5 percent or more of chromium, with or without other elements. The subject plate products are flat-rolled products, 254 mm or over in width and 4.75 mm or more in thickness, in coils, and annealed or otherwise heat treated and pickled or otherwise descaled. The subject plate may also be further processed (e.g., cold-rolled, polished, etc.) provided that it maintains the specified dimensions of plate following such processing.  Excluded from the scope of this review are the following: (1) Plate not in coils, (2) plate that is not annealed or otherwise heat treated and pickled or otherwise descaled, (3) sheet and strip, and (4) flat bars.  In addition, certain cold-rolled stainless steel plate in coils is also excluded from the scope of these orders.  The excluded cold-rolled stainless steel plate in coils is defined as that merchandise which meets the physical characteristics described above that has undergone a cold-reduction process that reduced the thickness of the steel by 25 percent or more, and has been annealed and pickled after this cold reduction process.  The merchandise subject to this review is currently classifiable in the HTS at subheadings: 7219.11.00.30, 7219.11.00.60, 7219.12.00.05, 7219.12.00.20, 7219.12.00.25, 7219.12.00.50, 7219.12.00.55, 7219.12.00.65, 7219.12.0070, 7219.12.00.80, 7219.31.00.10, 7219.90.00.10, 7219.90.00.20, 7219.90.00.25, 7219.90.00.60, 7219.90.00.80, 7220.11.00.00, 7220.20.10.10, 7220.20.10.15, 7220.20.10.60, 7220.20.10.80, 7220.20.60.05, 7220.20.60.10, 7220.20.60.15, 7220.20.60.60, 7220.20.60.80, 7220.90.00.10, 7220.90.00.15, 7220.90.00.60, and 7220.90.00.80.</P>
                <P>Although the HTS subheadings are provided for convenience and Customs purposes, the written description of the merchandise under investigation is dispositive.</P>
                <HD SOURCE="HD1">Period of Review</HD>
                <P>The POR is May 1, 2000 through April 30, 2001.</P>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>
                    All issues raised in the case and rebuttal briefs by parties to this administrative review are addressed in 
                    <PRTPAGE P="40916"/>
                    the “
                    <E T="03">Issues and Decision Memorandum</E>
                    ” (“Issues and Decision Memorandum”) from Joseph A. Spetrini, Deputy Assistant Secretary, Import Administration, to Faryar Shirzad, Assistant Secretary for Import Administration, dated June 7, 2002, which is hereby adopted by this notice.  A list of the issues which parties have raised and to which we have responded, all of which are in the 
                    <E T="03">Decision Memorandum</E>
                    , is attached to this notice as an Appendix.  Parties can find a complete discussion of all issues raised in this review and the corresponding recommendations in this public memorandum which is on file in the Central Records Unit, Room B-099 of the main Department building.  In addition, a complete version of the 
                    <E T="03">Decision Memorandum</E>
                     can be accessed directly on the Web at http://ia.ita.doc.gov/frn/frnhome.htm.  The paper copy and electronic version of the Decision Memorandum are identical in content.
                </P>
                <HD SOURCE="HD1">Facts Available</HD>
                <P>
                    Section 776(a)(2) of the Act provides that if an interested party withholds information that has been requested by the Department, fails to provide such information in a timely manner or in the form requested, significantly impedes a proceeding under the antidumping statute, or provides information that cannot be verified, the Department shall use facts available in reaching the applicable determination.  In selecting from among the facts otherwise available, section 776(b) of the Act authorizes the Department to use an adverse inference if the Department finds that a party has failed to cooperate by not acting to the best of its ability to comply with requests for information. 
                    <E T="03">See also</E>
                     The Statement of Administrative Action to the URAA, H. Doc. 103-316 (1994) at 870 (“SAA”) (further discussing the application of adverse facts available).
                </P>
                <P>For the final results, in accordance with section 776(a)(2) of the Act, we have determined that the use of facts available is appropriate for YUSCO.  We confirmed that YUSCO received, but failed to respond to, the Department's questionnaire.  Because YUSCO has failed to provide any information for our review on the record, we have therefore applied total facts available to the record for YUSCO.</P>
                <P>
                    As noted above, in selecting facts otherwise available, pursuant to section 776(b) of the Act, the Department may use an adverse inference if the Department finds that an interested party, such as YUSCO in this case, failed to cooperate by not acting to the best of its ability to comply with requests for information.  YUSCO has not acted to the best of its ability in this administrative review, failing to fully cooperate with the Department and respond to our questionnaire.  Consistent with Department practice in cases where a respondent fails to cooperate to the best of its ability, and in keeping with section 776(b)(3) of the Act, as adverse facts available we have applied a margin based on the highest margin from this or any prior segment of the proceeding. 
                    <E T="03">See Elemental Sulphur From Canada: Final Results of Antidumping Duty Administrative Review</E>
                    , 65 FR 77567 (December 12, 2000).
                </P>
                <P>
                    The Department notes that while the highest margin calculated during this or any prior segment of the proceeding is 10.20 percent, this margin represents a combined rate applied in a channel transaction in the investigation based on middleman dumping by Ta Chen, which is not present in the instant case.  Where circumstances indicate that a particular margin is not appropriate as adverse facts available, the Department will disregard the margin and determine another, more appropriate one as facts available. 
                    <E T="03">See Fresh Cut Flowers from Mexico; Final Results of Antidumping Duty Administrative Review</E>
                    , 61 FR 6812, 6814 (February 22, 1996) (where the Department disregarded the highest margin for use as adverse facts available because the margin was based on another company's uncharacteristic business expense, resulting in an unusually high margin).  Because the middleman dumping calculated margin would be inappropriate, given that the record indicates that none of YUSCO's exports to the United States during the POR involved a middleman, the Department has applied the highest margin from any segment of the proceeding for YUSCO's exports to the U.S. without a middleman, which is 8.02 percent, the petition rate in the less-than-fair-value (LTFV) investigation.
                </P>
                <P>
                    Section 776(c) of the Act requires the Department to corroborate, to the extent practicable, secondary information used as facts available. Secondary information is described in the SAA as “[i]nformation derived from the petition that gave rise to the investigation or review, the final determination concerning the subject merchandise, or any previous review under section 751 concerning the subject merchandise.” 
                    <E T="03">SAA</E>
                     at 870.  The SAA further provides that “corroborate” means simply that the Department will satisfy itself that the secondary information to be used has probative value. 
                    <E T="03">Id</E>
                     at 870.  Thus, to corroborate secondary information, to the extent practicable, the Department will examine the reliability and relevance of the information used.
                </P>
                <P>
                    In the investigation, the Department determined that the petition margin was fully corroborated by examining the key elements of the U.S. price and normal value calculations on which the petition margin was based, and then comparing the sources used in the petition to YUSCO's reported sales databases. 
                    <E T="03">Notice of Final Determination of Sales at Less Than Fair Value: Stainless Steel Plate in Coils From Taiwan</E>
                    , 64 FR 15493, 15497 (March 31, 1999).  This petition rate was applied to YUSCO in the investigation.  For purposes of this administrative review, we have reviewed the petition and information on the administrative record, and found no reason to believe that the reliability of this information should be called into question.  Further, the Department finds the administrative record of this review does not contain information which indicates that the application of the petition rate would be inappropriate in the instant review.  Therefore, we find that the petition rate is sufficiently reliable and relevant to YUSCO for the present review.
                </P>
                <HD SOURCE="HD1">Partial Rescission of Review</HD>
                <P>
                    Pursuant to 19 CFR 351.213(d)(3), the Department may rescind an administrative review, in whole or only with respect to a particular exporter or producer, if the Secretary concludes that,during the period covered by the review, there were no entries, exports, or sales of the subject merchandise, as the case may be.  As discussed above, in this case the Department is satisfied, after a review of information on the record and a Customs inquiry, that there were no entries of stainless steel plate in coils produced or exported from Ta Chen during the POR.   Therefore, we have decided to rescind this review with respect to Ta Chen in accordance with 19 CFR 351.213(d)(3).  The cash-deposit rate for YUSCO/Ta Chen
                    <SU>1</SU>
                    <FTREF/>
                     will remain as established in the original less-than-fair-value investigation.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         In those situations where Ta Chen is determined by the Department to be engaged in middleman dumping with YUSCO's subject merchandise, the Department will apply a rate which combines both YUSCO's and Ta Chen's cash deposit rates consistent with 19 CFR 351.107(b) and as explained in the Department's Position section of Comment 1 of the 
                        <E T="03">Issues and Decision Memorandum</E>
                        .
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Changes Since the Preliminary Results</HD>
                <P>We have made no changes from the preliminary determination.</P>
                <PRTPAGE P="40917"/>
                <HD SOURCE="HD1">Final Results of Review</HD>
                <P>We determine that the following percentage margin exists for the period May 1, 2000 through April 30, 2001:</P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s90,15">
                    <BOXHD>
                        <CHED H="1">Stainless Steel Plate in Coils from Taiwan</CHED>
                        <CHED H="2">Manufacturer/exporter/reseller</CHED>
                        <CHED H="2">Margin (percent)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">YUSCO</ENT>
                        <ENT>8.02</ENT>
                    </ROW>
                </GPOTABLE>
                <P>The Department shall determine, and U.S. Customs Service shall assess, antidumping duties on all appropriate entries.  The Department will issue appraisement instructions directly to the U.S. Customs Service.  For duty-assessment purposes, we will instruct Customs to assess the rate indicated above against the entered value of the subject merchandise entered during the period of review.</P>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>The following deposit requirements will be effective upon publication of the notice of the final results of this administrative review for all shipments of stainless steel plate in coils from Taiwan entered, or withdrawn from warehouse, for consumption on or after the date of publication, as provided by section 751(a)(1) of the Act: (1) The cash deposit rate for YUSCO will be the rate listed above, unless YUSCO's subject merchandise is exported to the United States through Ta Chen.  If YUSCO's subject merchandise is exported to the United States through Ta Chen, then Customs should continue to apply a cash deposit rate of 10.20 percent; (2) for previously reviewed or investigated companies not listed above, the cash deposit rate will continue to be the company-specific rate published for the most recent period; (3) if the exporter is not a firm covered in this review, a prior review, or the original less-than-fair-value (LTFV) investigation, but the manufacturer is, the cash deposit rate will be the rate established for the most recent period for the manufacturer of the merchandise; and (4) the cash deposit rate for all other manufacturers or exporters will continue to be the “all others” rate of 7.39 percent, which is the all others rate established in the LTFV investigation.These deposit requirements shall remain in effect until publication of the final results of the next administrative review.</P>
                <HD SOURCE="HD1">Notification of Interested Parties</HD>
                <P>This notice serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f)(2) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period.  Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of the antidumping duties occurred and the subsequent assessment of double antidumping duties.</P>
                <P>This notice also serves as a reminder to parties subject to administrative protective orders (“APOs”) of their responsibility concerning the return or destruction of proprietary information disclosed under APO in accordance with 19 CFR 351.305, which continues to govern business proprietary information in this segment of the proceeding.  Timely written notification of the return/destruction of APO materials or conversion to judicial protective order is hereby requested.  Failure to comply with the regulations and terms of an APO is a violation which is subject to sanction.</P>
                <P>This issuing and publishing this determination in accordance with sections 751(a)(1) and 777(i) of the Act.</P>
                <SIG>
                    <DATED>Dated:   June 7, 2002.</DATED>
                    <NAME>Faryar Shirzad,</NAME>
                    <TITLE>Assistant Secretary   for Import Administration.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix</HD>
                <FP>A. Issues with Respect to YUSCO</FP>
                <FP>1.Adverse Facts Available for YUSCO and YUSCO's Subject Merchandise</FP>
                <FP>B. Issues with Respect to Ta Chen</FP>
                <FP>2.Total Adverse Facts Available Rate of 10.20 percent Ad Valorem to Ta Chen's Subject Merchandise</FP>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15101 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Institute of Standards and Technology </SUBAGY>
                <SUBJECT>Advanced Technology Program (ATP) Advisory Committee </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology (NIST), Department of Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for nominations of members to serve on the Advanced Technology Program Advisory Committee. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NIST invites and requests nomination of individuals for appointment to the Advanced Technology Program Advisory Committee. NIST will consider nominations received in response to this notice for appointment to the Committee, in additional to nominations already received. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Please submit nominations on or before July 1, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please submit nominations to Mr. Marc Stanley, National Institute of Standards and Technology, 100 Bureau Drive, Mail Stop 4700, Gaithersburg, MD 20899-4700. Nominations may also be submitted via FAX to 301-869-1150. </P>
                    <P>
                        Additional information regarding the Committee, including its charter and current membership list may be found on its electronic home page at: 
                        <E T="03">http://www.atp.nist.gov/atp/adv_com/ac_menu.htm.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Marc Stanley, National Institute of Standards and Technology, 100 Bureau Drive, Mail Stop 4700, Gaithersburg, MD 20899-4700; telephone 301-975-4644, fax 301-301-869-1150; or via email at 
                        <E T="03">marc.stanley@nist.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Committee will advise the Director of the National Institute of Standards and Technology (NIST) on ATP programs, plans, and policies. </P>
                <P>The Committee will consist of not fewer than six nor more than twelve members appointed by the Director of NIST and its membership will be balanced to reflect the wide diversity of technical disciplines and industrial sectors represented in ATP projects. </P>
                <P>The Committee will function solely as an advisory body, in compliance with the provisions of the Federal Advisory Committee Act. </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Federal Advisory Committee Act: 5 U.S.C. App. 2 and General Services. Administration Rule: 41 CFR Subpart 101-6.10. </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 6, 2002. </DATED>
                    <NAME>Karen H. Brown, </NAME>
                    <TITLE>Deputy Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15029 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Institute of Standards and Technology </SUBAGY>
                <SUBJECT>Visiting Committee on Advanced Technology </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology (NIST), Department of Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for nominations of members to serve on the Visiting Committee on Advanced Technology. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        NIST invites and requests nomination of individuals for appointment to the Visiting Committee on Advanced Technology (VCAT). The 
                        <PRTPAGE P="40918"/>
                        terms of some of the members of the VCAT will soon expire. NIST will consider nominations received in response to this notice for appointment to the Committee, in addition to nominations already received. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Please submit nominations on or before July 1, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please submit nominations to Nancy Miles, Acting Administrative Coordinator, Visiting Committee on Advanced Technology, National Institute of Standards and Technology, 100 Bureau Drive, Mail Stop 1000, Gaithersburg, MD 20899-1000. Nominations may also be submitted via FAX to 301-869-8972. </P>
                    <P>
                        Additional information regarding the Committee, including its charter, current membership list, and executive summary may be found on its electronic home page at: 
                        <E T="03">http://www.nist.gov/director/vcat/vcat.htm.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Nancy Miles, Acting Administrative Coordinator, Visiting Committee on Advanced Technology, National Institute of Standards and Technology, 100 Bureau Drive, Mail Stop 1000, Gaithersburg, MD 20899-1000, telephone 301-975-2300, fax 301-869-8972; or via email at 
                        <E T="03">nancy.miles@nist.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">VCAT Information </HD>
                <P>The VCAT was established in accordance with 15 U.S.C. 278 and the Federal Advisory Committee Act (5 U.S.C. app. 2). </P>
                <HD SOURCE="HD2">Objectives and Duties </HD>
                <P>1. The Committee shall review and make recommendations regarding general policy for NIST, its organization, its budget, and its programs, within the framework of applicable national policies as set forth by the President and the Congress. </P>
                <P>2. The Committee functions solely as an advisory body, in accordance with the provisions of the Federal Advisory Committee Act. </P>
                <P>3. The Committee shall report to the Director of NIST. </P>
                <P>4. The Committee shall provide a written annual report, through the Director of NIST, to the Secretary of Commerce for submission to the Congress on or before January 31 each year. Such report shall deal essentially, though not necessarily exclusively, with policy issues or matters which affect the Institute, or with which the Committee in its official role as the private sector policy adviser of the Institute is concerned. Each such report shall identify areas of research and research techniques of the Institute of potential importance to the long-term competitiveness of United States industry, which could be used to assist United States enterprises and United States industrial joint research and development ventures. The Committee shall submit to the Secretary and the Congress such additional reports on specific policy matters as it deems appropriate. </P>
                <HD SOURCE="HD2">Membership </HD>
                <P>1. The Committee is composed of fifteen members that provide representation of a cross-section of traditional and emerging United States industries. Members shall be selected solely on the basis of established records of distinguished service and shall be eminent in one or more fields such as business, research, new product development, engineering, labor, education, management consulting, environment, and international relations. No employee of the Federal Government shall serve as a member of the Committee. </P>
                <P>2. The Director of the National Institute of Standards and Technology shall appoint the members of the Committee, and they will be selected on a clear, standardized basis, in accordance with applicable Department of Commerce guidance. </P>
                <HD SOURCE="HD2">Miscellaneous </HD>
                <P>
                    1. Members of the VCAT are not paid for their service, but will, upon request, be allowed travel expenses in accordance with 5 U.S.C. 5701 
                    <E T="03">et seq</E>
                    ., while attending meetings of the Committee or of its subcommittees, or while otherwise performing duties at the request of the chairperson, while away from their homes or a regular place of business. 
                </P>
                <P>2. Meetings of the VCAT take place in the Washington, DC metropolitan area, usually at the NIST headquarters in Gaithersburg, Maryland, and once each year at the NIST headquarters in Boulder, Colorado. Meetings are one or two days in duration and are held quarterly. </P>
                <P>3. Committee meetings are open to the public except for approximately one hour, usually at the beginning of the meeting, a closed session is held in accordance with 5 U.S.C. 552b(c)(6), because divulging information discussed in those portions of the meetings is likely to reveal information of a personal nature where disclosure would constitute a clearly unwarranted invasion of personal privacy. All other portions of the meetings are open to the public. </P>
                <HD SOURCE="HD1">Nomination Information </HD>
                <P>1. Nominations are sought from all fields described above. </P>
                <P>2. Nominees should have established records of distinguished service and shall be eminent in fields such as business, research, new product development, engineering, labor, education, management consulting, environment and international relations. The category (field of eminence) for which the candidate is qualified should be specified in the nomination letter. Nominations for a particular category should come from organizations or individuals within that category. A summary of the candidate's qualifications should be included with the nomination, including (where applicable) current or former service on federal advisory boards and federal employment. In addition, each nomination letter should state that the person agrees to the nomination, acknowledge the responsibilities of serving on the VCAT, and will actively participate in good faith in the tasks of the VCAT. Besides participation at meetings, it is desired that members be able to devote the equivalent of two days between meetings to either developing or researching topics of potential interest, and so forth in furtherance of their Committee duties. </P>
                <P>3. The Department of Commerce is committed to equal opportunity in the workplace and seeks a broad-based and diverse VCAT membership. </P>
                <SIG>
                    <DATED>Dated: June 6, 2002. </DATED>
                    <NAME>Karen H. Brown, </NAME>
                    <TITLE>Deputy Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15031 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Institute of Standards and Technology </SUBAGY>
                <SUBJECT>Judges Panel of the Malcolm Baldrige National Quality Award </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology (NIST), Department of Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for nominations of members to serve on the Judges Panel of the Malcolm Baldrige National Quality Award. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        NIST invites and requests nomination of individuals for appointment to the Judges Panel of the Malcolm Baldrige National Quality Award (Judges Panel). The terms of some of the members of the Judges Panel will soon expire. NIST will consider nominations received in 
                        <PRTPAGE P="40919"/>
                        response to this notice for appointment to the Committee, in addition to nominations already received. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Please submit nominations on or before July 1, 2002.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Please submit nominations to Harry Hertz, Director, National Quality Program, NIST, 100 Bureau Drive, Mail Stop 1020, Gaithersburg, MD 20899-1020. Nominations may also be submitted via FAX to 301-948-3716. Additional information regarding the Committee, including its charter, current membership list, and executive summary may be found on its electronic home page at: 
                        <E T="03">http://www.quality.nist.gov.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Harry Hertz, Director, National Quality Program and Designated Federal Official, NIST, 100 Bureau Drive, Mail Stop 1020, Gaithersburg, MD 20899-1020; telephone 301-975-2361; FAX 301-948-3716; or via e-mail at 
                        <E T="03">harry.hertz@nist.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Judges Panel Information</HD>
                <P>The Judges Panel was established in accordance with 15 U.S.C. 3711a(d)(1) , the Federal Advisory Committee Act (5 U.S.C. app. 2), The Malcolm Baldrige National Quality Improvement Act of 1987 (Public Law 101-107).</P>
                <HD SOURCE="HD2">Objectives and Duties </HD>
                <P>1. The Judges Panel will ensure the integrity of the Malcolm Baldrige National Quality Award selection process by reviewing the results of examiners' scoring of written applications, and then voting on which applicants merit site visits by examiners to verify the accuracy of quality improvements claimed by applicants. </P>
                <P>2. The Judges Panel will ensure that individuals on site visit teams for the Award finalists have no conflict of interest with respect to the finalists. The Panel will also review recommendations from site visits, and recommend Award recipients. </P>
                <P>3. The Judges Panel will function solely as an advisory body, and will comply with the provisions of the Federal Advisory Committee Act. </P>
                <P>4. The Panel will report to the Director of NIST.</P>
                <HD SOURCE="HD2">Membership </HD>
                <P>1. The Judges Panel is composed of nine members selected on a clear, standardized basis, in accordance with applicable Department of Commerce guidance. There will be a balanced representation from U.S. service and manufacturing industries, education, and health care and will include members familiar with quality improvement in their area of business. No employee of the Federal Government shall serve as a member of the Judges Panel. </P>
                <P>2. The Judges Panel will be appointed by the Secretary of Commerce and will serve at the discretion of the Secretary. The term of office of each Panel member shall be three years. All terms will commence on March 1 and end on February 28 of the appropriate year. </P>
                <HD SOURCE="HD2">Miscellaneous </HD>
                <P>
                    1. Members of the Judges Panel shall serve without compensation, but may, upon request, be reimbursed travel expenses, including per diem, as authorized by 5 U.S.C. 5701 
                    <E T="03">et seq.</E>
                </P>
                <P>2. The Judges Panel will meet four times per year. Additional meetings may be called as deemed necessary by the NIST Director or by the Chairperson. Meetings are one to four days in duration. In addition, each Judge must attend an annual three-day Examiner training course.</P>
                <P>3. Committee meetings are closed to the public pursuant to Section 10(d) of the Federal Advisory Committee Act, 5 U.S.C. app. 2, as amended by Section 5(c) of the Government in the Sunshine Act, Public Law 94-409, and in accordance with Section 552b(c)(4) of title 5, United States Code. Since the members of the Judges Panel examine records and discuss Award applicant data, the meeting is likely to disclose trade secrets and commercial or financial information obtained from a person may be privileged or confidential. </P>
                <HD SOURCE="HD1">II. Nomination Information </HD>
                <P>1. Nominations are sought from all U.S. service and manufacturing industries, education, and health care as described above. </P>
                <P>2. Nominees should have established records of distinguished service and shall be familiar with the quality improvement operations of manufacturing companies, service companies, small businesses, education and health care organizations. The category (field of eminence) for which the candidate is qualified should be specified in the nomination letter. Nominations for a particular category should come from organizations or individuals within that category. A summary of the candidate's qualifications should be included with the nomination, including (where applicable) current or former service on federal advisory boards and federal employment. In addition, each nomination letter should state that the person agrees to the nomination, acknowledge the responsibilities of serving on the Judges Panel, and will actively participate in good faith in the tasks of the Judges Panel. Besides participation at meetings, it is desired that members be able to devote the equivalent of seventeen days between meetings to either developing or researching topics of potential interest, reading Baldrige applications, and so forth, in furtherance of their Committee duties. </P>
                <P>3. The Department of Commerce is committed to equal opportunity in the workplace and seeks a broad-based and diverse Judges Panel membership. </P>
                <SIG>
                    <DATED>Dated: June 7, 2002. </DATED>
                    <NAME>Karen H. Brown, </NAME>
                    <TITLE>Deputy Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15103 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-25-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Institute of Standards and Technology </SUBAGY>
                <SUBJECT>Manufacturing Extension Partnership National Advisory Board (MEPNAB) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology (NIST), Department of Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Request for nominations of members to serve on the Manufacturing Extension Partnership National Advisory Board.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NIST invites and requests nomination of individuals for appointment to the Manufacturing Extension Partnership National Advisory Board. NIST will consider nominations received in response to this notice for appointment to the Board, in addition to nominations already received. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Please submit nominations on or before July 1, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Please submit nominations to Ms. Linda Acierto, National Institute of Standards and Technology, 100 Bureau Drive, Mail Stop 4800, Gaithersburg, MD 20899-4800. Nominations may also be submitted via FAX to 301-963-6556. </P>
                    <P>
                        Additional information regarding the Board, including its charter and current membership list may be found on its electronic home page at: 
                        <E T="03">http://www.mep.nist.gov/index-nist.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. Linda Acierto, National Institute of Standards and Technology, 100 Bureau Drive, Mail Stop 4800, Gaithersburg, MD 20899-4800; telephone 301-975-5033, fax 301-963-6556; or via email at 
                        <E T="03">linda.acierto@nist.gov.</E>
                        <PRTPAGE P="40920"/>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Board will advise the Director of the National Institute of Standards and Technology (NIST) on MEP programs, plans, and policies. </P>
                <P>The Board will consist of nine individuals appointed by the Director of the National Institute of Standards and Technology (NIST) under the advisement of the Director of MEP. Membership on the Board shall be balanced to represent the views and needs of customers, providers, and others involved in industrial extension throughout the United States. </P>
                <P>The Board will function solely as an advisory body, in compliance with the provisions of the Federal Advisory Committee Act. </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Federal Advisory Committee Act: 5 U.S.C. App. 2 and General Services Administration Rule: 41 CFR Subpart 101-6.10 </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 6, 2002. </DATED>
                    <NAME>Karen H. Brown, </NAME>
                    <TITLE>Deputy Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15030 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Institute of Standards and Technology </SUBAGY>
                <SUBJECT>Announcement of Public Meeting of the National Conference on Weights and Measures </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institute of Standards and Technology, Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that the annual meeting of the National Conference on Weights and Measures will be held July 14 through July 18, 2002, at the Omni Netherland Hotel, Cincinnati, OH. The meeting is open to the public. The National Conference on Weights and Measures is an organization of weights and measures enforcement officials of the States, counties, and cities of the United States, federal representatives, and private sector representatives. The annual meeting of the Conference brings together enforcement officials, other government officials, and representatives of business, industry, trade associations, and consumer organizations to discuss subjects that relate to the field of weights and measures technology and administration. Pursuant to (15 U.S.C. 272(b)(6)), the National Institute of Standards and Technology supports the National Conference on Weights and Measures in order to promote uniformity among the States in the laws, regulations, methods, and testing equipment that comprises regulatory control by the States of commercial weighing and measuring. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The meeting will be held July 14-July 18, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The meeting will be held at the Omni Netherland Hotel, 35 West 5th Street, Cincinnati, OH 45202 </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Henry V. Oppermann, Chief, NIST, Office of Weights and Measures, 100 Bureau Drive, Stop 2350, Gaithersburg, MD 20899-2350. Telephone (301) 975-4004, or E-mail 
                        <E T="03">owm@nist.gov.</E>
                    </P>
                    <SIG>
                        <DATED>Dated: June 6, 2002. </DATED>
                        <NAME>Karen H. Brown, </NAME>
                        <TITLE>Deputy Director. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15032 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY>DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[I.D. 052302B]</DEPDOC>
                <SUBJECT>Endangered Species; File No. 1174</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Issuance of permit modification.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Notice is hereby given that Harold Brundage III, Environmental Research and Consulting, Inc., 112 Commons Court, Chadds Ford, PA 19317, has been issued a permit to take endangered species for purposes of scientific research.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The permit and related documents are available for review upon written request or by appointment in the following office(s):</P>
                    <P>Permits, Conservation and Education Division, Office of Protected Resources, NMFS, 1315 East-West Highway, Room 13705, Silver Spring, MD 20910; phone (301)713--289; fax (301)713-0376.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lillian Becker, (301)713-2289.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On October 16, 2001, notice was published in the 
                    <E T="04">Federal Register</E>
                     (66 FR 200) that a request for scientific research Permit No. 1174 be modified to allow for the implantation of sonic transmitters in shortnose sturgeon.  The requested permits have been issued under the authority of the Endangered Species Act of 1973, as amended (ESA; 16 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ) and the regulations governing the taking, importing, and exporting of endangered and threatened species (50 CFR parts 222-226).
                </P>
                <P>Issuance of this permit, as required by the ESA, was based on a finding that such permit (1) was applied for in good faith, (2) will not operate to the disadvantage of the endangered species which is the subject of this permit, and (3) is consistent with the purposes and policies set forth in section 2 of the ESA.</P>
                <SIG>
                    <DATED>Dated:  June 10, 2002.</DATED>
                    <NAME>Eugene Nitta,</NAME>
                    <TITLE>Acting Chief, Permits, Conservation and Education Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15080 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE  3510-22-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <DEPDOC>[I.D. 052102D]</DEPDOC>
                <SUBJECT>Marine Mammals; File No. 116-1662</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Issuance of permit.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Notice is hereby given that Sea World, Inc., 7007 Sea World Drive, Orlando, Florida 32821, has been issued a permit to import one beluga whale (
                        <E T="03">Delphinapterus leucas</E>
                        ) for purposes of public display.
                    </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The permit and related documents are available for review upon written request or by appointment in the following office(s):</P>
                    <P>Permits, Conservation and Education Division, Office of Protected Resources, NMFS, 1315 East-West Highway, Room 13705, Silver Spring, MD 20910 (301/713-2289); and</P>
                    <P>Regional Administrator, Southwest Region, NMFS, 501 West Ocean Boulevard, Suite 4200, Long Beach, California 90802, (562/980-4000).</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jennifer Skidmore or Amy Sloan, (301/713-2289).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On March 8, 2002, notice was published in the 
                    <E T="04">Federal Register</E>
                     (67 FR 10681) that a request for a public display permit to import one adult male beluga whale had been submitted by the above-named organization.  The requested permit has been issued under the authority of the Marine Mammal Protection Act of 1972, as amended (16 U.S.C. 1361 
                    <E T="03">et seq.</E>
                    ), and the Regulations Governing the Taking and Importing of Marine Mammals (50 CFR part 216).
                </P>
                <SIG>
                    <PRTPAGE P="40921"/>
                    <DATED>Dated:  June 6, 2002.</DATED>
                    <NAME>Eugene T. Nitta,</NAME>
                    <TITLE>Acting Chief, Permits, Conservation and Education Division, Office of Protected Resources, National Marine Fisheries Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14962 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF DEFENSE </AGENCY>
                <SUBAGY>Department of the Army</SUBAGY>
                <SUBJECT>Record of Decision on the Final Environmental Impact Statement (FEIS) on the Disposal and Reuse of the Oakland Army Base, Oakland, CA </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Army, DoD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Record of decision.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of the Army announces its Record of Decision on the FEIS for the disposal and reuse of the Oakland Army BASE. The closure of Oakland Army BASE was mandated in accordance with the Defense BASE Closure and Realignment Act of 1990, Public Law 101-510, as amended.</P>
                    <P>The Record of Decision allows the Army to initiate action to dispose of the excess/surplus property at Oakland Army BASE, in accordance with the Oakland BASE Reuse Authority Amended Draft Final Reuse Plan for the Oakland Army BASE.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES: </HD>
                    <P>A copy of the Record of Decision may be obtained by contacting Mr. Chuck Hubbard, U.S. Army Corps of Engineers, U.S. Army Engineer District, Sacramento, (CESPK-PD), 1325 J Street, Sacramento, CA 95814-2922.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Chuck Hubbard at (916) 557-6958 and or by facsimile at (916) 557-7866.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FEIS analyzes three disposal alternatives with respect to the disposal and subsequent reuse of the 426-acre (approximately 370 acres unsubmerged and 56 acres submerged) comprising the Oakland Army BASE: (1) The no action alternative, under which the property would be maintained in a caretaker status after closure; (2) the unencumbered disposal alternative, under which the Army would transfer the property without use restrictions, such as environmental covenants, land use controls, and easements; and (3) the encumbered disposal alternative, under which the Army would transfer the property with various use restrictions which run with the land and limit future use.</P>
                <P>In the Record of Decision, the Army concludes that the FEIS adequately addresses the impacts of property disposal and documents its decision to transfer the property as encumbered. Possible encumbrances include: covenants and restrictions for asbestos-containing material, lead-BASEd paint, wildlife habitat protection, access easements and rights-of-way.</P>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>Raymond J. Fatz,</NAME>
                    <TITLE>Deputy Assistant Secretary of the Army, (Environment, Safety and Occupational Health), OASA (I&amp;E).</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15005  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3710-08-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF DEFENSE </AGENCY>
                <SUBAGY>Department of the Navy </SUBAGY>
                <SUBJECT>Notice of Availability of Invention for Licensing; Government-Owned Invention </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Navy, DoD. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The invention listed below is assigned to the United States Government as represented by the Secretary of the Navy and is available for licensing by the Department of the Navy. U.S. Patent Number 6,295,911: ENERGY DAMPER AND RECOIL LIMITING SYSTEM FOR LINE CHARGE.//U.S. Patent Number 6,305,877: BREAKWATER/ATTENTUATION DEVICE FOR HIGH SPEED VESSEL WAKE.//U.S. Patent Number 6,308,607: NEUTRALIZING MUNITION.//U.S. Patent Number 6,321,630: THERMOSET/THERMOPLASTIC LINE CHARGE WITH CONTOURED FABRIC FASTENING AND DETONATING CORD MANAGEMENT SYSTEM AND ASSEMBLY PROCESS.//U.S. Patent Number 6,325,015: SYSTEM FOR ARRESTING A SEAGOING VESSEL.//U.S. Patent Number 6,346,141: SUPPLYING BREATHABLE GAS FOR UNDERWATER HABITAT.//U.S. Patent Number 6,347,147: HIGH NOISE SUPPRESSION MICROPHONE.//U.S. Patent Number 6,359,833: UNDERWATER SMALL TARGET WEAPON.//U.S. Patent Number 6,359,834: MINE NEUTRALIZATION DEVICE.//U.S. Patent Number 6,360,495: SAND SPIKE SYSTEM.//U.S. Patent Number 6,362,625: ACTIVE MAGNETIC ANOMALY SENSING SYSTEM HAVING SYNCHRONIZED TRANSCEIVER AND DISCRIMINATOR.//U.S. Patent Number 6,364,253: REMOTE PILOTED VEHICLE POWERED BY BEAMED RADIATION.//U.S. Patent Number 6,366,533: UNDERWATER RECONNAISSANCE AND SURVEILLANCE SYSTEM.//U.S. Patent Number 6,366,534: UNDERWATER HIGH ENERGY ACOUSTIC COMMUNICATIONS DEVICE.//U.S. Patent Number 6,366,887: SIGNAL TRANSFORMATION FOR AURAL CLASSIFICATION.// </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Requests for copies of the patents cited should be directed to the Coastal Systems Station, Dahlgren Division, Naval Surface Warfare Center, 6703 W. Hwy 98, Code XP01L, Panama City, FL 32407-7001, and must include the Navy Case Number. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Harvey A. Gilbert, Counsel, Coastal Systems Station, Naval Surface Warfare Center, 6703 W. Hwy 98, Code XP01L, Panama City, FL 32407-7001, telephone (850) 234-4646. </P>
                    <EXTRACT>
                        <FP>(Authority: 35 U.S.C. 207, 37 CFR part 404.)</FP>
                    </EXTRACT>
                    <SIG>
                        <DATED>Dated: June 3, 2002. </DATED>
                        <NAME>R.E. Vincent II, </NAME>
                        <TITLE>Lieutenant Commander, Judge Advocate General's Corps's, U.S. Navy, Federal Register Liaison Officer. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15055 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3810-FF-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF EDUCATION</AGENCY>
                <SUBJECT>Notice of Proposed Information Collection Requests</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Education.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Leader, Regulatory Information Management Group, Office of the Chief Information Officer, invites comments on the proposed information collection requests as required by the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested persons are invited to submit comments on or before August 13, 2002.</P>
                </DATES>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Section 3506 of the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35) requires that the Office of Management and Budget (OMB) provide interested Federal agencies and the public an early opportunity to comment on information collection requests. OMB may amend or waive the requirement for public consultation to the extent that public participation in the approval process would defeat the purpose of the information collection, violate State or Fedearl law, or  substantially interfere with any agency's ability to perform its statutory obligations. The Leader, Regulatory Information Management Group, Office of the Chief Information Officer, publishes that notice  containing proposed information collection requests prior to submission of these requests to OMB. Each proposed information collection, grouped by 
                    <PRTPAGE P="40922"/>
                    office, contains the following: (1) Type of review requested, e.g. new, revision, extension, existing or reinstatement; (2) Title; (3) Summary of the collection; (4) Descriptionl of the need for, and proposed use of, the information; (5) Respondents and frequency of collection; and (6) Reporting and/or Recordkeeping burden. OMB invites public comment.
                </P>
                <P>The Department of Education is especially interested in public comment addressing the following issues: (1) Is this collection necessary to the proper functions of the Department; (2) will this information be   processed and used in a timely manner; (3) is the estimate of burden accurate; (4) how might the Department enhance the quality, utility, and clarity of the information to be collected; and (5) how might  the Department minimize the burden of this collection on the respondents, including through the use of  information technology.</P>
                <SIG>
                    <DATED>Dated: June 10, 2002.</DATED>
                    <NAME>John Tressler,</NAME>
                    <TITLE>Leader, Regulatory Information Management, Office of the Chief Information Officer.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Office of Educational Research and Improvement</HD>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision.
                </P>
                <P>
                    <E T="03">Title:</E>
                     International Adult Literacy and Lifeskills Survey.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     One time.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or household; Not-for-profit institutions; State, Local, or Tribal Gov't, SEAs or LEAs.
                </P>
                <P>
                    <E T="03">Reporting and Recordkeeping Hour Burden:</E>
                     Responses: 9,740; Burden Hours: 6,731.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The International Adult Literacy and Lifeskills Survey (IALLS) will collect internationally comparable information on the literacy and numeracy performancy of adults from around the world. The IALLS will be administered in the general household population aged 16-65 and in selected federally-funded adult education programs. The IALLS household assessment will provide a detailed picture of the literacy and numeracy skills of U.S. adults compared to adults in other countries. The IALLS adult education program assessment will show the literacy skills of the adults enrolled in adult education programs and how they differ from the U.S. general population and international populations.
                </P>
                <P>
                    Requests for copies of the proposed information collection request may be accessed from 
                    <E T="03">http://edicsweb.ed.gov</E>
                    , by selecting the “Browse Pending Collections” link and by clicking on link number 2063. When you access the information collection, click on “Download Attachments” to view. Written requests for information should be addressed to Vivian Reese, Department of Education, 400 Maryland Avenue, SW., Room 4050, Regional Office Building 3, Washington, DC 20202-4651 or to the e-mail address 
                    <E T="03">vivian_reese@ed.gov.</E>
                     Requests may also be electronically mailed to the internet address 
                    <E T="03">OCIO_RIMG@ed.gov</E>
                     or faxed to 202-708-9346. Please specify the complete title of the information collection when making your request.
                </P>
                <P>
                    Comments regarding burden and/or the collection activity requirements should be directed to Kathy Axt at her internet address 
                    <E T="03">Kathy.Axt@ed.gov.</E>
                     Individuals who use a telecommunications device for the deaf (TDD) may call the Federal Information Relay Service (FIRS) at 1-800-877-8339.
                </P>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15034  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4000-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF ENERGY </AGENCY>
                <SUBAGY>Federal Energy Regulatory Commission </SUBAGY>
                <DEPDOC>[Project No. P-3615-002] </DEPDOC>
                <SUBJECT>Drew River Mill, Inc.; Cancellation of June 20 Site Review </SUBJECT>
                <DATE>June 10, 2002.</DATE>
                <P>On May 24, 2002, the staff of the Office of Energy Projects issued a Notice of Site Review for the Branch River Mill Project for June 20, 2002. At the request of the exemptee, Drew River Mill, Inc., the scheduled site visit has been postponed until further notice.</P>
                <P>For further information, please contact the Commission's Office of External Affairs at (202) 208-1088.</P>
                <SIG>
                    <NAME>Magalie R. Salas,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15023 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6717-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[FRL-7231-3] </DEPDOC>
                <SUBJECT>Proposed Settlement Agreement; Motor Vehicle Emissions Budgets (“MVEBs”) in the Submitted Houston-Galveston Area Attainment Demonstration </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed settlement; request for public comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with section 113(g) of the Clean Air Act (Act), notice is hereby given of a proposed settlement in litigation instituted against the Environmental Protection Agency (EPA) challenging EPA's June 14, 2000, determination of adequacy of the motor vehicle emissions budgets (“MVEBs”) in the submitted Houston-Galveston Area Attainment Demonstration State Implementation Plan for ozone for transportation conformity purposes. Environmental Defense (ED) and several Houston area environmental organizations and individuals challenged EPA's adequacy determination published at 65 FR 37368. 
                        <E T="03">ED, et al.</E>
                         v. 
                        <E T="03">EPA,</E>
                         5th Cir. No. 00-60570. 
                    </P>
                    <P>EPA has entered into a proposed settlement with the litigants in this matter. Under this proposed settlement, the petitioners will dismiss the litigation with prejudice and EPA will take certain actions relating to the ongoing transportation conformity process in the Houston-Galveston Area. </P>
                    <P>For a period of thirty (30) days following the date of publication of this notice, the Agency will receive written comments relating to the proposed settlement. EPA or the Department of Justice may withhold or withdraw consent to the proposed settlement if the comments disclose facts or circumstances that indicate that such consent is inappropriate, improper, inadequate, or inconsistent with the requirements of the Act. </P>
                    <P>Copies of the proposed settlement are available from Phyllis Cochran, Air and Radiation Division (2344A), Office of General Counsel, U.S. Environmental Protection Agency, 1200 Pennsylvania Avenue, NW, Washington, DC 20460, (202) 564-7606. Written comments should be sent to Sara Schneeberg at the above address and must be submitted on or before July 15, 2002. </P>
                </SUM>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>Lisa K. Friedman, </NAME>
                    <TITLE>Associate General Counsel, Air and Radiation Law Office. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15092 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[ER-FRL-6630-2] </DEPDOC>
                <SUBJECT>Environmental Impact Statements; Notice of Availability </SUBJECT>
                <P>
                    <E T="03">Responsible Agency:</E>
                     Office of Federal Activities, General Information (202) 
                    <PRTPAGE P="40923"/>
                    564-7167 or 
                    <E T="03">http://www.epa.gov/compliance/nepa/</E>
                    . 
                </P>
                <FP SOURCE="FP-1">Weekly receipt of Environmental Impact Statements </FP>
                <FP SOURCE="FP-1">Filed June 03, 2002, through June 07, 2002, </FP>
                <FP SOURCE="FP-1">Pursuant to 40 CFR 1506.9.</FP>
                <FP SOURCE="FP-1">EIS No. 020228, FINAL EIS, AFS, ID, Meadow Face Stewardship Pilot Project, Implementation, Nez Perce National Forest, Clearwater Ranger District, Idaho County, ID, Wait Period Ends: July 15, 2002, Contact: Darcy Pederson (208) 983-1963.</FP>
                <FP SOURCE="FP-1">EIS No. 020229, DRAFT EIS, FHW, CA, Butte 70/149/99/191 Highway Improvement Project, Update State Route 149 to Four-Lane Expressway, From 70 North of Oroville to Route 99 South of Chico, Funding, Right-of-Way Acquisition, Endangered Species Act Section 7 and COE Section 404 Permit, Butte County, CA , Comment Period Ends: July 29, 2002, Contact: R. C. Slovensky (916) 498-5774. </FP>
                <FP SOURCE="FP-1">EIS No. 020230, FINAL EIS, AFS, PA, Lewis Run Project, Management Strategies for Road Construction and Reconstruction, Timber Management Activities, Soil and Water Improvements, Wildlife Habitat Enhancements and Recreation Improvements, Implementation, Lewis Run Project Area, Bradford Ranger District, Allegheny National Forest, McKean County, PA, Wait Period Ends: July 15, 2002, Contact: Andrea Hille, Ext 129 (814) 362-4613. </FP>
                <FP SOURCE="FP-1">EIS No. 020231, DRAFT EIS, COE, TX, North Padre Island Storm Damage Reduction and Environmental Restoration Project, Construction of a Channel between the Laguna Madre and the Gulf of Mexico across North Padre Island referred to as Packery Channel Project, Nueces County, IL , Comment Period Ends: July 29, 2002, Contact: Sam J. Watson (409) 766-3964. </FP>
                <FP SOURCE="FP-1">
                    EIS No. 020232, DRAFT EIS, FHW, WY, Wyoming Forest Highway 4 U.S. 212 (KP 39.5 to KP 69.4) the Beartooth Highway, A Portion Proposed for Reconstruction begins 7.l miles east of the Junction of WY-296 (Chief Joseph Highway) and Proceeds East for 18.6 miles to the Wyoming/Montana State Line, Park County, WY, Comment Period Ends: July 29, 2002, Contact: Richard J. Cushing (303) 716-2138. This document is available on the Internet at: 
                    <E T="03">http://www.cflhd.gov/projects/wy/beartooth/index.htm.</E>
                </FP>
                <FP SOURCE="FP-1">EIS No. 020233, DRAFT SUPPLEMENT, FHW, WA, Cross-Base Highway Project, Updated Information, Between I-I5 at the Thorne Lane Interchange and WA-7 at 176th Street South, Major Investment Study (MIS), COE Section 404 Permit, Pierce County, WA , Comment Period Ends: July 31, 2002, Contact: Steve Saxton (360) 753-9411.</FP>
                <FP SOURCE="FP-1">EIS No. 020234, DRAFT EIS, FTA, TX, Northwest Corridor Light Rail Transit (LRT) Line to Farmers Branch and Carrollton, Construction and Operation, NPDES and COE Section 404 Permits, Dallas Area Rapid Transit, Dallas and Denton Counties, TX , Comment Period Ends: July 30, 2002, Contact: John Sweek (817) 975-0550.</FP>
                <SIG>
                    <DATED>Dated: June 11, 2002. </DATED>
                    <NAME>Joseph C. Montgomery, </NAME>
                    <TITLE>Director, NEPA Compliance Division, Office of Federal Activities. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15093 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-60-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[ER-FRL-6630-3] </DEPDOC>
                <SUBJECT>Environmental Impact Statements and Regulations; Availability of EPA Comments </SUBJECT>
                <P>Availability of EPA comments prepared pursuant to the Environmental Review Process (ERP), under section 309 of the Clean Air Act and section 102(2)(c) of the National Environmental Policy Act as amended. Requests for copies of EPA comments can be directed to the Office of Federal Activities at (202) 564-7167. </P>
                <P>An explanation of the ratings assigned to draft environmental impact statements (EISs) was published in FR dated April 12, 2002 (67 FR 17992). </P>
                <HD SOURCE="HD1">Draft EISs </HD>
                <P>ERP No. D-BLM-L65399-OR Rating EC1, Kelsey Whisky Landscape Management Planning Area, Implementation, Associated Medford District Resource Management Plan Amendments, Josephine and Jackson Counties, OR. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed environmental concerns that the project may adversely affect two listed species under the Endangered Species Act. EPA requested that the conclusions from the US Fish and Wildlife Service Biological Opinion be included in the final EIS and referenced in the Record of Decision.
                </P>
                <P>ERP No. DS-NPS-K61121-NV Rating EC2, Great Basin National Park (GRBA) Amendment to the General Management Plan (GMP), Proposal to Construct a Visitor Learning Center on an 80-acre Parcel of Land north of the Town of Baker, White Pine County, NV. </P>
                <P>
                    <E T="03">Summary:</E>
                     expressed environmental concerns about a lack of pollution prevention measures in the project's construction and operation and that there was no discussion on the project's potential water quality impacts, mitigation to protect water quality, or conformity with the Clean Water Act. 
                </P>
                <SIG>
                    <DATED>Dated: June 11, 2002. </DATED>
                    <NAME>Joseph C. Montgomery, </NAME>
                    <TITLE>Director, NEPA Compliance Division, Office of Federal Activities. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15094 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[FRL-7231-5] </DEPDOC>
                <SUBJECT>Escambia Wood Preserving Superfund Sites; Brookhaven Wood Preserving Site—MS, Brunswick Wood Preserving Site—GA, Camilla Wood Preserving Site—GA, Pensacola Wood Preserving Site—FL; Notice of Proposed Settlement </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed settlement.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Environmental Protection Agency is proposing to enter into a settlement with Mr. Charles A. Soule, Jr., pursuant to 122(h)(1) of the Comprehensive Environmental Response, Compensation, and Liability Act of 1980, as amended, regarding the Escambia Wood Preserving Superfund Sites: Brookhaven Wood Preserving Site located in Brookhaven, Lincoln County, Mississippi; Brunswick Wood Preserving Site located in Brunswick, Glynn County, Georgia; Camilla Wood Preserving Site located in Camilla, Mitchell County, Georgia; Pensacola Wood Preserving Site located in Pensacola, Escambia County, Florida. EPA will consider public comments on the proposed settlement for thirty (30) days. EPA may withdraw from or modify the proposed settlement should such comments disclose facts or considerations which indicate the proposed settlement is inappropriate, improper or inadequate. Copies of the proposed settlement are available from: Ms. Paula Batchelor, U.S. EPA Region 4 (WMD-CPSB), Sam Nunn Atlanta Federal Center, 61 Forsyth Street SW, Atlanta, Georgia 30303, (404) 562-8887. Written comments may be submitted to Ms. Batchelor within thirty (30) calendar days of the date of this publication. </P>
                </SUM>
                <SIG>
                    <PRTPAGE P="40924"/>
                    <DATED>Dated: May 15, 2002. </DATED>
                    <NAME>Anita L. Davis, </NAME>
                    <TITLE>Acting Chief, CERCLA Program Services Branch Waste Management Division. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15090 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">EXPORT-IMPORT BANK OF THE UNITED STATES</AGENCY>
                <SUBJECT>Notice of Open Special Meeting of the Advisory Committee of the Export-Import Bank of the United States (Ex-Im Bank)</SUBJECT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Advisory Committee was established by Pub. L. 98-181, November 30, 1983, to advise the Export-Import Bank on its programs and to provide comments for inclusion in the reports of the Export-Import Bank of the United States to Congress.</P>
                    <P>
                        <E T="03">Time and Place:</E>
                         Wednesday, June 19, 2002, at 9:30 a.m. to 12:30 p.m. The meeting will be held at Ex-Im Bank in Room 1143, 811 Vermont Avenue, NW., Washington, DC 20571.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         Agenda items includes discussion on the TPCC report and Competitiveness report and reports for the Advisory Committee's Sub-Committees.
                    </P>
                    <P>
                        <E T="03">Public Participation:</E>
                         The meeting will be open to public participation, and the last 10 minutes will be set aside for oral questions or comments. Members of the public may also file written statement(s) before or after the meeting. If any person wishes auxiliary aids (such as a sign language interpreter) or other special accommodations, please contact, prior to June 15, 2002, Nichole Westin, Room 1257, 811 Vermont Avenue, NW., Washington, DC 20571, Voice: (202) 565-3542 or TDD (202) 565-3377.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For further information, contact Nichole Westin, Room 1257, 811 Vermont Ave., NW., Washington, DC 20571, (202) 565-3542.</P>
                    <SIG>
                        <NAME>Peter Saba,</NAME>
                        <TITLE>General Counsel.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15016  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-M+</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL COMMUNICATIONS COMMISSION </AGENCY>
                <SUBJECT>Notice of Public Information Collection(s) Being Reviewed by the Federal Communications Commission </SUBJECT>
                <DATE>June 7, 2002. </DATE>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Communications Commission, as part of its continuing effort to reduce paperwork burden invites the general public and other Federal agencies to take this opportunity to comment on the following information collection(s), as required by the Paperwork Reduction Act of 1995, Public Law 104-13. An agency may not conduct or sponsor a collection of information unless it displays a currently valid control number. No person shall be subject to any penalty for failing to comply with a collection of information subject to the Paperwork Reduction Act (PRA) that does not display a valid control number. Comments are requested concerning (a) whether the proposed collection of information is necessary for the proper performance of the functions of the Commission, including whether the information shall have practical utility; (b) the accuracy of the Commission's burden estimate; (c) ways to enhance the quality, utility, and clarity of the information collected; and (d) ways to minimize the burden of the collection of information on the respondents, including the use of automated collection techniques or other forms of information technology. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be submitted on or before July 15, 2002. If you anticipate that you will be submitting comments, but find it difficult to do so within the period of time allowed by this notice, you should advise the contact listed below as soon as possible. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all comments to Judith Boley Herman, Federal Communications Commission, Room 1-C804, 445 12th Street, SW., DC 20554 or via the Internet to 
                        <E T="03">jboley@fcc.gov</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For additional information or copies of the information collection(s), contact Judith Boley Herman at 202-418-0214 or via the Internet at 
                        <E T="03">jboley@fcc.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">OMB Control No.:</E>
                     3060-1004. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Orders Re: E911 Act. 
                </P>
                <P>
                    <E T="03">Form No.:</E>
                     N/A. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit, state, not-for-profit institutions, and state, local or tribal governments. 
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     6 respondents; 22 responses. 
                </P>
                <P>
                    <E T="03">Estimated Time Per Response:</E>
                     5 hours. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Recordkeeping requirement, quarterly, semi-annual reporting requirement. 
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     110 hours. 
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     N/A. 
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The quarterly and supplemental reports will be used by the Commission to monitor carrier progress of Phase I and Phase II deployment in transition to E911, and to facilitate the prompt enforcement of the E911 implementation milestones and other requirements of the plans. This will ensure that this important effort will continue in an orderly and timely fashion. The Commission is seeking the full three-year OMB approval for this collection of information. 
                </P>
                <P>
                    <E T="03">OMB Control No.:</E>
                     3060-1008. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Reallocation and Service Rules for the 698-746 MHz Band (Television Channels 52-59). 
                </P>
                <P>
                    <E T="03">Form No.:</E>
                     N/A. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit, and state, local or tribal governments. 
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     734. 
                </P>
                <P>
                    <E T="03">Estimated Time Per Response:</E>
                     .084 hours (five minutes). 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Recordkeeping requirement, on occasion reporting requirement, and third party disclosure requirement. 
                </P>
                <P>
                    <E T="03">Total Annual Burden:</E>
                     367 hours. 
                </P>
                <P>
                    <E T="03">Total Annual Cost:</E>
                     N/A. 
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The Commission adopted allocation and service rules for the 698-746 MHz spectrum band which is being reallocated pursuant to statutory requirements. The Commission took this action to support the development of new services in the lower 700 MHz band, and to protect existing television operations that will occupy the band throughout the transition to digital television. 
                </P>
                <P>Section 27.50(c)(5) provides that licensees intending to operate a base or fixed station at a power level greater than 1 kW ERP must provide advanced notice of such operation to the Commission and to licensees authorized in their area of operation. Notices must provide the location and operating parameters of the base or fixed station operating at a power level greater than 1 kW ERP, including the station's ERP, antenna coordinates, antenna height above ground, and vertical antenna pattern, and such notices must be provided at least 90 days prior to the commencement of station operation. The service rules have been designed to promote the development and rapid deployment of new technologies, products, and services for the benefit of the public; to promote economic opportunity and competition; and to create the efficient and intensive use of the spectrum by promoting the objectives identified in 47 U.S.C. 309(j). </P>
                <SIG>
                    <PRTPAGE P="40925"/>
                    <FP>Federal Communications Commission. </FP>
                    <NAME>Marlene H. Dortch, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15083 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6712-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <DEPDOC>[Report No. 2557]</DEPDOC>
                <SUBJECT>Petitions for Reconsideration and Clarification of Action in Rulemaking Proceeding</SUBJECT>
                <DATE>June 10, 2002.</DATE>
                <P>Petitions for Reconsideration and Clarification have been filed in the Commission's rulemaking proceeding listed in this Public Notice and published pursuant to 47 CFR Section 1.429(e). The full text of this document is available for viewing and copying in Room CY-A257, 445 12th Street, SW., Washington, DC or may be purchased from the Commission's copy contractor, Qualex International (202) 863-2893. Oppositions to these petitions must be filed by July 1, 2002. See Section 1.4(b)(1) of the Commission's rules (47 CFR 1.4(b)(1)). Replies to an opposition must be filed within 10 days after the time for filing oppositions has expired.</P>
                <P>
                    <E T="03">Subject:</E>
                     In the Matter of the 4.9 GHz Band Transferred from Federal Government Use (WT Docket No. 00-32).
                </P>
                <P>
                    <E T="03">Number of Petitions Filed:</E>
                     2.
                </P>
                <SIG>
                    <NAME>Marlene H. Dortch,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15081  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL EMERGENCY MANAGEMENT AGENCY </AGENCY>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Emergency Management Agency (FEMA), as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on a proposed new collection of information. This notice seeks comments concerning the creation and use of evaluation forms for arbitrators and claimants. The request is submitted under the emergency processing procedures in Office of Management and Budget (OMB) regulation 5 CFR 1320.13. FEMA is requesting that this collection of information be approved by July 7, 2002. The approval will authorize FEMA to use the collection through January 31, 2003.. </P>
                    <P>FEMA plans to follow this emergency request with a request for a 3-year approval. The request will be processed under OMB's normal clearance procedures in accordance with the provisions of OMB regulation 5 CFR 1320.10. To help us with the timely processing of the emergency and normal clearance submissions to OMB, FEMA invites the general public to comment on the proposed collection of information. This notice and request for comments is in accordance with the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. 3506(c)(2)(A)). </P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Cerro Grande Fire Assistance Act is authorized under Public Law 106-246, Division C, and is implemented by FEMA regulation 44 CFR 295.46. The Act establishes the Cerro Grande Fire Claim Program to provide assistance to claimants who were adversely impacted when the National Park Service's prescribed burn flared out of control at Bandolier National Monument, New Mexico, on May 4, 2000. This collection of information surveys claimants and arbitrators who participate in the Agency's Alternative Dispute Resolution process. The survey questionnaires provide feedback to the Agency on customer satisfaction and for program quality improvement purposes. It will assist us in complying with goals and objectives of the Government Performance Results Act (GPRA). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>
                    <E T="03">Title:</E>
                     Cerro Grande Arbitrator Questionnaire and Cerro Grande Claimant Questionnaire. 
                </P>
                <P>
                    <E T="03">Type of Information Collection:</E>
                     New. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The survey questionnaires will be used to gather information on how satisfied participants are with the arbitration currently in place. The respective arbitrator and claimant will be asked to complete the survey questionnaire and submit it to FEMA's Alternative Dispute Resolution Office after arbitration. This is strictly voluntary. The information will be collected over the course of the year and submitted to the Office of General Counsel in an End of Year Report. The information will also be formulated to answer specific questions regarding the satisfaction with the program. The information will also provide ways to improve the program so that it continues to provide a fair resolution to the claimant's problems and that its processes are the least burdensome and the most time- and cost-effective to the claimant, the arbitrator, and to the Federal Government. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals and households; business or other for-profit; not-for-profit institutions; farms; Federal government; and State, local or tribal governments. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     205 hours. 
                </P>
                <GPOTABLE COLS="5" OPTS="L2(4,0,4),tp0,i1" CDEF="s100,12,12,12,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">FEMA forms </CHED>
                        <CHED H="1">Number of respondents </CHED>
                        <CHED H="1">Frequency of response </CHED>
                        <CHED H="1">Hours per response </CHED>
                        <CHED H="1">Annual burden hours </CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="25"> </ENT>
                        <ENT>(A)</ENT>
                        <ENT>(B)</ENT>
                        <ENT>(C)</ENT>
                        <ENT>(A × B-× C) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arbitrators</ENT>
                        <ENT>420 </ENT>
                        <ENT>*1</ENT>
                        <ENT>.25 </ENT>
                        <ENT>105 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Claimants </ENT>
                        <ENT>400 </ENT>
                        <ENT>1 </ENT>
                        <ENT>.25 </ENT>
                        <ENT>100 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>428 </ENT>
                        <ENT/>
                        <ENT>.25 </ENT>
                        <ENT>205 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Estimated Cost:</E>
                     The total estimated burden hours is 205 hours based on 428 respondents surveyed once (arbitrators' frequency of response refers to one response per case/arbitration). Arbitrators hourly rate is estimated at $150, or $38 per arbitration. The estimated total annual cost for arbitrators is $15,960. The cost for claimants is estimated at $13.42 per hour or $3.50 per response. The estimated total annual cost for claimants is $1,400. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Written comments are solicited to (a) evaluate whether the 
                    <PRTPAGE P="40926"/>
                    proposed data collection is necessary for the proper performance of the agency, including whether the information shall have practical utility; (b) evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (c) enhance the quality, utility, and clarity of the information to be collected; and (d) minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses. Comments should be received within 60 days of the date of this notice. 
                </P>
                <SUPLHD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Interested persons should submit written comments to Muriel B. Anderson, Chief, Records Management Section, Program Services and Systems Branch, Facilities Management and Services Division, Administration and Resource Planning Directorate, Federal Emergency Management Agency, 500 C Street, SW, Room 316, Washington, DC 20472. </P>
                </SUPLHD>
                <SUPLHD>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Contact Cindy Mazur, ADR Specialist, Federal Emergency Management Agency, 202/646-4094, for additional information. You may contact Ms. Anderson for copies of the proposed collection of information at telephone number (202) 646-2625 or facsimile number (202) 646-3347 or e-mail: 
                        <E T="03">muriel.anderson@fema.gov.</E>
                    </P>
                </SUPLHD>
                <SIG>
                    <DATED>Dated: June 7, 2002. </DATED>
                    <NAME>Muriel B. Anderson, </NAME>
                    <TITLE>Acting Branch Chief, Program Services and Systems Branch, Facilities and Services Management Division, Administration and Resource Planning Directorate. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15051 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6718-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL EMERGENCY MANAGEMENT AGENCY </AGENCY>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Emergency Management Agency, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on the proposed continuation of a collection of information. In accordance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3506(c)(2)(A)), this notice seeks comments concerning the renewal of the National Flood Insurance Program Biennial Report forms. </P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>FEMA is seeking to extend the use of the National Flood Insurance Program Biennial Report forms, which is required by FEMA regulation 44 CFR 59.22(b)(2). The regulation requires that communities participating in the National Flood Insurance Program submit an annual or biennial report describing the progress made during the year in the implementation and enforcement of floodplain management regulations. FEMA has decided that the data be collected on a biennial rather than annual reporting cycle. The data collected on the Biennial Report forms will also be used to assess the need to revise and update all floodplain areas and flood risk zones identified, delineated, or established under section 1360 of the National Flood Insurance Act of 1968. </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>
                    <E T="03">Title:</E>
                     National Flood Insurance Program—Biennial Report. 
                </P>
                <P>
                    <E T="03">Type of Information Collection:</E>
                     Revision of a currently approved collection. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3067-0018. 
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     FEMA 81-28, Emergency and Regular Program (Minimally Floodprone); FEMA Form 81-29, Regular Program (with Base Flood Elevations); and FEMA Form 81-29A, Regular Program (No Special Flood Hazard Areas Designated). 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The National Flood Insurance Program Biennial Report forms provide information on changes to each participating community's flood hazard area, which may include new corporate boundaries, changes in flood hazard areas, new floodplain management measures, and changes in the rate of floodplain development. The information is also used to evaluate the effectiveness of a community's floodplain management activities by analyzing the number of variances and floodplain permits granted by each community against other information in the Biennial Report and the FEMA Community Information System. FEMA regional offices use the information to provide technical assistance to communities implementing a floodplain management program. Information from the forms will be input in FEMA's Mapping Needs Update Support System (MNUSS) for use in ranking and prioritizing one community's mapping needs against all other communities in the National Flood Insurance Program to determine how the limited flood hazard mapping funds will be allocated for map updates. Communities will have the option of responding on-line through a FEMA website or completing the paper forms and returning them via the mail system. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     State, local, or Tribal Government. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     Annual burden ranges from 8,925 “ 13,641 hours with an average of 11,283 hours per year (one-half of the biennial burden hours.) 
                </P>
                <GPOTABLE COLS="5" OPTS="L2,tp0,i1" CDEF="s100,13,13,r50,13">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">FEMA form </CHED>
                        <CHED H="1">Number of responses </CHED>
                        <CHED H="1">
                            Frequency of response 
                            <LI>(biennial) </LI>
                        </CHED>
                        <CHED H="1">Estimated hours per response </CHED>
                        <CHED H="1">Biennial burden hours </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">81-28, Section II Only </ENT>
                        <ENT>5,317 </ENT>
                        <ENT>1 </ENT>
                        <ENT>35 minutes </ENT>
                        <ENT>3,099 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">81-29, Section II Only </ENT>
                        <ENT>12,124</ENT>
                        <ENT>1 </ENT>
                        <ENT>63 minutes </ENT>
                        <ENT>12,773 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">81-28, or 81-29</ENT>
                        <ENT>3,059-7308</ENT>
                        <ENT>1 </ENT>
                        <ENT>.05-1.5 hours</ENT>
                        <ENT>1,530-10,962 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Section I, Estimated average</ENT>
                        <ENT>5,184</ENT>
                        <ENT/>
                        <ENT>1 hour</ENT>
                        <ENT>5,184 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">8-29A</ENT>
                        <ENT>2,246</ENT>
                        <ENT>1</ENT>
                        <ENT>12 minutes</ENT>
                        <ENT>449 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">Total Biennial Hours</ENT>
                        <ENT>22,746-26,995</ENT>
                        <ENT>1</ENT>
                        <ENT/>
                        <ENT>17,851-27,283 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Estimated average </ENT>
                        <ENT>24,871</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>22,567 </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="40927"/>
                <P>
                    <E T="03">Estimated   average Estimated Annual Cost to Respondents:</E>
                     Costs range from $135,503—$269,234 with an average of $202,369 (one-half of the biennial estimated costs). Costs include: respondent's cost at $20.00 per hour to complete section II of FEMA Form 81-28 or 81-29 or FEMA Form 81-29A; responses to Section I of FEMA Form 81-28 or 82-29 at $20.00 per hour; mailing cost at $.34 to return the form; and mailing costs to return supplementary materials or oversized items at $3.00 per response. 
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Written comments are solicited to (a) evaluate whether the proposed data collection is necessary for the proper performance of the agency, including whether the information shall have practical utility; (b) evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used; (c) enhance the quality, utility, and clarity of the information to be collected; and (d) minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.,</E>
                     permitting electronic submission of responses. Comments should be received within 60 days of the date of this notice. 
                </P>
                <SUPLHD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Interested persons should submit written comments to: Muriel B. Anderson, Chief, Records Management Section, Program Services and Systems Branch, Facilities Management and Services Division, Administration and Resource Planning Directorate, Federal Emergency Management Agency, 500 C Street, SW, Room 316, Washington, DC 20472. </P>
                </SUPLHD>
                <SUPLHD>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Contact William Lesser, Federal Insurance and Mitigation Administration, (202) 646-2807, for additional information. Contact Ms. Anderson at (202) 646-2625 (voice), (202) 646-3347(facsimile), or e-mail address: muriel.anderson@fema.gov for copies of the proposed collection of information. </P>
                </SUPLHD>
                <SIG>
                    <DATED>Dated: June 7, 2002. </DATED>
                    <NAME>Muriel B. Anderson, </NAME>
                    <TITLE>Acting Chief, Program Services and Systems Branch, Facilities Management and Services Division, Administration and Resource Planning Directorate. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15052 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6718-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL EMERGENCY MANAGEMENT AGENCY</AGENCY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Emergency Management Agency has submitted the following proposed information collection to the Office of Management and Budget for review and clearance in accordance with the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3507).</P>
                    <P>
                        <E T="03">Title:</E>
                         Claims of Federal Personnel for Personal Property Loss or Damage.
                    </P>
                    <P>
                        <E T="03">Type of Information Collection:</E>
                         Extension of a currently approved collection.
                    </P>
                    <P>
                        <E T="03">OMB Number:</E>
                         3067-0167.
                    </P>
                    <P>
                        <E T="03">Abstract:</E>
                         31 U.S.C 3721 requires FEMA employees who file a claim with the Federal Emergency Management Agency (FEMA) for the loss or damage to personal property to substantiate their claims as a condition of payment by the agency. FEMA personnel provide information to make claims against the agency's substantiation requirements are set forth at 44 CFR 11.76. The information provided by personnel is used by the agency to determine the appropriate disposition and payment of claims.
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         Federal Government.
                    </P>
                    <P>
                        <E T="03">Number of Respondents:</E>
                         7.
                    </P>
                    <P>
                        <E T="03">Estimated Time per Respondent:</E>
                         1 hour.
                    </P>
                    <P>
                        <E T="03">Estimated Total Annual Burden Hours:</E>
                         7 hours.
                    </P>
                    <P>
                        <E T="03">Frequency of Response:</E>
                         On occasion.
                    </P>
                    <P>
                        <E T="03">Comments:</E>
                         Interested persons are invited to submit written comments on the proposed information collection to the Desk Officer for the Federal Emergency Management Agency, Office of Information and Regulatory Affairs, Office of Management and Budget, Washington, DC 20503 within 30 days of the date of this notice.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the information collection should be made to Muriel B. Anderson, Chief, Records Management Section, Program Services and Systems Branch, Facilities Management and Services Division, Administration and Resource Planning Directorate, Federal Emergency Management Agency, 500 C Street, SW., Room 316, Washington, DC 20472, telephone number (202) 646-2625 or facsimile number (202) 646-3347, or e-mail 
                        <E T="03">muriel.anderson@fema.gov.</E>
                    </P>
                    <SIG>
                        <DATED>Dated: June 5, 2002.</DATED>
                        <NAME>Reginald Trujillo,</NAME>
                        <TITLE>Branch Chief, Program Services and Systems Branch, Facilities Management and Services Division, Administration and Resource Planning Directorate.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15053 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6718-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL EMERGENCY MANAGEMENT AGENCY</AGENCY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Emergency Management Agency is submitting a request for review and approval of a collection of information under the emergency processing procedures in the Office of Management and Budget (OMB) regulation 5 CFR 1320.13. FEMA is requesting the collection of information be approved by June 28, 2002, for use through September 30, 2002.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Interested persons should submit written comments to Muriel B. Anderson, Chief, Records Management Section, Program Services and Systems Branch, Facilities Management and Services Division, Administration and Resource Planning Directorate, Federal Emergency Management Agency, 500 C Street, SW, Room 316, Washington, DC 20472.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Contact Laurie Wivell, National Emergency Training Center, Training Division (301) 447-1216 for additional information. You may contact Ms. Anderson for copies of the proposed collection of information at telephone number (202) 646-2625 or facsimile number (202) 646-3347 or e-mail 
                        <E T="03">muriel.anderson@fema.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Emergency Management Institute (EMI) develops courses and administers resident and nonresident training programs in areas such as natural hazards, technical hazards, instructional methodology, professional development, leadership, exercise design and evaluation, information technology, public information, integrated emergency management, and train-the-trainer. A significant portion of the training is conducted by State emergency management agencies under cooperative agreements with FEMA.</P>
                <P>
                    In order to meet current information needs of EMI staff and management, the EMI uses this course evaluation form to 
                    <PRTPAGE P="40928"/>
                    identify problems with course materials, delivery, facilities, and instructors. This is a resident evaluation form. EMI staff will use the information to monitor and recommend changes in course materials, student selection criteria, training experience, and classroom environment. Reports will be generated and distributed to EMI management and staff. Without the information it will be difficult to determine the need for improvements and the degree of student satisfaction with each course. The respondents are students attending EMI resident courses. The evaluation form will be administered at the end of the course and will take no more than 10 minutes to complete. Contractors will scan the evaluation forms and generate the data reports using a computer program developed by a FEMA program analyst contractor. Evaluation forms are destroyed in accordance with FEMA's records retention schedule.
                </P>
                <HD SOURCE="HD1">Collection of Information</HD>
                <P>
                    <E T="03">Title:</E>
                     Emergency Management Institute Resident Course Evaluation Form.
                </P>
                <P>
                    <E T="03">Type of Information Collection:</E>
                     Reinstatement, without change, of a previously approved collection for which approval has expired.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3067-0237.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Students attending the Emergency Management Institute resident program courses at FEMA's National Emergency Training Center will be asked to complete a course evaluation form. The information will be used by EMI staff and management to identify problems with course materials, and evaluate the quality of the course delivery, facilities, and instructors. The data received will enable them to recommend changes in course materials, student selection criteria, and training experience and classroom environment.
                </P>
                <P>
                    <E T="03">FEMA Form:</E>
                     95-41.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     State, Local or Tribal Government; Individuals or Households; and Federal Government.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     667 hours.
                </P>
                <P>
                    <E T="03">Estimated Cost:</E>
                     $12,850, which includes operational and user costs.
                </P>
                <P>
                    <E T="03">Comments:</E>
                     Written comments are solicited to (a) evaluate whether the proposed data collection is necessary for the proper performance of the agency, including whether the information shall have practical utility; (b) evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information; (c) enhance the quality, utility, and clarity of the information to be collected; and (d) minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.</E>
                     permitting electronic submission of responses.
                </P>
                <FP>
                    <E T="02">ADDRESSES:</E>
                     Interested persons should submit written comments to Muriel B. Anderson, Chief, Records Management Section, Program Services and Systems Branch, Facilities Management and Services Division, Administration and Resource Planning Directorate, Federal Emergency Management Agency, 500 C Street, SW, Room 316, Washington, DC 20472.
                </FP>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Contact Laurie Wivell, National Emergency Training Center, Training Division (301) 447-1216 for additional information. You may contact Ms. Anderson for copies of the proposed collection of information at telephone number (202) 646-2625 or facsimile number (202) 646-3347 or e-mail 
                        <E T="03">muriel.anderson@fema.gov.</E>
                    </P>
                    <SIG>
                        <DATED>Dated: June 5, 2002.</DATED>
                        <NAME>Reginald Trujillo,</NAME>
                        <TITLE>Chief, Program Services &amp; Systems Branch, Facilities Management &amp; Services Division, Administration and Resource Planning Directorate.</TITLE>
                    </SIG>
                </FURINF>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15054 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6718-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL EMERGENCY MANAGEMENT AGENCY </AGENCY>
                <DEPDOC>[FEMA-1416-DR] </DEPDOC>
                <SUBJECT>Illinois; Amendment No. 3 to Notice of a Major Disaster Declaration </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency (FEMA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice amends the notice of a major disaster declaration for the State of Illinois, (FEMA-1416-DR), dated May 21, 2002, and related determinations. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 6, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rich Robuck, Readiness, Response and Recovery and Directorate, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705 or 
                        <E T="03">Rich.Robuck@fema.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The notice of a major disaster declaration for the State of Illinois is hereby amended to include Public Assistance in the following areas among those areas determined to have been adversely affected by the catastrophe declared a major disaster by the President in his declaration of May 21, 2002: </P>
                <EXTRACT>
                    <P>Alexander, Brown, Calhoun, Cass, Clark, Cumberland, Douglas, Edgar, Fulton, Gallatin, Greene, Jackson, Jasper, Jersey, Johnson, Lawrence, Macoupin, Mason, Menard, Morgan, Moultrie, Pike, Pope, Pulaski, Randolph, Saline, Sangamon, Schuyler, Scott, Shelby, Union, Wabash, and Wayne Counties for Public Assistance (already designated for Individual Assistance).</P>
                </EXTRACT>
                <SIG>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 83.537, Community Disaster Loans; 83.538, Cora Brown Fund Program; 83.539, Crisis Counseling; 83.540, Disaster Legal Services Program; 83.541, Disaster Unemployment Assistance (DUA); 83.542, Fire Suppression Assistance; 83.543, Individual and Family Grant (IFG) Program; 83.544, Public Assistance Grants; 83.545, Disaster Housing Program; 83.548, Hazard Mitigation Grant Program.) </FP>
                    <NAME>Joe M. Allbaugh, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15049 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6718-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL EMERGENCY MANAGEMENT AGENCY </AGENCY>
                <DEPDOC>[FEMA-1413-DR] </DEPDOC>
                <SUBJECT>Michigan; Amendment No. 3 to Notice of a Major Disaster Declaration </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency (FEMA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice amends the notice of a major disaster for the State of Michigan (FEMA-1413-DR), dated May 6, 2002, and related determinations. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 6, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rich Robuck, Readiness, Response and Recovery Directorate, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705 or 
                        <E T="03">Rich.Robuck@fema.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given that the incident period for this disaster is reopened. The incident period for this declared disaster is now April 10, 2002, through May 9, 2002. </P>
                <SIG>
                    <FP>
                        (The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 83.537, Community Disaster Loans; 83.538, Cora Brown Fund Program; 83.539, Crisis Counseling; 83.540, Disaster Legal Services Program; 83.541, Disaster Unemployment Assistance (DUA); 83.542, Fire Suppression Assistance; 83.543, Individual and Family Grant (IFG) Program; 83.544, Public Assistance Grants; 83.545, Disaster Housing 
                        <PRTPAGE P="40929"/>
                        Program; 83.548, Hazard Mitigation Grant Program.) 
                    </FP>
                    <NAME>Joe M. Allbaugh, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15048 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6718-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL EMERGENCY MANAGEMENT AGENCY </AGENCY>
                <DEPDOC>[FEMA-1417-DR] </DEPDOC>
                <SUBJECT>Federated States of Micronesia; Major Disaster and Related Determinations </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency (FEMA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is a notice of the Presidential declaration of a major disaster for the Federated States of Micronesia (FEMA-1417-DR), dated May 29, 2002, and related determinations. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>May 29, 2002. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Richard A. Robuck, Readiness, Response and Recovery Directorate, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705 or 
                        <E T="03">Rich.Robuck@fema.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given that, in a letter dated May 29, 2002, the President declared a major disaster under the authority of the Robert T. Stafford Disaster Relief and Emergency Assistance Act, 42 U.S.C. 5121-5206 (the Stafford Act), as follows: </P>
                <EXTRACT>
                    <P>I have determined that the damage in certain areas of the Federated States of Micronesia, resulting from Typhoon Mitag on February 26, 2002, through March 3, 2002, is of sufficient severity and magnitude to warrant a major disaster declaration under the Robert T. Stafford Disaster Relief and Emergency Assistance Act, 42 U.S.C. 5121-5206 (Stafford Act). I, therefore, declare that such a major disaster exists in the Federated States of Micronesia. </P>
                    <P>In order to provide Federal assistance, you are hereby authorized to allocate from funds available for these purposes, such amounts as you find necessary for Federal disaster assistance and administrative expenses. </P>
                    <P>You are authorized to provide Public Assistance, including direct Federal assistance in the designated areas, and Hazard Mitigation throughout the Federated States of Micronesia, and any other forms of assistance under the Stafford Act you may deem appropriate. Consistent with the requirement that Federal assistance be supplemental, any Federal funds provided under the Stafford Act for Public Assistance, including direct Federal assistance, and Hazard Mitigation will be limited to 75 percent of the total eligible costs. If Individual Assistance is later requested and warranted, Federal funds provided under the Individual and Family Grant program will also be limited to 75 percent of the total eligible costs. </P>
                    <P>Further, you are authorized to make changes to this declaration to the extent allowable under the Stafford Act. </P>
                </EXTRACT>
                <P>Notice is hereby given that pursuant to the authority vested in the Director of the Federal Emergency Management Agency under Executive Order 12148, I hereby appoint William L. Carwile III of the Federal Emergency Management Agency to act as the Federal Coordinating Officer for this declared disaster. </P>
                <P>I do hereby determine the following areas of the Federated States of Micronesia to have been affected adversely by this declared major disaster: </P>
                <FP SOURCE="FP-1">Yap State for Public Assistance. </FP>
                <FP SOURCE="FP-1">Emergency feeding program for Eauripik, Elato, Ifalik, Lamotrek, Ngulu, Satawal, and Woleai within Yap State. </FP>
                <P>All areas within the Federated States of Micronesia are eligible to apply for assistance under the Hazard Mitigation Grant Program. </P>
                <SIG>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 83.537, Community Disaster Loans; 83.538, Cora Brown Fund Program; 83.539, Crisis Counseling; 83.540, Disaster Legal Services Program; 83.541, Disaster Unemployment Assistance (DUA); 83.542, Fire Suppression Assistance; 83.543, Individual and Family Grant (IFG) Program; 83.544, Public Assistance Grants; 83.545, Disaster Housing Program; 83.548, Hazard Mitigation Grant Program.) </FP>
                    <NAME>Joe M. Allbaugh, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15050 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6718-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL EMERGENCY MANAGEMENT AGENCY </AGENCY>
                <DEPDOC>[FEMA-1412-DR] </DEPDOC>
                <SUBJECT>Missouri; Amendment No. 5 to Notice of a Major Disaster Declaration </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency (FEMA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice amends the notice of a major disaster declaration for the State of Missouri, (FEMA-1412-DR), dated May 6, 2002, and related determinations. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>May 31, 2002. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Richard A. Robuck, Readiness, Response and Recovery and Directorate, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705 or 
                        <E T="03">Rich.Robuck@fema.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The notice of a major disaster declaration for the State of Missouri is hereby amended to include the following areas among those areas determined to have been adversely affected by the catastrophe declared a major disaster by the President in his declaration of May 6, 2002: </P>
                <EXTRACT>
                    <P>Cedar, Crawford, Laclede, McDonald, Oregon, Ozark, Shannon, Ste. Genevieve, Stone, Vernon, and Wright Counties for Public Assistance (already designated for Individual Assistance). </P>
                    <P>Dekalb, Lincoln, Maries, Marion, Miller, Osage, Phelps, Pike, Pulaski, Ralls, and Ray Counties for Public Assistance. </P>
                </EXTRACT>
                <SIG>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 83.537, Community Disaster Loans; 83.538, Cora Brown Fund Program; 83.539, Crisis Counseling; 83.540, Disaster Legal Services Program; 83.541, Disaster Unemployment Assistance (DUA); 83.542, Fire Suppression Assistance; 83.543, Individual and Family Grant (IFG) Program; 83.544, Public Assistance Grants; 83.545, Disaster Housing Program; 83.548, Hazard Mitigation Grant Program.) </FP>
                    <NAME>Joe M. Allbaugh, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15047 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6718-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL EMERGENCY MANAGEMENT AGENCY </AGENCY>
                <DEPDOC>[FEMA-1410-DR] </DEPDOC>
                <SUBJECT>West Virginia; Amendment No. 4 to Notice of a Major Disaster Declaration </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency (FEMA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice amends the notice of a major disaster declaration for the State of West Virginia, (FEMA-1410-DR), dated May 5, 2002, and related determinations. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 6, 2002. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Rich Robuck, Readiness, Response and Recovery and Directorate, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705 or 
                        <E T="03">Rich.Robuck@fema.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The notice of a major disaster declaration for the State of West Virginia is hereby amended to include the following areas among those areas determined to have been adversely affected by the catastrophe declared a major disaster by the President in his declaration of May 5, 2002: 
                    <PRTPAGE P="40930"/>
                </P>
                <P>Kanawha and Raleigh Counties for Individual Assistance. </P>
                <SIG>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 83.537, Community Disaster Loans; 83.538, Cora Brown Fund Program; 83.539, Crisis Counseling; 83.540, Disaster Legal Services Program; 83.541, Disaster Unemployment Assistance (DUA); 83.542, Fire Suppression Assistance; 83.543, Individual and Family Grant (IFG) Program; 83.544, Public Assistance Grants; 83.545, Disaster Housing Program; 83.548, Hazard Mitigation Grant Program.) </FP>
                    <NAME>Joe M. Allbaugh, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15046 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6718-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention </SUBAGY>
                <DEPDOC>[30DAY-36-02] </DEPDOC>
                <SUBJECT>Agency Forms Undergoing Paperwork Reduction Act Review </SUBJECT>
                <P>The Centers for Disease Control and Prevention (CDC) publishes a list of information collection requests under review by the Office of Management and Budget (OMB) in compliance with the Paperwork Reduction Act (44 U.S.C. Chapter 35). To request a copy of these requests, call the CDC Reports Clearance Officer at (404) 498-1210. Send written comments to CDC, Desk Officer, Human Resources and Housing Branch, New Executive Office Building, Room 10235, Washington, DC 20503. Written comments should be received within 30 days of this notice. </P>
                <P>
                    <E T="03">Proposed Project:</E>
                     National Ambulatory Medical Care Survey (OMB No. 0920-0234)—Revision—National Center for Health Statistics (NCHS), Centers for Disease Control and Prevention (CDC). The National Ambulatory Medical Care Survey (NAMCS) was conducted annually from 1973 to 1981, again in 1985, and resumed as an annual survey in 1989. It is directed by the Division of Health Care Statistics, National Center for Health Statistics, CDC. The purpose of NAMCS is to meet the needs and demands for information about the provision of ambulatory medical care services in the United States. Ambulatory services are rendered in a wide variety of settings, including physicians' offices and hospital outpatient and emergency departments. The NAMCS target population consists of all office visits within the United States made by ambulatory patients to non-Federal office-based physicians (excluding those in the specialties of anesthesiology, radiology, and pathology) who are engaged in direct patient care. Since more than 80 percent of all direct ambulatory medical care visits occur in physicians' offices, the NAMCS provides data on the majority of ambulatory medical care services. To complement these data, in 1992 NCHS initiated the National Hospital Ambulatory Medical Care Survey (NHAMCS, OMB No. 0920-0278) to provide data concerning patient visits to hospital outpatient and emergency departments. The NAMCS, together with the NHAMCS constitute the ambulatory component of the National Health Care Survey (NHCS), and will provide coverage of more than 90 percent of ambulatory medical care. 
                </P>
                <P>The NAMCS provides a range of baseline data on the characteristics of the users and providers of ambulatory medical care. Data collected include the patients' demographic characteristics and reason(s) for visit, and the physicians' diagnosis(es) and diagnostic services, medications and disposition. These data, together with trend data, may be used to monitor the effects of change in the health care system, provide new insights into ambulatory medical care, and stimulate further research on the use, organization, and delivery of ambulatory care. </P>
                <P>Users of NAMCS data include, but are not limited to, congressional and other federal government agencies such as NIH and FDA, state and local governments, medical schools, schools of public health, colleges and universities, private businesses, nonprofit foundations and corporations, professional associations, as well as individual practitioners, researchers, administrators and health planners. Uses vary from the inclusion of a few selected statistics in a large research effort, to an in-depth analysis of the entire NAMCS data set covering several years. </P>
                <P>To calculate the burden hours the number of respondents for NAMCS is based on a sample of 3,150 physicians with a 50 percent participation rate (this includes physicians who are out-of-scope as well as those who refuse). The total annual burden for this data collection is 6,074 hours. </P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s100,12,12,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Form </CHED>
                        <CHED H="1">Number of respondents </CHED>
                        <CHED H="1">Number of responses per respondent </CHED>
                        <CHED H="1">Average burden per response </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="11">Induction: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">—Eligible </ENT>
                        <ENT>2,362 </ENT>
                        <ENT>1 </ENT>
                        <ENT>25/60 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">—Ineligible </ENT>
                        <ENT>788 </ENT>
                        <ENT>1 </ENT>
                        <ENT>5/60 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Patient Record </ENT>
                        <ENT>2,362 </ENT>
                        <ENT>30 </ENT>
                        <ENT>4/60 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Non-response studies </ENT>
                        <ENT>300 </ENT>
                        <ENT>1 </ENT>
                        <ENT>60/60 </ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: June 6, 2002. </DATED>
                    <NAME>Julie Fishman,</NAME>
                    <TITLE>Acting Associate Director for Policy, Planning and Evaluation, Centers for Disease Control and Prevention. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15013 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention </SUBAGY>
                <DEPDOC>[30DAY-34-02] </DEPDOC>
                <SUBJECT>Agency Forms Undergoing Paperwork Reduction Act Review </SUBJECT>
                <P>The Centers for Disease Control and Prevention (CDC) publishes a list of information collection requests under review by the Office of Management and Budget (OMB) in compliance with the Paperwork Reduction Act (44 U.S.C. Chapter 35). To request a copy of these requests, call the CDC Reports Clearance Officer at (404) 498-1210. Send written comments to CDC, Desk Officer, Human Resources and Housing Branch, New Executive Office Building, Room 10235, Washington, DC 20503. Written comments should be received within 30 days of this notice. </P>
                <P>
                    <E T="03">Proposed Project:</E>
                     The Development and Testing of a Tool to Assess the Public's Perception about People with 
                    <PRTPAGE P="40931"/>
                    Epilepsy—New—National Center for Chronic Disease Prevention and Health Promotion (NCCDPHP), Centers for Disease Control and Prevention (CDC). About 2.3 million people in the U.S. have some form of epilepsy, a neurological condition in which the brain's normal electrical functions may be interrupted with bursts of electrical impulses. Epilepsy affects people of all ages, but particularly the very young and the elderly. Persons with chronic or disabling health conditions like epilepsy face myriad challenges including establishing and following a treatment regimen, developing and enacting self-management plans, and finding social support. 
                </P>
                <P>Compounding these challenges are the reactions and beliefs of people with whom they interact. The stigma and perceived stigma of their health condition can lead to problems with self-management of their disease and further morbidity. </P>
                <P>The goal of this project is to develop a valid and reliable measurement tool to assess the public's perception of epilepsy and seizure disorders. This tool may shed light on the challenges in the social environment confronted by people with epilepsy and by their care givers. It will help gauge the climate of the general public and guide future epilepsy interventions. Once the tool has been developed, reliability and validity tests need to be conducted to ensure it is a scientifically rigorous instrument. </P>
                <P>The goals of the proposed data collection are to assess the instrument's: </P>
                <P>
                    • 
                    <E T="03">Internal consistency</E>
                    —how well different measures of the same construct reflect that construct 
                </P>
                <P>
                    • 
                    <E T="03">Concurrent validity</E>
                    —the degree to which an operation is able to predict the behavior it purports to predict 
                </P>
                <P>
                    • 
                    <E T="03">Construct validity</E>
                    —the extent to which an operation measures only the defined construct and not other constructs 
                </P>
                <P>
                    • 
                    <E T="03">Test-retest reliability</E>
                    —the stability of the measure over time 
                </P>
                <P>A random digit dial survey will be conducted with 750 respondents via computer assisted telephone interviewing (CATI) techniques. The number of respondents is sufficient to be generalizable to the U.S. population and to perform data reduction techniques such as factor analysis. Of the 750 respondents, 100 will be called back within two weeks to assess test-retest reliability. The total annual burden for this data collection is 318 hours. </P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s100,12,12,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Survey </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents </LI>
                        </CHED>
                        <CHED H="1">
                            Number of responses/
                            <LI>respondent </LI>
                        </CHED>
                        <CHED H="1">
                            Average burden/response 
                            <LI>(in hours) </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Screening Calls </ENT>
                        <ENT>900 </ENT>
                        <ENT>1 </ENT>
                        <ENT>2/60 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Completed Interviews</ENT>
                        <ENT>750 </ENT>
                        <ENT>1 </ENT>
                        <ENT>20/60 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Reliability Test-Screening</ENT>
                        <ENT>120 </ENT>
                        <ENT>1 </ENT>
                        <ENT>2/60 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Reliability Test-Completed Interviews</ENT>
                        <ENT>100 </ENT>
                        <ENT>1 </ENT>
                        <ENT>20/60 </ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: June 6, 2002. </DATED>
                    <NAME>Julie Fishman, </NAME>
                    <TITLE>Acting Associate Director for Policy, Planning and Evaluation, Centers for Disease Control and Prevention. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15014 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention </SUBAGY>
                <DEPDOC>[30DAY-35-02] </DEPDOC>
                <SUBJECT>Agency Forms Undergoing Paperwork Reduction Act Review </SUBJECT>
                <P>The Centers for Disease Control and Prevention (CDC) publishes a list of information collection requests under review by the Office of Management and Budget (OMB) in compliance with the Paperwork Reduction Act (44 U.S.C. Chapter 35). To request a copy of these requests, call the CDC Reports Clearance Officer at (404) 498-1210. Send written comments to CDC, Desk Officer, Human Resources and Housing Branch, New Executive Office Building, Room 10235, Washington, DC 20503. Written comments should be received within 30 days of this notice. </P>
                <P>
                    <E T="03">Proposed Project:</E>
                     Dissemination of Lessons Learned from the Community Coalition Partnership Programs for the Prevention of Teen Pregnancy—New—National Center for Chronic Disease Prevention and Health Promotion (NCCDPHP), Centers for Disease Control and Prevention (CDC). The United States has the highest teenage pregnancy rate of all developed countries. About 1 million teenagers become pregnant each year and most of those pregnancies are unintended. These pregnancies have profound economic, social and personal impacts on the teen mothers, their children, and society. 
                </P>
                <P>Since 1995, the Centers for Disease Control and Prevention (CDC) has funded 13 community-wide coalitions, the Community Coalition Partnership Programs for Prevention of Teen Pregnancy, to reduce the incidence of teenage pregnancy through a youth development model. Phase I of this effort included a 2-year planning phase and Phase II is the 5-year intervention phase to be completed in September 2002. The proposed data collection is an evaluation of lessons learned from this demonstration project. The goals of the proposed data collection are: </P>
                <P>• To provide evidence about effective long-term programs, their components, and approaches </P>
                <P>• To identify best practices, practices to avoid, best investments, and how-to steps </P>
                <P>• To inform the implementation of the demonstration program </P>
                <P>• To inform the modification (if any) and expansion (if any) of the program </P>
                <P>The data will be collected via interview with key stakeholders from the hub organization (the one receiving CDC funding), its partner organizations, and the community during tow 3-day site visits to each site. The second site visit will occur a year after the first site visit. If any key stakeholders cannot be present during this site visit, they will be interviewed by phone. The annual burden for this data collection is 416 hours.</P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s100,r100,12,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            Type of 
                            <LI>respondents </LI>
                        </CHED>
                        <CHED H="1">
                            Number of respondents 
                            <LI>per year </LI>
                        </CHED>
                        <CHED H="1">
                            Number of responses 
                            <LI>per respondent </LI>
                        </CHED>
                        <CHED H="1">
                            Avg. burden per response 
                            <LI>(in hours) </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Hub Organization Management </ENT>
                        <ENT>130 (13 sites, 10 per site)</ENT>
                        <ENT>1</ENT>
                        <ENT>1 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Coalition members</ENT>
                        <ENT>208 (13 sites, 16 per org)</ENT>
                        <ENT>1</ENT>
                        <ENT>1 </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="40932"/>
                        <ENT I="01">Evaluators</ENT>
                        <ENT>78 (13 sites, 6 per site)</ENT>
                        <ENT>1</ENT>
                        <ENT>1 </ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <DATED>Dated: June 6, 2002. </DATED>
                    <NAME>Julie Fishman, </NAME>
                    <TITLE>Acting Associate Director for Policy, Planning and Evaluation, Centers for Disease Control and Prevention. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15015 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <SUBJECT>Notice of Hearing: Reconsideration of Disapproval of Iowa State Plan Amendment 01-19 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of hearing. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces an administrative hearing on August 2, 2002, at 10 a.m., Plaza Room; Richard Bolling Federal Building; 601 E. Twelfth Street; Kansas City, Missouri 64106 to reconsider our decision to disapprove Iowa State Plan Amendment (SPA) 01-19. </P>
                    <P>
                        <E T="03">Closing Date:</E>
                         Requests to participate in the hearing as a party must be received by the presiding officer by (15 days after publication). 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Kathleen Scully-Hayes, Presiding Officer, CMS, C1-09-13, 7500 Security Boulevard, Baltimore, Maryland 21244, Telephone: (410) 786-2055. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice announces an administrative hearing to reconsider our decision to disapprove Iowa's State Plan Amendment (SPA) 01-19. This SPA would establish a new target group for case management services for children under age 18 in need of child welfare services. </P>
                <P>The issues that factored into the disapproval are: (1) Duplication of payment authority under other programs, which is not consistent with guidance in the State Medicaid Manual, applicable cost principles; and statutory requirements at section 1902(a)(30)(A) of the Social Security Act (Act) for rates consistent with efficiency, economy, and quality of care; (2) insufficient description of a functional payment methodology which means that the SPA does not contain all the information necessary to determine whether it is consistent with all applicable requirements (in particular the requirements that rates be consistent with efficiency, economy, and quality of care), as mandated by 42 CFR 430.10; and (3) while not part of the original disapproval letter, restriction of beneficiary freedom of choice of providers pursuant to section 1902(a)(23) of the Act because of the limitation of providers to employees of public welfare agencies, which CMS is now including as an issue for reconsideration. </P>
                <P>After consideration of the issues discussed above, and after consultation with the Secretary, as required by 42 CFR 430.15(c)(2), the CMS Administrator disapproved Iowa SPA 01-19. </P>
                <P>Section 1116 of the Social Security Act (the Act) and 42 CFR part 430 establish Department procedures that provide an administrative hearing for reconsideration of a disapproval of a State plan or plan amendment. The Centers for Medicare &amp; Medicaid Services (CMS) is required to publish a copy of the notice to a state Medicaid agency that informs the agency of the time and place of the hearing and the issues to be considered. If we subsequently notify the agency of additional issues that will be considered at the hearing, we will also publish that notice. </P>
                <P>
                    Any individual or group that wants to participate in the hearing as a party must petition the presiding officer within 15 days after publication of this notice, in accordance with the requirements contained at 42 CFR 430.76(b)(2). Any interested person or organization that wants to participate as 
                    <E T="03">amicus curiae</E>
                     must petition the presiding officer before the hearing begins in accordance with the requirements contained at 42 CFR 430.76(c). If the hearing is later rescheduled, the presiding officer will notify all participants. 
                </P>
                <P>The notice to Iowa announcing an administrative hearing to reconsider the disapproval of its SPA reads as follows:</P>
                <EXTRACT>
                    <P>Ms. Jessie K. Rasmussen, Director, Iowa Department of Human Services, Hoover State Office Building, Des Moines, IA 50319-0114. </P>
                    <P>Dear Ms. Rasmussen: I am responding to your request for reconsideration of the decision to disapprove Iowa State Plan Amendment (SPA) 01-19. Iowa submitted SPA 01-19 on July 13, 2001. This SPA would establish a new target group for case management services for children under age 18 in need of child welfare services. </P>
                    <P>The SPA was disapproved because of the following issues: (1) Duplication of payment authority under other programs, which is not consistent with guidance in the State Medicaid Manual, applicable cost principles, and statutory requirements at section 1902(a)(30)(A) of the Social Security Act (Act) for rates consistent with efficiency, economy, and quality of care; (2) insufficient description of a functional payment methodology, which means that the SPA does not contain all the information necessary to determine whether it is consistent with all applicable requirements (in particular the requirements that rates be consistent with efficiency, economy, and quality of care), as mandated by 42 CFR 430.10; and (3) while not part of the original disapproval letter, restriction of beneficiary freedom of choice of providers pursuant to section 1902(a)(23) of the Act because of the limitation of providers to employees of public welfare agencies, which the Centers for Medicare &amp; Medicaid Services is now including as an issue for reconsideration. </P>
                    <P>After consideration of the issues set forth above, and after consultation with the Secretary as required under 42 CFR 430.15(c)(2), I disapproved Iowa SPA 01-19. </P>
                    <P>I am scheduling a hearing on your request for reconsideration to be held on August 2, 2002, at 10 a.m.; Plaza Room; Richard Bolling Federal Building; 601 E. Twelfth Street; Kansas City, Missouri 64106. </P>
                    <P>If this date is not acceptable, we would be glad to set another date that is mutually agreeable to the parties. The hearing will be governed by the procedures prescribed at 42 CFR, part 430. </P>
                    <P>I am designating Ms. Kathleen Scully-Hayes as the presiding officer. If these arrangements present any problems, please contact the presiding officer. In order to facilitate any communication, which may be necessary between the parties to the hearing, please notify the presiding officer to indicate acceptability of the hearing date that has been scheduled and provide names of the individuals who will represent the State at the hearing. The presiding officer may be reached at (410) 786-2055. </P>
                    <P>  Sincerely, </P>
                    <FP>Thomas A. Scully.</FP>
                    <P>Section 1116 of the Act (42 U.S.C. section 1316); 42 CFR section 430.18) (Catalog of Federal Domestic Assistance Program No. 13.714, Medicaid Assistance Program)</P>
                </EXTRACT>
                <SIG>
                    <PRTPAGE P="40933"/>
                    <DATED>Dated: June 7, 2002. </DATED>
                    <NAME>Thomas A. Scully, </NAME>
                    <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15006 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <SUBJECT>Privacy Act of 1974; Report of Modified or Altered System </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Health and Human Services (HHS) Centers for Medicare &amp; Medicaid Services (CMS) (formerly the Health Care Financing Administration). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of modified or altered system of records (SOR). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the requirements of the Privacy Act of 1974, we are proposing to modify or alter an SOR, “Supplemental Medical Insurance (SMI) and Hospital Insurance (HI) Premium Accounting Collection and Enrollment (SPACE) System.” We propose to delete published routine uses number 1, authorizing disclosure to state Medicaid agencies, number 4, authorizing disclosure to the United States Office of Personnel Management (OPM), number 6, authorizing disclosure to a contractor for the purpose of processing records in this system, and an unnumbered routine use authorizing disclosure to the Social Security Administration (SSA). Disclosures allowed by routine uses number 1, 4, and to the SSA will be covered by proposed routine use number 2 to permit release of information to “another Federal and/or state agency, agency of a state government, an agency established by state law, or its fiscal agent.” Disclosures previously allowed by routine use number 6 will now be covered by proposed routine use number 3. </P>
                    <P>The security classification previously reported as “None” will be modified to reflect that the data in this system is considered to be “Level Three Privacy Act Sensitive.” We are modifying the language in the remaining routine uses to provide clarity to CMS's intention to disclose individual-specific information contained in this system. The routine uses will then be prioritized and reordered according to their usage. We will also take the opportunity to update any sections of the system that were affected by the recent reorganization and to update language in the administrative sections to correspond with language used in other CMS SORs. </P>
                    <P>
                        The primary purpose of this SOR is to process beneficiary premium billing accretions and deletions to third party premium payer accounts (state Medicaid agencies, OPM, and formal third party groups (latter as defined in 42 Code of Federal Regulations (CFR) §§ 408.80 through 408.92)) for the payment of Part B (SMI) and/or Part A (HI) premiums on behalf of Medicare beneficiaries and for enrolling individuals for HI or SMI coverage under state buy-in agreements. Information in this system may be used: by formal third party groups pursuant to agreements with CMS, by another Federal or state agency, agency of a state government, an agency established by state law, or its fiscal agent, to support regulatory and policy functions performed within the agency or by a contractor or consultant, to an individual or organization for a research, evaluation, or epidemiological project, to support constituent requests made to a congressional representative, to support litigation involving the Agency related to this SOR, and to combat fraud and abuse in certain Federally funded health care programs. We have provided background information about the modified system in the “Supplementary Information” section below. Although the Privacy Act requires only that CMS provide an opportunity for interested persons to comment on the proposed routine uses, CMS invites comments on all portions of this notice. 
                        <E T="03">See</E>
                          
                        <E T="02">EFFECTIVE DATES</E>
                         section for comment period. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">EFFECTIVE DATES:</HD>
                    <P>CMS filed a modified or altered system report with the Chair of the House Committee on Government Reform and Oversight, the Chair of the Senate Committee on Governmental Affairs, and the Administrator, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB) on May 22, 2002. To ensure that all parties have adequate time in which to comment, the modified or altered SOR, including routine uses, will become effective 40 days from the publication of the notice, or from the date it was submitted to OMB and the congress, whichever is later, unless CMS receives comments that require alterations to this notice. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The public should address comments to: Director, Division of Data Liaison and Distribution, CMS, Room N2-04-27, 7500 Security Boulevard, Baltimore, Maryland 21244-1850. Comments received will be available for review at this location, by appointment, during regular business hours, Monday through Friday from 9 a.m.-3 p.m., eastern daylight time. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jackie Fromm, Director, Division of Premium Billing, Benefits Operations Group, Center for Medicare Management, CMS, 7500 Security Boulevard, S1-06-03, Baltimore, Maryland 21244-1850. The telephone number is (410) 786-5885. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Description of the Modified SOR </HD>
                <HD SOURCE="HD2">A. Statutory and Regulatory Basis for SOR </HD>
                <P>
                    In 1982, CMS established a SOR under the authority of sections 1818, 1818A, (42 United States Code (USC) §§ 1395i-2 and 2a), §§ 1818(e) and (g) (42 USC 1395i-2(e) and (g)), 1840 (d) and (e) (42 USC 1395s (d) and (e)), and 1843 (42 USC 1395v) of Title XVIII of the Social Security Act (the Act). Notice of the modification to this system, “Supplemental Medical Insurance (SMI) Premium Accounting Collection and Enrollment (SPACE) System, System No. 09-70-0505” was published in the 
                    <E T="04">Federal Register</E>
                     (FR) at 47 FR 45693 (Oct. 23, 1982) (original publication with 3 routine uses), 51 FR 33134 (Sept. 18, 1986) (replaced litigation routine use), 60 FR 4176 (Jan. 20, 1995) (added 4 new routines uses), 61 FR 6645 (Feb. 21, 1996) (added unnumbered SSA use), 63 FR 38414 (July 16, 1998) (added three fraud and abuse uses), and 65 FR 50552 (Aug. 18, 2000) (deleted one and modified two fraud and abuse uses). 
                </P>
                <HD SOURCE="HD1">II. Collection and Maintenance of Data in the System </HD>
                <HD SOURCE="HD2">A. Scope of the Data Collected </HD>
                <P>The system contains information on Medicare beneficiaries whose HI benefit and/or SMI Medicare premiums are paid by a state Medicaid agency, OPM, or a formal third party group. Information consists of the beneficiary's name, social security number (SSN), health insurance claims number (HICN), date of birth, sex, amount of premium liability, date agency first became liable for HI or SMI premiums, last month of agency premium liability, agency identification number, and an OPM annuity number. </P>
                <HD SOURCE="HD2">B. Agency Policies, Procedures, and Restrictions on the Routine Use </HD>
                <P>
                    The Privacy Act permits us to disclose information without an individual's consent if the information is to be used for a purpose that is compatible with the purpose(s) for which the information was collected. Any such disclosure of data is known as a “routine use.” The government will only release SPACE 
                    <PRTPAGE P="40934"/>
                    information that can be associated with an individual as provided for under “Section III. Proposed Routine Use Disclosures of Data in the System.” Both identifiable and non-identifiable data may be disclosed under a routine use. 
                </P>
                <P>We will only collect the minimum personal data necessary to protect the integrity of the records maintained by SPACE. CMS has the following policies and procedures concerning disclosures of information that will be maintained in the system. Disclosure of information from the SOR will be approved only for the minimum information necessary to accomplish the purpose of the disclosure only after CMS: </P>
                <P>
                    1. Determines that the use or disclosure is consistent with the reason that the data is being collected, 
                    <E T="03">e.g.,</E>
                     process beneficiary premium accretions and deletions to third party payer accounts (state Medicaid agencies, OPM, and formal third party groups) for the payment of Part B (SMI) and/or Part A (HI) premiums on behalf of Medicare beneficiaries and for enrolling individuals for HI or SMI coverage under state buy-in agreements. 
                </P>
                <P>2. Determines that: </P>
                <P>a. The purpose for which the disclosure is to be made can only be accomplished if the record is provided in individually identifiable form; </P>
                <P>b. The purpose for which the disclosure is to be made is of sufficient importance to warrant the effect and/or risk on the privacy of the individual that additional exposure of the record might bring; and </P>
                <P>c. There is a strong probability that the proposed use of the data would in fact accomplish the stated purpose(s). </P>
                <P>3. Requires the information recipient to: </P>
                <P>a. Establish administrative, technical, and physical safeguards to prevent unauthorized use or disclosure of the record; </P>
                <P>b. Remove or destroy at the earliest time all individually-identifiable information; and </P>
                <P>c. Agree to not use or disclose the information for any purpose other than the stated purpose under which the information was disclosed. </P>
                <P>4. Determines that the data are valid and reliable. </P>
                <HD SOURCE="HD1">III. Proposed Routine Use Disclosures of Data in the System </HD>
                <HD SOURCE="HD2">A. Entities Who May Receive Disclosures Under Routine Use </HD>
                <P>These routine uses specify circumstances, in addition to those provided by statute in the Privacy Act of 1974, under which CMS may release information from the SPACE without the consent of the individual to whom such information pertains. Each proposed disclosure of information under these routine uses will be evaluated to ensure that the disclosure is legally permissible, including but not limited to ensuring that the purpose of the disclosure is compatible with the purpose for which the information was collected. We are proposing to establish or modify the following routine use disclosures of information maintained in the system: </P>
                <P>1. To formal third party groups pursuant to agreements with the CMS to pay the Medicare premiums on behalf of their members and who need to have access to the records in order to perform the activity. </P>
                <P>We contemplate disclosing information under this routine use only in situations in which CMS has entered into a contractual or similar agreement with a formal third party group to assist in a CMS function relating to the payment on behalf of their members. </P>
                <P>2. To another Federal or state agency, agency of a state government, an agency established by state law, or its fiscal agent pursuant to agreements with CMS to: </P>
                <P>a. Contribute to the accuracy of CMS's proper payment of Medicare benefits, </P>
                <P>b. Enable such agency to administer a Federal health benefits program, or as necessary to enable such agency to fulfill a requirement of a Federal statute or regulation that implements a health benefits program funded in whole or in part with Federal funds, and/or </P>
                <P>c. Assist Federal/state Medicaid programs within the state. </P>
                <P>Other Federal or state agencies in their administration of a Federal health program may require SPACE information in order to support monitoring of Medicare premium billing information. </P>
                <P>In addition, state Medicaid agencies may require SPACE data, pursuant to agreements with HHS, for enrollment of dually eligible beneficiaries for medical insurance under section 1843 of the Act. </P>
                <P>SSA requires SPACE data to enable them to assist in the implementation and maintenance of the Medicare program. </P>
                <P>RRB requires SPACE information to enable them to assist in the implementation and maintenance of the Medicare program. </P>
                <P>OPM requires SPACE information in order to perform monthly premium billing functions to identify annuitants for whom premium collections must be initiated, and to periodically reconcile third party master records. </P>
                <P>3. To Agency contractors or consultants who have been engaged by the Agency to assist in accomplishment of a CMS function relating to the purposes for this SOR and who need to have access to the records in order to assist CMS. </P>
                <P>We contemplate disclosing information under this routine use only in situations in which CMS may enter into a contractual or similar agreement with a third party to assist in accomplishing a CMS function relating to purposes for this SOR. </P>
                <P>CMS occasionally contracts out certain of its functions when doing so would contribute to effective and efficient operations. CMS must be able to give a contractor or consultant whatever information is necessary for the contractor or consultant to fulfill its duties. In these situations, safeguards are provided in the contract prohibiting the contractor or consultant from using or disclosing the information for any purpose other than that described in the contract, and requires the contractor or consultant to return or destroy all information at the completion of the contract. </P>
                <P>4. To an individual or organization for research, evaluation, or epidemiological projects related to the prevention of disease or disability, the restoration or maintenance of health, or payment related projects. </P>
                <P>SPACE data will provide for the research, evaluation, and epidemiological projects, a broader, longitudinal, national perspective of the status of Medicare beneficiaries. CMS anticipates that many researchers will have legitimate requests to use these data in projects that could ultimately improve the care provided to Medicare beneficiaries and the policy that governs the care. </P>
                <P>5. To a Member of Congress or a congressional staff member in response to an inquiry of the congressional office made at the written request of the constituent about whom the record is maintained. </P>
                <P>Beneficiaries and other individuals often request the help of a Member of Congress in resolving some issue relating to a matter before CMS. The Member of Congress then writes CMS, and CMS must be able to give sufficient information in response to the inquiry. </P>
                <P>6.To the Department of Justice (DOJ), court or adjudicatory body when:</P>
                <P>a. The Agency or any component thereof, or </P>
                <P>b. Any employee of the Agency in his or her official capacity, or </P>
                <P>
                    c. Any employee of the Agency in his or her individual capacity where the DOJ has agreed to represent the employee, or 
                    <PRTPAGE P="40935"/>
                </P>
                <P>d. The United States Government is a party to litigation or has an interest in such litigation, and by careful review, CMS determines that the records are both relevant and necessary to the litigation. </P>
                <P>Whenever CMS is involved in litigation, or occasionally when another party is involved in litigation and CMS's policies or operations could be affected by the outcome of the litigation, CMS would be able to disclose information to the DOJ, court or adjudicatory body involved. </P>
                <P>7. To a CMS contractor (including, but not limited to fiscal intermediaries and carriers) that assists in the administration of a CMS-administered health benefits program, or to a grantee of a CMS-administered grant program, when disclosure is deemed reasonably necessary by CMS to prevent, deter, discover, detect, investigate, examine, prosecute, sue with respect to, defend against, correct, remedy, or otherwise combat fraud or abuse in such program. </P>
                <P>We contemplate disclosing information under this routine use only in situations in which CMS has entered into a contract or grant with a third party to assist in accomplishing CMS functions relating to the purpose of combating fraud and abuse. </P>
                <P>CMS occasionally contracts out certain of its functions when doing so would contribute to effective and efficient operations. CMS must be able to give a contractor or grantee whatever information is necessary for the contractor or grantee to fulfill its duties. In these situations, safeguards are provided in the contract prohibiting the contractor or grantee from using or disclosing the information for any purpose other than that described in the contract and requiring the contractor or grantee to return or destroy all information. </P>
                <P>8. To another Federal agency or to an instrumentality of any governmental jurisdiction within or under the control of the United States (including any state or local governmental agency), that administers, or that has the authority to investigate potential fraud or abuse in, a health benefits program funded in whole or in part by Federal funds, when disclosure is deemed reasonably necessary by CMS to prevent, deter, discover, detect, investigate, examine, prosecute, sue with respect to, defend against, correct, remedy, or otherwise combat fraud or abuse in such programs. </P>
                <P>Other agencies may require SPACE information for the purpose of combating fraud and abuse in such Federally funded programs. </P>
                <HD SOURCE="HD2">B. Additional Circumstances Affecting Routine Use Disclosures </HD>
                <P>This SOR contains Protected Health Information as defined by HHS regulation “Standards for Privacy of Individually Identifiable Health Information” (45 CFR parts 160 and 164, 65 FR 82462 (Dec. 28, 00), as amended by 66 FR 12434 (Feb. 26, 01)). Disclosures of Protected Health Information authorized by these routine uses may only be made if, and as, permitted or required by the “Standards for Privacy of Individually Identifiable Health Information.” </P>
                <P>In addition, our policy will be to prohibit release even of non-identifiable data, except pursuant to one of the routine uses, if there is a possibility that an individual can be identified through implicit deduction based on small cell sizes (instances where the patient population is so small that individuals who are familiar with the enrollees could, because of the small size, use this information to deduce the identity of the beneficiary). </P>
                <HD SOURCE="HD1">IV. Safeguards </HD>
                <HD SOURCE="HD2">A. Administrative Safeguards </HD>
                <P>The SPACE system will conform to applicable law and policy governing the privacy and security of Federal automated information systems. These include but are not limited to: the Privacy Act of 1974, Computer Security Act of 1987, the Paperwork Reduction Act (PRA) of 1995, the Clinger-Cohen Act of 1996, and OMB Circular A-130, Appendix III, “Security of Federal Automated Information Resources.” CMS has prepared a comprehensive system security plan as required by the Office and Management and Budget (OMB) Circular A-130, Appendix III. This plan conforms fully to guidance issued by the National Institute for Standards and Technology (NIST) in NIST Special Publication 800-18, “Guide for Developing Security Plans for Information Technology Systems.” Paragraphs A-C of this section highlight some of the specific methods that CMS is using to ensure the security of this system and the information within it. </P>
                <P>
                    <E T="03">Authorized users:</E>
                     Personnel having access to the system have been trained in Privacy Act and systems security requirements. Employees and contractors who maintain records in the system are instructed not to release any data until the intended recipient agrees to implement appropriate administrative, technical, procedural, and physical safeguards sufficient to protect the confidentiality of the data and to prevent unauthorized access to the data. In addition, CMS will monitor the authorized users to ensure against excessive or unauthorized use. Records are used in a designated work area or workstation and the system location is attended at all times during working hours. 
                </P>
                <P>To assure security of the data, the proper level of class user is assigned for each individual user as determined at the Agency level. This prevents unauthorized users from accessing and modifying critical data. The system database configuration includes five classes of database users: </P>
                <P>
                    • 
                    <E T="03">Database Administrator</E>
                     class owns the database objects; e.g., tables, triggers, indexes, stored procedures, packages, and has database administration privileges to these objects;
                </P>
                <P>
                    • 
                    <E T="03">Quality Control Administrator</E>
                     class has read and write access to key fields in the database; 
                </P>
                <P>
                    • 
                    <E T="03">Quality Indicator (QI) Report Generator</E>
                     class has read-only access to all fields and tables; 
                </P>
                <P>
                    • 
                    <E T="03">Policy Research</E>
                     class has query access to tables, but are not allowed to access confidential individual identification information; and 
                </P>
                <P>
                    • 
                    <E T="03">Submitter</E>
                     class has read and write access to database objects, but no database administration privileges. 
                </P>
                <HD SOURCE="HD2">B. Physical Safeguards </HD>
                <P>All server sites have implemented the following minimum requirements to assist in reducing the exposure of computer equipment and thus achieve an optimum level of protection and security for the SPACE system: </P>
                <P>Access to all servers is controlled, with access limited to only those support personnel with a demonstrated need for access. Servers are to be kept in a locked room accessible only by specified management and system support personnel. Each server requires a specific log-on process. All entrance doors are identified and marked. A log is kept of all personnel who were issued a security card key and/or combination which grants access to the room housing the server, and all visitors are escorted while in this room. All servers are housed in an area where appropriate environmental security controls are implemented, which include measures implemented to mitigate damage to Automated Information System (AIS) resources caused by fire, electricity, water and inadequate climate controls. </P>
                <P>Protection applied to the workstations, servers and databases include: </P>
                <P>
                    • 
                    <E T="03">User Log-ons</E>
                    —Authentication is performed by the Primary Domain Controller/Backup Domain Controller of the log-on domain. 
                    <PRTPAGE P="40936"/>
                </P>
                <P>
                    • 
                    <E T="03">Workstation Names</E>
                    —Workstation naming conventions may be defined and implemented at the Agency level. 
                </P>
                <P>
                    • 
                    <E T="03">Hours of Operation</E>
                    —May be restricted by Windows NT. When activated all applicable processes will automatically shut down at a specific time and not be permitted to resume until the predetermined time. The appropriate hours of operation are determined and implemented at the Agency level. 
                </P>
                <P>
                    • 
                    <E T="03">Inactivity Log-out</E>
                    —Access to the NT workstation is automatically logged out after a specified period of inactivity. 
                </P>
                <P>
                    • 
                    <E T="03">Warnings</E>
                    —Legal notices and security warnings display on all servers and workstations.
                </P>
                <P>
                    • 
                    <E T="03">Remote Access Services (RAS)</E>
                    —Windows NT RAS security handles resource access control. Access to NT resources is controlled for remote users in the same manner as local users, by utilizing Windows NT file and sharing permissions. Dial-in access can be granted or restricted on a user-by-user basis through the Windows NT RAS administration tool. 
                </P>
                <HD SOURCE="HD2">C. Procedural Safeguards </HD>
                <P>All automated systems must comply with Federal laws, guidance, and policies for information systems security as stated previously in this section. Each automated information system should ensure a level of security commensurate with the level of sensitivity of the data, risk, and magnitude of the harm that may result from the loss, misuse, disclosure, or modification of the information contained in the system. </P>
                <HD SOURCE="HD1">V. Effect of the Modified SOR on Individual Rights </HD>
                <P>CMS proposes to establish this system in accordance with the principles and requirements of the Privacy Act and will collect, use, and disseminate information only as prescribed therein. Data in this system will be subject to the authorized releases in accordance with the routine uses identified in this SOR. </P>
                <P>CMS will monitor the collection and reporting of SPACE data. SPACE information on individuals is completed by contractor personnel and submitted to CMS through standard systems located at different locations. CMS will utilize a variety of onsite and offsite edits and audits to increase the accuracy of SPACE data. </P>
                <P>CMS will take precautionary measures (see item IV. above) to minimize the risks of unauthorized access to the records and the potential harm to individual privacy or other personal or property rights. CMS will collect only that information necessary to perform the system's functions. In addition, CMS will make disclosure of identifiable data from the modified system only with consent of the subject individual, or his/her legal representative, or in accordance with an applicable exception provision of the Privacy Act. </P>
                <P>CMS, therefore, does not anticipate an unfavorable effect on individual privacy as a result of the disclosure of information relating to individuals. </P>
                <SIG>
                    <DATED>Dated: May 22, 2002. </DATED>
                    <NAME>Thomas A. Scully, </NAME>
                    <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                </SIG>
                <PRIACT>
                    <HD SOURCE="HD1">09-70-0505 </HD>
                    <HD SOURCE="HD2">System Name: </HD>
                    <P>Supplemental Medical Insurance (SMI) and Hospital Insurance (HI) Premium Accounting Collection and Enrollment (SPACE) System, HHS/CMS/CMM </P>
                    <HD SOURCE="HD2">Security Classification: </HD>
                    <P>Level Three Privacy Act Sensitive. </P>
                    <HD SOURCE="HD2">System Location: </HD>
                    <P>CMS Data Center, 7500 Security Boulevard, North Building, First Floor, Baltimore, Maryland 21244-1850. </P>
                    <HD SOURCE="HD2">Categories of Individuals Covered by the System: </HD>
                    <P>The system contains information on Medicare beneficiaries whose Part A HI and/or Part B SMI premiums are paid by a state Medicaid agency, OPM, or a formal third party group (latter as defined in 42 Code of Federal Regulations (CFR) §§ 408.80 through 408.92). </P>
                    <HD SOURCE="HD2">Categories of Records in the System: </HD>
                    <P>Information contained in this SOR consist of the beneficiary's name, health insurance claims number (HICN), date of birth, sex, amount of premium liability, date agency first became liable for HI or SMI premiums, last month of agency premium liability, agency identification number, and an United States Office of Personnel Management (OPM) annuity number. </P>
                    <HD SOURCE="HD2">Authority for Maintenance of the System: </HD>
                    <P>Authority for the maintenance of this SOR is given under the authority of secs. 1818, 1818A, (42 USC 1395i-2 and 2a), 1818(e) and (g) (42 USC 1395i-2(e) and (g), 1840 (d) and (e) (42 USC 1395s (d) and (e), and 1843 (42 USC 1395v) of Title XVIII of the Social Security Act (the Act). </P>
                    <HD SOURCE="HD2">Purpose(s):</HD>
                    <P>The primary purpose of this SOR is to process beneficiary premium billing accretions and deletions to third party premium payer accounts (state Medicaid agencies, OPM, and formal third party groups (latter as defined in 42 Code of Federal Regulations (CFR) §§ 408.80 through 408.92)) for the payment of Part B (SMI) and/or Part A (HI) premiums on behalf of Medicare beneficiaries and for enrolling individuals for HI or SMI coverage under state buy-in agreements. Information in this system may be used: by formal third party groups pursuant to agreements with CMS, by another Federal or state agency, agency of a state government, an agency established by state law, or its fiscal agent, to support regulatory and policy functions performed within the Agency or by a contractor or consultant, to an individual or organization for a research, evaluation, or epidemiological project, to support constituent requests made to a congressional representative, to support litigation involving the Agency related to this SOR, and to combat fraud and abuse in certain Federally funded health care programs. </P>
                    <HD SOURCE="HD2">Routine Uses of Records Maintained in the System, Including Categories or Users and the Purposes of Such Uses: </HD>
                    <P>The Privacy Act allows us to disclose information without an individual's consent if the information is to be used for a purpose that is compatible with the purpose(s) for which the information was collected. Any such compatible use of data is known as a “routine use.” The proposed routine use in this system meets the compatibility requirement of the Privacy Act. This SOR contains Protected Health Information as defined by HHS regulation “Standards for Privacy of Individually Identifiable Health Information” (45 CFR parts 160 and 164, 65 FR 82462 (Dec. 28, 00), as amended by 66 FR 12434 (Feb. 26, 01)). Disclosures of Protected Health Information authorized by these routine uses may only be made if, and as, permitted or required by the “Standards for Privacy of Individually Identifiable Health Information.” </P>
                    <P>
                        In addition, our policy will be to prohibit release even of non-identifiable data, except pursuant to one of the routine uses, if there is a possibility that an individual can be identified through implicit deduction based on small cell sizes (instances where the patient population is so small that individuals who are familiar with the enrollees could, because of the small size, use this information to deduce the identity of the beneficiary). We are proposing to establish the following routine use disclosures of information that will be maintained in the system: 
                        <PRTPAGE P="40937"/>
                    </P>
                    <P>1. To formal third party groups pursuant to agreements with the CMS to pay Medicare premiums on behalf of their members and who need to have access to the records in order to perform the activity. </P>
                    <P>2. To another Federal or state agency, agency of a state government, an agency established by state law, or its fiscal agent pursuant to agreements with CMS to: </P>
                    <P>a. Contribute to the accuracy of CMS's proper payment of Medicare benefits, </P>
                    <P>b. Enable such agency to administer a Federal health benefits program, or as necessary to enable such agency to fulfill a requirement of a Federal statute or regulation that implements a health benefits program funded in whole or in part with Federal funds, and/or </P>
                    <P>c. Assist Federal/state Medicaid programs within the state. </P>
                    <P>3. To Agency contractors or consultants who have been engaged by the Agency to assist in accomplishment of an CMS function relating to the purposes for this SOR and who have need to have access to the records in order to assist CMS. </P>
                    <P>4. To an individual or organization for research, evaluation, or epidemiological projects related to the prevention of disease or disability, the restoration or maintenance of health, or payment related projects. </P>
                    <P>5. To a Member of Congress or congressional staff member in response to an inquiry of the congressional office made at the written request of the constituent about whom the record is maintained. </P>
                    <P>6. To the Department of Justice (DOJ), court or adjudicatory body when: </P>
                    <P>a. The Agency or any component thereof, or </P>
                    <P>b. Any employee of the Agency in his or her official capacity, or </P>
                    <P>c. Any employee of the Agency in his or her individual capacity where the DOJ has agreed to represent the employee, or </P>
                    <P>d. The United States Government is a party to litigation or has an interest in such litigation, and by careful review, CMS determines that the records are both relevant and necessary to the litigation. </P>
                    <P>7. To a CMS contractor (including, but not limited to fiscal intermediaries and carriers) that assists in the administration of a CMS-administered health benefits program, or to a grantee of a CMS-administered grant program, when disclosure is deemed reasonably necessary by CMS to prevent, deter, discover, detect, investigate, examine, prosecute, sue with respect to, defend against, correct, remedy, or otherwise combat fraud or abuse in such program. </P>
                    <P>8. To another Federal agency or to an instrumentality of any governmental jurisdiction within or under the control of the United States (including any state or local governmental agency), that administers, or that has the authority to investigate potential fraud or abuse in, a health benefits program funded in whole or in part by Federal funds, when disclosure is deemed reasonably necessary by CMS to prevent, deter, discover, detect, investigate, examine, prosecute, sue with respect to, defend against, correct, remedy, or otherwise combat fraud or abuse in such programs. </P>
                    <HD SOURCE="HD2">Policies and Practices for Storing, Retrieving, Accessing, Retaining, and Disposing of Records in the System: </HD>
                    <HD SOURCE="HD2">Storage: </HD>
                    <P>Computer diskette and on magnetic storage media. </P>
                    <HD SOURCE="HD2">Retrievability: </HD>
                    <P>Information can be retrieved by name, HICN, and assigned agency identification number. </P>
                    <HD SOURCE="HD2">Safeguards: </HD>
                    <P>CMS has safeguards for authorized users and monitors such users to ensure against excessive or unauthorized use. Personnel having access to the system have been trained in the Privacy Act and systems security requirements. Employees who maintain records in the system are instructed not to release any data until the intended recipient agrees to implement appropriate administrative, technical, procedural, and physical safeguards sufficient to protect the confidentiality of the data and to prevent unauthorized access to the data. </P>
                    <P>
                        In addition, CMS has physical safeguards in place to reduce the exposure of computer equipment and thus achieve an optimum level of protection and security for the SPACE system. For computerized records, safeguards have been established in accordance with the Department of Health and Human Services (HHS) standards and National Institute of Standards and Technology guidelines, 
                        <E T="03">e.g.,</E>
                         security codes will be used, limiting access to authorized personnel. System securities are established in accordance with HHS, Information Resource Management Circular #10, Automated Information Systems Security Program; CMS Automated Information Systems Guide, Systems Securities Policies, and OMB Circular No. A-130 (revised), Appendix III. 
                    </P>
                    <HD SOURCE="HD2">Retention and Disposal: </HD>
                    <P>Records are maintained in a secure storage area with identifiers for six years three months after final action of the case is completed. </P>
                    <HD SOURCE="HD2">System Manager(s) and Address: </HD>
                    <P>Director, Division of Premium Billing, Benefits Operations Group, Center for Medicare Management, CMS, 7500 Security Boulevard, S1-06-03, Baltimore, Maryland 21244-1850. </P>
                    <HD SOURCE="HD2">Notification Procedure: </HD>
                    <P>For purpose of access, the subject individual should write to the system manager who will require the system name, HIC, date of birth, and sex, and for verification purposes, the subject individual's name (woman's maiden name, if applicable), and social security number (SSN). Furnishing the SSN is voluntary, but it may make searching for a record easier and prevent delay. </P>
                    <HD SOURCE="HD2">Record Access Procedure: </HD>
                    <P>For purpose of access, use the same procedures outlined in Notification Procedures above. Requestors should also reasonably specify the record contents being sought. (These procedures are in accordance with Department regulation 45 CFR 5b.5(a)(2)). </P>
                    <HD SOURCE="HD2">Contesting Record Procedures: </HD>
                    <P>The subject individual should contact the system manager named above, and reasonably identify the record and specify the information to be contested. State the corrective action sought and the reasons for the correction with supporting justification. (These procedures are in accordance with Department regulation 45 CFR 5b.7). </P>
                    <HD SOURCE="HD2">Record Source Categories: </HD>
                    <P>Information contained in this records system is obtained from third party agencies, Social Security Administration's Master Beneficiary Record, and CMS’ Enrollment Database. </P>
                    <HD SOURCE="HD2">Systems Exempted from Certain Provisions of the Act: </HD>
                    <P>None.</P>
                </PRIACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15004 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-03-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <SUBJECT>Privacy Act of 1974; Report of Modified or Altered System </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Health and Human Services (HHS), Centers for Medicare &amp; Medicaid Services (CMS) (formerly the Health Care Financing Administration). </P>
                </AGY>
                <ACT>
                    <PRTPAGE P="40938"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of modified or altered system of records (SOR). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the requirements of the Privacy Act of 1974, we are proposing to modify or alter an SOR, “Employee Building Pass File (EBP) System, System No. 09-70-3002.” We propose to delete published routine uses number 1 authorizing disclosures to the Federal Protection Services (FPS), number 2 authorizing disclosures to “management officials inquiring about an individual's authorization to enter Federal occupied buildings,” number 3 authorizing disclosures to contractors, and an unnumbered routine use authorizing disclosure to the Social Security Administration (SSA). Disclosures allowed by routine use number 1, and to the SSA will be covered by proposed routine use number 2 to permit release of information to “another Federal agency.” Routine use number 2 is being deleted because it is not clear what “management officials” are being identified and who should receive information referred to in routine use number 2. Disclosures previously allowed by the former routine use number 2 will now be covered by the proposed routine use number 2 and by exceptions to the Privacy Act. Disclosures previously allowed by routine use number 3 will now be covered by proposed routine use number 1. </P>
                    <P>The security classification previously reported as “None” will be modified to reflect that the data in this system is considered to be “Level Three Privacy Act Sensitive.” We are modifying the language in the remaining routine uses to provide clarity to CMS's intention to disclose individual-specific information contained in this system. The routine uses will then be prioritized and reordered according to their proposed usage. We will also take the opportunity to update any sections of the system that were affected by the recent reorganization and to update language in the administrative sections to correspond with language used in other CMS SORs. </P>
                    <P>
                        The primary purpose of the SOR is to issue and control United States Government building passes issued to all CMS employees and non-CMS employees who require continuous access to CMS buildings in Baltimore and other CMS and HHS facilities. Information retrieved from this SOR will be used to: support regulatory and policy functions performed within the Agency or by a contractor or consultant, assist other Federal agencies with activities related to this system, support constituent requests made to congressional representatives, and support litigation involving the Agency. We have provided background information about the modified system in the “Supplementary Information” section below. Although the Privacy Act requires only that CMS provide an opportunity for interested persons to comment on the proposed routine uses, CMS invites comments on all portions of this notice. 
                        <E T="03">See</E>
                          
                        <E T="02">EFFECTIVE DATES</E>
                         section for comment period. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED"> EFFECTIVE DATES:</HD>
                    <P>CMS filed a modified or altered system report with the Chair of the House Committee on Government Reform and Oversight, the Chair of the Senate Committee on Governmental Affairs, and the Administrator, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB) on May 22, 2002. To ensure that all parties have adequate time in which to comment, the modified or altered SOR, including routine uses, will become effective 40 days from the publication of the notice, or from the date it was submitted to OMB and the Congress, whichever is later, unless CMS receives comments that require alterations to this notice. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The public should address comments to: Director, Division of Data Liaison and Distribution (DDLD), CMS, Room N2-04-27, 7500 Security Boulevard, Baltimore, Maryland 21244-1850. Comments received will be available for review at this location, by appointment, during regular business hours, Monday through Friday from 9 a.m.-3 p.m., eastern daylight time. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Marcia Levin, Division of Facilities Management Services, Administrative Services Group, CMS, SLL-11-18, 7500 Security Boulevard, Baltimore, Maryland, 21244-1850. The telephone number is 410-786-7840. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Description of the Modified System </HD>
                <HD SOURCE="HD2">A. Background </HD>
                <P>
                    In 1981, CMS established this system to carry out the directives authorizing Federal workers and other authorized personnel be issued United States Government identification cards. Notice of this system, “Employee Building Pass File (EBP) System, System No. 09-70-3002,” was published in the 
                    <E T="04">Federal Register</E>
                     (FR) at 46 FR 3524 (Jan. 15, 1981), and modified at 61 FR 6645 (added unnumbered SSA routine use). 
                </P>
                <HD SOURCE="HD2">B. Statutory and Regulatory Basis for System </HD>
                <P>Authority for maintenance of this system of records is given under section 486(c) of Title 40, United States Code (USC) and Title 41, Code of Federal Regulations (CFR), Chapter 101-20.302. </P>
                <HD SOURCE="HD1">II. Collection and Maintenance of Data in the System </HD>
                <HD SOURCE="HD2">A. Scope of the Data Collected </HD>
                <P>The system contain information on Federal employees, contractors and consultants, Government Services Administration employees, and contract guards working in CMS's central office complex in Baltimore, Maryland, and other CMS and HHS Federal buildings. The system contain name of the employee or other authorized individuals, social security number, identification card number, building/work location, phone number, position, title, grade, supervisor's name and telephone number. </P>
                <HD SOURCE="HD2">B. Agency Policies, Procedures, and Restrictions on the Routine Use </HD>
                <P>
                    The Privacy Act permits us to disclose information without an individual's consent if the information is to be used for a purpose that is compatible with the purpose(s) for which the information was collected. Any such disclosure of data is known as a “routine use.” The government will only release EBP information that can be associated with an individual as provided for under “
                    <E T="03">Section III. Proposed Routine Use Disclosures of Data in the System.</E>
                    ” Both identifiable and non-identifiable data may be disclosed under a routine use. 
                </P>
                <P>We will only disclose the minimum personal data necessary to achieve the purpose of EBP. CMS has the following policies and procedures concerning disclosures of information that will be maintained in the system. Disclosure of information from the SOR will be approved only to the extent necessary to accomplish the purpose of the disclosure and only after CMS: </P>
                <P>
                    1. Determines that the use or disclosure is consistent with the reason data is being collected; 
                    <E T="03">e.g.,</E>
                     to issue and control United States Government building passes issued to all CMS employees and non-CMS employees who require continuous access to CMS buildings in Baltimore and other CMS and HHS facilities. 
                </P>
                <P>2. Determines that: </P>
                <P>a. The purpose for which the disclosure is to be made can only be accomplished if the record is provided in individually identifiable form; </P>
                <P>
                    b. The purpose for which the disclosure is to be made is of sufficient importance to warrant the effect and/or risk on the privacy of the individual that additional exposure of the record might bring; and 
                    <PRTPAGE P="40939"/>
                </P>
                <P>c. There is a strong probability that the proposed use of the data would in fact accomplish the stated purpose(s). </P>
                <P>3. Requires the information recipient to: </P>
                <P>a. Establish administrative, technical, and physical safeguards to prevent unauthorized use of disclosure of the record; </P>
                <P>b. Remove or destroy at the earliest time all patient-identifiable information; and </P>
                <P>c. Agree to not use or disclose the information for any purpose other than the stated purpose under which the information was disclosed. </P>
                <P>4. Determines that the data are valid and reliable. </P>
                <HD SOURCE="HD1">III. Proposed Routine Use Disclosures of Data in the System </HD>
                <HD SOURCE="HD2">A. Entities Who May Receive Disclosures Under Routine Use </HD>
                <P>These routine uses specify circumstances, in addition to those provided by statute in the Privacy Act of 1974, under which CMS may release information from the EBP without the consent of the individual to whom such information pertains. Each proposed disclosure of information under these routine uses will be evaluated to ensure that the disclosure is legally permissible, including but not limited to ensuring that the purpose of the disclosure is compatible with the purpose for which the information was collected. We are proposing to establish or modify the following routine use disclosures of information maintained in the system: </P>
                <P>1. To agency contractors, or consultants who have been engaged by the Agency to assist in accomplishment of a CMS function relating to the purposes for this SOR and who need to have access to the records in order to assist CMS. </P>
                <P>We contemplate disclosing information under this routine use only in situations in which CMS may enter into a contractual or similar agreement with a third party to assist in accomplishing a CMS function relating to purposes for this SOR. </P>
                <P>CMS occasionally contracts out certain of its functions when doing so would contribute to effective and efficient operations. CMS must be able to give a contractor or consultant whatever information is necessary for the contractor or consultant to fulfill its duties. In these situations, safeguards are provided in the contract prohibiting the contractor or consultant from using or disclosing the information for any purpose other than that described in the contract and requires the contractor or consultant to return or destroy all information at the completion of the contract. </P>
                <P>2. To assist other Federal agencies with activities related to this system and who need to have access to the records in order to perform the activity. </P>
                <P>The FPS may require EBP data to enable them to assist in inquiries about an individual's authorization to enter CMS's central office complex in Baltimore, Maryland and other CMS and HHS Federal buildings </P>
                <P>We contemplate disclosing information under this routine use only in situations in which CMS may enter into a contractual or similar agreement with another Federal agency to assist in accomplishing CMS functions relating to purposes for this SOR. </P>
                <P>3. To Members of Congress or to congressional staff members in response to an inquiry of the congressional office made at the written request of the constituent about whom the record is maintained. </P>
                <P>Federal employees and other individuals who may be identified in this system sometimes request the help of a Member of Congress in resolving an issue relating to a matter before CMS. The Member of Congress then writes CMS, and CMS must be able to give sufficient information to be responsive to the inquiry. </P>
                <P>4. To the Department of Justice (DOJ), court or adjudicatory body when: </P>
                <P>a. The agency or any component thereof, or </P>
                <P>b. Any employee of the agency in his or her official capacity, or </P>
                <P>c. Any employee of the agency in his or her individual capacity where the DOJ agreed to represent the employee, or </P>
                <P>d. The United States Government is a party to litigation or has an interest in such litigation, and by careful review, CMS determines that the records are both relevant and necessary to the litigation. </P>
                <P>Whenever CMS is involved in litigation, or occasionally when another party is involved in litigation and CMS's policies or operations could be affected by the outcome of the litigation, CMS would be able to disclose information to the DOJ, court or adjudicatory body involved. </P>
                <HD SOURCE="HD2">B. Additional Circumstances Affecting Routine Use Disclosures </HD>
                <P>This SOR contains Protected Health Information as defined by HHS regulation “Standards for Privacy of Individually Identifiable Health Information” (45 CFR parts 160 and 164, 65 FR 82462 (12-28-00), as amended by 66 FR 12434 (2-26-01)). Disclosures of Protected Health Information authorized by these routine uses may only be made if, and as, permitted or required by the “Standards for Privacy of Individually Identifiable Health Information”. </P>
                <P>In addition, our policy will be to prohibit release even of non-identifiable data, except pursuant to one of the routine uses, if there is a possibility that an individual can be identified through implicit deduction based on small cell sizes (instances where the patient population is so small that individuals who are familiar with the enrollees could, because of the small size, use this information to deduce the identity of the beneficiary). </P>
                <HD SOURCE="HD1">IV. Safeguards </HD>
                <HD SOURCE="HD2">A. Administrative Safeguards </HD>
                <P>The EBP system will conform to applicable law and policy governing the privacy and security of Federal automated information systems. These include but are not limited to: the Privacy Act of 1984, Computer Security Act of 1987, the Paperwork Reduction Act of 1995, the Clinger-Cohen Act of 1996, and the Office and Management and Budget (OMB) Circular A-130, Appendix III, “Security of Federal Automated Information Resources.” CMS has prepared a comprehensive system security plan as required by OMB Circular A-130, Appendix III. This plan conforms fully to guidance issued by the National Institute for Standards and Technology (NIST) in NIST Special Publication 800-18, “Guide for Developing Security Plans for Information Technology Systems. Paragraphs A-C of this section highlight some of the specific methods that CMS is using to ensure the security of this system and the information within it. </P>
                <P>
                    <E T="03">Authorized users:</E>
                     Personnel having access to the system have been trained in Privacy Act and systems security requirements. Employees and contractors who maintain records in the system are instructed not to release any data until the intended recipient agrees to implement appropriate administrative, technical, procedural, and physical safeguards sufficient to protect the confidentiality of the data and to prevent unauthorized access to the data. In addition, CMS is monitoring the authorized users to ensure against excessive or unauthorized use. Records are used in a designated work area or workstation and the system location is attended at all times during working hours. 
                </P>
                <P>
                    To insure security of the data, the proper level of class user is assigned for each individual user as determined at the Agency level. This prevents 
                    <PRTPAGE P="40940"/>
                    unauthorized users from accessing and modifying critical data. The system database configuration includes five classes of database users: 
                </P>
                <P>
                    • Database Administrator class owns the database objects; 
                    <E T="03">e.g.,</E>
                     tables, triggers, indexes, stored procedures, packages, and has database administration privileges to these objects; 
                </P>
                <P>• Quality Control Administrator class has read and write access to key fields in the database; </P>
                <P>• Quality Indicator Report Generator class has read-only access to all fields and tables; </P>
                <P>• Policy Research class has query access to tables, but are not allowed to access confidential patient identification information; and </P>
                <P>• Submitter class has read and write access to database objects, but no database administration privileges. </P>
                <HD SOURCE="HD2">B. Physical Safeguards </HD>
                <P>All server sites have implemented the following minimum requirements to assist in reducing the exposure of computer equipment and thus achieve an optimum level of protection and security for the EBP system: </P>
                <P>Access to all servers is controlled, with access limited to only those support personnel with a demonstrated need for access. Servers are to be kept in a locked room accessible only by specified management and system support personnel. Each server requires a specific log-on process. All entrance doors are identified and marked. A log is kept of all personnel who were issued a security card, key and/or combination that grants access to the room housing the server, and all visitors are escorted while in this room. All servers are housed in an area where appropriate environmental security controls are implemented, which include measures implemented to mitigate damage to Automated Information System resources caused by fire, electricity, water and inadequate climate controls. </P>
                <P>Protection applied to the workstations, servers and databases include: </P>
                <P>
                    • 
                    <E T="03">User Log on</E>
                    —Authentication is performed by the Primary Domain Controller/Backup Domain Controller of the log-on domain. 
                </P>
                <P>
                    • 
                    <E T="03">Workstation Names</E>
                    —Workstation naming conventions may be defined and implemented at the Agency level. 
                </P>
                <P>
                    • 
                    <E T="03">Hours of Operation</E>
                    —May be restricted by Windows NT. When activated all applicable processes will automatically shut down at a specific time and not be permitted to resume until the predetermined time. The appropriate hours of operation are determined and implemented at the Agency level. 
                </P>
                <P>
                    • 
                    <E T="03">Inactivity Log-out</E>
                    —Access to the NT workstation is automatically logged out after a specified period of inactivity. 
                </P>
                <P>
                    • 
                    <E T="03">Warnings</E>
                    —Legal notices and security warnings display on all servers and workstations. 
                </P>
                <P>
                    • 
                    <E T="03">Remote Access Services (RAS)</E>
                    —Windows NT RAS security handles resource access control. Access to NT resources is controlled for remote users in the same manner as local users, by utilizing Windows NT file and sharing permissions. Dial-in access can be granted or restricted on a user-by-user basis through the Windows NT RAS administration tool. 
                </P>
                <HD SOURCE="HD2">C. Procedural Safeguards </HD>
                <P>All automated systems must comply with Federal laws, guidance, and policies for information systems security as stated previously in this section. Each automated information system should ensure a level of security commensurate with the level of sensitivity of the data, risk, and magnitude of the harm that may result from the loss, misuse, disclosure, or modification of the information contained in the system. </P>
                <HD SOURCE="HD1">V. Effect of the Modified System on Individual Rights </HD>
                <P>CMS proposes to establish this system in accordance with the principles and requirements of the Privacy Act and will collect, use, and disseminate information only as prescribed therein. We will only disclose the minimum personal data necessary to achieve the purpose of EBP. </P>
                <P>Disclosure of information from the SOR will be approved only to the extent necessary to accomplish the purpose of the disclosure. CMS has assigned a higher level of security clearance for the information in this system to provide added security and protection of data in this system. </P>
                <P>CMS will take precautionary measures to minimize the risks of unauthorized access to the records and the potential harm to individual privacy or other personal or property rights. CMS will collect only that information necessary to perform the system's functions. In addition, CMS will make disclosure from the proposed system only with consent of the subject individual, or his/her legal representative, or in accordance with an applicable exception provision of the Privacy Act. </P>
                <P>CMS, therefore, does not anticipate an unfavorable effect on individual privacy as a result of the disclosure of information relating to individuals. </P>
                <SIG>
                    <DATED>Dated: May 22, 2002. </DATED>
                    <NAME>Thomas A. Scully, </NAME>
                    <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                </SIG>
                <PRIACT>
                    <HD SOURCE="HD1">09-70-3002 </HD>
                    <HD SOURCE="HD2">System Name: </HD>
                    <P>Employee Building Pass File (EBP) System, HHS/CMS/OICS. </P>
                    <HD SOURCE="HD2">Security Classification: </HD>
                    <P>Level Three Privacy Act Sensitive. </P>
                    <HD SOURCE="HD2">System Location: </HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), 7500 Security Boulevard, North Building, First Floor (magnetic media), and South Building, Lower Level, Baltimore, Maryland 21244-1850. </P>
                    <HD SOURCE="HD2">Categories of Individuals Covered by the System: </HD>
                    <P>The identified individual includes Federal employees, contractors and consultants, and Government Services Administration (GSA) employees, and contract guards working in CMS's central office complex in Baltimore, Maryland. </P>
                    <HD SOURCE="HD2">Categories of Records in the System: </HD>
                    <P>The system includes the employees' or other individual's name, social security number, identification card number, building/work location, phone number, position, title, grade, and supervisor's name and telephone number. </P>
                    <HD SOURCE="HD2">Authority for Maintenance of the System: </HD>
                    <P>Authority for maintenance of this system of records is given under section 486(c) of Title 40, United States Code (USC) and Title 41, Code of Federal Regulations (CFR), Chapter 101-20.302. </P>
                    <HD SOURCE="HD2">Purpose(s) of the System: </HD>
                    <P>The primary purpose of the system of records is to issue and control United States Government building passes issued to all CMS employees and non-CMS employees who require continuous access to CMS buildings in Baltimore and other CMS and HHS facilities. Information retrieved from this system of records will be used to: support regulatory and policy functions performed within the Agency or by a contractor or consultant, assist other Federal agencies with activities related to this system, support constituent requests made to a congressional representative, and support litigation involving the Agency. </P>
                    <HD SOURCE="HD2">Routine Uses of Records Maintained in the System, Including Categories or Users and the Purposes of Such Uses: </HD>
                    <P>
                        The Privacy Act allows us to disclose information without an individual's 
                        <PRTPAGE P="40941"/>
                        consent if the information is to be used for a purpose that is compatible with the purpose(s) for which the information was collected. Any such compatible use of data is known as a “routine use.” The proposed routine use in this system meets the compatibility requirement of the Privacy Act. 
                    </P>
                    <P>This SOR contains Protected Health Information as defined by HHS regulation “Standards for Privacy of Individually Identifiable Health Information” (45 CFR parts 160 and 164, 65 FR 82462 (12-28-00), as amended by 66 FR 12434 (2-26-01)). Disclosures of Protected Health Information authorized by these routine uses may only be made if, and as, permitted or required by the “Standards for Privacy of Individually Identifiable Health Information”. </P>
                    <P>In addition, our policy will be to prohibit release even of non-identifiable data, except pursuant to one of the routine uses, if there is a possibility that an individual can be identified through implicit deduction based on small cell sizes (instances where the patient population is so small that individuals who are familiar with the enrollees could, because of the small size, use this information to deduce the identity of the beneficiary). We are proposing to establish or modify he following routine use disclosures of information which will be maintained in the system: </P>
                    <P>1. To agency contractors, or consultants who have been engaged by the Agency to assist in accomplishment of a CMS function relating to the purposes for this SOR and who need to have access to the records in order to assist CMS. </P>
                    <P>2. To assist other Federal agencies with activities related to this system and who need to have access to the records in order to perform the activity. </P>
                    <P>3. To Member of Congress or to a congressional staff member in response to an inquiry of the congressional office made at the written request of the constituent about whom the record is maintained. </P>
                    <P>4. To the Department of Justice (DOJ), court or adjudicatory body when:</P>
                    <P>a. The agency or any component thereof, or</P>
                    <P>b. Any employee of the agency in his or her official capacity, or</P>
                    <P>c. Any employee of the agency in his or her individual capacity where the DOJ has agreed to represent the employee, or</P>
                    <P>d. The United States Government is a party to litigation or has an interest in such litigation, and by careful review, CMS determines that the records are both relevant and necessary to the litigation. </P>
                    <HD SOURCE="HD2">Policies and Practices for Storing, Retrieving, Accessing, Retaining, and Disposing of Records in the System: </HD>
                    <HD SOURCE="HD2">Storage: </HD>
                    <P>All records are stored on paper and magnetic media. </P>
                    <HD SOURCE="HD2">Retrievability: </HD>
                    <P>Magnetic media records are retrieved by the name of the employees or other authorized individuals. Paper records are retrieved alphabetically by name. </P>
                    <HD SOURCE="HD2">Safeguards: </HD>
                    <P>CMS has safeguards for authorized users and monitors such users to ensure against excessive or unauthorized use. Personnel having access to the system have been trained in the Privacy Act and systems security requirements. Employees who maintain records in the system are instructed not to release any data until the intended recipient agrees to implement appropriate administrative, technical, procedural, and physical safeguards sufficient to protect the confidentiality of the data and to prevent unauthorized access to the data. </P>
                    <P>In addition, CMS has physical safeguards in place to reduce the exposure of computer equipment and thus achieve an optimum level of protection and security for the EBP system. For computerized records, safeguards have been established in accordance with HHS standards and National Institute of Standards and Technology guidelines, e.g., security codes will be used, limiting access to authorized personnel. System securities are established in accordance with HHS, Information Resource Management (IRM) Circular #10, Automated Information Systems Security Program, CMS Automated Information Systems (AIS) Guide, Systems Securities Policies, and OMB Circular No. A-130 (revised), Appendix III. </P>
                    <HD SOURCE="HD2">Retention and Disposal: </HD>
                    <P>Records are retained for up to 3 years following expiration of an individual's authority to enter designated federal facilities. When an individual is no longer authorized, information is deleted from magnetic media immediately. </P>
                    <HD SOURCE="HD2">System Manager and Address: </HD>
                    <P>Director, Division of Facilities Management Services, Administrative Services Group, Office of Internal Customer Support, CMS, Room SLL-11-08, 7500 Security Boulevard, Baltimore, Maryland 21244-1850. </P>
                    <HD SOURCE="HD2">Notification Procedure: </HD>
                    <P>For purpose of access, the subject individual should write to the system manager who will require the system name, identification card number, address, and for verification purposes, the subject individual's name (woman's maiden name, if applicable), and social security number (SSN). Furnishing the SSN is voluntary, but it may make searching for a record easier and prevent delay. </P>
                    <HD SOURCE="HD2">Record Access Procedure: </HD>
                    <P>For purpose of access, use the same procedures outlined in Notification Procedures above. Requestors should also reasonably specify the record contents being sought. (These procedures are in accordance with Department regulation 45 CFR 5b.5(a)(2)). </P>
                    <HD SOURCE="HD2">Contesting Record Procedures: </HD>
                    <P>The subject individual should contact the system manager named above, and reasonably identify the record and specify the information to be contested. State the corrective action sought and the reasons for the correction with supporting justification. (These procedures are in accordance with Department regulation 45 CFR 5b.7). </P>
                    <HD SOURCE="HD2">Record Source Categories: </HD>
                    <P>CMS obtains information in this system from the individuals who are covered by this system. </P>
                    <HD SOURCE="HD2">Systems Exempted from Certain Provisions of the Act: </HD>
                    <P>None. </P>
                </PRIACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15008 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-03-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <SUBJECT>Privacy Act of 1974; Report of Modified or Altered System </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Health and Human Services (HHS), Centers for Medicare &amp; Medicaid Services (CMS) (formerly the Health Care Financing Administration). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of modified or altered system of records (SOR). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In accordance with the requirements of the Privacy Act of 1974, we are proposing to modify or alter a SOR, “Physician/Supplier 1099 File (Statement for Recipients of Medical and Health Care Payments)(1099), System No. 09-70-0517.” We propose to delete published routine use number 4 authorizing disclosure to contractors, and an unnumbered routine use 
                        <PRTPAGE P="40942"/>
                        authorizing disclosure to the Social Security Administration (SSA). The proposed routine use for contractors and consultants makes material changes to published routine use number 4, and as proposed should be treated as a new routine use. Disclosure of data from this system to the SSA is no longer necessary since SSA has been established as a separate agency outside of the HHS and a routine use for the purpose stated is no longer necessary. 
                    </P>
                    <P>We propose to add two new routine uses to combat fraud and abuse in certain federally funded health care programs. The security classification previously reported as “None” will be modified to reflect that the data in this system is considered to be “Level Three Privacy Act Sensitive.” We are modifying the language in the remaining routine uses to provide clarity to CMS's intention to disclose individual-specific information contained in this system. The routine uses will then be prioritized and reordered according to their usage. We will also take the opportunity to update any sections of the system that were affected by the recent reorganization and to update language in the administrative sections to correspond with language used in other CMS SORs. </P>
                    <P>
                        The primary purpose of the SOR is to provide periodic reporting to the Internal Revenue Service (IRS). Information in this system will also be disclosed to: the IRS, support regulatory and policy functions performed within the agency or by a contractor or consultant, support constituent requests made to a congressional representative, support litigation involving the agency related to this system of records, and combat fraud and abuse in certain federally funded health care programs. We have provided background information about the modified system in the “Supplementary Information” section below. Although the Privacy Act requires only that CMS provide an opportunity for interested persons to comment on the proposed routine uses, CMS invites comments on all portions of this notice. 
                        <E T="03">See</E>
                          
                        <E T="02">Effective Dates</E>
                         section for comment period. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">EFFECTIVE DATES:</HD>
                    <P>CMS filed a modified or altered system report with the Chair of the House Committee on Government Reform and Oversight, the Chair of the Senate Committee on Governmental Affairs, and the Administrator, Office of Information and Regulatory Affairs, Office of Management and Budget (OMB) on May 30, 2002. To ensure that all parties have adequate time in which to comment, the modified or altered SOR, including routine uses, will become effective 40 days from the publication of the notice, or from the date it was submitted to OMB and the congress, whichever is later, unless CMS receives comments that require alterations to this notice. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>The public should address comments to: Director, Division of Data Liaison and Distribution, CMS, Room N2-04-27, 7500 Security Boulevard, Baltimore, Maryland 21244-1850. Comments received will be available for review at this location, by appointment, during regular business hours, Monday through Friday from 9 a.m.-3 p.m., eastern daylight time. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        G. Jeff Chaney, Director, Division of Accounting, Accounting and Risk Management Group, Office of Financial Management, CMS, Room N3-11-17, 7500 Security Boulevard, Baltimore, Maryland 21244-1850. The telephone number is 410-786-5412. The e-mail address is 
                        <E T="03">gchaney@cms.hhs.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Description of the Modified System </HD>
                <HD SOURCE="HD2">A. Background </HD>
                <P>
                    In 1980, CMS established a SOR under the authority of the Internal Revenue Code, Title 26 United States Code (USC) sec. 6041. Notice of this system, “Physician/Supplier 1099 File (Statement for Recipients of Medical and Health Care Payments), HHS/CMS/BPO, System No. 09-70-0517” was published in the 
                    <E T="04">Federal Register</E>
                     on Monday, December 22, 1980 (45 FR 84476), 61 FR 6645 (added unnumbered social security use), 63 FR 50552 (added three fraud and abuse uses), and 65 FR 50552 (deleted one and modified two fraud and abuse uses). 
                </P>
                <HD SOURCE="HD2">B. Statutory and Regulatory Basis for SOR </HD>
                <P>Authority for the maintenance of this SOR is given under the Internal Revenue Code, Title 26 United States Code (USC) sec. 6041. </P>
                <HD SOURCE="HD1">II. Collection and Maintenance of Data in the System </HD>
                <HD SOURCE="HD2">A. Scope of the Data Collected </HD>
                <P>The system contains information on total Medicare payments that have been made to physicians and suppliers by Medicare carriers and intermediaries. It contains the name, address, assigned provider number, employer identification number (EIN), and social security number (SSN) of the physicians and suppliers. </P>
                <HD SOURCE="HD2">B. Agency Policies, Procedures, and Restrictions on the Routine Use </HD>
                <P>The Privacy Act permits us to disclose information without an individual's consent if the information is to be used for a purpose which is compatible with the purpose(s) for which the information was collected. Any such disclosure of data is known as a “routine use.” The government will only release 1099 information that can be associated with an individual as provided for under “Section III. Proposed Routine Use Disclosures of Data in the System.” Both identifiable and non-identifiable data may be disclosed under a routine use. We will only disclose the minimum personal data necessary to achieve the purpose of 1099. CMS has the following policies and procedures concerning disclosures of information which will be maintained in the system. In general, disclosure of information from the system of records will be approved only for the minimum information necessary to accomplish the purpose of the disclosure only after CMS: </P>
                <P>1. Determines that the use or disclosure is consistent with the reason that the data is being collected, e.g., to provide periodic reporting to the IRS. </P>
                <P>2. Determines:</P>
                <P>a. That the purpose for which the disclosure is to be made can only be accomplished if the record is provided in individually identifiable form; </P>
                <P>b. That the purpose for which the disclosure is to be made is of sufficient importance to warrant the effect and/or risk on the privacy of the individual that additional exposure of the record might bring; and </P>
                <P>c. That there is a strong probability that the proposed use of the data would in fact accomplish the stated purpose(s). </P>
                <P>3. Requires the information recipient to: </P>
                <P>a. Establish administrative, technical, and physical safeguards to prevent unauthorized use of disclosure of the record; </P>
                <P>b. Remove or destroy at the earliest time all individually-identifiable information; andgree to not use or disclose the information for any purpose other than the stated purpose under which the information was disclosed. </P>
                <P>4. Determines that the data are valid and reliable. </P>
                <HD SOURCE="HD1">III. Proposed Routine Use Disclosures of Data in the System </HD>
                <HD SOURCE="HD2">A. Entities Who May Receive Disclosures Under Routine Use </HD>
                <P>
                    These routine uses specify circumstances, in addition to those provided by statute in the Privacy Act 
                    <PRTPAGE P="40943"/>
                    of 1974, under which CMS may release information from the 1099 without the consent of the individual to whom such information pertains. Each proposed disclosure of information under these routine uses will be evaluated to ensure that the disclosure is legally permissible, including but not limited to ensuring that the purpose of the disclosure is compatible with the purpose for which the information was collected. We are proposing to establish or modify the following routine use disclosures of information maintained in the system: 
                </P>
                <P>1. To the Internal Revenue Service in connection with the determination of the individual's self-employment income. </P>
                <P>We contemplate disclosing information under this routine use only in situations in which the IRS requires 1099 data to assist in the implementation and maintenance of the IRS code. </P>
                <P>2. To agency contractors, or consultants who have been engaged by the agency to assist in accomplishment of a CMS function relating to the purposes for this SOR and who need to have access to the records in order to assist CMS. </P>
                <P>We contemplate disclosing information under this routine use only in situations in which CMS may enter into a contractual or similar agreement with a third party to assist in accomplishing a CMS function relating to purposes for this SOR. CMS occasionally contracts out certain of its functions when doing so would contribute to effective and efficient operations. CMS must be able to give a contractor or consultant whatever information is necessary for the contractor or consultant to fulfill its duties. In these situations, safeguards are provided in the contract prohibiting the contractor or consultant from using or disclosing the information for any purpose other than that described in the contract and requires the contractor or consultant to return or destroy all information at the completion of the contract. </P>
                <P>3. To Member of Congress or to a congressional staff member in response to an inquiry of the congressional office made at the written request of the constituent about whom the record is maintained. </P>
                <P>Individuals sometimes request the help of a Member of Congress in resolving issues relating to a matter before CMS. The Member of Congress then writes CMS, and CMS must be able to give sufficient information to be responsive to the inquiry. </P>
                <P>4. To the Department of Justice (DOJ), court or adjudicatory body when: </P>
                <P>a. The agency or any component thereof, or </P>
                <P>b. Any employee of the agency in his or her official capacity, or </P>
                <P>c. Any employee of the agency in his or her individual capacity where the DOJ has agreed to represent the employee, or </P>
                <P>d. The United States Government, </P>
                <FP>is a party to litigation or has an interest in such litigation, and by careful review, CMS determines that the records are both relevant and necessary to the litigation. </FP>
                <P>Whenever CMS is involved in litigation, or occasionally when another party is involved in litigation and CMS's policies or operations could be affected by the outcome of the litigation, CMS would be able to disclose information to the DOJ, court or adjudicatory body involved. </P>
                <P>5. To a CMS contractor (including, but not limited to fiscal intermediaries and carriers) that assists in the administration of a CMS-administered health benefits program, or to a grantee of a CMS-administered grant program, when disclosure is deemed reasonably necessary by CMS to prevent, deter, discover, detect, investigate, examine, prosecute, sue with respect to, defend against, correct, remedy, or otherwise combat fraud or abuse in such program. </P>
                <P>We contemplate disclosing information under this routine use only in situations in which CMS may enter into a contract or grant with a third party to assist in accomplishing CMS functions relating to the purpose of combating fraud and abuse. </P>
                <P>CMS occasionally contracts out certain of its functions when doing so would contribute to effective and efficient operations. CMS must be able to give a contractor or grantee whatever information is necessary for the contractor or grantee to fulfill its duties. In these situations, safeguards are provided in the contract prohibiting the contractor or grantee from using or disclosing the information for any purpose other than that described in the contract and requiring the contractor or grantee to return or destroy all information. </P>
                <P>6. To another federal agency or to an instrumentality of any governmental jurisdiction within or under the control of the United States (including any state or local governmental agency), that administers, or that has the authority to investigate potential fraud or abuse in, a health benefits program funded in whole or in part by federal funds, when disclosure is deemed reasonably necessary by CMS to prevent, deter, discover, detect, investigate, examine, prosecute, sue with respect to, defend against, correct, remedy, or otherwise combat fraud or abuse in such programs. </P>
                <P>Other agencies may require 1099 information for the purpose of combating fraud and abuse in such federally funded programs. </P>
                <HD SOURCE="HD2">B. Additional Circumstances Affecting Routine Use Disclosures </HD>
                <P>This SOR contains Protected Health Information as defined by HHS regulation “Standards for Privacy of Individually Identifiable Health Information” (45 CFR parts 160 and 164, 65 FR 82462 (12-28-00), as amended by 66 FR 12434 (2-26-01)). Disclosures of Protected Health Information authorized by these routine uses may only be made if, and as, permitted or required by the “Standards for Privacy of Individually Identifiable Health Information”. </P>
                <P>In addition, our policy will be to prohibit release even of non-identifiable data, except pursuant to one of the routine uses, if there is a possibility that an individual can be identified through implicit deduction based on small cell sizes (instances where the patient population is so small that individuals who are familiar with the enrollees could, because of the small size, use this information to deduce the identity of the beneficiary). </P>
                <HD SOURCE="HD1">IV. Safeguards </HD>
                <HD SOURCE="HD2">A. Administrative Safeguards </HD>
                <P>The 1099 system will conform to applicable law and policy governing the privacy and security of Federal automated information systems. These include but are not limited to: the Privacy Act of 1984, Computer Security Act of 1987, the Paperwork Reduction Act of 1995, the Clinger-Cohen Act of 1996, and the Office and Management and Budget (OMB) Circular A-130, Appendix III, “Security of Federal Automated Information Resources.” CMS has prepared a comprehensive system security plan as required by OMB Circular A-130, Appendix III. This plan conforms fully to guidance issued by the National Institute for Standards and Technology (NIST) in NIST Special Publication 800-18, “Guide for Developing Security Plans for Information Technology Systems. Paragraphs A-C of this section highlight some of the specific methods that CMS is using to ensure the security of this system and the information within it. </P>
                <P>
                    <E T="03">Authorized users:</E>
                     Personnel having access to the system have been trained in Privacy Act and systems security requirements. Employees and 
                    <PRTPAGE P="40944"/>
                    contractors who maintain records in the system are instructed not to release any data until the intended recipient agrees to implement appropriate administrative, technical, procedural, and physical safeguards sufficient to protect the confidentiality of the data and to prevent unauthorized access to the data. In addition, CMS is monitoring the authorized users to ensure against excessive or unauthorized use. Records are used in a designated work area or workstation and the system location is attended at all times during working hours. 
                </P>
                <P>To insure security of the data, the proper level of class user is assigned for each individual user as determined at the Agency level. This prevents unauthorized users from accessing and modifying critical data. The system database configuration includes five classes of database users: </P>
                <P>• Database Administrator class owns the database objects; e.g., tables, triggers, indexes, stored procedures, packages, and has database administration privileges to these objects; </P>
                <P>• Quality Control Administrator class has read and write access to key fields in the database; </P>
                <P>• Quality Indicator Report Generator class has read-only access to all fields and tables; </P>
                <P>• Policy Research class has query access to tables, but are not allowed to access confidential patient identification information; and </P>
                <P>• Submitter class has read and write access to database objects, but no database administration privileges. </P>
                <HD SOURCE="HD2">
                    B. 
                    <E T="03">Physical Safeguards:</E>
                </HD>
                <P>All server sites have implemented the following minimum requirements to assist in reducing the exposure of computer equipment and thus achieve an optimum level of protection and security for the 1099 system: </P>
                <P>Access to all servers is controlled, with access limited to only those support personnel with a demonstrated need for access. Servers are to be kept in a locked room accessible only by specified management and system support personnel. Each server requires a specific log-on process. All entrance doors are identified and marked. A log is kept of all personnel who were issued a security card, key and/or combination that grants access to the room housing the server, and all visitors are escorted while in this room. All servers are housed in an area where appropriate environmental security controls are implemented, which include measures implemented to mitigate damage to Automated Information System resources caused by fire, electricity, water and inadequate climate controls. </P>
                <P>Protection applied to the workstations, servers and databases include: </P>
                <P>• User Log on—Authentication is performed by the Primary Domain Controller/Backup Domain Controller of the log-on domain. </P>
                <P>• Workstation Names—Workstation naming conventions may be defined and implemented at the Agency level. </P>
                <P>• Hours of Operation—May be restricted by Windows NT. When activated all applicable processes will automatically shut down at a specific time and not be permitted to resume until the predetermined time. The appropriate hours of operation are determined and implemented at the Agency level. </P>
                <P>• Inactivity Log-out—Access to the NT workstation is automatically logged out after a specified period of inactivity. </P>
                <P>• Warnings—Legal notices and security warnings display on all servers and workstations. </P>
                <P>• Remote Access Services (RAS)—Windows NT RAS security handles resource access control. Access to NT resources is controlled for remote users in the same manner as local users, by utilizing Windows NT file and sharing permissions. Dial-in access can be granted or restricted on a user-by-user basis through the Windows NT RAS administration tool. </P>
                <HD SOURCE="HD2">C. Procedural Safeguards</HD>
                <P>All automated systems must comply with Federal laws, guidance, and policies for information systems security as stated previously in this section. Each automated information system should ensure a level of security commensurate with the level of sensitivity of the data, risk, and magnitude of the harm that may result from the loss, misuse, disclosure, or modification of the information contained in the system. </P>
                <HD SOURCE="HD1">V. Effect of the Modified System on Individual Rights </HD>
                <P>CMS proposes to establish this system in accordance with the principles and requirements of the Privacy Act and will collect, use, and disseminate information only as prescribed therein. We will only disclose the minimum personal data necessary to achieve the purpose of 1099. Disclosure of information from the SOR will be approved only to the extent necessary to accomplish the purpose of the disclosure. CMS has assigned a higher level of security clearance for the information in this system to provide added security and protection of data in this system. </P>
                <P>CMS will take precautionary measures to minimize the risks of unauthorized access to the records and the potential harm to individual privacy or other personal or property rights. CMS will collect only that information necessary to perform the system's functions. In addition, CMS will make disclosure from the proposed system only with consent of the subject individual, or his/her legal representative, or in accordance with an applicable exception provision of the Privacy Act. </P>
                <P>CMS, therefore, does not anticipate an unfavorable effect on individual privacy as a result of the disclosure of information relating to individuals. </P>
                <SIG>
                    <DATED>Dated: May 30, 2002. </DATED>
                    <NAME>Thomas A. Scully, </NAME>
                    <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                </SIG>
                <PRIACT>
                    <HD SOURCE="HD1">09-70-0517 </HD>
                    <HD SOURCE="HD2">SYSTEM NAME: </HD>
                    <P>Physician/Supplier 1099 File (Statement for Recipients of Medical and Health Care Payments)(1099), HHS/CMS/OFM. </P>
                    <HD SOURCE="HD2">SECURITY CLASSIFICATION: </HD>
                    <P>Level Three Privacy Act Sensitive </P>
                    <HD SOURCE="HD2">SYSTEM LOCATION: </HD>
                    <P>CMS Data Center, 7500 Security Boulevard, North Building, First Floor, Baltimore, Maryland 21244-1850. </P>
                    <HD SOURCE="HD2">CATEGORIES OF INDIVIDUALS COVERED BY THE SYSTEM: </HD>
                    <P>The system contains information on total Medicare payments that have been made to physicians and suppliers by Medicare carriers and intermediaries. </P>
                    <HD SOURCE="HD2">CATEGORIES OF RECORDS IN THE SYSTEM: </HD>
                    <P>The system contains the name, address, assigned provider number, employer identification number (EIN), and social security number (SSN) of the physicians and suppliers. </P>
                    <HD SOURCE="HD2">AUTHORITY FOR MAINTENANCE OF THE SYSTEM: </HD>
                    <P>Authority for the maintenance of this SOR is given under the Internal Revenue Code, Title 26 United States Code (USC) sec. 6041. </P>
                    <HD SOURCE="HD2">PURPOSE(S): </HD>
                    <P>
                        The primary purpose of the SOR is to provide periodic reporting to the Internal Revenue Service (IRS). Information in this system will also be disclosed to: the IRS, support regulatory and policy functions performed within the agency or by a contractor or consultant, support constituent requests 
                        <PRTPAGE P="40945"/>
                        made to a congressional representative, support litigation involving the agency related to this system of records, and combat fraud and abuse in certain federally funded health care programs. 
                    </P>
                    <HD SOURCE="HD2">ROUTINE USES OF RECORDS MAINTAINED IN THE SYSTEM, INCLUDING CATEGORIES OR USERS AND THE PURPOSES OF SUCH USES: </HD>
                    <P>These routine uses specify circumstances, in addition to those provided by statute in the Privacy Act of 1974, under which CMS may release information from the EDB without the consent of the individual to whom such information pertains. Each proposed disclosure of information under these routine uses will be evaluated to ensure that the disclosure is legally permissible, including but not limited to ensuring that the purpose of the disclosure is compatible with the purpose for which the information was collected. In addition, our policy will be to prohibit release even of non-identifiable data, except pursuant to one of the routine uses, if there is a possibility that an individual can be identified through implicit deduction based on small cell sizes (instances where the patient population is so small that individuals who are familiar with the enrollees could, because of the small size, use this information to deduce the identity of the beneficiary). </P>
                    <P>
                        This SOR contains Protected Health Information as defined by HHS regulation “Standards for Privacy of Individually Identifiable Health Information” (45 CFR parts 160 and 164, 65 
                        <E T="04">Federal Register</E>
                         (FR) 82462 (12-28-00), as amended by 66 FR 12434 (2-26-01)). Disclosures of Protected Health Information authorized by these routine uses may only be made if, and as, permitted or required by the “Standards for Privacy of Individually Identifiable Health Information.” We are proposing to establish or modify the following routine use disclosures of information maintained in the system: 
                    </P>
                    <P>1. To the Internal Revenue Service in connection with the determination of the individual's self-employment income. </P>
                    <P>2. To agency contractors, or consultants who have been engaged by the agency to assist in accomplishment of a CMS function relating to the purposes for this SOR and who need to have access to the records in order to assist CMS. </P>
                    <P>3. To a Member of Congress or to a congressional staff member in response to an inquiry of the congressional office made at the written request of the constituent about whom the record is maintained. </P>
                    <P>4. To the Department of Justice (DOJ), court or adjudicatory body when: </P>
                    <P>a. The agency or any component thereof, or </P>
                    <P>b. Any employee of the agency in his or her official capacity, or </P>
                    <P>c. Any employee of the agency in his or her individual capacity where the DOJ has agreed to represent the employee, or </P>
                    <P>d. The United States Government, is a party to litigation or has an interest in such litigation, and by careful review, CMS determines that the records are both relevant and necessary to the litigation </P>
                    <P>5. To a CMS contractor (including, but not limited to fiscal intermediaries and carriers) that assists in the administration of a CMS-administered health benefits program, or to a grantee of a CMS-administered grant program, when disclosure is deemed reasonably necessary by CMS to prevent, deter, discover, detect, investigate, examine, prosecute, sue with respect to, defend against, correct, remedy, or otherwise combat fraud or abuse in such program. </P>
                    <P>6. To another federal agency or to an instrumentality of any governmental jurisdiction within or under the control of the United States (including any state or local governmental agency), that administers, or that has the authority to investigate potential fraud or abuse in, a health benefits program funded in whole or in part by federal funds, when disclosure is deemed reasonably necessary by CMS to prevent, deter, discover, detect, investigate, examine, prosecute, sue with respect to, defend against, correct, remedy, or otherwise combat fraud or abuse in such programs. </P>
                    <HD SOURCE="HD2">POLICIES AND PRACTICES FOR STORING, RETRIEVING, ACCESSING, RETAINING, AND DISPOSING OF RECORDS IN THE SYSTEM: </HD>
                    <HD SOURCE="HD2">STORAGE: </HD>
                    <P>Computer diskette and on magnetic storage media. </P>
                    <HD SOURCE="HD2">RETRIEVABILITY: </HD>
                    <P>Information maintained in this system can be retrieved by the name, SSN, EIN, and an assigned physician/supplier identification number. </P>
                    <HD SOURCE="HD2">SAFEGUARDS: </HD>
                    <P>CMS has safeguards for authorized users and monitors such users to ensure against excessive or unauthorized use. Personnel having access to the system have been trained in the Privacy Act and systems security requirements. Employees who maintain records in the system are instructed not to release any data until the intended recipient agrees to implement appropriate administrative, technical, procedural, and physical safeguards sufficient to protect the confidentiality of the data and to prevent unauthorized access to the data. </P>
                    <P>In addition, CMS has physical safeguards in place to reduce the exposure of computer equipment and thus achieve an optimum level of protection and security for the 1099 system. For computerized records, safeguards have been established in accordance with the Department of Health and Human Services (HHS) standards and National Institute of Standards and Technology guidelines, e.g., security codes will be used, limiting access to authorized personnel. System securities are established in accordance with HHS, Information Resource Management (IRM) Circular #10, Automated Information Systems Security Program; CMS Automated Information Systems (AIS) Guide, Systems Securities Policies, and OMB Circular No. A-130 (revised), Appendix III. </P>
                    <HD SOURCE="HD2">RETENTION AND DISPOSAL: </HD>
                    <P>Records are maintained in a secure storage area with identifiers for 5 years. </P>
                    <HD SOURCE="HD2">SYSTEM MANAGER(S) AND ADDRESSES</HD>
                    <P>Director, Division of Accounting, Accounting and Risk Management Group, Office of Financial Management, CMS, Room N3-11-17, 7500 Security Boulevard, Baltimore, Maryland 21244-1850. </P>
                    <HD SOURCE="HD2">NOTIFICATION PROCEDURE: </HD>
                    <P>For purpose of access, the subject individual should write to the system manager who will require the system name, address, date of birth, and sex, and for verification purposes, the subject individual's name (woman's maiden name, if applicable), and social security number (SSN). Furnishing the SSN is voluntary, but it may make searching for a record easier and prevent delay. </P>
                    <HD SOURCE="HD2">RECORD ACCESS PROCEDURE: </HD>
                    <P>For purpose of access, use the same procedures outlined in Notification Procedures above. Requestors should also reasonably specify the record contents being sought. (These procedures are in accordance with Department regulation 45 CFR 5b.5(a)(2)). </P>
                    <HD SOURCE="HD2">CONTESTING RECORD PROCEDURES: </HD>
                    <P>
                        The subject individual should contact the system manager named above, and reasonably identify the record and specify the information to be contested. State the corrective action sought and the reasons for the correction with supporting justification. (These 
                        <PRTPAGE P="40946"/>
                        procedures are in accordance with Department regulation 45 CFR 5b.7). 
                    </P>
                    <HD SOURCE="HD2">RECORD SOURCE CATEGORIES: </HD>
                    <P>The record of the total annual payments made to each physician or supplier is derived from the individual Medicare bill payments. </P>
                    <HD SOURCE="HD2">SYSTEMS EXEMPTED FROM CERTAIN PROVISIONS OF THE ACT: </HD>
                    <P>None.</P>
                </PRIACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15009 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-03-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. 01N-0590]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for OMB Review; Comment Request; Salmonella Discovery System Pilot Study</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing that the proposed collection of information listed below has been submitted to the Office of Management and Budget (OMB) for review and clearance under the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments on the collection of information by July 15, 2002.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit written comments on the collection of information to the Office of Information and Regulatory Affairs, OMB, New Executive Office Bldg., 725 17th St. NW., rm. 10235, Washington, DC 20503, Attn:  Stuart Shapiro, Desk Officer for FDA.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Karen L. Nelson, Office of Information Resources Management (HFA-250), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857, 301-827-1482.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with 44 U.S.C. 3507, FDA has submitted the following proposed collection of information to OMB for review and clearance.</P>
                <HD SOURCE="HD1">Salmonella Discovery System Pilot Study</HD>
                <P>
                    FDA's Center for Drug Evaluation and Research, Office of Pharmaceutical Science, Informatics and Computational Safety Analysis Staff  intends to conduct a 
                    <E T="03">Salmonella</E>
                     Discovery System Pilot Study (the pilot study).  The primary goal of the pilot study is to construct and execute a mutually beneficial process by which FDA and pharmaceutical companies can share information based on their proprietary toxicology study data and thereby expand their own knowledge databases.  This process will be designed and conducted using procedures that do not compromise the identity and chemical structures of the individual collaborator's proprietary chemicals.
                </P>
                <P>The three major objectives of the pilot study are to:</P>
                <P>
                    •  Build a joint and comprehensive FDA/pharmaceutical industry database for compounds tested in the 
                    <E T="03">Salmonella typhimurium</E>
                     reverse mutagenicity assay;
                </P>
                <P>
                    •  Use these data to construct a new enhanced 
                    <E T="03">Salmonella t.</E>
                     mutagenicity assay database module for the MultiCASE quantitative structure activity relationship software program; and
                </P>
                <P>
                    •  Employ the recently developed MultiCASE expert system (MCASE-ES) to predict the mutagenic response, mutagenic potency, and mechanism of mutagenesis of test chemicals in 
                    <E T="03">Salmonella t.</E>
                </P>
                <P>The pilot study will be a joint venture designed to maximize the benefits and minimize the risks to all collaborators.  FDA intends to send letters to companies that have purchased either MultiCASE or CASETOXII software programs to invite them to become a collaborator in the project.</P>
                <P>
                    FDA intends to request that each collaborator submit the following data electronically:   (1)  Test compound chemical structures; and (2) assay data, identifying  the type of 
                    <E T="03">Salmonella</E>
                     mutagenicity assay used in the studies, the source and concentration of any exogenous activation system used, and the average number of revertants/plate for the negative control, positive control, and each of the test compound treatment groups.  Although there is no minimum requirement for the number of test compounds to be submitted to FDA, the agency would expect to receive at least 200 compounds from each collaborator.  Each company will be able to identify its own compounds in the resulting discovery system,  and the more data submitted, the greater the coverage will be for each company's molecular universe.
                </P>
                <P>
                    FDA intends to act as the broker for the pilot study and will be responsible for the confidentiality and integrity of each collaborator's proprietary data.  The number of compounds in the database module will depend upon the number of collaborators and the size of the data sets they contribute to the pilot study.  After the enhanced 
                    <E T="03">Salmonella</E>
                     discovery system has been constructed and tested, FDA intends to custom prepare individual discovery systems for each collaborator.
                </P>
                <P>The anticipated benefits to collaborators include:</P>
                <P>
                    •  Receipt of a new expanded 
                    <E T="03">Salmonella in silico</E>
                     discovery tool at no cost;
                </P>
                <P>
                    •  Access to proprietary molecular fragment data derived from 
                    <E T="03">Salmonella t.</E>
                     mutagenicity studies from FDA and other collaborator archives;
                </P>
                <P>
                    •  Comprehensive lists of molecular structural alerts correlated with mutagenicity in 
                    <E T="03">Salmonella t.</E>
                    , including previously uncharacterized alerts derived from heretofore inaccessible undeveloped lead pharmaceutical test data; and
                </P>
                <P>
                    •  A 
                    <E T="03">Salmonella</E>
                     discovery system which should provide high coverage and high predictive performance for organic chemicals in each company's combinatorial and lead chemical data sets.
                </P>
                <P>
                    The 
                    <E T="03">Salmonella</E>
                     discovery system provided by FDA will be compatible with each company's current MCASE software program currently v. 3.46 and will supplement current 
                    <E T="03">Salmonella</E>
                     modules purchased from MultiCASE, Inc.
                </P>
                <P>Participation in this pilot study will be voluntary.  FDA estimates that approximately 12 companies will participate, and that it will take each company approximately 8 hours to compile the information from electronic archives and submit the requested data and information.</P>
                <P>FDA estimates the burden of this collection of information as follows:</P>
                <PRTPAGE P="40947"/>
                <GPOTABLE COLS="5" OPTS="L1,nj,i1" CDEF="xl50,15,15,15,15">
                    <TTITLE>
                        <E T="04">Table</E>
                         1.—
                        <E T="04">Estimated Annual Reporting Burden</E>
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">No. of Respondents</CHED>
                        <CHED H="1">Annual Frequency Per Response</CHED>
                        <CHED H="1">Total Annual Responses</CHED>
                        <CHED H="1">Hours per Response</CHED>
                        <CHED H="1">Total Hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">12</ENT>
                        <ENT>1</ENT>
                        <ENT>12</ENT>
                        <ENT>8</ENT>
                        <ENT>96</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                        There are no capital costs or operating and maintenance costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of January 28, 2002 (67 FR 3902), the agency requested comments on the proposed collections of information.  No comments were received.
                </P>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>Margaret M. Dotzel,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15002 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. 02N-0054]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities; Submission for OMB Review; Comment Request; Labeling Requirements for Color Additives (Other Than Hair Dyes) and Petitions</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing that the proposed collection of information listed below has been submitted to the Office of Management and Budget (OMB) for review and clearance under the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written comments on the collection of information by July 15, 2002.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit written comments on the collection of information to the Office of Information and Regulatory Affairs, OMB, New Executive Office Bldg., 725 17th St. NW., rm. 10235, Washington, DC  20503, Attn: Stuart Shapiro, Desk Officer for FDA.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Peggy Schlosburg, Office of Information Resources Management (HFA-250), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD  20857, 301-827-1223.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In compliance with 44 U.S.C. 3507, FDA has submitted the following proposed collection of information to OMB for review and clearance.</P>
                <HD SOURCE="HD1">Labeling Requirements for Color Additives (Other Than Hair Dyes)—21 CFR 70.25 and Petitions—21 CFR 71.1 (OMB Control Number 0910-0185)—Extension</HD>
                <P>Section 721(a) of the Federal Food, Drug, and Cosmetic Act (the act) (21 U.S.C. 379e(a)) provides that a color additive shall be deemed to be unsafe unless the additive and its use are in conformity with a regulation that describes the condition(s) under which the additive may safely be used, or unless the additive and its use conform to the terms of an exemption for investigational use issued under section 721(f) of the act. Color additive petitions are submitted by individuals or companies to obtain approval of a new color additive or a change in the conditions of use permitted for a color additive that is already approved. Section 71.1 (21 CFR 71.1) specifies the information that a petitioner must submit in order to establish the safety of a color additive and to secure the issuance of a regulation permitting its use.</P>
                <P>FDA scientific personnel review color additive petitions to ensure that the intended use of the color additive in or on food, drugs, cosmetics, and medical devices is suitable and safe. Color additive petitions were specifically provided for by Congress when it enacted the Color Additive Amendments of 1960 (Public Law 94-295). If FDA stopped accepting color additive petitions or stopped requiring them to contain the information specified in § 71.1, there would be no way to bring new uses of listed color additives or new color additives to market.  FDA's color additive labeling requirements in § 70.25 (21 CFR 70.25) require that color additives that are to be used in food, drugs, devices, or cosmetics be labeled with sufficient information to ensure their safe use.</P>
                <P>Respondents are businesses engaged in the manufacture or sale of color additives for use in food, drugs, cosmetics, or medical devices.</P>
                <P>
                    In the 
                    <E T="04">Federal Register</E>
                     of February 28, 2002 (67 FR 9297), the agency requested comments on the proposed collection of information.  No comments were received that pertained to this collection of information.
                </P>
                <P>FDA estimates the burden of this collection of information as follows:</P>
                <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="xl18,6.6,8.8,6.6,8.8,8.8,7.7">
                    <TTITLE>
                        <E T="04">Table</E>
                         1.—
                        <E T="04">Estimated Annual Reporting Burden</E>
                        <SU>1</SU>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">21 CFR Section</CHED>
                        <CHED H="1">
                            No. of 
                            <LI>Respondents</LI>
                        </CHED>
                        <CHED H="1">Annual Frequency per Response</CHED>
                        <CHED H="1">Total Annual Responses</CHED>
                        <CHED H="1">Hours per Response</CHED>
                        <CHED H="1">Total Operating and Maintenance Costs</CHED>
                        <CHED H="1">Total Hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">70.25</ENT>
                        <ENT>0</ENT>
                        <ENT>1</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">71.1</ENT>
                        <ENT>3</ENT>
                        <ENT>1</ENT>
                        <ENT>3</ENT>
                        <ENT>2,000</ENT>
                        <ENT>$8,600</ENT>
                        <ENT>6,000</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total</ENT>
                        <ENT> </ENT>
                        <ENT> </ENT>
                        <ENT> </ENT>
                        <ENT> </ENT>
                        <ENT> </ENT>
                        <ENT>6,000</ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         There are no capital costs associated with this collection of information.
                    </TNOTE>
                </GPOTABLE>
                <P>This estimate is based on the number of new color additive petitions received in fiscal year 2000 and the total hours expended by petitioners to prepare the petitions. Although the burden varies with the type of petition submitted, a color additive petition involves analytical work and appropriate toxicology studies, as well as the work of drafting the petition itself. Because labeling requirements under § 70.25 for a particular color additive involve information required as part of the color additive petition safety review process, the estimate for the number of respondents is the same for § 70.25 as for § 71.1, and the burden hours for labeling are included in the estimate for § 71.1.</P>
                <P>
                    Color additives are subjected to payment of fees for the petitioning 
                    <PRTPAGE P="40948"/>
                    process. The listing fee for a color additive petition ranges from $1,600 to $3,000, depending on the intended use of the color and the scope of the requested amendment. A complete schedule of fees is set forth in 21 CFR 70.19. An average of one category A and two category B color additive petitions are expected per year. The maximum color additive petition fee for a category A petition is $2,600 and the maximum color additive petition fee for a category B petition is $3,000. Since an average of three color additive petitions are expected per calendar year, the estimated total annual cost burden to petitioners for this start-up cost would be less than or equal to $8,600.
                </P>
                <SIG>
                    <DATED>Dated: May 23, 2002.</DATED>
                    <NAME>Margaret M. Dotzel,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15043 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. 01D-0435]</DEPDOC>
                <SUBJECT>International Conference on Harmonisation; Draft Guidance on Electronic Common Technical Document Specification; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing the availability of a second draft guidance entitled “Electronic Common Technical Document Specification” (eCTD).  The draft guidance was prepared under the auspices of the International Conference on Harmonisation of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH).  The draft guidance defines the means for industry-to-agency transfer of regulatory information that will facilitate the creation, review, life cycle management, and archiving of the electronic submission.  The draft guidance is intended to assist industry in transferring electronically their marketing applications for human drug and biological products to a regulatory authority.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written or electronic comments on the draft guidance by August 1, 2002.  General comments on agency guidance documents are welcome at any time.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written requests for single copies of the draft guidance to the Division of Drug Information (HFD-240), Center for Drug Evaluation and Research, Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857, or the Office of Communication, Training and Manufacturers Assistance (HFM-40), Center for Biologics Evaluation and Research (CBER), Food and Drug Administration, 1401 Rockville Pike, Rockville, MD 20852-1448, 301-827-3844, FAX 888-CBERFAX.  Send two self-addressed adhesive labels to assist that office in processing your requests.  Submit written comments on the draft guidance to the Dockets Management Branch (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852.  Submit electronic comments to http://www.fda.gov/dockets/ecomments.  See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for electronic access to the draft guidance document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <FP SOURCE="FP1-2">
                        <E T="03">Regarding the draft guidance</E>
                        :  Robert Yetter, Center for Biologics Evaluation and Research (HFM-25), Food and Drug Administration, 1401 Rockville Pike, Rockville, MD 20852, 301-827-0373, or Gregory V. Brolund, Center for Drug Evaluation and Research (HFD-70), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857, 301-827-3517.
                    </FP>
                    <FP SOURCE="FP1-2">
                        <E T="03">Regarding the ICH</E>
                        :  Janet J. Showalter, Office of International Programs (HFG-1), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857, 301-827-0864.
                    </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background</HD>
                <P>In recent years, many important initiatives have been undertaken by regulatory authorities and industry associations to promote international harmonization of regulatory requirements.  FDA has participated in many meetings designed to enhance harmonization and is committed to seeking scientifically based harmonized technical procedures for pharmaceutical development.  One of the goals of harmonization is to identify and then reduce differences in technical requirements for drug development among regulatory agencies.</P>
                <P>ICH was organized to provide an opportunity for tripartite harmonization initiatives to be developed with input from both regulatory and industry representatives. FDA also seeks input from consumer representatives and others.  ICH is concerned with harmonization of technical requirements for the registration of pharmaceutical products among three regions:   The European Union, Japan, and the United States.  The six ICH sponsors are the European Commission; the European Federation of Pharmaceutical Industries Associations; the Japanese Ministry of Health, Labour, and Welfare; the Japanese Pharmaceutical Manufacturers Association; the Centers for Drug Evaluation and Research and Biologics Evaluation and Research, FDA; and the Pharmaceutical Research and Manufacturers of America.  The ICH Secretariat, which coordinates the preparation of documentation, is provided by the International Federation of Pharmaceutical Manufacturers Associations (IFPMA).  The ICH Steering Committee includes representatives from each of the ICH sponsors and the IFPMA, as well as observers from the World Health Organization, Health Canada's Health Products and Food Branch, and the European Free Trade Area.</P>
                <P>In accordance with FDA's good guidance practices (GGPs) regulation (21 CFR 10.115), this document is being called a guidance, rather than a guideline.</P>
                <P>
                    To facilitate the process of making ICH guidances available to the public, the agency has changed its procedure for publishing ICH guidances.  As of April 2000, we no longer include the text of ICH guidances in the 
                    <E T="04">Federal Register</E>
                    .  Instead, we publish a notice in the 
                    <E T="04">Federal Register</E>
                     announcing the availability of an ICH guidance.  The ICH guidance will be placed in the docket and can be obtained through regular agency sources (see 
                    <E T="02">ADDRESSES</E>
                    ).  Draft guidances are left in the original ICH format.  The final guidance is reformatted to conform to the GGP style before publication.
                </P>
                <P>
                    In June 2001, the ICH Steering Committee agreed that a draft guidance entitled “Electronic Common Technical Document Specification” would be made available for public comment and testing.  The draft guidance, a product of the Multidisciplinary Group 2 (M2) Expert Working Group (EWG) of the ICH, was made available for comment in the 
                    <E T="04">Federal Register</E>
                     of November 28, 2001 (66 FR 59431).  Comments about the draft guidance were considered by FDA and the M2 EWG, and in February 2002, the ICH Steering Committee agreed that a second draft guidance should be made available for public comment (step 2).
                </P>
                <P>
                    The draft guidance on the eCTD provides guidance on industry-to-agency electronic transfer of marketing applications for human drug and 
                    <PRTPAGE P="40949"/>
                    biological products.  The draft guidance defines the means for industry-to-agency transfer of regulatory information that will facilitate the creation, review, life cycle management, and archiving of the electronic submission.  The draft guidance is intended to assist industry in transferring their marketing applications for human drug and biological products to a regulatory authority.  The second draft guidance includes the following changes:
                </P>
                <P>•  The language in the guidance has been edited to improve clarity.</P>
                <P>•  The maximum length of a file name has been increased from 32 characters to 64 characters.</P>
                <P>•  Throughout the guidance, references to Common Technical Document (CTD) sections have been updated to reflect the current CTD.</P>
                <P>•  Appendix 4 has been reorganized.</P>
                <P>•  The examples in Appendix 6 have been updated.</P>
                <P>•  The Glossary of Terms has been completed.</P>
                <P>This draft guidance, when finalized, will represent the agency's current thinking on “Electronic Common Technical Document Specification.”  It does not create or confer any rights for or on any person and does not operate to bind FDA or the public.  An alternative approach may be used if such approach satisfies the requirements of the applicable statutes and regulations.</P>
                <HD SOURCE="HD1">II.  Comments</HD>
                <P>
                    Interested persons may submit to the Dockets Management Branch (see 
                    <E T="02">ADDRESSES</E>
                    ) written or electronic comments on the draft guidance by August 1, 2002.  Two copies of any comments are to be submitted, except that individuals may submit one copy.  Comments are to be identified with the docket number found in brackets in the heading of this document.  The draft guidance and received comments may be seen in the Dockets Management Branch between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <HD SOURCE="HD1">III.  Electronic Access</HD>
                <P>Persons with access to the Internet may obtain the document at either http://www.fda.gov/cder/guidance/index.htm or http://www.fda.gov/ohrms/dockets/default.htm.</P>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>Margaret M. Dotzel,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15003 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. 02D-0237]</DEPDOC>
                <SUBJECT>International Conference on Harmonisation; Draft Guidance on Q1E Evaluation of Stability Data; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing the availability of a draft guidance entitled “Q1E Evaluation of Stability Data.”  The draft guidance was prepared under the auspices of the International Conference on Harmonisation of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH).  This draft guidance is an annex to an ICH guidance entitled “Q1A(R) Stability Testing of New Drug Substances and Products.”  The draft guidance is intended to provide guidance on how to use stability data, generated in accordance with the principles outlined in Q1A(R), to propose a retest period for the drug substance and a shelf life for the drug product.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written or electronic comments on the draft guidance by August 1, 2002.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written comments on the draft guidance to the Dockets Management Branch (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852. Submit electronic comments to http://www.fda.gov/dockets/ecomments. Submit written requests for single copies of the draft guidance to the Division of Drug Information (HFD-240), Center for Drug Evaluation and Research, Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857; or the Office of Communication, Training, and Manufacturers Assistance (HFM-40), Center for Biologics Evaluation and Research (CBER), Food and Drug Administration, 1401 Rockville Pike, Rockville, MD  20852-1448, 301-827-3844, FAX 888-CBERFAX.  Send two self-addressed adhesive labels to assist the office in processing your requests.  See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for electronic access to the draft guidance document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Regarding the guidance</E>
                        : Chi-wan Chen, Center for Drug Evaluation and Research (HFD-830), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD  20857, 301-827-2001; or Andrew Shrake, Center for Biologics Evaluation and Research (HFM-345), Food and Drug Administration, 1401 Rockville Pike, Rockville, MD 20852-1148, 301-402-4635.
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Regarding the ICH</E>
                        : Janet J. Showalter, Office of International Programs (HFG-1), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857, 301-827-0864.
                    </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I.  Background</HD>
                <P>In recent years, many important initiatives have been undertaken by regulatory authorities and industry associations to promote international harmonization of regulatory requirements.  FDA has participated in many meetings designed to enhance harmonization and is committed to seeking scientifically based harmonized technical procedures for pharmaceutical development.  One of the goals of harmonization is to identify and then reduce differences in technical requirements for drug development among regulatory agencies.</P>
                <P>ICH was organized to provide an opportunity for tripartite harmonization initiatives to be developed with input from both regulatory and industry representatives.  FDA also seeks input from consumer representatives and others.  ICH is concerned with harmonization of technical requirements for the registration of pharmaceutical products among three regions:   The European Union, Japan, and the United States.  The six ICH sponsors are the European Commission; the European Federation of Pharmaceutical Industries Associations; the Japanese Ministry of Health, Labour, and Welfare; the Japanese Pharmaceutical Manufacturers Association; the Centers for Drug Evaluation and Research and Biologics Evaluation and Research, FDA; and the Pharmaceutical Research and Manufacturers of America.  The ICH Secretariat, which coordinates the preparation of documentation, is provided by the International Federation of Pharmaceutical Manufacturers Associations (IFPMA).</P>
                <P>The ICH Steering Committee includes representatives from each of the ICH sponsors and the IFPMA, as well as observers from the World Health Organization, Health Canada's Health Products and Food Branch, and the European Free Trade Area.</P>
                <P>
                    In accordance with FDA's good guidance practices (GGPs) regulation (21 CFR 10.115), this document is being 
                    <PRTPAGE P="40950"/>
                    called a guidance, rather than a guideline.
                </P>
                <P>
                    To facilitate the process of making ICH guidances available to the public, the agency has changed its procedure for publishing ICH guidances.  Beginning April 2000, we no longer include the text of ICH guidances in the 
                    <E T="04">Federal Register</E>
                    . Instead, we publish a notice in the 
                    <E T="04">Federal Register</E>
                     announcing the availability of an ICH guidance.  The ICH guidance will be placed in the docket and can be obtained through regular agency sources (see 
                    <E T="02">ADDRESSES</E>
                    ).  Draft guidances are left in the original ICH format.  The final guidance is reformatted to conform to the GGP style before publication.
                </P>
                <P>In February 2002, the ICH Steering Committee agreed that a draft guidance entitled “Q1E Evaluation of Stability Data” should be made available for public comment.  The draft guidance is the product of the Quality Expert Working Group of the ICH.  Comments about this draft will be considered by FDA and the Quality Expert Working Group.</P>
                <P>This draft guidance is an annex to an ICH guidance entitled “Q1A(R) Stability Testing of New Drug Substances and Products” (66 FR 56332, November 7, 2001).  The draft guidance is intended to provide guidance on how to use stability data, generated in accordance with the principles outlined in Q1A(R), to propose a retest period for the drug substance and a shelf life for the drug product.</P>
                <P>The guidance on the evaluation and statistical analysis of stability data provided in Q1A(R) is brief in nature and limited in scope.  Although Q1A(R) states that regression analysis is an acceptable approach to analyzing quantitative stability data for retest period or shelf life estimation and recommends that a statistical test for batch poolability be performed using a level of significance of 0.25, it includes few details on these topics. In addition, Q1A(R) does not cover situations where multiple factors are involved in a full- or reduced-design study.  This draft guidance provides a clear explanation of expectations when proposing a retest period or shelf life and storage conditions based on the evaluation of stability data for both quantitative and qualitative test attributes.  It outlines recommendations for establishing a retest period or shelf life based on stability data from single-factor or multifactor and full- or reduced-design studies.  The draft guidance further describes when and how limited extrapolation can be undertaken to propose a retest period or shelf life beyond the observed range of data from the long-term storage condition.  When finalized, the Q1E guidance will supersede the “Evaluation” sections of Q1A(R).</P>
                <P>This draft guidance, when finalized, will represent the agency's current thinking on stability data evaluation.  It does not create or confer any rights for or on any person and does not operate to bind FDA or the public.  An alternative approach may be used if such approach satisfies the requirements of the applicable statutes and regulations.</P>
                <HD SOURCE="HD1">II.  Comments</HD>
                <P>
                    Interested persons may submit to the Dockets Management Branch (see 
                    <E T="02">ADDRESSES</E>
                    ) written comments on the draft guidance by August 1, 2002.  Two copies of any comments are to be submitted, except that individuals may submit one copy.  Comments are to be identified with the docket number found in brackets in the heading of this document.  The draft guidance and received comments may be seen in the office above between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <HD SOURCE="HD1">III.  Electronic Access</HD>
                <P>Persons with access to the Internet may obtain the document at http://www.fda.gov/ohrms/dockets/default.htm, http://www.fda.gov/cder/guidance/index.htm, or http://www.fda.gov/cber/publications.htm.</P>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>Margaret M. Dotzel,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15001 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No.  02D-0232]</DEPDOC>
                <SUBJECT>International Conference on Harmonisation; Draft Guidance on S7B Safety Pharmacology Studies for Assessing the Potential for Delayed Ventricular Repolarization (QT Interval Prolongation) by Human Pharmaceuticals; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing the availability of a draft guidance entitled “S7B Safety Pharmacology Studies for Assessing the Potential for Delayed Ventricular Repolarization (QT Interval Prolongation) by Human Pharmaceuticals.”  The draft guidance was prepared under the auspices of the International Conference on Harmonisation of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH).  The draft guidance provides general principles and information on currently available nonclinical methodologies to identify the potential risk of QT interval prolongation by a pharmaceutical and recommends study types and timing of studies in relation to clinical development of a pharmaceutical.  The draft guidance is intended to protect clinical trial participants and patients receiving marketed products from delayed repolarization-associated ventricular tachycardia, torsade de pointes, and lethal arrhythmias resulting from administration of pharmaceuticals.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written or electronic comments on the draft guidance by August 1, 2002.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written comments on the draft guidance to the Dockets Management Branch (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD  20852.  Submit electronic comments to http://www.fda.gov/dockets/ecomments.  Submit written requests for single copies of the draft guidance to the Division of Drug Information (HFD-240), Center for Drug Evaluation and Research, Food and Drug Administration, 5600 Fishers Lane, Rockville, MD  20857; or the Office of Communication, Training and Manufacturers Assistance (HFM-40), Food and Drug Administration, Center for Biologics Evaluation and Research (CBER), 1401 Rockville Pike, Rockville, MD  20852-1448, 301-827-3844, FAX: 888-CBERFAX.  Send two self-addressed adhesive labels to assist the office in processing your requests.  See the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section for electronic access to the draft guidance document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P> </P>
                    <P SOURCE="P-2">
                        <E T="03">Regarding the guidance</E>
                        :  John Koerner, Center for Drug Evaluation and Research (HFD-110), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD  20857, 301-594-5338, or David Green, Center for Biologics Evaluation and Research (HFM-579), Food and Drug Administration, 1401 Rockville Pike, Rockville, MD  20852-1448.
                    </P>
                    <P SOURCE="P-2">
                        <E T="03">Regarding the ICH</E>
                        :  Janet J. Showalter, Office of International Programs (HFG-1), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD  20857, 301-827-
                        <PRTPAGE P="40951"/>
                        0864.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I.  Background</HD>
                <P>In recent years, many important initiatives have been undertaken by regulatory authorities and industry associations to promote international harmonization of regulatory requirements.  FDA has participated in many meetings designed to enhance harmonization and is committed to seeking scientifically based harmonized technical procedures for pharmaceutical development.  One of the goals of harmonization is to identify and then reduce differences in technical requirements for drug development among regulatory agencies.</P>
                <P>ICH was organized to provide an opportunity for tripartite harmonization initiatives to be developed with input from both regulatory and industry representatives.  FDA also seeks input from consumer representatives and others.  ICH is concerned with harmonization of technical requirements for the registration of pharmaceutical products among three regions:  The European Union, Japan, and the United States.  The six ICH sponsors are the European Commission; the European Federation of Pharmaceutical Industries Associations; the Japanese Ministry of Health, Labour, and Welfare; the Japanese Pharmaceutical Manufacturers Association; the Centers for Drug Evaluation and Research and Biologics Evaluation and Research; FDA; and the Pharmaceutical Research and Manufacturers of America.  The ICH Secretariat, which coordinates the preparation of documentation, is provided by the International Federation of Pharmaceutical Manufacturers Associations (IFPMA).</P>
                <P>The ICH Steering Committee includes representatives from each of the ICH sponsors and the IFPMA, as well as observers from the World Health Organization, Health Canada's Health Products and Food Branch,  and the European Free Trade Area.</P>
                <P>In accordance with FDA's good guidance practices (GGPs) regulation (21 CFR 10.115), this document is being called a guidance, rather than a guideline.</P>
                <P>
                    To facilitate the process of making ICH guidances available to the public, the agency has changed its procedure for publishing ICH guidances.  As of April 2000, we no longer include the text of ICH guidances in the 
                    <E T="04">Federal Register</E>
                    . Instead, we publish a notice in the 
                    <E T="04">Federal Register</E>
                     announcing the availability of an ICH guidance.  The ICH guidance will be placed in the docket and can be obtained through regular agency sources (see 
                    <E T="02">ADDRESSES</E>
                    ).  Draft guidances are left in the original ICH format.  The final guidance is reformatted to conform to the GGP style before publication.
                </P>
                <P>In February 2002, the ICH Steering Committee agreed that a draft guidance entitled “S7B Safety Pharmacology Studies for Assessing the Potential for Delayed Ventricular Repolarization (QT Interval Prolongation) by Human Pharmaceuticals” should be made available for public comment.  The draft guidance is the product of the Safety Expert Working Group of the ICH.  Comments about this draft will be considered by FDA and the Safety Expert Working Group.</P>
                <P>The draft guidance provides general principles and information on currently available nonclinical methodologies to identify the potential risk of QT interval prolongation by a pharmaceutical and recommends study types and timing of studies in relation to clinical development of a pharmaceutical.  The draft guidance is intended to protect clinical trial participants and patients receiving marketed products from delayed repolarization-associated ventricular tachycardia, torsade de pointes, and lethal arrhythmias resulting from administration of pharmaceuticals.</P>
                <P>This draft guidance, when finalized, will represent the agency's current thinking on this topic.  It does not create or confer any rights for or on any person and does not operate to bind FDA or the public.  An alternative approach may be used if such approach satisfies the requirements of the applicable statutes and regulations.</P>
                <HD SOURCE="HD1">II.  Comments</HD>
                <P>
                    Interested persons may submit to the Dockets Management Branch (see 
                    <E T="02">ADDRESSES</E>
                    ) written or electronic comments on the draft guidance by August 1, 2002.  Two copies of any comments are to be submitted, except that individuals may submit one copy.  Comments are to be identified with the docket number found in brackets in the heading of this document.  The draft guidance and received comments may be seen in the Dockets Management Branch between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <HD SOURCE="HD1">III.  Electronic Access</HD>
                <P>Persons with access to the Internet may obtain the document at http://www.fda.gov/ohrms/dockets/default.htm, http://www.fda.gov/cder/guidance/index.htm, or http://www.fda.gov/cber/publications.htm.</P>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>Margaret M. Dotzel,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15000 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Food and Drug Administration</SUBAGY>
                <DEPDOC>[Docket No. 02D-0231]</DEPDOC>
                <SUBJECT>International Conference on Harmonisation; Stability Data Package for Registration in Climatic Zones III and IV; Availability</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Food and Drug Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Food and Drug Administration (FDA) is announcing the availability of a draft guidance entitled “Q1F Stability Data Package for Registration in Climatic Zones III and IV.”  The draft guidance was prepared under the auspices of the International Conference on Harmonisation of Technical Requirements for Registration of Pharmaceuticals for Human Use (ICH).  This draft guidance, an annex to an ICH guidance entitled “Q1A(R) Stability Testing of New Drug Substances and Products,” defines an approach for broader use of Q1A(R) for territories in climatic zones III and IV.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Submit written or electronic comments on the draft guidance by August 20, 2002.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit written comments on the guidance to the Dockets Management Branch (HFA-305), Food and Drug Administration, 5630 Fishers Lane, rm. 1061, Rockville, MD 20852. Submit electronic comments to http://www.fda.gov/dockets/ecomments.  Submit written requests for single copies of the draft guidance to the Division of Drug Information (HFD-240), Center for Drug Evaluation and Research, Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857; or the Office of Communication, Training and Manufacturers Assistance (HFM-40), Center for Biologics Evaluation and Research (CBER), Food and Drug Administration, 1401 Rockville Pike, Rockville, MD  20852-1448, 301-827-3844, FAX 888-CBERFAX.  Send two self-addressed adhesive labels to assist the office in processing your requests.  Requests and comments should be identified with the docket number found in brackets in the heading of this document.  See the 
                        <E T="02">
                            SUPPLEMENTARY 
                            <PRTPAGE P="40952"/>
                            INFORMATION
                        </E>
                         section for electronic access to the draft guidance document.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <FP SOURCE="FP-1">
                        <E T="03">Regarding the guidance</E>
                        :  Chi-wan Chen, Center for Drug Evaluation and Research (HFD-830), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD  20857, 301-827-2001; or Andrew Shrake, Center for Biologics Evaluation and Research (HFM-345), Food and Drug Administration, 1401 Rockville Pike, Rockville, MD 20852-1148, 301-402-4635.
                    </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Regarding the ICH</E>
                        :  Janet J. Showalter, Office of International Programs (HFG-1), Food and Drug Administration, 5600 Fishers Lane, Rockville, MD 20857, 301-827-0864.
                    </FP>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I.  Background</HD>
                <P>In recent years, many important initiatives have been undertaken by regulatory authorities and industry associations to promote international harmonization of regulatory requirements.  FDA has participated in many meetings designed to enhance harmonization and is committed to seeking scientifically based harmonized technical procedures for pharmaceutical development.  One of the goals of harmonization is to identify and then reduce differences in technical requirements for drug development among regulatory agencies.</P>
                <P>ICH was organized to provide an opportunity for tripartite harmonization initiatives to be developed with input from both regulatory and industry representatives.  FDA also seeks input from consumer representatives and others.  ICH is concerned with harmonization of technical requirements for the registration of pharmaceutical products among three regions:   The European Union (EU), Japan, and the United States.  The six ICH sponsors are:  The European Commission; the European Federation of Pharmaceutical Industries Associations; the Japanese Ministry of Health, Labour, and Welfare; the Japanese Pharmaceutical Manufacturers Association; the Centers for Drug Evaluation and Research and Biologics Evaluation and Research, FDA; and the Pharmaceutical Research and Manufacturers of America.  The ICH Secretariat, which coordinates the preparation of documentation, is provided by the International Federation of Pharmaceutical Manufacturers Associations (IFPMA).</P>
                <P>The ICH Steering Committee includes representatives from each of the ICH sponsors and the IFPMA, as well as observers from the World Health Organization (WHO), Health Canada's Health Products and Food Branch, and the European Free Trade Area.</P>
                <P>In accordance with FDA's good guidance practices (GGPs) regulation (21 CFR 10.115), this document is being called a guidance, rather than a guideline.</P>
                <P>
                    To facilitate the process of making ICH guidances available to the public, the agency has changed its procedure for publishing ICH guidances.  Beginning April 2000, we no longer include the text of ICH guidances in the 
                    <E T="04">Federal Register</E>
                    . Instead, we publish a notice in the 
                    <E T="04">Federal Register</E>
                     announcing the availability of an ICH guidance.  The ICH guidance will be placed in the docket and can be obtained through regular agency sources (see 
                    <E T="02">ADDRESSES</E>
                    ).  Draft guidances are left in the original ICH format.  The final guidance is reformatted to conform to the GGP style before publication.
                </P>
                <P>In February 2002, the ICH Steering Committee agreed that a draft guidance entitled “Q1F Stability Data Package for Registration in Climatic Zones III and IV” should be made available for public comment.  The draft guidance is the product of the Quality Expert Working Group of the ICH.  Comments about this draft will be considered by FDA and the Quality Expert Working Group.</P>
                <P>This draft guidance, an annex to an ICH guidance entitled “Q1A(R) Stability Testing of New Drug Substances and Products” (66 FR 56332, November 7, 2001), defines an approach for broader use of Q1A(R) for territories in climatic zones III and IV.</P>
                <P>
                    There are four climatic zones in the world that are distinguished by their characteristic prevalent annual climatic conditions, based on the concept described by P. Schumacher (
                    <E T="03">Pharmazeutische Zeitung</E>
                    , 119:321-324, 1974).  The Q1A(R) guidance defines the stability data package for the ICH tripartite regions (the EU, Japan, and the United States), which are in climatic zones I or II.  The WHO has published a guideline entitled “Stability testing of pharmaceutical products containing well established drug substances in conventional dosage forms” (WHO technical report series, no. 863, annex 5), updated in the “Report of the thirty-seventh meeting of the WHO Expert Committee on Specifications for Pharmaceutical Preparations,” Geneva, October 22-26, 2001.  The WHO guideline defines stability testing recommendations, including storage conditions for all four climatic zones.
                </P>
                <P>Harmonized global stability testing recommendations have been established in this draft guidance based on Q1A(R) and the WHO guideline.  For territories in climatic zones III and IV, the data package as described in Q1A(R) can be considered applicable except for the defined long-term storage condition.  The draft guidance recommends the long-term storage condition for a stability data package for registration of drug substances and products intended to be marketed in climatic zones III and IV.</P>
                <P>When this draft guidance is finalized, Q1A(R) will be revised to harmonize the intermediate storage condition for zones I and II with the long-term storage condition for zones III and IV.</P>
                <P>This draft guidance, when finalized, will represent the agency's current thinking on a stability data package for registration in climatic zones III and IV.  It does not create or confer any rights for or on any person and does not operate to bind FDA or the public.  An alternative approach may be used if such approach satisfies the requirements of the applicable statues and regulations.</P>
                <HD SOURCE="HD1">II.  Comments</HD>
                <P>
                    Interested persons may submit to the Dockets Management Branch (see 
                    <E T="02">ADDRESSES</E>
                    ) written or electronic comments on the draft guidance by  August 20, 2002.  Two copies of any comments are to be submitted, except that individuals may submit one copy.  Comments are to be identified with the docket number found in brackets in the heading of this document.  The guidance and received comments may be seen in the office above between 9 a.m. and 4 p.m., Monday through Friday.
                </P>
                <HD SOURCE="HD1">III.  Electronic Access</HD>
                <P>Persons with access to the Internet may obtain the document at http://www.fda.gov/ohrms/dockets/default.htm, http://www.fda.gov/cder/guidance/index.htm, or http://www.fda.gov/cber/publications.htm.</P>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>Margaret M. Dotzel,</NAME>
                    <TITLE>Associate Commissioner for Policy.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14999 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Heart, Lung, and Blood Institute; Notice of Closed Meeting</SUBJECT>
                <P>
                    Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. Appendix 2), notice 
                    <PRTPAGE P="40953"/>
                    is hereby given of the following meeting.
                </P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Heart, Lung, and Blood Institute Special Emphasis Panel, Gene and Environment.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 24-25, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         7 p.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Double Tree Hotel, 1750 Rockville Pike, Rockville, MD 20852.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         William J. Johnson, Scientific Review Administrator, NHLBI Review Branch, Division of Extramural Affairs, Two Rockledge Centre, Room 7184, MSC7924, 6701 Rockledge Drive, Bethesda, MD 20892, 301/435-0275; 
                        <E T="03">johnsonw@nhlbi.nih.gov</E>
                        .
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.233, National Center for Sleep Disorders Research; 93.837, Heart and Vascular Diseases Research; 93.838, Lung Diseases Research; 93.839, Blood Diseases and Resources Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 7, 2002.</DATED>
                    <NAME>LaVerne Y. Stringfield,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15018 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Environmental Health Sciences; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. Appendix 2), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Environmental Health Sciences Review Committee.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 18-19, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Nat. Institute of Environmental Health Sciences, South Campus, Building 101 Conference Room, Research Triangle Park, NC 27709.
                    </P>
                    <P>
                        <E T="03">Contract Person:</E>
                         Linda K. Bass, PhD, Scientific Review Administrator, Nat'l Institute of Environmental Health Sciences, P.O. Box 12233, MD EC-24, Research Triangle Park, NC 27709, (919) 541-1307.
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.113, Biological Response to Environmental Health Hazards; 93.114, Applied Toxicological Research and Testing; 93.115, Biometry and Risk Estimation—Health Risks from Environmental Exposures; 93.142, NIEHS Hazardous Waste Worker Health and Safety Training; 93.143, NIEHS Superfund Hazardous Substances—Basic Research and Education; 93.894, Resources and Manpower Development in the Environmental Health Sciences, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: June 7, 2002.</DATED>
                    <NAME>LaVerne Y. Stringfield,</NAME>
                    <TITLE>Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15019 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Notice of Closed Meetings</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. Appendix 2), notice is hereby given of the following meetings.</P>
                <P>The meetings will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Immunological Sciences Integrated Review Group, immunobiology Study Section. 
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 20-21, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 3 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         The Westin Grand, 2350 M Street NW., Washington, DC 20037.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Betty Hayden, PhD., Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4206, MSC 7812, Bethesda, MD 20892. (301) 435-1223.
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG1 SSS-Y (01).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 20, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1 p.m. to 2 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NIH, Rockledge 2, Bethesda, MD 20892. (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Michael R. Schaefer, PhD., Genetic Sciences IRG, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6166, MSC 7890, Bethesda, MD 20892. (301) 435-2477, 
                        <E T="03">schaefem@csr.nih.gov.</E>
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, SBIR Special Study Section Meeting-3 (10).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 24-25, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Holiday Inn Georgetown, 2101 Wisconsin Avenue, NW., Washington, DC 20007.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Gopal C. Sharma, DVM, MS, PhD, Diplomat American Board of Toxicology, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2184, MSC 7818, Bethesda, MD 20892. (301) 435-1783. 
                        <E T="03">sharmag@csr.nih.gov.</E>
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG1 MEP (04) Leukemia virus.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 27, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         5:30 p.m. to 6:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NIH, Rockledge 2, Bethesda, MD 20892. (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Angela Y. Ng, PhD, MBA, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4142, MSC 7804, (For courier delivery, use MD 20817), Bethesda, MD 20892. 301-435-1715. 
                        <E T="03">nga@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG1 SSS-3 (04).
                        <PRTPAGE P="40954"/>
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         June 28, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1 p.m. to 2 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NIH, Rockledge 2, Bethesda, MD 20892. (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Gopal C. Sharma, DVM, MS, PhD, Diplomate American Board of Toxicology, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2184, MSC 7818, Bethesda, MD 20892. (301) 435-1783. 
                        <E T="03">sharmag@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG1 MDCN-2 (05) Interdisciplinary Research in Women's Health Program.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 1-2, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 11:59 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Monarch Hotel, 2400 M Street, NW, Washington, DC 10037.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Gillian Einstein, PhD, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5198, MSC 7850, Bethesda, MD 20817. (301) 435-4433. 
                        <E T="03">einsteig@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG-1 Special Study Section-8 (10).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 1-2, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Holiday Inn, 8120 Wisconsin Avenue, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Paul Parakkal, PhD, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5122, MSC 7854, Bethesda, MD 20892. 301-435-1176. 
                        <E T="03">parakkap@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Fellowship Study Section 06 (20).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 1, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Hyatt Regency Hotel, One Bethesda Metro Center, Bethesda, MD 20814.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Krish Krishnam, PhD, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 6164, MSC 7892, Bethesda, MD 20892. (301) 435-1041.
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         AIDS and Related Research Integrated Review Group, AIDS and Related Research 4.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 1-2, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8 a.m. to 5:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Latham Hotel, 3000 M Street, NW, Washington, DC 20007-3701.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Eduardo A. Montalvo, PhD, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5108, MSC 7852, Bethesda, MD 20892. (301) 435-1168.
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Cardiovascular Sciences Integrated Review Group, Hematology Subcommittee 2.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 1-2, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 1 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Embassy Suites, Chevy Chase Pavilion, 4300 Military Rd., Wisconsin at Western Ave., Washington, DC 20015.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Jerrold Fried, PhD, Scientfic Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive,  Room 4126, MSC 7802, Bethesda, MD 20892-7802. 301-435-1777. 
                        <E T="03">friedj@csr.nih.gov</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, Brain Disorders and Clinical Neurosciences 4 Study Section.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 1-2, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         8:30 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Melrose Hotel, 2430 Pennsylvania Avenue, NW, Washington, DC 20037.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Jay Joshi, PhD, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 5184, MSC 7846, Bethesda, MD 20892. (301) 435-1184.
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG1 GMA-2 (01) Barrett's Esophagus, Gastroesophageal Reflux Disease and Adenocarcinoma of the Esophagus (RFA-02-015).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 1-2, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         830 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Monarch Hotel, 2400 M Street, NW, Washington, DC 20037.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Mushtaq A. Khan, DVM, PhD, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2176, MSC 7818, Bethesda, MD 20892. (301) 435-1778. 
                        <E T="03">khanm@csr.nih.gov</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG1 SMB (02).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 1, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1 p.m. to 3 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NIH, Rockledge 2, Bethesda, MD 20892. (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Paul D. Wagner, PhD, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4108, MSC 7814, Bethesda, MD 20892. (301) 435-6809. 
                        <E T="03">wagnerp@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG1 SSS-E (02).
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 2, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1 p.m. to 3 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate bioengineering.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NIH, Rockledge 2, Bethesda, MD 20892. (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Gopal C. Sharma, DVM, MS, PhD, Diplomate American Board of Toxicology, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 2184, MSC 7818, Bethesda, MD 20892. (301) 4351783. 
                        <E T="03">sharmag@csr.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Name of Committee:</E>
                         Center for Scientific Review Special Emphasis Panel, ZRG1 CPA (04) Brain Cancer.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         July 2, 2002.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         1 p.m. to 3 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         NIH, Rockledge 2, Bethesda, MD 20892. (Telephone Conference Call). 
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Victor A. Fung, PhD, Scientific Review Administrator, Center for Scientific Review, National Institutes of Health, 6701 Rockledge Drive, Room 4120, MSC 7804, Bethesda, MD 20814-9692. 301-435-3504. 
                        <E T="03">fungv@csr.nih.gov.</E>
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.306, Comparative Medicine, 93.306; 93.333, Clinical Research, 93.333, 93.337, 93.393-93.396, 93.837-93.844, 93.846-93.878, 93.892, 93.893, National Institutes of Health, (HHS)</FP>
                    <SIG>
                        <DATED>June 7, 2002.</DATED>
                        <NAME>LaVerne Y. Stringfield, </NAME>
                        <TITLE>Director, Office Federal Advisory Committee Policy.</TITLE>
                    </SIG>
                </EXTRACT>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15020 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-4734-N-21]</DEPDOC>
                <SUBJECT>Notice of Submission of Proposed Information Collection to OMB: Mail Survey of HOME Investment Partnership Program Administrators</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief Information Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The proposed information collection requirement described below has been submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act. The Department is soliciting public comments on the subject proposal.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         July 15, 2002.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB approval number and should be sent to: Joseph F. Lackey, Jr., OMB Desk Officer, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503; Fax number (202) 395-6974; E-mail 
                        <E T="03">Joseph_F._Lackey_Jr@OMB.EOP.GOV</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Wayne Eddins, Reports Management 
                        <PRTPAGE P="40955"/>
                        Officer, QDAM, Department of Housing and Urban Development, 451 Seventh Street, Southwest, Washington, DC 20410; e-mail 
                        <E T="03">Wayne_Eddins@HUD.gov</E>
                        ; telephone (202) 708-2374. This is not a toll-free number. Copies of the proposed forms and other available documents submitted to OMB may be obtained from Mr. Eddins.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department has submitted the proposal for the collection of information, as described below, to OMB for review, as required by the Paperwork Reduction Act (44 U.S.C. Chapter 35). The Notice lists the following information: (1) The title of the information collection proposal; (2) the office of the agency to collect the information; (3) the OMB approval number, if applicable; (4) the description of the need for the information and its proposed use; (5) the agency form number, if applicable; (6) what members of the public will be affected by the proposal; (7) how frequently information submissions will be required; (8) an estimate of the total number of hours needed to prepare the information submission including number of respondents, frequency of response, and hours of response; (9) whether the proposal is new, an extension, reinstatement, or revision of an information collection requirement; and (10) the name and telephone number of an agency official familiar with the proposal and of the OMB Desk Officer for the Department.</P>
                <P>
                    <E T="03">This Notice also lists the following information:</E>
                </P>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Mail Survey of HOME Investment Partnership Program Administrators.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2528-XXXX.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     None.
                </P>
                <P>
                    <E T="03">Description of the Need for the Information and Its Proposed Use:</E>
                     Mail survey of the universe of State and local administrators of HOME Investment Partnership programs concerning homebuyer programs.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     State, Local or Tribal Government.
                </P>
                <P>
                    <E T="03">Frequency of Submission:</E>
                     On occasion, One.
                </P>
                <GPOTABLE COLS="7" OPTS="L1,tp0,i1" CDEF="s50,12C,12C,2,12C,2,12C">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">
                            <E T="03">Reporting Burden</E>
                        </CHED>
                        <CHED H="1">Number of respondents </CHED>
                        <CHED H="1">Annual responses </CHED>
                        <CHED H="1">× </CHED>
                        <CHED H="1">Hours per response </CHED>
                        <CHED H="1">= </CHED>
                        <CHED H="1">Burden hours </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>595</ENT>
                        <ENT>1</ENT>
                        <ENT> </ENT>
                        <ENT>1</ENT>
                        <ENT> </ENT>
                        <ENT>595 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Total Estimated Burden Hours:</E>
                     595.
                </P>
                <P>
                    <E T="03">Status:</E>
                     New Collection.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Section 3507 of the Paperwork Reduction Act of 1995, 44 U.S.C. 35, as amended.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>Wayne Eddins,</NAME>
                    <TITLE>Departmental Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15026 Filed 6-14-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-72-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-4734-N-22]</DEPDOC>
                <SUBJECT>Notice of Submission of Proposed Information Collection to OMB; Statement of Real Estate Taxes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief Information Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The proposed information collection requirement described below has been submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act. The Department is soliciting public comments on the subject proposal.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         July 15, 2002.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB approval number and should be sent to: Joseph F. Lackey, Jr., OMB Desk Officer, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503; Fax number (202) 395-6974; E-mail 
                        <E T="03">Joseph._F. Lackey_Jr@OMB.EOP.GOV.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Wayne Eddins, Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 Seventh Street, Southwest, Washington, DC 20410; e-mail 
                        <E T="03">Wayne_Eddins@HUD.gov</E>
                        ; telephone (202) 708-2374. This is not a toll-free number. Copies of the proposed forms and other available documents submitted to OBM may be obtained from Mr. Eddins.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department has submitted the proposal for the collection of information, as described below, to OMB for review, as required by the Paperwork Reduction Act (44 U.S.C. Chapter 35). The Notice lists the following information: (1) The title of the information collection proposal; (2) the office of the agency to collect the information; (3) the OMB approval number, if applicable; (4) the description of the need for the information and its proposed use; (5) the agency form number, if applicable; (6) what members of the public will be affected by the proposal; (7) how frequently information submissions will be required; (8) an estimate of the total number of hours needed to prepare the information submission including number of respondents, frequency of response, and hours of response; (9) whether the proposal is new, an extension, reinstatement, or revision of an information collection requirement; and (10) the name and telephone number of an agency official familiar with the proposal and of the OMB Desk Officer for the Department.</P>
                <P>
                    <E T="03">This Notice also lists the following information:</E>
                </P>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Statement of REAL ESTATE Taxes
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0418
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     HUD-434
                </P>
                <P>
                    <E T="03">Description of the Need for the Information and its Proposed Use:</E>
                     The statement of taxes reports mortgagors' tax payments for use in audits or claims for insurance benefits.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profits, State, Local or Tribal Governments.
                </P>
                <P>
                    <E T="03">Frequency of Submission:</E>
                     On occasion, One.
                </P>
                <GPOTABLE COLS="7" OPTS="L1,tp0,i1" CDEF="s50,12C,12C,2,12C,2,12C">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Reporting burden </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents </LI>
                        </CHED>
                        <CHED H="1">
                            Annual 
                            <LI>responses </LI>
                        </CHED>
                        <CHED H="1">× </CHED>
                        <CHED H="1">
                            Hours per 
                            <LI>response </LI>
                        </CHED>
                        <CHED H="1">= </CHED>
                        <CHED H="1">Burden hours </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>215</ENT>
                        <ENT>1</ENT>
                        <ENT> </ENT>
                        <ENT>1</ENT>
                        <ENT> </ENT>
                        <ENT>107 </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="40956"/>
                <P>
                    <E T="03">Total Estimated Burden Hours:</E>
                     107.
                </P>
                <P>
                    <E T="03">Status:</E>
                     Extension of a currently approved information collection.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Section 3507 of the Paperwork Reduction Act of 1995, 44 U.S.C. 35, as amended.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>Wayne Eddins,</NAME>
                    <TITLE>Departmental Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15027  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-72-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-4734-N-23] </DEPDOC>
                <SUBJECT>Notice of Submission of Proposed Information Collection to OMB; Personal Financial Statement</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Chief Information Officer, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The proposed information collection requirement described below has been submitted to the Office of Management and Budget (OMB) for review, as required by the Paperwork Reduction Act. The Department is soliciting public comments on the subject proposal.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Comments Due Date:</E>
                         July 15, 2002.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested persons are invited to submit comments regarding this proposal. Comments should refer to the proposal by name and/or OMB approval number and should be sent to: Joseph F. Lackey, Jr., OMB Desk Officer, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503; Fax number (202) 395-6974; E-mail 
                        <E T="03">Joseph_F._Lackey_Jr@OMB.EOP.GOV.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Wayne Eddins, Reports Management Officer, QDAM, Department of Housing and Urban Development, 451 Seventh Street, Southwest, Washington, DC 20410; e-mail 
                        <E T="03">Wayne_Eddins@HUD.gov;</E>
                         telephone (202) 708-2374. This is not a toll-free number. Copies of the proposed forms and other available documents submitted to OMB may be obtained from Mr. Eddins.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department has submitted the proposal for the collection of information, as described below, to OMB for review, as required by the Paperwork Reduction Act (44 U.S.C. Chapter 35). The Notice lists the following information: (1) The title of the information collection proposal; (2) the office of the agency to collect the information; (3) the OMB approval number, if applicable; (4) the description of the need for the information and its proposed use; (5) the agency form number if applicable; (6) what members of the public will be affected by the proposal; (7) how frequently information submissions will be required; (8) an estimate of the total number of hours needed to prepare the information submission including number of respondents, frequency of response, and hours of response; (9) whether the proposal is new, an extension, reinstatement, or revision of an information collection requirement; and (10) the name and telephone number of an agency official familiar with the proposal and of the OMB Desk Officer for the Department.</P>
                <P>
                    <E T="03">This notice also lists the following information</E>
                </P>
                <P>
                    <E T="03">Title of Proposal:</E>
                     Mail Survey of HOME Investment Partnership Program Administrators.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     2502-0098.
                </P>
                <P>
                    <E T="03">Form Numbers:</E>
                     HUD-56142.
                </P>
                <P>
                    <E T="03">Description of the Need for the Information and its Proposed Use:</E>
                     Financial Statements provide the information necessary to evaluate an individual debtor's financial postion for establishing payment plans and or settlement offers.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Frequency of Submission:</E>
                     On occasion.
                </P>
                <GPOTABLE COLS="7" OPTS="L1,i1" CDEF="s100,11C,10C,2,10C,2,7">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">  </CHED>
                        <CHED H="1">
                            Number of 
                            <LI>respondents </LI>
                        </CHED>
                        <CHED H="1">
                            Annual 
                            <LI>responses </LI>
                        </CHED>
                        <CHED H="1">x </CHED>
                        <CHED H="1">
                            Hours per 
                            <LI>response </LI>
                        </CHED>
                        <CHED H="1">= </CHED>
                        <CHED H="1">
                            Burden 
                            <LI>hours </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Reporting burden</ENT>
                        <ENT>800</ENT>
                        <ENT>1</ENT>
                        <ENT> </ENT>
                        <ENT>1</ENT>
                        <ENT> </ENT>
                        <ENT>800 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Total estimated burden hours:</E>
                     800.
                </P>
                <P>
                    <E T="03">Status:</E>
                     Extension of a currently approved collection.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>Section 3507 of the Paperwork Reduction Act of 1995, 44 U.S.C. 35, as amended.</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: June 7, 2002.</DATED>
                    <NAME>Wayne Eddins,</NAME>
                    <TITLE>Departmental Reports Management Officer, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15028  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-72-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-4730-N-24]</DEPDOC>
                <SUBJECT>Federal Property Suitable as Facilities to Assist the Homeless</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Community Planning and Development, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This Notice identifies unutilized, underutilized, excess, and surplus Federal property reviewed by HUD for suitability for possible use to assist the homeless.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mark Johnston, room 7266, Department of Housing and Urban Development, 451 Seventh Street, SW., Washington, DC 20410; telephone (202) 708-1234; TTY number for the hearing- and speech-impaired (202) 708-2565 (these telephone numbers are not toll-free), or call the toll-free Title V information line at 1-800-927-7588.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In accordance with 24 CFR part 581 and section 501 of the Stewart B. McKinney Homeless Assistance Act (42 U.S.C. 11411), as amended, HUD is publishing this Notice to identify Federal buildings and other real property that HUD has reviewed for suitability for use to assist the homeless. The properties were reviewed using information provided to HUD by Federal landholding agencies regarding unutilized and underutilized buildings and real property controlled by such agencies or by GSA regarding its inventory of excess or surplus Federal property. This Notice is also published in order to comply with the December 12, 1988 Court Order in 
                    <E T="03">National Coalition for the Homeless</E>
                     v. 
                    <E T="03">Veterans Administration,</E>
                     No. 88-2503-OG (D.D.C.).
                    <PRTPAGE P="40957"/>
                </P>
                <P>Properties reviewed are listed in this Notice according to the following categories: Suitable/available, suitable/unavailable, suitable/to be excess, and unsuitable. The properties listed in the three suitable categories have been reviewed by the landholding agencies, and each agency has transmitted to HUD: (1) Its intention to make the property available for use to assist the homeless, (2) its intention to declare the property excess to the agency's needs, or (3) a statement of the reasons that the property cannot be declared excess or made available for use as facilities to assist the homeless.</P>
                <P>Properties listed as suitable/available will be available exclusively for homeless use for a period of 60 days from the date of this Notice. Where property is described as for “off-site use only” recipients of the property will be required to relocate the building to their own site at their own expense. Homeless assistance providers interested in any such property should send a written expression of interest to HHS, addressed to Brian Rooney, Division of Property Management, Program Support Center, HHS, room 5B-41, 5600 Fishers Lane, Rockville, MD 20857; (301) 443-2265. (This is not a toll-free number.) HHS will mail to the interested provider an application packet, which will include instructions for completing the application. In order to maximize the opportunity to utilize a suitable property, providers should submit their written expressions of interest as soon as possible. For complete details concerning the processing of applications, the reader is encouraged to refer to the interim rule governing this program, 24 CFR part 581.</P>
                <P>For properties listed as suitable/to be excess, that property may, if subsequently accepted as excess by GSA, be made available for use by the homeless in accordance with applicable law, subject to screening for other Federal use. At the appropriate time, HUD will publish the property in a Notice showing it as either suitable/available or suitable/unavailable.</P>
                <P>For properties listed as suitable/unavailable, the landholding agency has decided that the property cannot be declared excess or made available for use to assist the homeless, and the property will not be available.</P>
                <P>
                    Properties listed as unsuitable will not be made available for any other purpose for 20 days from the date of this Notice. Homeless assistance providers interested in a review by HUD of determination of unsuitability should call the toll free information line at 1-800-927-7588 for detailed instructions or write a letter to Mark Johnston at the address listed at the beginning of this Notice. Included in the request for review should be the property address (including zip code), the date of publication in the 
                    <E T="04">Federal Register,</E>
                     the landholding agency, and the property number.
                </P>
                <P>
                    For more information regarding particular properties identified in this Notice (
                    <E T="03">i.e.,</E>
                     acreage, floor plan, existing sanitary facilities, exact street address), providers should contact the appropriate landholding agencies at the following addresses: AF: Ms. Barbara Jenkins, Air Force Real Estate Agency (Area-MI), Bolling Air Force Base, 112 Luke Avenue suite 104, Building 5683, Washington, DC 20332-8020; (202) 767-4148; COE: Ms. Shirley Middleswarth, Army Corps of Engineers, Management &amp; Disposal Division, 441 G Street, Washington, DC 20314-1000; (202) 761-7425; Energy: Mr. Tom Knox, Department of Energy, Office of Engineering &amp; Construction Management, CR-80, Washington, DC 20585; (202) 586-8715; GSA: Mr. Brian K. Polly, Assistant Commissioner, General Services Administration, Office of Property Disposal, 18th and F Streets, NW., Washington, DC 20405; (202) 501-0052; NAVY: Mr. Charles C. Cocks, Director, Department of the Navy, Real Estate Policy Division, Naval Facilities Engineering Command, Washington Navy Yard, 1322 Patterson Ave., SE., suite 1000, Washington, DC 20374-5065; (202) 685-9200; (These are not toll-free numbers).
                </P>
                <SIG>
                    <DATED>Dated: June 6, 2002.</DATED>
                    <NAME>John D. Garrity,</NAME>
                    <TITLE>Director, Office of Special Needs Assistance Programs.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">TITLE V, FEDERAL SURPLUS PROPERTY PROGRAM FEDERAL REGISTER REPORT FOR 6/14/02</HD>
                    <HD SOURCE="HD1">Suitable/Available Properties</HD>
                    <HD SOURCE="HD2">Buildings (by State)</HD>
                    <HD SOURCE="HD3">Mississippi</HD>
                    <FP SOURCE="FP-1">Quonset Bldg.</FP>
                    <FP SOURCE="FP-1">Greenville Casting Plant</FP>
                    <FP SOURCE="FP-1">Greenville Co: Washington MS 38701-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220010</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 26,250 sq. ft., presence of asbestos/lead paint, most recent use—storage/office, off-site use only</FP>
                    <FP SOURCE="FP-1">Storage Bldg. #1</FP>
                    <FP SOURCE="FP-1">Greenville Casting Plant</FP>
                    <FP SOURCE="FP-1">Greenville Co: Washington MS 38701-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220011</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 32,502 sq. ft., presence of asbestos/lead paint, most recent use—storage/office, off-site use only</FP>
                    <FP SOURCE="FP-1">Storage Bldg. #2</FP>
                    <FP SOURCE="FP-1">Greenville Casting Plant</FP>
                    <FP SOURCE="FP-1">Greenville Co: Washington MS 38701-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220012</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 16,170 sq. ft., presence of asbestos/lead paint, most recent use—storage, off-site use only</FP>
                    <FP SOURCE="FP-1">Yellow Office Bldg.</FP>
                    <FP SOURCE="FP-1">Greenville Casting Plant</FP>
                    <FP SOURCE="FP-1">Greenville Co: Washington MS 38701-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220013</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 1820 sq. ft., presence of asbestos/lead paint, most recent use—office, off-site use only</FP>
                    <FP SOURCE="FP-1">Storage Bldg.</FP>
                    <FP SOURCE="FP-1">Greenville Casting Plant</FP>
                    <FP SOURCE="FP-1">Greenville Co: Washington MS 38701-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220014</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 1820 sq. ft., presence of asbestos/lead paint, most recent use—office, off-site use only</FP>
                    <FP SOURCE="FP-1">Container Bldg.</FP>
                    <FP SOURCE="FP-1">Greenville Casting Plant</FP>
                    <FP SOURCE="FP-1">Greenville Co: Washington MS 38701-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220015</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 270 sq. ft., presence lead paint, most recent use—storage, off-site use only</FP>
                    <FP SOURCE="FP-1">Bldgs. 90A/B, 91A/B, 92A/B</FP>
                    <FP SOURCE="FP-1">Jefferson Barracks Housing</FP>
                    <FP SOURCE="FP-1">St. Louis Co: MO 63125-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220002</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 6450 sq.ft., needs repair, includes 2 acres</FP>
                    <HD SOURCE="HD3">Pennsylvania</HD>
                    <FP SOURCE="FP-1">House/Storage</FP>
                    <FP SOURCE="FP-1">Cowanesque Lake Project</FP>
                    <FP SOURCE="FP-1">Bliss Road</FP>
                    <FP SOURCE="FP-1">Lawrenceville Co: Tioga PA 16929-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200220011</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 1653/2640 sq. ft., no public water or sewer, needs rehab</FP>
                    <FP SOURCE="FP-1">GSA Number: 4-D-PA-791</FP>
                    <HD SOURCE="HD3">Tennessee</HD>
                    <FP SOURCE="FP-1">Federal Bldg.</FP>
                    <FP SOURCE="FP-1">118 East Locust Street</FP>
                    <FP SOURCE="FP-1">Lafayette Co: Macon TN 37083-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200220010</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 12,605 sq.ft., most recent use—office, protion occupied by U.S. Postal Service</FP>
                    <FP SOURCE="FP-1">GSA Number: 4-G-TN-656</FP>
                    <HD SOURCE="HD3">Virginia</HD>
                    <FP SOURCE="FP-1">Bldg. 106(G)</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220046</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 2767 sq. ft. garage, most recent use—storage, off-site use only</FP>
                    <PRTPAGE P="40958"/>
                    <FP SOURCE="FP-1">Bldg. CEP-184</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220047</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 200 sq. ft., most recent use—gate/sentry house, off-site use only</FP>
                    <HD SOURCE="HD2">Land (by State)</HD>
                    <HD SOURCE="HD3">Hawaii</HD>
                    <FP SOURCE="FP-1">Parcels 9, 2, 4</FP>
                    <FP SOURCE="FP-1">Loran Station Upolu Point</FP>
                    <FP SOURCE="FP-1">Hawi Co: Hawaii HI</FP>
                    <FP SOURCE="FP-1">Location: Resubmitted to Federal Register for publication</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200220002</FP>
                    <FP SOURCE="FP-1">Status: Surplus</FP>
                    <FP SOURCE="FP-1">Comment: parcel 9 = 6.242 acres/encumbered by utility and road access easements, parcel 2 = 1.007 acres; parcel 4 =5.239 acres</FP>
                    <FP SOURCE="FP-1">GSA Number: 9-U-HI-0572</FP>
                    <HD SOURCE="HD2">Land (by State)</HD>
                    <HD SOURCE="HD3">South Dakota</HD>
                    <FP SOURCE="FP-1">S. Nike Ed. Annex Land</FP>
                    <FP SOURCE="FP-1">Ellsworth AFB</FP>
                    <FP SOURCE="FP-1">Pennington Co: SD 57706-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220010</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 7 acres w/five foundations from demolished bldgs. remain on site; with a road and a parking lot</FP>
                    <HD SOURCE="HD1">Suitable/Unavailable Properties</HD>
                    <HD SOURCE="HD2">Buildings (by State)</HD>
                    <HD SOURCE="HD3">Hawaii</HD>
                    <FP SOURCE="FP-1">Bldg. 5</FP>
                    <FP SOURCE="FP-1">Naval Region</FP>
                    <FP SOURCE="FP-1">Barbers Point Co: Honolulu HI 96707-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220039</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Comment: 3606 sq. ft. needs major repair, possible lead paint, presence of asbestos</FP>
                    <HD SOURCE="HD3">New York</HD>
                    <FP SOURCE="FP-1">Bldg. 1225</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220014</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 3865 sq. ft. needs repairs, presence of asbestos/lead paint, most recent use—research lab.</FP>
                    <FP SOURCE="FP-1">Bldg. 1226</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220015</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 7500 sq. ft., most recent use—storage</FP>
                    <FP SOURCE="FP-1">Bldg. 1227</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220016</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 1152 sq. ft., presence of asbestos/lead paint, most recent use—power station </FP>
                    <FP SOURCE="FP-1">Bldg. 1231</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220017</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 3865 sq. ft., presence of asbestos/lead paint/volatile organic compounds, access requirements, most recent use—research lab </FP>
                    <FP SOURCE="FP-1">Bldg. 1233</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220018</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 1152 sq. ft., needs repair, presence of asbestos/lead paint/volatile organic compounds, access requirements, most recent use—power station </FP>
                    <FP SOURCE="FP-1">Bldg. 1235, 1239</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220019</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 144/825 sq. ft., need repairs, presence of lead paint, most recent use—electric switch station </FP>
                    <FP SOURCE="FP-1">Bldg. 1241</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220020</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 159 sq. ft., presence of lead paint, most recent use—sewage pump station </FP>
                    <FP SOURCE="FP-1">Bldg. 1243</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220021</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 25 sq. ft., most recent use—waste treatment </FP>
                    <FP SOURCE="FP-1">Bldg. 1245</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220022</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 3835 sq. ft., needs repair, presence of asbestos/lead paint, most recent use—research lab </FP>
                    <FP SOURCE="FP-1">Bldg. 1247</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220023</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 576 sq. ft., needs repair, presence of asbestos/lead paint, most recent use—power station </FP>
                    <FP SOURCE="FP-1">Bldg. 1250 + land</FP>
                    <FP SOURCE="FP-1">Verona Text Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220024</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 11,766 sq. ft., offices/lab with 495 acres, presence of asbestos/lead paint/wetlands </FP>
                    <FP SOURCE="FP-1">Bldg. 1253</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220025</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 3835 sq. ft., needs repair, presence of asbestos/lead paint/volatile organic compounds, access requirements, most recent use—research lab </FP>
                    <FP SOURCE="FP-1">Bldg. 1255</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220026</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 576 sq. ft., needs repair, presence of lead paint/volatile organic compounds, access requirements, most recent use—power station</FP>
                    <FP SOURCE="FP-1">Bldg. 1261</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220027</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 3835 sq. ft., needs repair, presence of asbestos/lead paint, most recent use—research lab</FP>
                    <FP SOURCE="FP-1">Bldg. 1263</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220028</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 576 sq. ft., repair, presence of lead paint, most recent use—power station</FP>
                    <FP SOURCE="FP-1">Bldgs. 1266, 1269</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220029</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 3730/3865 sq. ft., need repairs, presence of asbestos/lead paint, most recent use—research lab</FP>
                    <FP SOURCE="FP-1">Bldg. 1271</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220030</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 1152 sq. ft., needs repair, presence of lead paint, most recent use—power station</FP>
                    <FP SOURCE="FP-1">Bldg. 1273</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220031</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 87 sq. ft., presence of asbestos, most recent use—sewage pump station</FP>
                    <FP SOURCE="FP-1">Bldg. 1277</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220032</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 3865 sq. ft., needs repair, presence of asbestos/lead paint, most recent use—research lab</FP>
                    <FP SOURCE="FP-1">Bldg. 1279</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">
                        Landholding Agency: Air Force
                        <PRTPAGE P="40959"/>
                    </FP>
                    <FP SOURCE="FP-1">Property Number: 18200220033</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 1152 sq. ft., needs repair, presence of lead paint, most recent use—power station</FP>
                    <FP SOURCE="FP-1">Bldg. 1285</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220034</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 4690 sq. ft., needs repair, presence of asbestos/lead paint, most recent use—research lab</FP>
                    <FP SOURCE="FP-1">Bldg. 1287</FP>
                    <FP SOURCE="FP-1">Verona Test Annex</FP>
                    <FP SOURCE="FP-1">Verona Co: Oneida NY 13478-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220035</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 1152 sq. ft., needs repair, presence of lead paint, most recent use—power station </FP>
                    <HD SOURCE="HD1">Unsuitable Properties</HD>
                    <HD SOURCE="HD2">Buildings (by State)</HD>
                    <HD SOURCE="HD3">Alaska</HD>
                    <FP SOURCE="FP-1">Bldg. 15532</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB Co: AK 99506-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220001</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within airport runway clear zone; Secured Area</FP>
                    <HD SOURCE="HD3">Arkansas</HD>
                    <FP SOURCE="FP-1">Helena Casting Plant</FP>
                    <FP SOURCE="FP-1">Helena Co: Phillips AR 72342-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE </FP>
                    <FP SOURCE="FP-1">Property Number: 31200220001</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">California</HD>
                    <FP SOURCE="FP-1">Bldg. 41308</FP>
                    <FP SOURCE="FP-1">Marine Corps Base</FP>
                    <FP SOURCE="FP-1">Camp Pendleton Co: CA 92055-</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220031</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Eniwetok Carports</FP>
                    <FP SOURCE="FP-1">Marine Corps Logistics Base</FP>
                    <FP SOURCE="FP-1">Barstow Co: San Bernardino CA 92311-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220032</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Eniwetok Public Quarters</FP>
                    <FP SOURCE="FP-1">Marine Corps Logistics Base</FP>
                    <FP SOURCE="FP-1">Barstow Co: San Bernardino CA 92311-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220033</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 229</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Seal Beach</FP>
                    <FP SOURCE="FP-1">Fallbrook Co: CA 92028-3187</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220048</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 331</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Seal Beach</FP>
                    <FP SOURCE="FP-1">Fallbrook Co: CA 92028-3187</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220049</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 434</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Seal Beach</FP>
                    <FP SOURCE="FP-1">Fallbrook Co: CA 92028-3187</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220050</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 437</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Seal Beach</FP>
                    <FP SOURCE="FP-1">Fallbrook Co: CA 92028-3187</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220051</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 440</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Seal Beach</FP>
                    <FP SOURCE="FP-1">Fallbrook Co: CA 92028-3187</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220052</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 906</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Seal Beach</FP>
                    <FP SOURCE="FP-1">Fallbrook Co: CA 92028-3187</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220053</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Iowa</HD>
                    <FP SOURCE="FP-1">Treatment Plant</FP>
                    <FP SOURCE="FP-1">South Fork Park</FP>
                    <FP SOURCE="FP-1">Mystic Co: Appanoose IA 52574-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220002</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Kansas</HD>
                    <FP SOURCE="FP-1">Bldg. #1</FP>
                    <FP SOURCE="FP-1">Kanopolis Project</FP>
                    <FP SOURCE="FP-1">Marquette Co: Ellsworth KS 67456-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220003</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. #2</FP>
                    <FP SOURCE="FP-1">Kanopolis Project</FP>
                    <FP SOURCE="FP-1">Marquette Co: Ellsworth KS 67456-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220004</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. #4</FP>
                    <FP SOURCE="FP-1">Kanopolis Project</FP>
                    <FP SOURCE="FP-1">Marquette Co: Ellsworth KS 67456-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220005</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Comfort Station</FP>
                    <FP SOURCE="FP-1">Clinton Lake Project</FP>
                    <FP SOURCE="FP-1">Lawrence Co: Douglas KS 66049-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220006</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Missouri</HD>
                    <FP SOURCE="FP-1">#07004, 60006, 60007</FP>
                    <FP SOURCE="FP-1">Crabtree Cove/Stockton Area</FP>
                    <FP SOURCE="FP-1">Stockton Co: MO 65785-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220007</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Montana</HD>
                    <FP SOURCE="FP-1">Bldg. 347</FP>
                    <FP SOURCE="FP-1">Malmstrom AFB</FP>
                    <FP SOURCE="FP-1">Malmstrom AFB Co: Cascade MT 59402-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220011</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 3063</FP>
                    <FP SOURCE="FP-1">Malmstrom AFB</FP>
                    <FP SOURCE="FP-1">Malmstrom AFB Co: Cascade MT 5940-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220012</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 3064</FP>
                    <FP SOURCE="FP-1">Malmstrom AFB</FP>
                    <FP SOURCE="FP-1">Malmstrom AFB Co: Cascade MT 59402-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220013</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material Secured Area</FP>
                    <HD SOURCE="HD3">Nebraska</HD>
                    <FP SOURCE="FP-1">#30004</FP>
                    <FP SOURCE="FP-1">Harlan County Project</FP>
                    <FP SOURCE="FP-1">Republican Co: Harlan NE 68971-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220008</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">#30005, 3006</FP>
                    <FP SOURCE="FP-1">Harlan County Project</FP>
                    <FP SOURCE="FP-1">Republican Co: Harlan NE 68971-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200220009</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">New Mexico</HD>
                    <FP SOURCE="FP-1">Bldg. 6721</FP>
                    <FP SOURCE="FP-1">Kirkland AFB</FP>
                    <FP SOURCE="FP-1">Albuquerque Co: Bernalillo NM 87185-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220042</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">New York</HD>
                    <FP SOURCE="FP-1">6 UG Missile Silos</FP>
                    <FP SOURCE="FP-1">Youngstown Text Annex</FP>
                    <FP SOURCE="FP-1">Porter Co: Niagara NY</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220003</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 100</FP>
                    <FP SOURCE="FP-1">Youngstown Test Annex</FP>
                    <FP SOURCE="FP-1">Porter Co: Niagara NY</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220004</FP>
                    <FP SOURCE="FP-1">
                        Status: Unutilized
                        <PRTPAGE P="40960"/>
                    </FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 101</FP>
                    <FP SOURCE="FP-1">Youngstown Test Annex</FP>
                    <FP SOURCE="FP-1">Porter Co: Niagara NY</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220005</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 104</FP>
                    <FP SOURCE="FP-1">Youngstown Test Annex</FP>
                    <FP SOURCE="FP-1">Porter Co: Niagara NY</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220006</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 107</FP>
                    <FP SOURCE="FP-1">Youngstown Test Annex</FP>
                    <FP SOURCE="FP-1">Porter Co: Niagara NY</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220007</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 109</FP>
                    <FP SOURCE="FP-1">Youngstown Test Annex</FP>
                    <FP SOURCE="FP-1">Porter Co: Niagara NY</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220008</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 116</FP>
                    <FP SOURCE="FP-1">Youngstown Test Annex</FP>
                    <FP SOURCE="FP-1">Porter Co: Niagara NY</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200220009</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Tennessee</HD>
                    <FP SOURCE="FP-1">Bldg. 9723-21</FP>
                    <FP SOURCE="FP-1">Y-12 Natl Security Complex</FP>
                    <FP SOURCE="FP-1">Oak Ridge Co: Anderson TN 37831-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220043</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldgs. 9205, 9208</FP>
                    <FP SOURCE="FP-1">Y-12 Natl Security Complex</FP>
                    <FP SOURCE="FP-1">Oak Ridge Co: Anderson TN 37831-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220059</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area Extensive deterioration</FP>
                    <HD SOURCE="HD3">Texas</HD>
                    <FP SOURCE="FP-1">Zone 5, Bldg. FS-18</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220044</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 11, Bldg. 11-001</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220045</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 11, 3 Bldgs.</FP>
                    <FP SOURCE="FP-1">11-015, 11-015B, 11-046</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220046</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area </FP>
                    <FP SOURCE="FP-1">Zone 11, Bldg. 11-041</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220047</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 11, Bldg. 11-044 </FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220048</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, Bldg. 12-003P</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220049</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, Bldg. 12-05G1</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220050</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, 11 Bldgs.</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Location: 12-010, 12-010V1, 12-010V2, 12-010L, 12-R-010, 12-012, 12-R-012, 12-012V, 12-R-013, 12-R-013RR, 12-13V</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220051</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, Bldg. 12-017C</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220052</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, Bldg. 12-20</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200220053</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, 8 Bldgs.</FP>
                    <FP SOURCE="FP-1">Pantex Plant</FP>
                    <FP SOURCE="FP-1">Amarillo Co:  Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Location: 12-024, 12-024A, 12-02455, 12-025, 12-R-025, 12-030, 12-043, 12-043A </FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy  </FP>
                    <FP SOURCE="FP-1">Property Number: 41200220054</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, Bldg. 12-27</FP>
                    <FP SOURCE="FP-1">Pantex  Plant </FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy </FP>
                    <FP SOURCE="FP-1">Property Number: 41200220055</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, Bldg. 12-038</FP>
                    <FP SOURCE="FP-1">Pantex  Plant </FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy </FP>
                    <FP SOURCE="FP-1">Property Number: 41200220056</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 12, 2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Pantex  Plant </FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy </FP>
                    <FP SOURCE="FP-1">Property Number: 41200220057</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Zone 13, 6 Bldgs.</FP>
                    <FP SOURCE="FP-1">Pantex  Plant </FP>
                    <FP SOURCE="FP-1">Amarillo Co: Carson TX 79120-</FP>
                    <FP SOURCE="FP-1">Location: 13-041, 13-042, 13-043, 13-044, 13-045, 13-046</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy </FP>
                    <FP SOURCE="FP-1">Property Number: 41200220058</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <HD SOURCE="HD3">Virginia</HD>
                    <FP SOURCE="FP-1">Pier 12 </FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Helena Annex</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                    <FP SOURCE="FP-1">Property Number: 77200220035</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. SP-46</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA 23511-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                    <FP SOURCE="FP-1">Property Number: 77200220036</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. SP-93</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA 23511-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                    <FP SOURCE="FP-1">Property Number: 77200220037</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. AMF-3</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA 23511-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                    <FP SOURCE="FP-1">Property Number: 77200220038</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. U-40/Portion</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA </FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                    <FP SOURCE="FP-1">Property Number: 77200220040</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. SP-63</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">
                        Norfolk Co: VA 
                        <PRTPAGE P="40961"/>
                    </FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                    <FP SOURCE="FP-1">Property Number: 77200220041</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. SP-63A</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA </FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy </FP>
                    <FP SOURCE="FP-1">Property Number: 77200220042</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. A-67</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220043</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. U-124</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220044</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. CEP-213</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Norfolk Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220045</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 51</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220054</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 79</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220055</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 89</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220056</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">5 Bldgs.</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">#90, 91, 95, 96, 101</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220057</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 119A</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220058</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 378</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220059</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 398</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220060</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 415</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220061</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldgs. 440, 441</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220062</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Secured Area; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 508</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220063</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 510</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220064</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 605</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220065</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 624</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220066</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 688</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220067</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Bldgs. 1271, 1272, 1273</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220068</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                    <FP SOURCE="FP-1">Bldgs. 1465, 1466</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220069</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Bldgs. 1467, 1468. 1469</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220070</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 1799</FP>
                    <FP SOURCE="FP-1">Naval Weapons Station</FP>
                    <FP SOURCE="FP-1">Yorktown Co: VA 23691-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220071</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Secured Area</FP>
                    <HD SOURCE="HD2">Land</HD>
                    <HD SOURCE="HD3">California</HD>
                    <FP SOURCE="FP-1">Eniwetok Playgrounds</FP>
                    <FP SOURCE="FP-1">Marine Corps Logistics Base</FP>
                    <FP SOURCE="FP-1">Barstow Co: San Bernardino CA 92311-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200220034</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-14722 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4210-29-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Reclamation </SUBAGY>
                <DEPDOC>[INT-DES-02-23].</DEPDOC>
                <SUBJECT>City of Albuquerque Drinking Water Project, New Mexico </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Reclamation, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability and notice of public hearings for the draft environmental impact statement for the City of Albuquerque drinking water project. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        Pursuant to the National Environmental Policy Act (NEPA) of 1969 (as amended), the Department of the Interior, Bureau of Reclamation (Reclamation), as lead agency, and the City of Albuquerque (City), as co-lead 
                        <PRTPAGE P="40962"/>
                        agency, have prepared a draft environmental impact statement (DEIS) for the City of Albuquerque Drinking Water Project. The U.S. Army Corps of Engineers is a cooperating agency. The project is the main component of the Albuquerque Water Resources Management Strategy, adopted by the City Council, which aims to efficiently use existing water resources and develop a safe and sustainable water supply for City residents to the year 2060. The proposed alternatives provide a means of action through which the City would fully consumptively use the City's San Juan-Chama Project water to provide a sustainable water supply. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        A 60-day public review period commences with the publication of this notice. Written comments on the DEIS are due by August 13, 2002, and should be submitted to Lori Robertson at the address given below. Public hearings to receive oral and/or written comments from interested individuals and organizations on the environmental impacts of the proposal will be held during the month of July in Albuquerque, Socorro, and Espano
                        <AC T="6"/>
                        la, New Mexico. The public hearings schedule is as follows: 
                    </P>
                    <P>• July 2, 2002—6 p.m. to 9 p.m. (local time) at the Albuquerque Convention Center, Brazos Room, 401 2nd Street, Albuquerque, New Mexico. </P>
                    <P>• July 9, 2002—6 p.m. to 9 p.m. (local time) at the Macey Hall, New Mexico Tech Campus, 801 Leroy Place, Socorro, New Mexico. </P>
                    <P>
                        • July 10, 2002—6 p.m. to 9 p.m. (local time) at the City Council Chambers, 405 Paseo del On
                        <AC T="6"/>
                        ate, Espano
                        <AC T="6"/>
                        la, New Mexico. 
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Written comments on the DEIS should be addressed to Lori Robertson, Bureau of Reclamation, Albuquerque Area Office, 505 Marquette, NW., Suite 1313, Albuquerque, New Mexico 87102; faxogram (505) 248-5356; e-mail: 
                        <E T="03">lrobertson@uc.usbr.gov.</E>
                         Our practice is to make comments, including names and home addresses of respondents, available for public review. Individual respondents may request that we withhold their home address from public disclosure, which we will honor to the extent allowable by law. If you wish us to withhold your name and/or address, you must state this prominently at the beginning of your comment. We will make all submissions from organizations or businesses, and from individuals identifying themselves as representatives or officials of organizations or businesses, available for public disclosure in their entirely. 
                    </P>
                    <P>
                        The document is available on the Internet at 
                        <E T="03">www.uc.usbr.gov.</E>
                         We encourage you to review the DEIS on-line or at the locations listed below. You may request a copy of the document by contacting Rick Billings, Parsons Engineering Science, Inc., 3150 Carlisle Blvd., N.E., Suite 205, Albuquerque, New Mexico 87110; telephone (505) 889-4525. 
                    </P>
                    <P>Copies of the DEIS are available for public review and inspection at the following locations: </P>
                    <P>• City of Albuquerque Public Works Department, 500 Marquette, N.W., City/County Building, Albuquerque, New Mexico 87102. </P>
                    <P>• Bureau of Reclamation, Upper Colorado Regional Office, 125 South State Street, Room 6107, Salt Lake City, Utah 84138-1102. </P>
                    <P>• Bureau of Reclamation, Albuquerque Area Office, 505 Marquette, N.W., Suite 1313, Albuquerque, New Mexico 87102. </P>
                    <P>• Local Government Division, Attention: Ken Hughes, Bataan Memorial Building, Room 201, Santa Fe, New Mexico 87503. </P>
                    <P>• Parsons Engineering Science, Inc., 3150 Carlisle Blvd., N.E., Suite 205, Albuquerque, New Mexico 87110. </P>
                </ADD>
                <HD SOURCE="HD1">Libraries </HD>
                <FP SOURCE="FP-1">Albuquerque Public Library, Reference Desk, Main Library, 501 Copper, N.E., Albuquerque, New Mexico </FP>
                <FP SOURCE="FP-1">North Valley Public Library, Reference Desk, 7704 2nd Street, N.W., Albuquerque, New Mexico </FP>
                <FP SOURCE="FP-1">South Broadway Public Library, Reference Library, 1205 Broadway, S.E., Albuquerque, New Mexico </FP>
                <FP SOURCE="FP-1">Cherry Hills Public Library, Reference Library, 6901 Barstow, N.E., Albuquerque, New Mexico </FP>
                <FP SOURCE="FP-1">
                    Socorro Public Library, 401 Park Street, Socorro, New Mexico Espano
                    <AC T="6"/>
                    la Public Library, 921 Paseo del Norte, Espano
                    <AC T="6"/>
                    la, New Mexico 
                </FP>
                <FP SOURCE="FP-1">Santa Fe Public Library, 145 Washington Avenue, Santa Fe, New Mexico </FP>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Lori Robertson, Bureau of Reclamation, Albuquerque Area Office, 505 Marquette, NW., Suite 1313, Albuquerque, New Mexico 87102, telephone (505) 248-5326 or John Stomp, City of Albuquerque, Public Works Department, PO Box 1293, Albuquerque, New Mexico 87103, telephone (505) 768-3631. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The City proposes to construct and operate a surface water diversion on the Rio Grande, with associated water treatment and transmission facilities, to fully consumptively use the City's San Juan-Chama water to provide a sustainable drinking water supply for its citizens. The proposed project, referred to as the City's Drinking Water Project, would entail four elements: (1) Diverting surface water from the Rio Grande, (2) transporting the raw water to a new water treatment plant, (3) treating the raw water to drinking water standards, and (4) distributing the treated, potable water to customers in the City's water service area. The Drinking Water Project is the most significant aspect of the Albuquerque Water Resources Management Strategy for purposes of ensuring a sustainable water supply. </P>
                <P>The project would use the City's allocation of its San Juan-Chama water (48,200 acre-feet per year) to be supplied through existing San Juan-Chama Project facilities. After transit losses to Albuquerque, the amount available for full use would approximate 47,000 acre-feet per year. A total of approximately 94,000 acre-feet per year, consisting of 47,000 acre-feet per year of the City's San Juan-Chama water and 47,000 acre-feet per year of native Rio Grande surface water, would be diverted from the Rio Grande near Albuquerque and conveyed to a new water treatment plant for treatment. After the City's San Juan-Chama water is fully consumed, the native Rio Grande water, about half of the 94,000 acre-feet per year, would be returned to the Rio Grande following treatment at the City's Southside Water Reclamation Plant. </P>
                <P>The Santa Fe Group aquifer, the aquifer underlying the Albuquerque metropolitan area, is currently the City's sole source of water. Continued reliance on groundwater as the sole source of supply is not sustainable. The proposed project provides a sustainable water supply through full use of renewable surface supplies, reduces the demand on the aquifer, and restores it as a drought reserve. Demand on the aquifer would be reduced by approximately 94,000 acre-feet per year. The proposed project also includes a conjunctive use component by using San Juan-Chama water in an aquifer storage and recovery project. </P>
                <P>
                    Current and projected water demands would not be met without the proposed project. The aquifer would continue to be mined and could not serve as a drought reserve. The long-term effects on the aquifer from groundwater extraction would have serious consequences for Albuquerque and other users in the metropolitan area and throughout the Middle Rio Grande. Environmental consequences from continued and increased pumping from the aquifer likely would include large 
                    <PRTPAGE P="40963"/>
                    groundwater level declines, land-surface subsidence, and water quality degradation. The proposed project also represents a viable way for the City to satisfy Environmental Protection Agency promulgated arsenic standards under the Safe Drinking Water Act. The project would combine treated San Juan-Chama surface water that is low in arsenic with groundwater that has higher background levels. 
                </P>
                <P>Public process and participation in the selection and ranking of alternatives for the Drinking Water Project, and ultimately for analysis in this DEIS, has been extensive. Commencing in 1995 and continuing through the present, the City has held over 100 public meetings for purposes of presenting, analyzing, ranking, and/or selecting alternatives. Pursuant to compliance with NEPA, the identification of environmental issues and concerns, and development of potential mitigation and environmental enhancements, has been a primary focus of the City throughout the course of the development of the Drinking Water Project and the alternatives for implementation. </P>
                <P>Public and agency scoping and involvement continued with agency scoping workshops conducted in December 1998. Three formal public scoping meetings were held during September 1999, one each in the cities of Albuquerque, Socorro, and Espanola, New Mexico. Eighteen interagency workgroup meetings have been completed to solicit input from federal, state, City, and Pueblo entities. Numerous public meetings to present status reports and obtain input also have been undertaken to review the water treatment plant location and Drinking Water Project alternatives-selection process. A Town Hall meeting was held in April 2001 to present a preferred alternative. </P>
                <P>Over the course of six years, the City conducted a comprehensive evaluation process that incorporated public and agency input into the development of the Drinking Water Project as part of the City's Albuquerque Water Resources Management Strategy. As a result of this extensive public process, three action alternatives and the No Action Alternative were selected for further evaluation of environmental and socioeconomic consequences in the DEIS. The four alternatives retained for detailed analysis are: </P>
                <P>(1) No Action, or continued reliance on groundwater resources to meet current and projected drinking water demand, and continuation of conservation measures; </P>
                <P>(2) The diversion and full consumptive use of the City's San Juan-Chama water via the existing Angostura Diversion Dam (a Middle Rio Grande Project facility) on the Rio Grande, with conveyance of raw water to a new water treatment plant via two existing Middle Rio Grande Project conveyance facilities, and distribution of treated, potable water to consumers in the Albuquerque metropolitan area; </P>
                <P>(3) The diversion and full consumptive use of the City's San Juan-Chama water at a new surface diversion dam to be constructed on the Rio Grande north of Paseo del Norte in Albuquerque, with conveyance of raw water to a new water treatment plant via a new pipeline, and distribution of treated, potable water to consumers in the Albuquerque metropolitan area; and </P>
                <P>(4) The diversion and full consumptive use of the City's San Juan-Chama water via a new subsurface diversion to be constructed in the Rio Grande near Paseo del Norte, with conveyance of raw water to a new water treatment plant via a new pipeline, and distribution of treated, potable water to consumers in the Albuquerque metropolitan area. </P>
                <P>The following project components would be common to each of the action alternatives: </P>
                <P>• A new water treatment plant, </P>
                <P>• A potable water distribution pipeline system and associated storage facilities, and </P>
                <P>• Aquifer storage and recovery.</P>
                <P>The Chappell Drive water treatment plant would treat the raw water diverted from the Rio Grande to meet or exceed federal and state standards for municipal drinking water. The proposed water treatment plant would have a treatment capacity of 92 million gallons per day, or 142 cubic feet per second. The potable water transmission pipeline alignment would distribute treated water via pipelines from the water treatment plant to the City's customers. The selected piping transmission corridors would permit optimum use of existing hydraulic gradients and existing City water distribution lines. Aquifer storage and recovery would occur by injection of treated potable water into a number of City wells during low demand periods and would later be recovered by groundwater pumping. </P>
                <HD SOURCE="HD1">Proposed Federal Action </HD>
                <P>The federal actions requiring NEPA compliance are: (1) Issuance of a license by Reclamation to the City for the location of project facilities on Reclamation-owned property or right-of-way, or approval of a license between the City and the Middle Rio Grande Conservancy District for the location of facilities on a right-of-way held by Reclamation over property owned by the Middle Rio Grande Conservancy District; (2) execution of a water carriage contract authorizing use of federal irrigation canals to convey non-project water (this action would be required only if there would be diversion of the City's San Juan-Chama Project water at the Angostura Diversion Dam and conveyance of the water through existing facilities of the Middle Rio Grande Project). Special legislation would be needed to authorize carriage of non-project water for municipal and industrial purposes through Middle Rio Grande Project facilities; and (3) Clean Water Act Section 404 permitting from the U.S. Army Corps of Engineers in conjunction with construction of project facilities in waters of the United States. The U.S. Fish and Wildlife Service and the Environmental Protection Agency will provide consultation and review pursuant to their respective statutory authority under the Endangered Species Act, Clean Water Act, and NEPA. </P>
                <P>
                    <E T="03">Hearing Process Information:</E>
                     An open house will begin at 6 p.m. followed by an informal question and answer period at 6:30 p.m. The formal public hearings will begin at 7 p.m. A question and answer period before the hearing serves to assist the public in focusing their comments on the DEIS and issues related to it. The question and answer period will not be part of the formal hearing record. Oral comments at the hearings will be limited to 10 minutes. The hearing officer may allow any speaker to provide additional oral comments after all persons wishing to comment have been heard. All comments will be formally recorded. Speakers not present when called will lose their privilege in the scheduled order and will be recalled at the end of the scheduled speakers. Speakers are encouraged to provide written versions of their oral comments, and any other additional written materials, for the hearing record. 
                </P>
                <P>Written comments from those unable to attend or those wishing to supplement their oral presentations at the hearings should be received by Reclamation's Albuquerque Area Office at the address given above no later than August 13, 2002, for inclusion in the hearing record. Under the NEPA process, written and oral comments received by the due date are given the same consideration. </P>
                <SIG>
                    <DATED>Dated: June 7, 2002. </DATED>
                    <NAME>Connie L. Rupp, </NAME>
                    <TITLE>Acting Regional Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15022 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-MN-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="40964"/>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Reclamation </SUBAGY>
                <SUBJECT>Resource Management Plan for Elephant Butte and Caballo Reservoirs, New Mexico </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Reclamation, Interior </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability of the Final Environmental Impact Statement on the Resource Management Plan for Elephant Butte and Caballo Reservoirs INT-FES-02-17.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to section 102 (2) (C) of the National Environmental Policy Act of 1969, as amended, the Bureau of Reclamation (Reclamation) has prepared a Final Environmental Impact Statement (FEIS) on the Resource Management Plan (RMP) for Elephant Butte and Caballo Reservoirs. Reclamation's proposed action is to develop an RMP that provides a conceptual framework for the conservation, protection, development, use, enhancement, and management of resources at Elephant Butte and Caballo Reservoirs. The proposed action exercises the provisions of several federal laws applicable to Reclamation. </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Copies of the FEIS are available for public review and inspection at the following locations: </P>
                    <P>• Bureau of Reclamation, Upper Colorado Regional Office, 125 South State Street, Room 6107, Salt Lake City, Utah 84138-1147; telephone (801) 524-3829 </P>
                    <P>• Bureau of Reclamation, Albuquerque Area Office, 505 Marquette NW., Suite 1313, Albuquerque, New Mexico 87102; telephone (505) 248-5357 </P>
                    <P>• Bureau of Reclamation, Elephant Butte Field Division, HC32, Box 312, Truth or Consequences, New Mexico 87901; telephone (505) 894-6661 </P>
                    <P>• Bureau of Reclamation, El Paso Field Division, 700 East San Antonio Avenue, Room 710, El Paso, Texas 79901; telephone (915) 534-6299 </P>
                    <P>• Local Government Division, Attention: Ken Hughes, Bataan Memorial Building, Room 201, Santa Fe, New Mexico 87503. </P>
                </ADD>
                <HD SOURCE="HD1">Libraries </HD>
                <P>• Copies will also be available for public review and inspection at the following public libraries: </P>
                <P>• Santa Fe Library, 145 Washington Avenue, Santa Fe, New Mexico </P>
                <P>• Rio Grande Valley Library, 501 Cooper Avenue, N.W., Albuquerque, New Mexico </P>
                <P>• Socorro Public Library, 401 Park Street, Socorro, New Mexico </P>
                <P>• Truth or Consequences Public Library, 325 Library Lane, Truth or Consequences, New Mexico </P>
                <P>• Las Cruces Library, 200 East Picacho, Las Cruces, New Mexico </P>
                <P>• El Paso Public Library, 501 North Oregon Street, El Paso, Texas </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Clay McDermeit, Reclamation Team Leader, Elephant Butte and Caballo Reservoirs RMP, 505 Marquette NW., Suite 1313, Albuquerque, New Mexico, 87102, telephone (505) 248-5391; or Ms. Rosemary Romero, Western Network, 1350-B, San Juan Drive, Santa Fe, New Mexico 87505; telephone (505) 982-9805. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FEIS considers the effects of four management alternatives on the land and water resources at Elephant Butte and Caballo Reservoirs. The Multi-Purpose Emphasis Alternative, which provides for a variety of multiple uses including expanded developed recreation areas, improved primitive recreation areas, and designated wildlife management areas, has been selected as the preferred alternative. This alternative further identifies a course of action with minimal environmental impact, increased resource protection, and an acceptable level of recreational use. Under the selected alternative, grazing would continue based on extensive monitoring and confirmation of the capability of the resources to sustain grazing, a total of 378 lease lots would be privatized, additional wildlife management areas would be established, and selected recreation facilities would be expanded to accommodate future public recreation needs. </P>
                <P>The Draft Environmental Impact Statement was issued September 24, 1999. Responses to comments received from interested organizations and individuals on the draft are addressed in the FEIS. No decision will be made on the proposed action until 30 days after release of the FEIS. After the 30-day waiting period, Reclamation will complete a Record of Decision. The Record of Decision will state the action that will be implemented and discuss all factors leading to that decision. </P>
                <SIG>
                    <DATED>Dated: May 3, 2002. </DATED>
                    <NAME>Rick L. Gold, </NAME>
                    <TITLE>Regional Director. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15021 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-MN-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION </AGENCY>
                <DEPDOC>[Investigation No. 731-TA-744 (Review)] </DEPDOC>
                <SUBJECT>Brake Rotors From China </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>United States International Trade Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Scheduling of an expedited five-year review concerning the antidumping duty order on brake rotors from China.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission hereby gives notice of the scheduling of an expedited review pursuant to section 751(c)(3) of the Tariff Act of 1930 (19 U.S.C. 1675(c)(3)) (the Act) to determine whether revocation of the antidumping duty order on brake rotors from China would be likely to lead to continuation or recurrence of material injury within a reasonably foreseeable time. For further information concerning the conduct of this review and rules of general application, consult the Commission's Rules of Practice and Procedure, part 201, subparts A through E (19 CFR part 201), and part 207, subparts A, D, E, and F (19 CFR part 207). </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 4, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Debra Baker (202-205-3180), Office of Investigations, U.S. International Trade Commission, 500 E Street SW., Washington, DC 20436. Hearing-impaired persons can obtain information on this matter by contacting the Commission's TDD terminal on 202-205-1810. Persons with mobility impairments who will need special assistance in gaining access to the Commission should contact the Office of the Secretary at 202-205-2000. General information concerning the Commission may also be obtained by accessing its internet server 
                        <E T="03">(http://www.usitc.gov).</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>
                    On June 4, 2002, the Commission determined that the domestic interested party group response to its notice of institution (67 FR 9462, March 1, 2002) was adequate and the respondent interested party group response was inadequate. The Commission did not find any other circumstances that would warrant conducting a full review.
                    <SU>1</SU>
                    <FTREF/>
                     Accordingly, the Commission determined that it would conduct an 
                    <PRTPAGE P="40965"/>
                    expedited review pursuant to section 751(c)(3) of the Act. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         A record of the Commissioners' votes, the Commission's statement on adequacy, and any individual Commissioner's statements will be available from the Office of the Secretary and at the Commission's web site.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Staff report </HD>
                <P>A staff report containing information concerning the subject matter of the review will be placed in the nonpublic record on June 28, 2002, and made available to persons on the Administrative Protective Order service list for this review. A public version will be issued thereafter, pursuant to section 207.62(d)(4) of the Commission's rules. </P>
                <HD SOURCE="HD1">Written submissions </HD>
                <P>
                    As provided in section 207.62(d) of the Commission's rules, interested parties that are parties to the review and that have provided individually adequate responses to the notice of institution,
                    <SU>2</SU>
                    <FTREF/>
                     and any party other than an interested party to the review may file written comments with the Secretary on what determination the Commission should reach in the review. Comments are due on or before July 3, 2002, and may not contain new factual information. Any person that is neither a party to the five-year review nor an interested party may submit a brief written statement (which shall not contain any new factual information) pertinent to the review by July 3, 2002. However, should Commerce extend the time limit for its completion of the final results of its review, the deadline for comments (which may not contain new factual information) on Commerce's final results is three business days after the issuance of Commerce's results. If comments contain business proprietary information (BPI), they must conform with the requirements of sections 201.6, 207.3, and 207.7 of the Commission's rules. The Commission's rules do not authorize filing of submissions with the Secretary by facsimile or electronic means. 
                </P>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The Commission has found the response submitted by the Coalition for the Preservation of American Brake Drum and Rotor Aftermarket Manufacturers to be individually adequate. Comments from other interested parties will not be accepted (
                        <E T="03">see</E>
                         19 CFR 207.62(d)(2)).
                    </P>
                </FTNT>
                <P>In accordance with sections 201.16(c) and 207.3 of the rules, each document filed by a party to the review must be served on all other parties to the review (as identified by either the public or BPI service list), and a certificate of service must be timely filed. The Secretary will not accept a document for filing without a certificate of service. </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>This review is being conducted under authority of title VII of the Tariff Act of 1930; this notice is published pursuant to section 207.62 of the Commission's rules. </P>
                    <P>By order of the Commission. </P>
                </AUTH>
                <SIG>
                    <DATED>Issued: June 11, 2002. </DATED>
                    <NAME>Marilyn R. Abbott, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15044 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">INTERNATIONAL TRADE COMMISSION </AGENCY>
                <DEPDOC>[Investigation No. 731-TA-745 (Review)] </DEPDOC>
                <SUBJECT>Steel Concrete Reinforcing Bar From Turkey </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>United States International Trade Commission. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Commission determination to conduct a full five-year review concerning the antidumping duty order on steel concrete reinforcing bar from Turkey. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Commission hereby gives notice that it will proceed with a full review pursuant to section 751(c)(5) of the Tariff Act of 1930 (19 U.S.C. 1675(c)(5)) to determine whether revocation of the antidumping duty order on steel concrete reinforcing bar from Turkey would be likely to lead to continuation or recurrence of material injury within a reasonably foreseeable time. A schedule for the review will be established and announced at a later date. For further information concerning the conduct of this review and rules of general application, consult the Commission's Rules of Practice and Procedure, part 201, subparts A through E (19 CFR part 201), and part 207, subparts A, D, E, and F (19 CFR part 207). </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>June 4, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mary Messer (202-205-3193), Office of Investigations, U.S. International Trade Commission, 500 E Street SW., Washington, DC 20436. Hearing-impaired persons can obtain information on this matter by contacting the Commission's TDD terminal on 202-205-1810. Persons with mobility impairments who will need special assistance in gaining access to the Commission should contact the Office of the Secretary at 202-205-2000. General information concerning the Commission may also be obtained by accessing its internet server (
                        <E T="03">http://www.usitc.gov</E>
                        ). The public record for this investigation may be viewed on the Commission's electronic docket (EDIS-ON-LINE) at 
                        <E T="03">http://dockets.usitc.gov/eol/public.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On June 4, 2002, the Commission determined that it should proceed to a full review in the subject five-year review pursuant to section 751(c)(5) of the Act. The Commission found that both the domestic and respondent interested party group responses to its notice of institution (67 F.R. 9465, March 1, 2002) were adequate. A record of the Commissioners' votes, the Commission's statement on adequacy, and any individual Commissioner's statements will be available from the Office of the Secretary and at the Commission's web site. </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>This review is being conducted under authority of title VII of the Tariff Act of 1930; this notice is published pursuant to section 207.62 of the Commission's rules. </P>
                </AUTH>
                <SIG>
                    <P>By order of the Commission.</P>
                    <DATED>Issued: June 10, 2002. </DATED>
                    <NAME>Marilyn R. Abbott, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15045 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Office of the Secretary </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>GovBenefits Office, U.S. Department of Labor. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of an opportunity for public comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Labor, as part of its continuing effort to reduce paperwork and respondent burden, conducts a pre-clearance consultation program to provide the general public and Federal agencies with an opportunity to comment on proposed the proposed continued collections of information in accordance with the Paperwork Reduction Act of 1995 (PRA95) [44 U.S.C. 3506 C (2)(A)]. This program helps to ensure that requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements on respondents can be properly assessed. A copy of the proposed information collection request (ICR) can be obtained by contacting the office listed below in the 
                        <E T="02">ADDRESS</E>
                         section of this notice. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATE:</HD>
                    <P>Comments are to be submitted by August 13, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESS:</HD>
                    <P>
                        A copy of the ICR and supporting documentation as submitted to the Office of Management and Budget can be obtained by contacting the Department of Labor. To obtain copies, contact Darrin King on 202-693-4129 or 
                        <PRTPAGE P="40966"/>
                        email: 
                        <E T="03">king_darrin@dol.gov.</E>
                         Send comments regarding this proposed collection of information, including suggestions for reducing the burden to the U.S. Department of Labor, GovBenefits Office, FPB, Room N-4309, Washington, D.C. 20210. 
                    </P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>The President's Management Agenda for E-Government (February 27, 2002) sets forth a strategy for simplifying the delivery of services to citizens. The President's agenda outlines a Federal E-Government Enterprise Architecture that will transition the management and delivery of government services from a bureaucracy-centered to a citizen-centered paradigm. To this end, the Department of Labor serves as the managing partner of the Administration's “GovBenefits” (formerly Eligibility Assistance Online”) strategy for assisting citizens in identifying and locating information on benefits sponsored by the Federal government. This tool will greatly reduce the burden on citizens attempting to locate services available from many different government agencies by providing one-stop access to information on obtaining those services. </P>
                <P>From time-to time, the precise questions or content my require modification to accommodate addition to the GovBenefits portal as well as new or revised services. Furthermore, while the initial launch version scheduled for April 2002 does not “collect” information, to better serve citizens through website design, subsequent versions may need to collect user demographics such as “average age.” Respondents answer a series of questions to the extent necessary for locating relevant information on Federal benefits. Responses are used by the respondent to expedite the identification and retrieval of sought after information and resources pertaining to the benefits sponsored by the Federal Government. </P>
                <HD SOURCE="HD1">II. Desired Focus of Comments </HD>
                <P>The Department of Labor is particularly interested in comments which: </P>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; </P>
                <P>• evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information; including the validity of the methodology and assumptions used. </P>
                <P>• enhance the quality, utility, and clarity of the information to be collected; and </P>
                <P>• minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, e.g., permitting electronic submissions of responses. </P>
                <HD SOURCE="HD1">III. Current Actions </HD>
                <P>This notice requests approval from OMB for the collection of information required for locating information on the GovBenefits web site. </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Agency:</E>
                     Office of the Secretary. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Information Collection Plan for GovBenefits. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1290-0003. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Not-for-profit institutions. 
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     500,000. 
                </P>
                <P>
                    <E T="03">Number of Responses:</E>
                     500,000. 
                </P>
                <P>
                    <E T="03">Average Time Per Response:</E>
                     2.5 minutes. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours:</E>
                     20,000. 
                </P>
                <P>
                    <E T="03">Total Annualized Capital/startup costs:</E>
                     $0. 
                </P>
                <P>
                    <E T="03">Total Initial Annual Costs:</E>
                     $0. 
                </P>
                <P>Comments submitted in response to this notice will be summarized and included in the agency's request for OMB approval of the information collection request. Comments will become a matter of public record. </P>
                <SIG>
                    <DATED>Dated: June 10, 2002. </DATED>
                    <NAME>George Wollner, </NAME>
                    <TITLE>Department of Labor, GovBenefits Project Manager. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15071 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-23-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR </AGENCY>
                <SUBAGY>Employment and Training Administration </SUBAGY>
                <SUBJECT>Workforce Investment Act (WIA) Section 167, the National Farmworker Jobs Program (NFJP) </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Employment and Training Administration (ETA), Labor. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of formula allocations for the Program Year (PY) 2002 National Farmworker Jobs Program (NFJP), request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Under section 182(d) of the Workforce Investment Act (WIA) of 1998, ETA is publishing the PY 2002 allocations for the NFJP authorized under Section 167 of the WIA. The allocations are distributed to the States by a formula that estimates, by state, the relative demand for NFJP services. The allocations in this Notice apply to the program year beginning July 1, 2002. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before June 24, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments should be sent to Ms. Alicia Fernandez-Mott, Chief, Division of Seasonal Farmworker Programs, Room N-4641, Employment and Training Administration, U.S. Department of Labor, 200 Constitution Avenue, NW., Washington, DC 20210. Her e-mail address is 
                        <E T="03">afernandez@doleta.gov</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Alicia Fernandez-Mott, Chief, Division of Seasonal Farmworker Programs, Room N-4641, Employment and Training Administration, U.S. Department of Labor, 200 Constitution Avenue, NW., Washington, DC 20210. Her telephone number is (202) 693-3729. (This is not a toll-free number.) </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>
                    On May 19, 1999, we published a Notice of a new formula for allocating funds available for the NFJP (formerly referred to as the Section 402 Migrant and Seasonal Farmworker (MSFW) Program) in the 
                    <E T="04">Federal Register</E>
                     at 64 FR 27390 (May 19, 1999). The Notice explains how the new formula achieves its purpose of distributing funds geographically by state service area on the basis of each area's relative share of farmworkers who are eligible for enrollment in the NFJP. The new formula consists of a rational combination of multiple data sets that were selected to yield the relative share distribution of eligible farmworkers. The combined-data formula is substantially more relevant to the purpose of aligning the allocations with the eligible population than the allocations determined by the prior formula. 
                </P>
                <P>
                    The realignments made by the new formula gave rise to significant changes in relative funding levels. The magnitude of the realignments was substantial for some of the state areas that are scheduled to experience decreases as a result of the transition from the original distributions to the distributions provided by the new formula. To provide a smooth transition to the realigned distributions, Part IV of the May 19, 1999, Notice provided a strategy for phased implementation of the new formula through four incremental “hold harmless” stages. The stages provide a graduated implementation of the formula 
                    <PRTPAGE P="40967"/>
                    allocations by limiting the rate of reduction in relative funding levels to the four annual increments of 95 percent of the 1998 level in PY 1999, 90 percent in PY 2000, 85 percent in PY 2001, and 80 percent in PY 2002. Full implementation of the new (combined-data) formula will be reached on the 5th year allocation in PY 2003. 
                </P>
                <P>Because it is the best available allocation tool, we continue to implement the new formula by applying the fourth implementation step of the formula described in the May 19, 1999, Notice to allocate PY 2002 WIA Section 167 funds. Section III of this Notice describes how the PY 2002 formula allocations are adjusted to account for the budget additions provided by Congress. </P>
                <P>The Department of Labor invites comments on our decision to continue the phased implementation of this formula in allocating PY 2002 funds for the NFJP. </P>
                <HD SOURCE="HD1">II. Limitations on Uses of Section 167 Funds </HD>
                <P>In appropriating the funds for PY 2002, Congress provided in its Appropriations Conference Report 107-342, as follows: “That, notwithstanding any other provision of law or related regulation, $80,770,000 shall be for carrying out Section 167 of the Workforce Investment Act, including $74,965,000 for formula grants, $4,786,000 for migrant and seasonal housing, and $1,019,000 for other discretionary purposes * * *.” </P>
                <HD SOURCE="HD1">III. PY 2002 Allocations </HD>
                <P>The PY 2002 allocations and the details of how they are made are provided in the Table at the end of this Notice. As in the prior three program years, the base amount selected for allocation under the formula is the PY 1999 allocated amount of $67,596,408. (Refer to column “C” to see the PY 1999 State allocations without the “hold-harmless” adjustments.) </P>
                <P>The fourth step (80 percent hold-harmless) allocations are given in column “E”. For comparison with the figures in column “E”, column “F” uses a spreadsheet formula to calculate 80 percent of the PY 1998 allocations. </P>
                <P>Sustaining 100 percent of the PY 1998 levels: Additional funding is provided under congressional direction in each of PY's 1999, 2000, 2001 and 2002 that establishes the 1998 level as a minimum level for all states. This requirement is applied cumulatively in PY 2002 to sustain at their 1998 levels those state service areas that receive a declining relative share of funding by the progressively-phased implementation of the new formula. Column “G” shows the additional “make whole” amounts allocated under the congressional recommendation to bring to their PY 1998 levels those State service areas where the demographics reflected under the formula show a smaller relative share of eligible farmworkers. Column “H” shows the total allocations after applying the “make whole” allocations that sustain the PY 1998 levels as the minimum allocation amounts. </P>
                <P>A total of $73,120,657 is allocated as the result of applying this requirement. At this stage, the PY 2002 amount allocated is the sum of the fourth (80 percent) step's formula allocation (column “E”) of $67,596,409 and the “make-whole” amount of $5,524,248, which brings all states to a minimum of their PY 1998 levels (column “G”). The total amount allocated at this stage is $1,844,343 less than the $74,965,000 minimum amount reserved in the Conference Report “for formula grants.” For informational purposes, column “I” shows what the allocation of the PY 2002 formula grants would be without adjustments of any kind. PY 2002 is the final step of the graduated phase-in of the new formula. To allocate this additional amount remaining from the amount reserved for the formula grants, the states with a higher amount in Column “I” than Column “H” are identified in column “J” by the entries, taken from column “D”, of the unadjusted formula relative shares. Column “K” shows the calculation of the relative distribution among those states identified in column “J”. Column “L” distributes the $1,844,343 by using the shares determined under column “K”. Column “M” (the sum of columns “H” and “L ”) provides the final NFJP allocations for PY 2002. </P>
                <HD SOURCE="HD1">IV. Rhode Island and the Minimum Funding Provisions </HD>
                <P>
                    Part V of the May 19, 1999, 
                    <E T="04">Federal Register</E>
                     Notice provides that a state service area allocated less than $60,000 could be combined with an adjoining state service area. As in PY's 2000 and 2001, the PY 2002 Rhode Island area allocation is combined with the Connecticut area allocation. 
                </P>
                <HD SOURCE="HD1">V. PY 2002 Allocations </HD>
                <P>Column “M” of the “Allocation Table” provides the allocations for the NFJP in PY 2002. Grantees will use these figures in preparing the PY 2002 NFJP grant plans. </P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 31st day of May, 2002. </DATED>
                    <NAME>Emily Stover DeRocco, </NAME>
                    <TITLE>Assistant Secretary, Employment and Training Administration. </TITLE>
                </SIG>
                <BILCOD>BILLING CODE 4510-30-P</BILCOD>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="40968"/>
                    <GID>EN14JN02.006</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="40969"/>
                    <GID>EN14JN02.007</GID>
                </GPH>
                <PRTPAGE P="40970"/>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15070 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4510-30-C</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBJECT>Employment Standards Administration Wage and Hour Division; Minimum Wages for Federal and Federally Assisted Construction; General Wage Determination Decisions</SUBJECT>
                <P>General wage determination decisions of the Secretary of Labor are issued in accordance with applicable law and are based on the information obtained by the Department of Labor from its study of local wage conditions and data made available from other sources. They specify the basic hourly wage rates and fringe benefits which are determined to be prevailing for the described classes of laborers and mechanics employed on construction projects of a similar character and in the localities specified therein.</P>
                <P>The determinations in these decisions of prevailing rates and fringe benefits have been made in accordance with 29 CFR part 1, by authority of the Secretary of Labor pursuant to the provisions of the Davis-Bacon Act of March 3, 1931, as amended (46 Stat. 1494, as amended, 40 U.S.C. 276a) and of other Federal statutes referred to in 29 CFR part 1, Appendix, as well as such additional statutes as may from time to time be enacted containing provisions for the payment of wages determined to be prevailing by the Secretary of Labor in accordance with the Davis-Bacon Act. The prevailing rates and fringe benefits determined in these decisions shall, in accordance with the provisions of the foregoing statutes, constitute the minimum wages payable on Federal and federally assisted construction projects to laborers and mechanics of the specified classes engaged on contract work of the character and in the localities described therein.</P>
                <P>Good cause is hereby found for not utilizing notice and public comment procedure thereon prior to the issuance of these determinations as prescribed in 5 U.S.C. 553 and not providing for delay in the effective date as prescribed in that section, because the necessity to issue current construction industry wage determinations frequently and in large volume causes procedures to be impractical and contrary to the public interest.</P>
                <P>
                    General wage determination decisions, and modifications and supersedeas decisions thereto, contain no expiration dates and are effective from their date of notice in the 
                    <E T="04">Federal Register</E>
                    , or on the date written notice is received by the agency, whichever is earlier. These decisions are to be used in accordance with the provisions of 29 CFR parts 1 and 5. Accordingly, the applicable decision, together with any modifications issued, must be made a part of every contract for performance of the described work within the geographic area indicated as required by an applicable Federal prevailing wage law and 29 CFR part 5. The wage rates and fringe benefits, notice of which is published herein, and which are contained in the Government Printing Office (GPO) document entitled “General Wage Determinations Issued Under The Davis-Bacon and Related Acts,” shall be the minimum paid by contractors and subcontractors to laborers and mechanics.
                </P>
                <P>Any person, organization, or governmental agency having an interest in the rates determined as prevailing is encouraged to submit wage rate and fringe benefit information for consideration by the Department.</P>
                <P>Further information and self-explanatory forms for the purpose of submitting this data may be obtained by writing to the U.S. Department of Labor, Employment Standards Administration, Wage and Hour Division, Division of Wage Determinations, 200 Constitution Avenue, NW., Room S-3014, Washington, DC 20210.</P>
                <HD SOURCE="HD1">Modification to General Wage Determination Decisions</HD>
                <P>
                    The number of the decisions listed to the Government Printing Office document entitled “General Wage Determinations Issued Under the Davis-Bacon and Related Acts” being modified are listed by Volume and State. Dates of publication in the 
                    <E T="04">Federal Register</E>
                     are in parentheses following the decisions being modified.
                </P>
                <EXTRACT>
                    <HD SOURCE="HD2">Volume I</HD>
                    <FP SOURCE="FP-2">Connecticut </FP>
                    <FP SOURCE="FP1-2">CT020001 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">CT020002 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">CT020003 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">CT020004 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">CT020005 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">CT020006 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP-2">New Hampshire</FP>
                    <FP SOURCE="FP1-2">NH020001 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">NH020002 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">NH020003 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">NH020004 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">NH020007 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP-2">Rhode Island</FP>
                    <FP SOURCE="FP1-2">RI020001 (Mar. 1, 2002)</FP>
                    <HD SOURCE="HD2">Volume II</HD>
                    <FP SOURCE="FP-2">Delaware</FP>
                    <FP SOURCE="FP1-2">DE020002 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">DE020005 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">DE020009 (Mar. 1, 2002)</FP>
                    <HD SOURCE="HD2">Volume III</HD>
                    <FP SOURCE="FP-2">None</FP>
                    <HD SOURCE="HD2">Volume IV</HD>
                    <FP SOURCE="FP-2">Minnesota</FP>
                    <FP SOURCE="FP1-2">MN020004 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020005 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020007 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020008 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020010 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020013 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020014 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020015 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020017 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020019 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020043 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020045 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020047 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020049 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020054 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020058 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MN020059 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP-2">Wisconsin</FP>
                    <FP SOURCE="FP1-2">WI020019 (Mar. 1, 2002)</FP>
                    <HD SOURCE="HD2">Volume V</HD>
                    <FP SOURCE="FP-2">Kansas</FP>
                    <FP SOURCE="FP1-2">KS020004 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020005 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020006 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020009 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020013 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020019 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020025 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020026 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020063 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">KS020067 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP-2">Texas</FP>
                    <FP SOURCE="FP1-2">TX020007 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">TX020010 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">TX020014 (Mar. 1, 2002)</FP>
                    <HD SOURCE="HD2">Volume VI</HD>
                    <FP SOURCE="FP-2">MONTANA</FP>
                    <FP SOURCE="FP1-2">MT020001 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MT020004 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MT020005 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MT020007 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MT020008 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">MT020033 (Mar. 1, 2002)</FP>
                    <HD SOURCE="HD2">Volume VII</HD>
                    <FP SOURCE="FP-2">CALIFORNIA </FP>
                    <FP SOURCE="FP1-2">CA020009 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">CA020009 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">CA020029 (Mar. 1, 2002)</FP>
                    <FP SOURCE="FP1-2">CA020030 (Mar. 1, 2002)</FP>
                </EXTRACT>
                <HD SOURCE="HD1">General Wage Determination Publication</HD>
                <P>General wage determinations issued under the Davis-Bacon and related Acts, including those noted above, may be found in the Government Printing Office (GPO) document entitled “General Wage Determination Issued Under the Davis-Bacon And Related Acts”. This publication is available at each of the 50 Regional Government Depository Libraries and many of the 1,400 Government Depository Libraries across the country.</P>
                <P>
                    General wage determinations issued under the Davis-Bacon and related Acts are available electronically at no cost on 
                    <PRTPAGE P="40971"/>
                    the Government Printing Office site at 
                    <E T="03">www.access.gpo.gov/davisbacon.</E>
                     They are also available electronically by subscription to the Davis-Bacon Online Service (
                    <E T="03">http://davisbacon.fedworld.gov</E>
                    ) of the National Technical Information Service (NTIS) of the U.S. Department of Commerce at 1-800-363-2068. This subscription offers value-added features such as electronic delivery of modified wage decisions directly to the user's desktop, the ability to access prior wage decisions issued during the year, extensive Help Desk Support, etc.
                </P>
                <P>Hard-copy subscriptions may be purchased from: Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402. (202) 512—1800.</P>
                <P>When ordering hard-copy subscription(s), be sure to specify the State(s) since subscriptions may be ordered for any or all of the six separate Volumes, arranged by State. Subscriptions include an annual edition (issued in January or February) which includes all current general wage determinations for the States covered by each volume. Throughout the remainder of the year, regular weekly updates will be distributed to subscribers.</P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 6 day of June, 2002.</DATED>
                    <NAME>Carl J. Poleskey,</NAME>
                    <TITLE>Chief, Branch of Construction Wage Determinations.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-14731 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-27-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL FOUNDATION ON THE ARTS AND THE HUMANITIES </AGENCY>
                <SUBJECT>National Endowment for the Arts; Proposed Collection; Comment Request </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Endowment for the Arts (NEA), as part of its continuing effort to reduce paperwork and respondent burden, conducts a preclearance consultation program to provide the general public and federal agencies with an opportunity to comment on proposed and/or continuing collections of information in accordance with the Paperwork Reduction Act of 1995 (PRA95) [44 U.S.C. 3506(c)(A)]. This program helps to ensure that requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirements on respondents can be properly assessed. Currently, the NEA is soliciting comments concerning the proposed information collection of: FY 2004-FY 2007 Blanket Justification for NEA Funding Application Guidelines and Reporting Requirements. A copy of the current information collection request can be obtained by contacting the office listed below in the address section of this notice. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Written comments must be submitted to the office listed in the address section below within 60 days from the date of this publication in the 
                        <E T="04">Federal Register</E>
                        . The NEA is particularly interested in comments which: 
                    </P>
                    <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; </P>
                    <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information including the validity of the methodology and assumptions used; </P>
                    <P>• Enhance the quality, utility, and clarity of the information to be collected; and </P>
                    <P>• Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, e.g., permitting electronic submissions of responses. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>A.B. Spellman, Deputy Chairman for Guidelines, Panel, and Council Operations, National Endowment for the Arts, 1100 Pennsylvania Avenue, NW., Room 516, Washington, DC 20506-0001, telephone (202) 682-5421 (this is not a toll-free number), fax (202) 682-5049. </P>
                </ADD>
                <SIG>
                    <NAME>Murray Welsh, </NAME>
                    <TITLE>Director, Administrative Services, National Endowment for the Arts. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15079 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7537-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Maritime Administration </SUBAGY>
                <SUBJECT>Reports, Forms and Recordkeeping Requirements; Agency Information Collection Activity Under OMB Review </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Maritime Administration, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In compliance with the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                        ), this notice announces that the Information Collection abstracted below has been forwarded to the Office of Management and Budget (OMB) for review and comment. The nature of the information collection is described as well as its expected burden. The 
                        <E T="04">Federal Register</E>
                         notice with a 60-day comment period soliciting comments on the following collection of information was published on March 1, 2002. No comments were received. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before July 15, 2002. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Kenneth Willis, 400 Seventh Street, Southwest, Washington, DC 20590. Telephone 202-366-2306; FAX 202-493-2180, or E-Mail: 
                        <E T="03">kenneth.willis@marad.dot.gov.</E>
                    </P>
                    <P>Copies of this collection can also be obtained from that office. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Maritime Administration (MARAD). </P>
                <P>
                    <E T="03">Title:</E>
                     Application and Reporting Elements for Participation in the Maritime Security Program. 
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     2133-0525. 
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of currently approved collection. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Operators of U.S.-flag vessels who are interested in participating in the Maritime Security Fleet. 
                </P>
                <P>
                    <E T="03">Form(s):</E>
                     None. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Maritime Security Act of 1996 established the Maritime Security Program which supports the operations of U.S.-flag vessels in the foreign commerce of the United States through assistance payments. Participating vessel operators receive assistance payments and are required to make their ships and other commercial transportation resources available to the Government during times of national emergency. The vessel operators who are interested in participating in the Maritime Security Fleet are required to submit an application to MARAD for its review and approval. MARAD uses this information to determine if selected vessels are qualified to participate in the Maritime Security Program. 
                </P>
                <P>
                    <E T="03">Annual Estimated Burden Hours:</E>
                     152 hours. 
                </P>
                <SUPLHD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P> Send comments to the Office of Information and Regulatory Affairs, Office of Management and Budget, 725 17th Street, NW., Washington, DC 20503, Attention MARAD Desk Officer. </P>
                    <P>
                        <E T="03">Comments are invited on:</E>
                         (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have 
                        <PRTPAGE P="40972"/>
                        practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed information collection; (c) ways to enhance the quality, utility and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including the use of automated collection techniques or other forms of information technology. 
                    </P>
                    <P>A comment to OMB is best assured of having its full effect if OMB receives it within 30 days of publication. </P>
                </SUPLHD>
                <SIG>
                    <DATED>Issued in Washington, DC on June 7, 2002. </DATED>
                    <NAME>Joel C. Richard, </NAME>
                    <TITLE>Secretary, Maritime Administration. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15025 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-81-P 1 </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION </AGENCY>
                <DEPDOC>[Docket No. 50-443] </DEPDOC>
                <SUBJECT>North Atlantic Energy Service Corporation; Seabrook Station, Unit No. 1; Notice of Consideration of Approval of Transfer of Facility Operating License and Conforming Amendment, and Opportunity for a Hearing </SUBJECT>
                <P>The U.S. Nuclear Regulatory Commission (the Commission) is considering the issuance of an order under 10 CFR 50.80 approving the transfer of Facility Operating License No. NPF-86 to the extent currently held by North Atlantic Energy Service Corporation (NAESCO), as the licensed operator and a non-owner of Seabrook Station, Unit No. 1 (Seabrook Station) and by certain owners of Seabrook Station (“Selling Owners”). The transfer would be to FPL Energy Seabrook, LLC (FPLE Seabrook), an indirect, wholly owned subsidiary of FPL Energy, LLC (FPLE), which is a wholly owned subsidiary of FPL Group Capital, Inc., which, in turn, is a wholly owned subsidiary of FPL Group, Inc. (FPL Group). The Commission is also considering amending the license for administrative purposes to reflect the proposed transfer. </P>
                <P>The following is a list of the Selling Owners who hold ownership interests in Seabrook Station and their respective interests: </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,8">
                    <TTITLE/>
                    <BOXHD>
                        <CHED H="1">Selling owners </CHED>
                        <CHED H="1">Percent </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">North Atlantic Energy Service Corporation </ENT>
                        <ENT>35.98201 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The United Illuminating Company </ENT>
                        <ENT>17.50000 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Great Bay Power Corporation </ENT>
                        <ENT>12.13240 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">New England Power Company </ENT>
                        <ENT>9.95766 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">The Connecticut Light and Power Company </ENT>
                        <ENT>4.05985 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Canal Electric Company </ENT>
                        <ENT>3.52317 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Little Bay Power Corporation </ENT>
                        <ENT>2.89989 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">New Hampshire Electric Cooperative, Inc. </ENT>
                        <ENT>2.17391 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="04">Total Ownership Included in Sale </ENT>
                        <ENT>88.22889 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>Massachusetts Municipal Wholesale Electric Company which holds a 11.59340% ownership interest, Taunton Municipal Lighting Plant which holds a 0.10034% ownership interest, and Hudson Light and Power Department which holds a 0.07737% ownership interest in Seabrook Station are not involved in the subject license transfer. </P>
                <P>According to an application for approval filed by NAESCO on behalf of itself and the Selling Owners, FPLE Seabrook would assume title to the acquired ownership interests in the facility following approval of the proposed license transfer, and would be responsible for the operation, maintenance, and eventual decommissioning of Seabrook Station. No physical changes to the facility or operational changes are being proposed in the application. </P>
                <P>The proposed amendment would replace references to NAESCO in the license as the operator of Seabrook Station with references to FPLE Seabrook, make changes consistent with FPLE Seabrook's acquisition of the ownership interests of the Selling Owners, and delete the Selling Owners from the license to reflect the proposed transfer. </P>
                <P>While the application contemplates that all of the Selling Owners will eventually transfer their respective interests in the facility to FPLE Seabrook, albeit not necessarily on the same closing date, the NRC is also considering approving the application such that in the event one or more Selling Owners do not or are unable to complete their transfers, the remaining Selling Owners will be authorized nonetheless to transfer their interests to FPLE Seabrook. </P>
                <P>Pursuant to 10 CFR 50.80, no license, or any right thereunder, shall be transferred, directly or indirectly, through transfer of control of the license, unless the Commission shall give its consent in writing. The Commission will approve an application for the transfer of a license, if the Commission determines that the proposed transferee is qualified to hold the license, and that the transfer is otherwise consistent with applicable provisions of law, regulations, and orders issued by the Commission pursuant thereto. </P>
                <P>Before issuance of the proposed conforming license amendment, the Commission will have made findings required by the Atomic Energy Act of 1954, as amended (the Act), and the Commission's regulations. </P>
                <P>As provided in 10 CFR 2.1315, unless otherwise determined by the Commission with regard to a specific application, the Commission has determined that any amendment to the license of a utilization facility which does no more than conform the license to reflect the transfer action involves no significant hazards consideration. No contrary determination has been made with respect to this specific license amendment application. In light of the generic determination reflected in 10 CFR 2.1315, no public comments with respect to significant hazards considerations are being solicited, notwithstanding the general comment procedures contained in 10 CFR 50.91. </P>
                <P>The filing of requests for hearing and petitions for leave to intervene, and written comments with regard to the license transfer application, are discussed below. </P>
                <P>By July 5, 2002, any person whose interest may be affected by the Commission's action on the application may request a hearing and, if not the applicant, may petition for leave to intervene in a hearing proceeding on the Commission's action. Requests for a hearing and petitions for leave to intervene should be filed in accordance with the Commission's rules of practice set forth in Subpart M, “Public Notification, Availability of Documents and Records, Hearing Requests and Procedures for Hearings on License Transfer Applications,” of 10 CFR part 2. In particular, such requests and petitions must comply with the requirements set forth in 10 CFR 2.1306, and should address the considerations contained in 10 CFR 2.1308(a). Untimely requests and petitions may be denied, as provided in 10 CFR 2.1308(b), unless good cause for failure to file on time is established. In addition, an untimely request or petition should address the factors that the Commission will also consider, in reviewing untimely requests or petitions, set forth in 10 CFR 2.1308(b)(1)-(2). </P>
                <P>
                    Requests for a hearing and petitions for leave to intervene should be served upon Mitchell S. Ross, Counsel for FPLE Seabrook, FPL Energy, LLC, Law Department, 700 Universe Boulevard, P.O. Box 14000, Juno Beach, FL 33408-0420, Phone: 561-691-7126, Fax: 561-691-7135, e-mail: 
                    <E T="03">Mitch_Ross@fpl.com;</E>
                      
                    <PRTPAGE P="40973"/>
                    and William J. Quinlan, Deputy General Counsel, Northeast Utilities, P.O. Box 270, Hartford, CT 06141, Phone: 860-665-3761, Fax: 860-665-5504, e-mail: 
                    <E T="03">quinlwj@nu.com</E>
                    ; the General Counsel, U.S. Nuclear Regulatory Commission, Washington, DC 20555 (e-mail address for filings regarding license transfer cases only: 
                    <E T="03">OGCLT@NRC.gov</E>
                    ); and the Secretary of the Commission, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemakings and Adjudications Staff, in accordance with 10 CFR 2.1313. 
                </P>
                <P>
                    The Commission will issue a notice or order granting or denying a hearing request or intervention petition, designating the issues for any hearing that will be held and designating the Presiding Officer. A notice granting a hearing will be published in the 
                    <E T="04">Federal Register</E>
                     and served on the parties to the hearing. 
                </P>
                <P>
                    As an alternative to requests for hearing and petitions to intervene, by July 15, 2002, persons may submit written comments regarding the license transfer application, as provided for in 10 CFR 2.1305. The Commission will consider and, if appropriate, respond to these comments, but such comments will not otherwise constitute part of the decisional record. Comments should be submitted to the Secretary, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, Attention: Rulemakings and Adjudications Staff, and should cite the publication date and page number of this 
                    <E T="04">Federal Register</E>
                     notice. 
                </P>
                <P>
                    For further details with respect to this action, see the application dated May 17, 2002, available for public inspection at the Commission's Public Document Room (PDR), located at One White Flint North, 11555 Rockville Pike (first floor), Rockville, Maryland. Publicly available records will be accessible electronically from the Agencywide Documents Access and Management Systems (ADAMS) Public Electronic Reading Room on the Internet at the NRC Web site, 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html</E>
                    . Persons who do not have access to ADAMS or who encounter problems in accessing the documents located in ADAMS, should contact the NRC PDR Reference staff by telephone at 1-800-397-4209, 301-415-4737 or by e-mail to 
                    <E T="03">pdr@nrc.gov</E>
                    . 
                </P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland this 5th day of June, 2002. </DATED>
                    <P>For the Nuclear Regulatory Commission. </P>
                    <NAME>Robert D. Starkey, </NAME>
                    <TITLE>Project Manager, Section 2, Project Directorate I, Division of Licensing Project Management, Office of Nuclear Reactor Regulation. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15089 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NUCLEAR REGULATORY COMMISSION </AGENCY>
                <SUBJECT>Advisory Committee on Reactor Safeguards, Meeting of the Subcommittee on Plant License Renewal; Notice of Meeting </SUBJECT>
                <P>The ACRS Subcommittee on Plant License Renewal will hold a meeting on July 9, 2002, Room T-2B3, 11545 Rockville Pike, Rockville, Maryland. </P>
                <P>The entire meeting will be open to public attendance. </P>
                <P>The agenda for the subject meeting shall be as follows: </P>
                <P>
                    <E T="03">Tuesday, July 9, 2002—8:30 a.m. until the conclusion of business</E>
                </P>
                <P>The Subcommittee will review the Virginia Electric and Power Company's (Dominion's) license renewal application for Surry Power Sation Units 1 and 2, and North Anna Power Station Units 1 and 2, and the associated Safety Evaluation Report with open items. The purpose of this meeting is to gather information, analyze relevant issues and facts, and to formulate proposed positions and actions, as appropriate, for deliberation by the full Committee. </P>
                <P>Oral statements may be presented by members of the public with the concurrence of the Subcommittee Chairman; written statements will be accepted and made available to the Committee. Electronic recordings will be permitted only during those portions of the meeting that are open to the public, and questions may be asked only by members of the Subcommittee, its consultants, and staff. Persons desiring to make oral statements should notify the Designated Federal Official or the cognizant ACRS staff engineer named below five days prior to the meeting, if possible, so that appropriate arrangements can be made. </P>
                <P>During the initial portion of the meeting, the Subcommittee, along with any of its consultants who may be present, may exchange preliminary views regarding matters to be considered during the balance of the meeting. </P>
                <P>The Subcommittee will then hear presentations by and hold discussions with representatives of the NRC staff, Dominion, and other interested persons regarding this review. </P>
                <P>Further information regarding topics to be discussed, whether the meeting has been canceled or rescheduled, and the Chairman's ruling on requests for the opportunity to present oral statements and the time allotted therefor can be obtained by contacting the Designated Federal Official, Mr. Sam Duraiswamy (telephone 301/415-7364) or the cognizant ACRS staff engineer, Mr. Timothy Kobetz (telephone 301/415-8716) between 7:30 a.m. and 4:30 p.m. (EDT). Persons planning to attend this meeting are urged to contact one of the above named individuals one or two working days prior to the meeting to be advised of any potential changes to the agenda that may have occurred. </P>
                <SIG>
                    <DATED>Dated: June 7, 2002. </DATED>
                    <NAME>Sher Bahadur, </NAME>
                    <TITLE>Associate Director for Technical Support ACRS/ACNW. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15087 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">PENSION BENEFIT GUARANTY CORPORATION </AGENCY>
                <SUBJECT>Required Interest Rate Assumption for Determining Variable-Rate Premium; Interest Assumptions for Multiemployer Plan Valuations Following Mass Withdrawal </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Pension Benefit Guaranty Corporation. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of interest rates and assumptions. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This notice informs the public of the interest rates and assumptions to be used under certain Pension Benefit Guaranty Corporation regulations. These rates and assumptions are published elsewhere (or can be derived from rates published elsewhere), but are collected and published in this notice for the convenience of the public. Interest rates are also published on the PBGC's Web site (
                        <E T="03">http://www.pbgc.gov</E>
                        ). 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The required interest rate for determining the variable-rate premium under part 4006 applies to premium payment years beginning in June 2002. The interest assumptions for performing multiemployer plan valuations following mass withdrawal under part 4281 apply to valuation dates occurring in July 2002. </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Harold J. Ashner, Assistant General Counsel, Office of the General Counsel, Pension Benefit Guaranty Corporation, 1200 K Street, NW., Washington, DC 20005, 202-326-4024. (TTY/TDD users may call the Federal relay service toll-
                        <PRTPAGE P="40974"/>
                        free at 1-800-877-8339 and ask to be connected to 202-326-4024.) 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Variable-Rate Premiums </HD>
                <P>Section 4006(a)(3)(E)(iii)(II) of the Employee Retirement Income Security Act of 1974 (ERISA) and § 4006.4(b)(1) of the PBGC's regulation on Premium Rates (29 CFR part 4006) prescribe use of an assumed interest rate (the “required interest rate”) in determining a single-employer plan's variable-rate premium. The required interest rate is the “applicable percentage” (currently 100 percent) of the annual yield on 30-year Treasury securities for the month preceding the beginning of the plan year for which premiums are being paid (the “premium payment year”). (Although the Treasury Department has ceased issuing 30-year securities, the Internal Revenue Service announces a surrogate yield figure each month—based on the 30-year Treasury bond maturing in February 2031—which the PBGC uses to determine the required interest rate.) </P>
                <P>The required interest rate to be used in determining variable-rate premiums for premium payment years beginning in June 2002 is 5.65 percent. </P>
                <P>The following table lists the required interest rates to be used in determining variable-rate premiums for premium payment years beginning between July 2001 and June 2002. </P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s40,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">For premium payment years beginning in— </CHED>
                        <CHED H="1">the required interest rate is— </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">July 2001 </ENT>
                        <ENT>4.82 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">August 2001 </ENT>
                        <ENT>4.77 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">September 2001 </ENT>
                        <ENT>4.66 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">October 2001 </ENT>
                        <ENT>4.66 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">November 2001 </ENT>
                        <ENT>4.52 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">December 2001 </ENT>
                        <ENT>4.35 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">January 2002 </ENT>
                        <ENT>5.48 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">February 2002 </ENT>
                        <ENT>5.45 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">March 2002 </ENT>
                        <ENT>5.40 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April 2002 </ENT>
                        <ENT>5.71 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">May 2002 </ENT>
                        <ENT>5.68 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">June 2002 </ENT>
                        <ENT>5.65 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Multiemployer Plan Valuations Following Mass Withdrawal </HD>
                <P>
                    The PBGC's regulation on Duties of Plan Sponsor Following Mass Withdrawal (29 CFR part 4281) prescribes the use of interest assumptions under the PBGC's regulation on Allocation of Assets in Single-Employer Plans (29 CFR part 4044). The interest assumptions applicable to valuation dates in July 2002 under part 4044 are contained in an amendment to part 4044 published elsewhere in today's 
                    <E T="04">Federal Register</E>
                    . Tables showing the assumptions applicable to prior periods are codified in appendix B to 29 CFR part 4044. 
                </P>
                <SIG>
                    <P>Issued in Washington, DC, on this 10th day of June, 2002. </P>
                    <NAME>Steven A. Kandarian, </NAME>
                    <TITLE>Executive Director, Pension Benefit Guaranty Corporation. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15039 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7708-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">OFFICE OF PERSONNEL MANAGEMENT </AGENCY>
                <DEPDOC>[SF 3102] </DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request for Reclearance of a Revised Information Collection </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Personnel Management. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 (Public Law 104-13, May 22, 1995), this notice announces that the Office of Personnel Management has submitted to the Office of Management and Budget a request for reclearance of a revised information collection. SF 3102, Designation of Beneficiary—(FERS), is used by an employee or an annuitant covered under the Federal Employees Retirement System to designate a beneficiary to receive any lump sum due in the event of his/her death. </P>
                    <P>Approximately 2,037 SF 3102 forms are completed annually. Each form takes approximately 15 minutes to complete. The annual estimated burden is 509.25 hours. </P>
                    <P>
                        For copies of this proposal, contact Mary Beth Smith-Toomey at (202) 606-8358, FAX 202-418-3251 or via email at 
                        <E T="03">mbtoomey@opm.gov.</E>
                         Please include a mailing address with your request. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this proposal should be received on or before July 15, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send or deliver comments to—</P>
                    <FP SOURCE="FP-1">Lawrence P. Holman, Acting Chief, FERS Division, Retirement and Insurance Service, U.S. Office of Personnel Management, 1900 E Street, NW., Room 3313, Washington, DC 20415, and </FP>
                    <FP SOURCE="FP-1">Joseph Lackey, OPM Desk Officer, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, NW, Room 10235, Washington, DC 20503. </FP>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR INFORMATION REGARDING ADMINISTRATIVE COORDINATION—CONTACT: </HD>
                    <P>Cyrus S. Benson, Team Leader, Desktop Publishing and Printing Team, Budget &amp; Administrative Services Division, (202) 606-0623. </P>
                    <SIG>
                        <FP>U.S. Office of Personnel Management. </FP>
                        <NAME>Kay Coles James, </NAME>
                        <TITLE>Director. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15010 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6325-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">OFFICE OF PERSONNEL MANAGEMENT </AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request for Revised Information Collection: OPM Form 1203-AW, Occupational Questionnaire OPM Form 1203-AW, OPM Form 1203-FX, Occupational Questionnaire OPM Form 1203-FX, and OPM Form 1203-EZ, Occupational Questionnaire OPM Form 1203-EZ</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of Personnel Management. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 (Public Law 104-13, May 22, 1995), this notice announces that the Office of Personnel Management (OPM) submitted to the Office of Management and Budget a request for review of a revised information collection for Occupational Questionnaire (OPM Forms 1203-AW, 1203-FX and 1203-EZ). The Occupational Questionnaire is an optical scan form designed to collect applicant information and qualifications in a format suitable for automated processing and to create applicant records for an automated examining system. Each version of this form contains a unique scan form identifier in the upper left-hand corner for the scanning equipment to recognize which version is being used. The 1203 series was commonly referred to as the Qualifications and Availability Form C. OPM has re-titled the series as Occupational Questionnaire, to fit a more generic need. OPM uses these forms to carry out its responsibility for open competitive examining for admission to the competitive service in accordance with section 3304, of title 5, United States Code. </P>
                    <P>
                        OPM Form 1203-AW is a scan form that contains a unique control number pre-printed within the footer of the form that is scanned in along with the applicant's information. It is OPM's intention to phase out this version of the Occupational Questionnaire during fiscal year 2002. Applicants will be asked to use OPM Form1203-FX or 1203-EZ in its place. OPM will 
                        <PRTPAGE P="40975"/>
                        officially cancel Form 1203-AW at that time. 
                    </P>
                    <P>OPM Form 1203-FX is a seven page version of the Occupational Questionnaire that allows the applicant to transmit via facsimile. This version does not contain a unique control number pre-printed within the footer of the form. However, this revised version will be phased in to allow continued acceptance of the existing version dated October 1998, making the existing version still usable. (See the comments identified below for what changes were made.) </P>
                    <P>OPM Form 1203-EZ is a three page version that is shorter and is transmittable via facsimile. This version does not contain a unique control number pre-printed within the footer of the form. </P>
                    <P>
                        A comment request for these forms was published in the 
                        <E T="04">Federal Register</E>
                         on August 6, 2001 [FR Doc. 01-19551]. During the initial 60-day comment request period, OPM received no comments. 
                    </P>
                    <P>OPM has revised the Occupational Questionnaire to include the following: (1) Updated the Privacy Act and Public Burden Statements; (2) slightly re-designed the forms for scanning technology; (3) improved the sections that allow overseas applicants to enter foreign addresses and phone numbers; (4) removed the requirement for the applicant to sign and date (since this is a scan form that only recognizes certain characters written in blocks and filled-in bubbles); (5) added “Date of Birth” to all versions; (6) updated the Veterans' Preference section; and (7) changed the title of this series from “Qualifications and Availability Form” (commonly referred as the “Form C”) to “Occupational Questionnaire'. </P>
                    <P>Upon clearance from the Office of Management and Budget, the Occupational Questionnaire will be available via OPM's web site and OPM's USAJOBS web site. The form will be made available electronically as a fillable Adobe Acrobat Reader (.PDF) file and fillable on-line when applying on OPM's USAJOBS web site (when applicable). A transmittal memo from OPM will be sent to all Federal agency personnel directors via the Human Resources Management Council, announcing the approved, revised form and where/how to obtain it. </P>
                    <P>
                        For copies of this proposal, contact Mary Beth Smith-Toomey on 202-606-8358, fax at 202-418-3251, or e-mail at 
                        <E T="03">mbtoomey@opm.gov.</E>
                         Please include a mailing address with your request.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this proposal should be received on or before July 15, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Send or deliver comments to— </P>
                    <FP SOURCE="FP-1">
                        U.S. Office of Personnel Management, Employment Service, ATTN: Rob Timmins, 1900 E Street, NW., Room 1425, Washington, DC 20415-9820, E-mail: 
                        <E T="03">ratimmin@opm.gov,</E>
                         and 
                    </FP>
                    <FP SOURCE="FP-1">Office of Management &amp; Budget, Office of Information &amp; Regulatory Affairs, ATTN: Joseph Lackey, OPM Desk Officer, New Executive Office Building, NW., Room 10235, Washington, DC 20503. </FP>
                </ADD>
                <SIG>
                    <FP>Office of Personnel Management. </FP>
                    <NAME>Kay Coles James, </NAME>
                    <TITLE>Director. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15011 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6325-38-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION </AGENCY>
                <DEPDOC>[Release No. 34-46056; File No. SR-NASD-2002-59] </DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Notice of Filing of Proposed Rule Change by the National Association of Securities Dealers, Inc. Relating to a New Trade Report Modifier to be Attached to Trades Whose Prices Exceed Certain Parameters </SUBJECT>
                <DATE>June 10, 2002. </DATE>
                <P>
                    Pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     notice is hereby given that on April 29, 2002, the National Association of Securities Dealers, Inc. (“NASD” or “Association”), through its subsidiary, the Nasdaq Stock Market, Inc. (“Nasdaq”), filed with the Securities and Exchange Commission (“Commission”) the proposed rule change as described in Items I, II, and III below, which Items have been prepared by Nasdaq. The Commission is publishing this notice to solicit comments on the proposed rule change from interested persons. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4. 
                    </P>
                </FTNT>
                <HD SOURCE="HD1">I. Self-Regulatory Organization's Statement of the Terms of Substance of the Proposed Rule Change </HD>
                <P>Nasdaq is proposing to create a new trade report modifier to be attached to trades whose prices exceed certain parameters. Under the proposed rule change, members would not have the ability to append this modifier to trade reports. Nasdaq proposes that only Nasdaq staff and Nasdaq systems would append this modifier, and only for transactions in Nasdaq National Market System, SmallCap Market, and OTC Bulletin Board securities. </P>
                <HD SOURCE="HD1">II. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <P>In its filing with the Commission, Nasdaq included statements concerning the purpose of and basis for the proposed rule change and discussed any comments it received on the proposed rule change. The text of these statements may be examined at the places specified in Item IV below. Nasdaq has prepared summaries, set forth in Sections A, B, and C below, of the most significant aspects of such statements. </P>
                <HD SOURCE="HD2">A. Self-Regulatory Organization's Statement of the Purpose of, and Statutory Basis for, the Proposed Rule Change </HD>
                <HD SOURCE="HD3">1. Purpose </HD>
                <P>Trades reported to Nasdaq using the Automated Confirmation Transaction (“ACT”) Service are subject to procedures that identify trades executed at prices away from the current market. This process helps to ensure a fair and orderly market by preventing such trades from being disseminated to the public as last sale reports and/or by detecting trades that are reported at erroneous prices. </P>
                <P>
                    The process differs slightly depending on whether a trade is executed using a Nasdaq system, which then automatically reports the trade to ACT (
                    <E T="03">e.g.,</E>
                     SelectNet), or the trade is submitted to ACT directly by a member. ACT rejects a trade that is submitted directly by a member if the price reported is outside established parameters. The member has an opportunity to resubmit the trade, which then will be subject to a different set of parameters. If the price is rejected after this second process, the member must call Nasdaq's MarketWatch Department to explain why the execution price was so far away from the current market. If the MarketWatch staff determines, on the basis of its conversation with the member, that there is an adequate rationale for such price, the staff would submit the trade to ACT.
                    <SU>3</SU>
                    <FTREF/>
                     In such circumstances, the trade is normally being reported more than 90 seconds after the trade was 
                    <PRTPAGE P="40976"/>
                    executed, and so the MarketWatch staff would report the trade with the .SLD modifier attached, which indicates a late trade report.
                    <SU>4</SU>
                    <FTREF/>
                     Trades reported with a .SLD modifier are not included in the last sale calculation, but are included in the calculation of the high and low price for the security. 
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         If the MarketWatch staff believes the price would be misleading to the market, the trade report would be submitted for clearing purposes only. Nasdaq believes that the number of instances in which the staff submits the report only for clearing purposes is very limited. The staff estimates that this occurs less than 10 times a year. In addition, the staff can refer the transaction to NASD Regulation for further investigation. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         NASD rules require that trades be marked late, using the .SLD modifier, if they are reported more than 90 seconds after execution. 
                        <E T="03">See e.g.,</E>
                         NASD Rule 4632. 
                    </P>
                </FTNT>
                <P>Trades executed using Nasdaq systems, however, are subject to a different process due to the manner in which such trades are transmitted to ACT. The information passed to ACT from a Nasdaq system does not include the exact location, or terminal, within a member from which an order/execution emanates. Therefore, such trades are not subject to the second validation process which allows members to resubmit a trade report after it is rejected initially, since the exact location within a member to which a reject message can be sent is unknown. To compensate for this difference and to prevent such trades from being included in the last sale calculation, Nasdaq automatically attaches the .SLD modifier to any trades executed using a Nasdaq system whose prices exceed the initial parameters. Nasdaq also includes another modifier with these trade reports to indicate that the .SLD modifier has been attached by a Nasdaq system. This other modifier ensures that members would not be cited for late trade reporting on the basis of these trades. </P>
                <P>
                    Nasdaq believes that the process described above has worked well in promoting a fair and orderly market because it has prevented certain anomalous prices from being included in the last sale calculation, which is used for many purposes including as a measure of the current market for a security; a determinant of the execution price of certain types of orders (
                    <E T="03">e.g.,</E>
                     market on close orders); and in determining index values. Nasdaq believes this process has helped provide more accurate information about the prices at which individual securities are trading, and for that matter, the market, or a segment of the market, if such securities are components of indices designed to measure the entire market or a particular segment. 
                </P>
                <P>However, Nasdaq has identified a means of further improving the current process. The .SLD modifier prevents a trade report from being included in the last sale calculation, but it does not prevent such a report from being included in the calculation of the high and low price of a security. As such, a trade that has been excluded from the last sale calculation because its price exceeds the parameters, nevertheless, may set the high or low price for a security. Nasdaq believes that these trades should not establish the high or low price for a security because the high and low prices are also used as a measure of a security's performance, or could trigger certain actions. </P>
                <P>
                    Therefore, Nasdaq is proposing to create a new modifier that would exclude such trades from the high/low calculations, as well as the last sale calculation.
                    <SU>5</SU>
                    <FTREF/>
                     This new modifier tentatively would be known as the “Out of Range,” or .OR , modifier and would be used instead of the .SLD modifier in the circumstances described above.
                    <SU>6</SU>
                    <FTREF/>
                     For example, if a trade executed using SelectNet exceeds the price parameters, ACT automatically would append the .OR modifier to the trade report instead of the .SLD modifier. Similarly, the Nasdaq MarketWatch staff would append the .OR modifier to reports they submit. Nasdaq believes that the number of trade reports that contain the .SLD modifier either attached by ACT or the Nasdaq MarketWatch staff because the price is outside the parameters is very small.
                    <SU>7</SU>
                    <FTREF/>
                     Nasdaq believes that the current proposal to create a new modifier would not affect this number since all that is being changed is the modifier that is being attached, and Nasdaq is not proposing to modify the price parameters. 
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         Nasdaq recognizes that trades whose prices exceed the price parameters nevertheless may be valid transactions that the parties want to settle. As such, these trades are transmitted to The Depository Trust and Clearing Corporation for clearing and settlement. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         As discussed earlier, members will not have the ability to append the .OR modifier to trade reports. Only Nasdaq staff and Nasdaq systems will append this modifier, and only for transactions in Nasdaq National Market System, SmallCap Market, and OTC Bulletin Board securities. 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Nasdaq estimates that, on a daily average, less than .002% of trades executed on Nasdaq are reported with the .SLD modifier due to the trade being executed at a price that exceeds the price parameters. 
                    </P>
                </FTNT>
                <P>Nasdaq recognizes that, in certain circumstances, members may believe that they have executed a trade at a price that provides valuable information to the market, even though the price is outside the parameters. To ensure that such trades are not inappropriately withheld from the last sale and high/low calculations, members would be able to contact the Nasdaq MarketWatch staff to request that the .OR modifier be removed from the trade report. The member must explain the facts and circumstances surrounding the trade and why the price was reasonable, as measured against the market at the time of execution. If the MarketWatch staff agrees with the explanation, it can remove the .OR modifier from the trade report. </P>
                <P>The process for developing and implementing the modifier, which will include testing with market data vendors, will take several months. Nasdaq will continue to utilize the .SLD modifier in the manner described until the new modifier can be implemented. </P>
                <HD SOURCE="HD3">2. Statutory Basis </HD>
                <P>
                    Nasdaq believes the proposed rule change is consistent with the provisions of sections 15A(b)(2) of the Act 
                    <SU>8</SU>
                    <FTREF/>
                     in that the proposal is designed for the NASD to be organized and have the capacity to carry out the purposes of the Act. Nasdaq also believes the proposal is consistent with section 15A(b)(6) of the Act 
                    <SU>9</SU>
                    <FTREF/>
                     in that it is designed to protect investors and the public interest. In addition, Nasdaq believes that its proposal is consistent with the NASD's obligations under these provisions of the Act because it will result in the public dissemination of information that more accurately reflects the current trading in a particular security. Furthermore, Nasdaq believes that, to the extent a security is a component of an index, the index will more accurately reflect the value of the market, or segment of the market, that the index is designed to measure. Nasdaq believes that the corresponding result should be trades, or other actions, executed at prices more reflective of the current market when the price of an execution, or other action, is based on the last sale, the high price or low price of a security, or the value of an index. 
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78o-3(b)(2). 
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78o-3(b)(6). 
                    </P>
                </FTNT>
                <P>
                    Nasdaq also believes the proposal is consistent with the NASD's obligations under its transaction reporting plan for Nasdaq National Market System securities approved by the Commission.
                    <SU>10</SU>
                    <FTREF/>
                     In this plan, the NASD committed to validate prices for reasonableness as measured against previous trades in a security. 
                </P>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         Securities Exchange Act Release No. 18590 (March 24, 1982), 47 FR 13617 (March 31, 1982). 
                    </P>
                </FTNT>
                <HD SOURCE="HD2">B. Self-Regulatory Organization's Statement on Burden on Competition </HD>
                <P>
                    Nasdaq does not believe that the proposed rule change will impose any burden on competition that is not necessary or appropriate in furtherance of the purposes of the Act. 
                    <PRTPAGE P="40977"/>
                </P>
                <HD SOURCE="HD2">C. Self-Regulatory Organization's Statement on Comments on the Proposed Rule Change Received From Members, Participants or Others </HD>
                <P>No written comments were solicited or received with respect to the proposed rule change. </P>
                <HD SOURCE="HD1">III. Date of Effectiveness of the Proposed Rule Change and Timing for Commission Action </HD>
                <P>
                    Within 35 days of the date of publication of this notice in the 
                    <E T="04">Federal Register</E>
                     or within such longer period (i) as the Commission may designate up to 90 days of such date if it finds such longer period to be appropriate and publishes its reasons for so finding or (ii) as to which Nasdaq consents, the Commission will: 
                </P>
                <P>(A) By order approve such proposed rule change, or </P>
                <P>(B) Institute proceedings to determine whether the proposed rule change should be disapproved. </P>
                <HD SOURCE="HD1">IV. Solicitation of Comments </HD>
                <P>Interested persons are invited to submit written data, views and arguments concerning the foregoing, including whether the proposed rule change is consistent with the Act. Persons making written submissions should file six copies thereof with the Secretary, Securities and Exchange Commission, 450 Fifth Street, NW., Washington, DC 20549-0609. Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for inspection and copying in the Commission's Public Reference Room. Copies of such filing will also be available for inspection and copying at the principal office of the NASD. All submissions should refer to File No. SR-NASD-2002-59 and should be submitted by July 5, 2002. </P>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             17 CFR 200.30-3(a)(12). 
                        </P>
                    </FTNT>
                    <NAME>Jill M. Peterson, </NAME>
                    <TITLE>Assistant Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15076 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 8010-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">OFFICE OF THE UNITED STATES TRADE REPRESENTATIVE</AGENCY>
                <DEPDOC>[Docket No. WTO/DS-245]</DEPDOC>
                <SUBJECT>WTO Dispute Settlement Proceeding Regarding Japanese Measures Affecting the Importation of Apples</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the United States Trade Representative.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice; request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Office of the United States Trade Representative (USTR) is providing notice that on June 3, 2002, at the request of the United States, the Dispute Settlement Body (DSB) of the World Trade Organization (WTO) established a dispute settlement panel under the Marrakesh Agreement Establishing the WTO to examine measures imposed by Japan restricting the importation of U.S. apples in connection with fire blight or the fire blight disease-causing organism, 
                        <E T="03">Erwinia amylovora.</E>
                         The United States alleges that these measures are inconsistent with the obligations of Japan under the General Agreement on Tariffs and Trade 1994, the Agreement on the Application of Sanitary and Phytosanitary Measures, and the Agreement on Agriculture. USTR invites written comments from the public concerning the issues raised in this dispute.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Although USTR will accept any comments received during the course of the dispute settlement proceedings, comments should be submitted on or before June 30, 2002, to be assured of timely consideration by USTR.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments should be submitted (i) electronically to 
                        <E T="03">japanapples@ustr.gov</E>
                         or (ii) by mail to Sandy McKinzy, Litigation Assistant, Office of Monitoring and Enforcement, Attn: Japan—Measures Affecting the Importation of Apples, Office of the United States Trade Representative, 600 17th Street, NW, Washington, DC 20508, with a confirmation copy sent electronically or by fax to (202) 395-3640.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Juan A. Milla
                        <AC T="1"/>
                        n, Assistant General Counsel, Office of the United States Trade Representatives, 600 17th Street, NW., Washington, DC, (202) 395-3581.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Section 127(b) of the Uruguay Round Agreements Act (URAA) (19 U.S.C. 3537(b)(1)) requires that notice and opportunity for comment be provided after the United States submits or receives a request for the establishment of a WTO dispute settlement panel. USTR is providing notice that on June 3, 2002, at the request of the United States, a WTO dispute settlement panel was established to examine measures imposed by Japan restricting the importation of U.S. apples in connection with fire blight or the fire blight disease-causing organism, 
                    <E T="03">Erwinia amylovora.</E>
                     The panel, which will hold its meetings in Geneva, Switzerland, is expected to issue a report on its findings and recommendations within six to nine months after it is established.
                </P>
                <HD SOURCE="HD1">Major Issues Raised by the United States</HD>
                <P>
                    The United States has requested WTO consultations with Japan regarding its restrictions on the importation of U.S. apples in connection with fire blight or the fire blight disease-causing organism, 
                    <E T="03">Erwinia amylovora.</E>
                     These restrictions include, 
                    <E T="03">inter alia,</E>
                     the prohibition of imported apples from U.S. states other than Washington or Oregon; the prohibition of imported apples from orchards in which any fire blight is detected; the prohibition of imported apples from any orchard (whether or not it is free of fire blight) should fire blight be detected within a 500 meter buffer zone surrounding such orchard; the requirement that export orchards be inspected three times yearly (at blossom, fruitlet, and harvest stages) for the presence of fire blight for purposes of applying the above-mentioned prohibitions; a post-harvest surface treatment of exported apples with chlorine; production requirements, such as chlorine treatment of containers for harvesting and chlorine treatment of the packing line; and the post-harvest separation of apples for export to Japan from those apples destined for other destinations.
                </P>
                <P>The United States contends that Japan's measures are inconsistent with the obligations of Japan under Article XI of the General Agreement on Tariffs and Trade 1994, Article 4.2 of the Agreement on Agriculture, and Articles 2.2, 2.3, 5.1, 5.2, 5.3, 5.5, 5.6, 6.1, 6.2, and 7 and paragraphs 5, 6, and 8 of Annex B of the Agreement on the Application of Sanitary and Phytosanitary Measures. Japan's measures also appear to nullify or impair the benefits accruing to the United States directly or indirectly under the cited agreements.</P>
                <HD SOURCE="HD1">Public Comment: Requirements for Submissions</HD>
                <P>
                    Interested persons are invited to submit written comments concerning the issues raised in the dispute. Comments must be in English. 
                    <PRTPAGE P="40978"/>
                    Commenters should send either one copy by U.S. mail, first class, postage, prepaid, to Sandy McKinzy at the address listed above, or transmit a copy electronically to 
                    <E T="03">japanapples@ustr.gov.</E>
                     For documents sent by U.S. mail, USTR requests that the submitter provide a confirmation copy, either electronically or by fax to (202) 395-3640. USTR encourages the submission of documents in Adobe PDF format, as attachments to an electronic mail.
                </P>
                <P>A person requesting that information contained in a comment submitted by that person be treated as confidential business information must certify that such information is business confidential and would not customarily be released to the public by the commenter. Confidential business information must be clearly marked BUSINESS CONFIDENTIAL in a contrasting color ink at the top of each page of each copy. For any document containing business confidential information submitted by electronic transmission, the file name of the business confidential version should begin with the characters “BC”, and the file name of the public version should begin with the characters “P”. The “P” or “BC” should be followed by the name of the commenter. Interested persons who make submissions by electronic mail should not provide separate cover letters; information that might appear in a cover letter should be included in the submission itself. Similarly, to the extent possible, any attachments to the submission should be included in the same file as the submission itself and not as separate files.</P>
                <P>Information or advice contained in a comment submitted, other than business confidential information, may be determined by USTR to be confidential in accordance with section 135(g)(2)of the Trade Act of 1974 (19 U.S.C. 2155(g)(2)). If the submitter believes that information or advice may qualify as such, the submitter—</P>
                <P>(1) Must so designate the information or advice;</P>
                <P>(2) Must clearly mark the material as SUBMITTED IN CONFIDENCE in a contrasting color ink at the top of each page of each copy; and </P>
                <P>(3) Is encouraged to provide a non-confidential summary of the information or advice.</P>
                <P>Pursuant to section 127(e) of the URAA (19 U.S.C. 3537(e)), USTR will maintain a file on the dispute settlement proceeding, accessible to the public, in the USTR Reading Room: Office of the United States Trade Representative, 1724 F Street, NW, Washington, DC 20508. The public file will include a listing of any comments received by USTR from the public with respect to the dispute; if a dispute settlement panel is convened, the U.S. submissions to that panel, the submissions, or non-confidential summaries of submissions, to the panel received from other participants in the dispute, as well as the report of the panel; and, if applicable, the report of the Appellate Body. An appointment to review the public file (Docket WTO/DS-245, Japan—Measures Affecting the Importation of Apples) may be made by calling Brenda Webb, (202) 395-6186. The USTR Reading Room is open to the public from 9:30 a.m. to 12 noon and 1 p.m. to 4 p.m., Monday through Friday.</P>
                <SIG>
                    <NAME>Bruce R. Hirsh,</NAME>
                    <TITLE>Acting Assistant United States Trade Representative for Monitoring and Enforcement.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15078  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3190-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Highway Administration</SUBAGY>
                <SUBJECT>Environmental Impact Statement: Clinton County, NY</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration (FHWA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P> Notice of intent.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FHWA is issuing this notice to advise the public that an environmental impact statement will be prepared for a proposed highway project in Clinton County, New York.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Robert Arnold, Division Administrator, Federal Highway Administration, New York Division, Leo W. O'Brien Federal Building, 7th Floor, Clinton Avenue and North Pearl Street, Albany, New York 12207, Telephone: (518) 431-4127; 
                        <E T="03">or</E>
                         Albert H. Rascoe, Highway Superintendent, Clinton County Highway Department, 736 Route 3, Plattsburgh, NY, 12901, Telephone: (518) 565-4626; 
                        <E T="03">or</E>
                         R. Carey Babyak, Regional Director, New York State Department of Transportation, Region 7,317 Washington Street, Watertown, NY13601, Telephone: (315) 785-2333.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> The FHWA, in cooperation with the New York State Department of Transportation (NYSDOT) and the Clinton County Highway Department will prepare an environmental impact statement (EIS) on a proposal to improve a portion of County Route 57 and construct a new section of County Route 57 in Clinton County, New York. The proposed project will rehabilitate County Route 57 for a distance of about 1 mile (1.6 km) from its intersection with US Route 9 to its' separation into East &amp; West roads (perimeter road) and the construction of a new roadway from the separation down the center of the peninsula to the Lake Champlain Ferries Terminal (Grand Isle Ferry) at the southern end of the peninsula for a distance of about 3.3 miles (5.3 km). Improvements to the corridor are considered necessary to reduce traffic volumes on the existing East &amp; West roads, improve safety, and address geometric deficiencies and incompatible usage of the existing Cumberland Head Road (County Route 57).</P>
                <P>Alternatives given consideration include (1) taking no action; (2) widening and improving the horizontal and vertical geometry of the existing two-lane road; and (3) constructing a new two-lane limited access highway in a new location. Incorporated into and studied with the various build alternatives will be design variations of grade, intersecting roadways, and alignment.</P>
                <P>Letters describing the proposed action and soliciting comments have been sent to appropriate Federal, State, and local agencies, and to private organizations and citizens who have previously expressed interest in this proposal. Public information meetings were held in the Town of Plattsburgh on April 4 and October 17, 2000. In addition, a public hearing will be held. Public Notice was given of the time and place of those meetings and will be given of the time and place of the hearing. The draft EIS will be available for public and agency review and comment. No formal NEPA scoping meeting is planned at this time.</P>
                <P>To ensure that the full range of issues related to this proposed action are addressed and all significant issues identified, comments and suggestions are invited from all interested parties. Comments or questions concerning this proposed action and the EIS should be directed to the Clinton County Highway Department, the NYSDOT or FHWA at the addresses provided above.</P>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program Number 20.205, Highway Planning and Construction. The regulations implementing Executive Order 12372 regarding intergovernmental consultation of Federal programs and activities apply to this program.)</FP>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>23 U.S.C. 315; 23 CFR 771.123</P>
                    </AUTH>
                </EXTRACT>
                <SIG>
                    <PRTPAGE P="40979"/>
                    <DATED>Issued on May 30, 2002.</DATED>
                    <NAME>Douglas P. Conlan,</NAME>
                    <TITLE>District Operations Engineer, Federal Highway Administration, Albany, New York.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15086  Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-22-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Highway Administration</SUBAGY>
                <SUBJECT>Environmental Impact Statement: Oakland County, MI</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Highway Administration (FHWA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FHWA is issuing this notice to advise the public that an environmental impact statement will be prepared for the I-75 Oakland County Planning/Environmental Study.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        James A. Kirschensteiner, Assistant Division Administrator, Federal Highway Administration, 315 West Allegan Street, Room 207, Lansing, Michigan 48933, Telephone: (517) 702-1835, Fax: 377-1804, email 
                        <E T="03">james.kirschensteiner@fhwa.dot.gov</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The FHWA, in cooperation with the Michigan Department of Transportation, will prepare an environmental impact statement (EIS) on a proposal to add an additional through travel land in each direction on I-75 between 8-Mile Road and M-59 to bring the total number of through travel lanes to four in each direction, together with other improvements. Improvements are considered necessary to provide for improved travel on I-75, which is already highly congested through much of the day. The EIS will include the evaluation of recommendations from the previous I-75 Corridor Feasibility Study (November 2000), including a through analysis of transit alternatives utilizing the Southeast Michigan Council of governments (SEMCOG) Transit Vision and the 1999 Southeast Michigan High Occupancy Vehicle (HOV) Feasibility Study. The Feasibility Study recommended the addition of a fourth lane in those areas where it is needed to provide four through lanes, improving several interchanges, and implementing intelligent transportation systems (ITS) throughout the corridor.</P>
                <P>Alternatives under consideration include (1) taking no action; (2) providing mass transit; (3) implementing transportation system management and/or transportation demand management techniques; (4) developing the proposed lanes for use either all day or during a portion of the day by high occupancy vehicles (carpools, vanpool, and buses) only; and (5) developing normal, unrestricted freeway travel lanes.</P>
                <P>Letters describing the proposed action and soliciting comments will be sent to appropriate federal, state, and local agencies, and to private organizations and citizens who have previously expressed or are known to have an interest in this proposal. Five rounds of public meetings were held during the Feasibility Study phase during 1999 and 2000. Additional meetings and a public hearing are planned. Public notice will be given of the time and place of the  hearing(s). The draft EIS will be available for public and agency review and comment prior to the public hearing. NO formal scoping meeting is planned at this time.</P>
                <P>To ensure that the full range of issues related to this proposed action are addressed and all significant issues identified, comments and suggestions are invited from all interested parties. Comments or questions concerning this proposed action and the EIS should be directed to the FHWA at the address provided above.</P>
                <SIG>
                    <FP>(Catalog of Federal Domestic Assistance Program Number 20.205, Highway Planning and Construction. The regulations implementing Executive Order 12372 regarding intergovernmental consultation of Federal programs and activities apply to this program.)</FP>
                    <DATED>Issued on May 30, 2002</DATED>
                    <NAME>James J. Steele,</NAME>
                    <TITLE>Division Administrator Lansing, Michigan.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15085 Filed 6-13-02; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-22-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <DEPDOC>[STB Finance Docket No. 34206] </DEPDOC>
                <SUBJECT>Permian Basin Railways, Inc.—Continuance in Control Exemption—West Texas and Lubbock Railway Company, Inc. and Austin &amp; Northwestern Railroad Company, Inc. </SUBJECT>
                <P>
                    Permian Basin Railways, Inc. (Permian), a noncarrier holding company, has filed a verified notice of exemption to (1) acquire control through stock purchase of Austin &amp; Northwestern Railroad Company, Inc. (Austin),
                    <SU>1</SU>
                    <FTREF/>
                     a Class III rail carrier, and (2) continue in control of Austin and West Texas and Lubbock Railway Company, Inc. (Railway), upon Railway's becoming a Class III railroad. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         
                        <E T="03">See Austin &amp; Northwestern Railroad Company, Inc.—Acquisition and Operation Exemption-Missouri Pacific Railroad Company,</E>
                         Finance Docket No. 31444 (ICC served May 22, 1989).
                    </P>
                </FTNT>
                <P>This transaction was scheduled to be consummated on or after the May 24, 2002 effective date of the exemption, 7 days after the exemption was filed. </P>
                <P>
                    This transaction is related to STB Docket No. 34205, 
                    <E T="03">West Texas and Lubbock Railway Company, Inc.—Acquisition and Operation Exemption—West Texas Lubbock Railroad Company, Inc.,</E>
                     wherein Railway seeks to acquire and operate approximately 107 miles of rail line by lease (with a future purchase option) and assumption of trackage rights from West Texas Lubbock Railroad Company, Inc. 
                </P>
                <P>Permian states that: (i) The railroads will not connect with each other or any railroads in their corporate family; (ii) the continuance in control is not part of a series of anticipated transactions that would connect the railroads with each other or any railroad in their corporate family; and (iii) the transaction does not involve a Class I carrier. </P>
                <FP>
                    Therefore, the transaction is exempt from the prior approval requirements of 49 U.S.C. 11323. 
                    <E T="03">See</E>
                     49 CFR 1180.2(d)(2). 
                </FP>
                <P>Under 49 U.S.C. 10502(g), the Board may not use its exemption authority to relieve a rail carrier of its statutory obligation to protect the interests of its employees. Section 11326(c), however, does not provide for labor protection for transactions under sections 11324 and 11325 that involve only Class III rail carriers. Because this transaction involves Class III rail carriers only, the Board, under the statute, may not impose labor protective conditions for this transaction. </P>
                <P>
                    If the notice contains false or misleading information, the exemption is void 
                    <E T="03">ab initio.</E>
                     Petitions to revoke the exemption under 49 U.S.C. 10502(d) may be filed at any time. The filing of a petition to revoke will not automatically stay the transaction. 
                </P>
                <P>An original and 10 copies of all pleadings, referring to STB Finance Docket No. 34206, must be filed with the Surface Transportation Board, Case Control Unit, 1925 K Street, NW., Washington, DC 20423-0001. In addition, a copy of each pleading must be served on John D. Heffner, 555 12th Street, NW., Suite 950N, Washington, DC 20004. </P>
                <P>
                    Boards decisions and notices are available on our website at “
                    <E T="03">www.stb.dot.gov.</E>
                    ” 
                </P>
                <SIG>
                    <DATED>Decided: June 7, 2002. </DATED>
                    <PRTPAGE P="40980"/>
                    <P>By the Board, David M. Konschnik, Director, Office of Proceedings. </P>
                    <NAME>Vernon A. Williams, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-14952 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4915-00-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <DEPDOC>[STB Finance Docket No. 34205] </DEPDOC>
                <SUBJECT>West Texas and Lubbock Railway Company, Inc.—Acquisition and Operation Exemption—West Texas and Lubbock Railroad Company, Inc. </SUBJECT>
                <P>
                    West Texas and Lubbock Railway Company, Inc. (Railway), a noncarrier, has filed a verified notice of exemption under 49 CFR 1150.31 to acquire by lease (with a future purchase option) and operate two rail lines owned by the West Texas and Lubbock Railroad Company, Inc. (Railroad): (1) Between milepost 06.3 on the outskirts of Lubbock and the end of the line at milepost 63.8 at Seagraves; and (2) between milepost 3.2 at Lubbock and milepost 38.9 at Whiteface. In addition, Railway will acquire by assignment approximately 5 miles of trackage rights which Railroad presently holds over The Burlington and Northern and Santa Fe Railway Company (BNSF) between BNSF milepost 83.6 at Broadview and BNSF milepost 88.6 at Canyon Junction in the vicinity of Lubbock. These trackage rights shall be used for the purpose of interchange only. The total trackage involved is approximately 107 miles.
                    <SU>1</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Due to a track relocation project, the mileposts do not accurately reflect the actual length of the rail line.
                    </P>
                </FTNT>
                <P>Railway certifies that its projected annual revenues will not exceed those that would qualify it as a Class III rail carrier and that its annual revenues are not projected to exceed $5 million. </P>
                <P>The transaction was scheduled to be consummated on or after the May 24, 2002 effective date of the exemption, 7 days after the exemption was filed. </P>
                <P>
                    This transaction is related to STB Finance Docket No. 34206, 
                    <E T="03">Permian Basin Railways, Inc.—Continuance in Control Exemption—West Texas and Lubbock Railway Company, Inc. and Austin &amp; Northwestern Railroad Company, Inc.,</E>
                     wherein Permian Basin Railways, Inc. (Permian) has concurrently filed a verified notice to continue in control of Austin &amp; Northwestern Railroad Company, Inc. and Railway, upon Railway's becoming a Class III railroad. 
                </P>
                <P>
                    If the verified notice contains false or misleading information, the exemption is void 
                    <E T="03">ab initio.</E>
                     Petitions to reopen the proceeding to revoke the exemption under 49 U.S.C. 10502(d) may be filed at any time. The filing of a petition to revoke will not automatically stay the transaction. 
                </P>
                <P>An original and 10 copies of all pleadings, referring to STB Finance Docket No. 34205, must be filed with the Surface Transportation Board, Case Control Unit, 1925 K Street, NW., Washington, DC 20423-0001. In addition, a copy of each pleading must be served on John D. Heffner, 555 12th Street, NW., Suite 950N, Washington, DC 20004. </P>
                <P>
                    Board decisions and notices are available on our website at “
                    <E T="03">www.stb.dot.gov.</E>
                    ” 
                </P>
                <SIG>
                    <DATED>Decided: June 7, 2002. </DATED>
                    <P>By the Board, David M. Konschnik, Director, Office of Proceedings. </P>
                    <NAME>Vernon A. Williams, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-14951 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4915-00-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request </SUBJECT>
                <DATE>June 6, 2002. </DATE>
                <P>The Department of Treasury has submitted the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 2110, 1425 New York Avenue, NW., Washington, DC 20220. </P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before July 15, 2002, to be assured of consideration. </P>
                </DATES>
                <HD SOURCE="HD1">Internal Revenue Service (IRS) </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0351. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 3975. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Tax Professionals Annual Mailing List Application and Order Blank. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 3975 allows a tax professional a systematic way to remain on the Tax Professionals Mailing File and to order copies of tax materials. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     320,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     3 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Annually. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     16,000 hours. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1407. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 8848. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Consent To Extend the Time To Assess the Branch Profits Tax Under Regulations Sections 1.884-2(a) and (c). 
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 8848 is used by foreign corporations that have (a) completely terminated all of their U.S. trade or business within the meaning of Temporary Regulations section 1.884-2T(a) during the tax year or (b) transferred their U.S. assets to a domestic corporation in a transaction described in Code section 381(a), if the foreign corporation was engaged in a U.S. trade or business at that time. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Business or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     5,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent/Recordkeeper:</E>
                </P>
                <FP SOURCE="FP-1">Recordkeeping—3 hr., 3 min. </FP>
                <FP SOURCE="FP-1">Learning about the law or the form—11 min. </FP>
                <FP SOURCE="FP-1">Preparing and sending the form to the IRS—1 hr., 6 min. </FP>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Annually. 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     22,500 hours. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-1773. 
                </P>
                <P>
                    <E T="03">Revenue Procedure Number:</E>
                     Revenue Procedure 2002-23. 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension. 
                </P>
                <P>
                    <E T="03">Title:</E>
                     Taxation of Canadian Retirement Plans Under U.S.—Canada Income Tax Treaty. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     This Revenue Procedure provides guidance for the application by U.S. citizens and residents of the U.S.—Canada Income Tax Treaty, as amended by the 1995 protocol, in order to defer U.S. Income taxes on income accrued in certain Canadian retirement plans. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals or households. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     20,000. 
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Per Respondent:</E>
                     30 minutes. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Other (once). 
                </P>
                <P>
                    <E T="03">Estimated Total Reporting Burden:</E>
                     10,000 hours. 
                </P>
                <FP SOURCE="FP-1">Clearance Officer: Glenn Kirkland, Internal Revenue Service, Room 6411-03, 1111 Constitution Avenue, NW., Washington, DC 20224. </FP>
                <FP SOURCE="FP-1">
                    <E T="03">OMB Reviewer:</E>
                     Alexander T. Hunt, Office of Management and Budget, Room 10202, New Executive Office 
                    <PRTPAGE P="40981"/>
                    Building, Washington, DC 20503, (202) 395-7860. 
                </FP>
                <SIG>
                    <NAME>Mary A. Able, </NAME>
                    <TITLE>Departmental Reports Management Officer. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 02-15017 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4830-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Office of the Comptroller of the Currency </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Comptroller of the Currency (OCC), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The OCC, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995. An agency may not conduct or sponsor, and a respondent is not required to respond to, an information collection unless the information collection displays a currently valid OMB control number. The OCC is soliciting comment concerning its information collection titled, “Fair Housing Home Loan Data System Regulation—12 CFR 27.” The OCC also gives notice that it has sent the information collection to OMB for review and approval. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>You should submit your comments to the OCC and the OMB Desk Officer by July 15, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You should direct comments to: </P>
                    <P SOURCE="NPAR">
                        Communications Division, Office of the Comptroller of the Currency, Public Information Room, Mailstop 1-5, Attention: 1557-0159, 250 E Street, SW., Washington, DC 20219. Due to recent, temporary disruptions in the OCC's mail service, commenters are encouraged to submit comments by fax or e-mail. Comments may be sent by fax to (202) 874-4448, or by e-mail to 
                        <E T="03">regs.comments@occ.treas.gov</E>
                        . You can inspect and photocopy the comments at the OCC's Public Information Room, 250 E Street, SW., Washington, DC 20219. You can make an appointment to inspect the comments by calling (202) 874-5043. 
                    </P>
                    <P>Alexander T. Hunt, OMB Desk Officer for the OCC, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 3208, Washington, DC 20503. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>You can request additional information or a copy of the collection from Jessie Dunaway, OCC Clearance Officer, or Camille Dixon, (202) 874-5090, Legislative and Regulatory Activities Division, Office of the Comptroller of the Currency, 250 E Street, SW., Washington, DC 20219. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The OCC is proposing to extend OMB approval of the following information collection: </P>
                <P>
                    <E T="03">Title:</E>
                     Fair Housing Home Loan Data System Regulation—12 CFR 27. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1557-0159. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     This submission covers an existing regulation and involves no change to the regulation or to the information collection. The OCC requests only that OMB extend its approval of the information collection. 
                </P>
                <P>
                    The Fair Housing Act (42 U.S.C. 3605) prohibits discrimination in the financing of housing on the basis of race, color, religion, sex, or national origin. The Equal Credit Opportunity Act (15 U.S.C. 1691 
                    <E T="03">et seq.</E>
                    ) prohibits discrimination in any aspect of a credit transaction on the basis of race, color, religion, national origin, sex, marital status, age, receipt of income from public assistance, or exercise of any right under the Consumer Credit Protection Act. The information collection requirements ensure bank compliance with applicable Federal law, further bank safety and soundness, provide protections for banks and the public, and further public policy interests. 
                </P>
                <P>The information collection requirements in 12 CFR part 27 are as follows: </P>
                <P>Section 27.3 requires a national bank that is required to collect data on home loans under 12 CFR part 203 to present the data on Federal Reserve Form FR HMDA-LAR, or in automated format in accordance with the HMDA-LAR instructions, and to include one additional item (the reason for denial) on the HMDA-LAR. Section 27.3 also lists exceptions to the HMDA-LAR recordkeeping requirements. Section 27.3 further lists the information banks should obtain from an applicant as part of a home loan application, and states information that a bank must disclose to an applicant. </P>
                <P>
                    Section 27.4 states that the OCC may require a national bank to maintain a Fair Housing Inquiry/Application Log if there is reason to believe that the bank is engaging in discriminatory practices or if analysis of the data compiled by the bank under the Home Mortgage Disclosure Act (12 U.S.C. 2801 
                    <E T="03">et seq.</E>
                    ) and 12 CFR part 203 indicates a pattern of significant variation in the number of home loans between census tracts with similar incomes and home ownership levels differentiated only by race or national origin. 
                </P>
                <P>Section 27.5 requires a national bank to maintain the information for 25 months after the bank notifies the applicant of action taken on an application, or after withdrawal of an application. </P>
                <P>Section 27.7 requires a national bank to submit the information to the OCC upon its request, prior to a scheduled examination. </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     2,137. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Responses:</E>
                     2,137. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     3,894 hours. 
                </P>
                <SIG>
                    <DATED>Dated: May 29, 2002. </DATED>
                    <NAME>Mark J. Tenhundfeld, </NAME>
                    <TITLE>Assistant Director, Legislative and Regulatory Activities Division. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15066 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4810-33-P 1 </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Office of the Comptroller of the Currency </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Comptroller of the Currency (OCC), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The OCC, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995. An agency may not conduct or sponsor, and a respondent is not required to respond to, an information collection unless the information collection displays a currently valid OMB control number. The OCC is soliciting comment concerning its information collection titled, “(MA)-Securities Offering Disclosure Rules—12 CFR 16.” The OCC also gives notice that it has sent the information collection to OMB for review and approval. </P>
                </SUM>
                <DATES>
                    <PRTPAGE P="40982"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>You should submit your comments to the OCC and the OMB Desk Officer by July 15, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You should direct comments to: </P>
                    <P>
                        Communications Division, Office of the Comptroller of the Currency, Public Information Room, Mailstop 1-5, Attention: 1557-0120, 250 E Street, SW., Washington, DC 20219. Due to recent, temporary disruptions in the OCC's mail service, commenters are encouraged to submit comments by fax or e-mail. Comments may be sent by fax to (202) 874-4448, or by e-mail to 
                        <E T="03">regs.comments@occ.treas.gov.</E>
                         You can inspect and photocopy the comments at the OCC's Public Information Room, 250 E Street, SW., Washington, DC 20219. You can make an appointment to inspect the comments by calling (202) 874-5043. 
                    </P>
                    <P>Alexander T. Hunt, OMB Desk Officer for the OCC, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 3208, Washington, DC 20503. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>You can request additional information or a copy of the collection from Jessie Dunaway, OCC Clearance Officer, or Camille Dixon, (202) 874-5090, Legislative and Regulatory Activities Division, Office of the Comptroller of the Currency, 250 E Street, SW., Washington, DC 20219. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The OCC is proposing to extend OMB approval of the following information collection: </P>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     (MA)-Securities Offering Disclosure Rules—12 CFR 16. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1557-0120. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     This submission covers an existing regulation and involves no change to the regulation or to the information collection. The OCC requests only that OMB extend its approval of the information collection. 
                </P>
                <P>The requirements in 12 CFR part 16 enable the OCC to perform its responsibilities relating to offerings of securities by national banks by providing the investing public with facts about the condition of the bank, the reasons for raising new capital, and the terms of the offering. Part 16 requires national banks to conform generally to Securities and Exchange Commission rules. </P>
                <P>The collections of information in part 16 are as follows: </P>
                <P>Sections 16.3 and 16.15 require a national bank to file its registration statement with the OCC. </P>
                <P>Section 16.4 requires a national bank to submit certain communications not deemed an offer to the OCC. </P>
                <P>Section 16.5 provides an exemption for items that satisfy the requirements of SEC Rule 144, which, in turn, requires certain filings. </P>
                <P>Section 16.6 requires a national bank to file documents with the OCC and to make certain disclosures to purchasers in sales of nonconvertible debt. </P>
                <P>Section 16.7 requires a national bank to file a notice with the OCC. </P>
                <P>Section 16.8 requires a national bank to file offering documents with the OCC. </P>
                <P>Section 16.15 requires a national bank to file a registration statement and sets forth content requirements for the registration statement. </P>
                <P>Section 16.17 requires a national bank to file four copies of each document filed under part 16, and requires filers of amendments or revisions to underline or otherwise indicate clearly any changed information. </P>
                <P>Section 16.18 requires a national bank to file an amended prospectus when the information in the current prospectus becomes stale, or when a change in circumstances makes the current prospectus incorrect. </P>
                <P>Section 16.19 requires a national bank to submit a request to the OCC if it wishes to withdraw a registration statement, amendment, or exhibit. </P>
                <P>Section 16.20 requires a national bank to file current and periodic reports as requires by sections 12 and 13 of the Exchange Act (15 U.S.C. 78l and m) and SEC Regulation 15d (17 CFR 240.15d-1 through 240.15Aa-1). </P>
                <P>Section 16.30 requires a national bank to include certain elements and follow certain procedures in any request to the OCC for a no-objection letter. </P>
                <P>These information collection requirements ensure bank compliance with applicable Federal law, further bank safety and soundness, provide protections for banks, and further public policy interests. </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses or other for-profit (national banks). 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     101. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Responses:</E>
                     101. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     2,333 hours. 
                </P>
                <SIG>
                    <DATED>Dated: May 29, 2002. </DATED>
                    <NAME>Mark J. Tenhundfeld, </NAME>
                    <TITLE>Assistant Director, Legislative and Regulatory Activities Division. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15067 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4810-33-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Office of the Comptroller of the Currency </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Comptroller of the Currency (OCC), Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comment. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The OCC, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on a continuing information collection, as required by the Paperwork Reduction Act of 1995. An agency may not conduct or sponsor, and a respondent is not required to respond to, an information collection unless the information collection displays a currently valid OMB control number. The OCC is soliciting comment concerning its information collection titled, “International Regulation—12 CFR 28.” The OCC also gives notice that it has sent the information collection to OMB for review and approval. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>You should submit your comments to the OCC and the OMB Desk Officer by July 15, 2002. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You should direct comments to: </P>
                    <P>
                        Communications Division, Office of the Comptroller of the Currency, Public Information Room, Mailstop 1-5, Attention: 1557-0102, 250 E Street, SW., Washington, DC 20219. Due to recent, temporary disruptions in the OCC's mail service, commenters are encouraged to submit comments by fax or e-mail. Comments may be sent by fax to (202) 874-4448, or by e-mail to 
                        <E T="03">regs.comments@occ.treas.gov.</E>
                         You can inspect and photocopy the comments at the OCC's Public Information Room, 250 E Street, SW., Washington, DC 20219. You can make an appointment to inspect the comments by calling (202) 874-5043. 
                    </P>
                    <P>Alexander T. Hunt, OMB Desk Officer for the OCC, Office of Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 3208, Washington, DC 20503. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        You can request additional information or a copy of the collection from Jessie Dunaway, OCC Clearance Officer, or Camille Dixon, (202) 874-5090, Legislative and Regulatory Activities Division, Office of the Comptroller of the Currency, 250 E Street, SW., Washington, DC 20219. 
                        <PRTPAGE P="40983"/>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The OCC is proposing to extend OMB approval of the following information collection: </P>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     International Regulation—12 CFR 28. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1557-0102. 
                </P>
                <P>
                    <E T="03">Description:</E>
                     This submission covers an existing regulation and involves no change to the regulation or to the information collection. The OCC requests only that OMB extend its approval of the information collection. The OCC's regulations at 12 CFR part 28 implement requirements imposed on national banks and Federal branches and agencies concerning international activities. The information collections in part 28 that are covered by this notice are as follows: 
                </P>
                <P>Section 28.3 requires a national bank to notify the OCC when it takes certain actions regarding its foreign operations. </P>
                <P>Section 28.14 requires a foreign bank to designate one Federal branch or agency to maintain consolidated information for purposes of monitoring compliance with limitations based upon capital. </P>
                <P>Section 28.15 requires a foreign bank with a Federal branch or agency to maintain records regarding its capital equivalency deposit (CED), including agreements entered into with the OCC and a depository bank regarding the CED, and liabilities requiring CED coverage. Section 28.15 also requires a foreign bank to apply to the OCC for exceptions to its rules regarding the CED. </P>
                <P>Section 28.16 requires an uninsured Federal branch to maintain records regarding its deposits, such as the average of its deposits during the last 30 days, if the Federal branch seeks to accept deposits from types of depositors that are not listed in the regulation. Section 28.16 also requires a foreign bank to apply to the OCC for an exemption allowing its uninsured Federal branch to accept or maintain types of deposit accounts not listed in the regulation. </P>
                <P>Section 28.18 requires a Federal branch or agency to comply with the record keeping and reporting requirements that apply to a national bank, as well as any additional requirements that may be prescribed by the OCC. It requires a Federal branch or agency to maintain records of its transactions separate from those of the parent foreign bank or other branches and agencies of that bank. It also requires the Federal branch or agency to provide the OCC with a copy of certain reports filed with other Federal regulatory agencies. </P>
                <P>Section 28.20 requires a foreign bank that is subject to an asset maintenance requirement to keep records of assets maintained in the state in which the Federal branch or agency is located and records of liabilities on which the asset maintenance requirement is based. </P>
                <P>Section 28.52 requires a national bank or District of Columbia bank to maintain records regarding any allocated transfer risk reserve for specified international assets. </P>
                <P>Section 28.53 requires a national bank or District of Columbia bank to maintain records regarding its accounting for fees and administrative costs on restructured international loans. </P>
                <P>These information collection requirements ensure bank compliance with applicable Federal law, further bank safety and soundness, provide protections for banks, and further public policy interests. </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension of a currently approved collection. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses or other for-profit. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     79. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Responses:</E>
                     130. 
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     4,625 hours. 
                </P>
                <SIG>
                    <DATED>Dated: June 7, 2002. </DATED>
                    <NAME>Mark J. Tenhundfeld, </NAME>
                    <TITLE>Assistant Director, Legislative and Regulatory Activities Division. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15068 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4810-33-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE TREASURY </AGENCY>
                <SUBAGY>Customs Service </SUBAGY>
                <SUBJECT>Customs COBRA Fees Advisory Committee </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>U.S. Customs Service, Department of the Treasury. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document announces the date, time and location of the first meeting of the U.S. Customs COBRA Fees Advisory Committee. The meeting is open to the public. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The first meeting of the U.S. Customs COBRA Fees Advisory Committee will be held on June 28, 2002, from 10 a.m. until 12 p.m., in room 6.4-B of the Ronald Reagan Building located at 1300 Pennsylvania Avenue, NW., Washington, DC 20229. Interested parties must provide Customs with notice of their intent to attend the meeting by June 25, 2002. Notice may be provided to Carlene Warren at (202) 927-1391 or via e-mail at 
                        <E T="03">Carlene.warren@customs.treas.gov.</E>
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Carlene Warren, U.S. Customs Service, Office of Field Operations, Passenger Programs, at (202) 927-1391 or via e-mail at 
                        <E T="03">Carlene.warren@customs.treas.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>Section 13031 of the Consolidated Omnibus Budget Reconciliation Act (COBRA) of 1985 (19 U.S.C. 58c), as amended by the Miscellaneous Trade and Technical Corrections Act of 1999 (Public Law 106-36), directs the Commissioner of Customs to establish an advisory committee whose membership consists of representatives from the airline, cruise ship, and other transportation industries who may be subject to fees under 19 U.S.C. 58c. </P>
                <P>The Committee will advise the Commissioner of Customs on issues relating to inspection services performed by the Customs Service, including issues pertaining to the time periods during which inspections should be performed, the proper number and deployment of inspection officers, and the amount of any proposed fees. </P>
                <P>
                    On February 8, 2000, Customs published a notice in the 
                    <E T="04">Federal Register</E>
                     (65 FR 6254) announcing the establishment of a COBRA Fee Advisory Committee, the criteria for membership, and requesting membership applications. In a notice published in the 
                    <E T="04">Federal Register</E>
                     (65 FR 38884) on June 22, 2000, Customs set forth amended criteria for membership in the Customs COBRA Fees Advisory Committee and requested that new applications for membership be submitted. A subsequent notice published in the 
                    <E T="04">Federal Register</E>
                     (65 FR 69993) on November 21, 2000, again amended membership criteria and extended the time within which membership applications were to be submitted. 
                </P>
                <P>This notice announces the first COBRA Fee Advisory Committee meeting. The meeting is scheduled for June 28, 2002, from 10 a.m. until 12 p.m., in room 6.4-B of the Ronald Reagan Building located at 1300 Pennsylvania Avenue, NW., Washington, DC 20229.</P>
                <P>
                    The agenda for this meeting will cover issues pertaining to the performance of Customs inspection services. The meeting is open to the public; however, participation in the Committee's deliberations is limited to Committee members and Customs and Treasury Department staff. Interested parties, other than Advisory Committee 
                    <PRTPAGE P="40984"/>
                    members, who wish to attend the meeting should contact Carlene Warren by June 25, 2002, at (202) 927-1391 or via e-mail at 
                    <E T="03">Carlene.warren@customs.treas.gov.</E>
                </P>
                <SIG>
                    <DATED>Dated: June 11, 2002. </DATED>
                    <NAME>Douglas M. Browning, </NAME>
                    <TITLE>Deputy Commissioner of Customs. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 02-15110 Filed 6-13-02; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4820-02-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <PRESDOCS>
        <PRESDOCU>
            <DETERM>
                <TITLE3>Title 3—</TITLE3>
                <PRES>
                    The President
                    <PRTPAGE P="40833"/>
                </PRES>
                <DETNO>Presidential Determination No. 02-21 of June 3, 2002</DETNO>
                <HD SOURCE="HED">Presidential Determination Under Subsection 402(d)(1) of the Trade Act of 1974, as Amended—Continuation of Waiver </HD>
                <LI>Authority for the Republic of Belarus</LI>
                <HD SOURCE="HED">Memorandum for the Secretary of State</HD>
                <FP>Pursuant to the authority vested in me under the Trade Act of 1974, as amended, Public Law 93-618, 88 Stat. 1978 (hereinafter the “Act”), I determine, pursuant to section 402(d)(1) of the waiver authority granted by section 402 of the Act will substantially promote the objectives of section 402 of the Act. I further determine that continuation of the waiver applicable to the Republic of Belarus will substantially promote the objectives of section 402 of the Act.</FP>
                <FP>On my behalf, please transmit this determination to the Speaker of the House of Representatives and to the President of the Senate.</FP>
                <FP>
                    You are authorized and directed to publish this determination in the 
                    <E T="04">Federal Register</E>
                    .
                </FP>
                <PSIG>B</PSIG>
                <PLACE>THE WHITE HOUSE,</PLACE>
                <DATE>Washington, June 3, 2002</DATE>
                <FRDOC>[FR Doc. 02-15180</FRDOC>
                <FILED>Filed 6-13-02; 8:45 am]</FILED>
                <BILCOD>Billing code 4710-10-P</BILCOD>
            </DETERM>
        </PRESDOCU>
    </PRESDOCS>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Presidential Documents</UNITNAME>
    <PRESDOC>
        <PRESDOCU>
            <DETERM>
                <PRTPAGE P="40835"/>
                <DETNO>Presidential Determination No. 02-22 of June 3, 2002</DETNO>
                <HD SOURCE="HED">Presidential Determination Under Subsection 402(d)(1) of the Trade Act of 1974, as Amended—Continuation of Waiver </HD>
                <LI>Authority for Vietnam</LI>
                <HD SOURCE="HED">Memorandum for the Secretary of State</HD>
                <FP>Pursuant to the authority vested in me under the Trade Act of 1974, as amended, Public Law 93-618, 88 Stat. 1978 (hereinafter the “Act”), I determine, pursuant to section 402(d)(1) of the waiver authority granted by section 402 of the Act will substantially promote the objectives of section 402 of the Act.  I further determine that continuation of the waiver applicable to Vietnam will substantially promote the objectives of section 402 of the Act.</FP>
                <FP>On my behalf, please transmit this determination to the Speaker of the House of Representatives and to the President of the Senate.</FP>
                <FP>
                    You are authorized and directed to publish this determination in the 
                    <E T="04">Federal Register</E>
                    .
                </FP>
                <PSIG>B</PSIG>
                <PLACE>THE WHITE HOUSE,</PLACE>
                <DATE>Washington, June 3, 2002.</DATE>
                <FRDOC>[FR Doc. 02-15181</FRDOC>
                <FILED>Filed 6-13-02; 8:45 am]</FILED>
                <BILCOD>Billing code 4710-10-P</BILCOD>
            </DETERM>
        </PRESDOCU>
    </PRESDOC>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>CORRECTIONS</UNITNAME>
    <CORRECT>
        <EDITOR>!!!Michele</EDITOR>
        <PREAMB>
            <PRTPAGE P="40985"/>
            <AGENCY TYPE="F">DEPARTMENT OF JUSTICE</AGENCY>
            <SUBAGY>Immigration and Naturalization Service</SUBAGY>
            <CFR>8 CFR Parts 214 and 264</CFR>
            <DEPDOC>[INS No. 2216-02; AG Order No. 2589-2002]</DEPDOC>
            <RIN>RIN 1115-AG70</RIN>
            <SUBJECT>Registration and Monitoring of Certain Nonimmigrants</SUBJECT>
        </PREAMB>
        <SUPLINF>
            <HD SOURCE="HD2">Correction</HD>
            <P>Federal Register document 02-15037 was inadvertently published in the Rules and Regulations section of the issue of Thursday, June 13, 2002 beginning on pages 40581-40586.  It should have appeared in the Proposed Rules section.</P>
        </SUPLINF>
        <FRDOC>[FR Doc. C2-15037  Filed 6-13-02; 8:45 am]</FRDOC>
        <BILCOD>BILLING CODE 1505-01-D</BILCOD>
        <EDITOR>!!!Michele</EDITOR>
        <PREAMB>
            <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
            <SUBAGY>Federal Aviation Administration</SUBAGY>
            <CFR>14 CFR Part 71</CFR>
            <DEPDOC>[Airspace Docket No. 01-AGL-17]</DEPDOC>
            <SUBJECT>Modification of Class E Airspace; Athens, OH</SUBJECT>
        </PREAMB>
        <SUPLINF>
            <HD SOURCE="HD2">Correction</HD>
            <P>In rule document 02-13214  beginning on page 36807 in the issue of Tuesday, May 28, 2002 make the following corrections:</P>
            <P>
                1. On page 36807, in the second column, under the heading, 
                <E T="02">SUPPLEMENTARY INFORMATION:</E>
                 in the 13th line, “200” should read “2001”.
            </P>
            <P>
                2. On the same page, in the third column, under 
                <E T="04">“Comments Invited”</E>
                , in the third paragraph, in the seventh line,“91-AGL-17” should read “01-AGL-17”.
            </P>
        </SUPLINF>
        <FRDOC>[FR Doc. C2-13214  Filed 6-13-02; 8:45 am]</FRDOC>
        <BILCOD>BILLING CODE 1505-01-D</BILCOD>
    </CORRECT>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="40987"/>
            <PARTNO>Part II</PARTNO>
            <AGENCY TYPE="P">Department of Health and Human Services</AGENCY>
            <SUBAGY>Centers for Medicare &amp; Medicaid Services</SUBAGY>
            <HRULE/>
            <CFR>42 CFR Parts 400 et al.</CFR>
            <TITLE>Medicaid Program; Medicaid Managed Care; Final Rules</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="40988"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                    <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                    <CFR>42 CFR Parts 400, 430, 431, 434, 435, 438, 440, and 447 </CFR>
                    <DEPDOC>[CMS-2001-F4] </DEPDOC>
                    <RIN>RIN 0938-AL83 </RIN>
                    <SUBJECT>Medicaid Program; Medicaid Managed Care </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Withdrawal of final rule with comment period. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            This document withdraws all provisions of the final rule with comment period on Medicaid managed care that we published in the 
                            <E T="04">Federal Register</E>
                             on January 19, 2001 (66 FR 6228) with an initial effective date of April 19, 2001. This January 19, 2001 final rule, which has never taken effect, would have combined Medicaid managed care regulations in a new part 438, implemented Medicaid managed care requirements of the Balanced Budget Act of 1997 (Pub. L. 105-33), and imposed new requirements on entities currently regulated as “prepaid health plans” (PHPs). The regulations set forth in the final rule being withdrawn have been superseded by regulations promulgated in a subsequent rulemaking initiated on August 20, 2001 (66 FR 43613). In addition, this document addresses comments received in response to an interim final rule with comment period that we published on August 17, 2001 in the 
                            <E T="04">Federal Register</E>
                             (66 FR 43090) that further delayed, until August 16, 2002, the effective date of the January 19, 2001 final rule with comment period. 
                        </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            The final rule with comment period amending 42 CFR parts 400, 430, 431, 434, 435, 438, 440, and 447 that was published in the January 19, 2001 
                            <E T="04">Federal Register</E>
                             (66 FR 6228), delayed in the February 26, 2001 
                            <E T="04">Federal Register</E>
                             (66 FR 11546) until June 18, 2001, delayed further in the June 18, 2001 
                            <E T="04">Federal Register</E>
                             (66 FR 32776) until August 17, 2001, and further delayed in the August 17, 2001 
                            <E T="04">Federal Register</E>
                             (66 FR 43090) until August 16, 2002 is withdrawn effective June 14, 2002. 
                        </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Bruce Johnson, (410) 786-0615. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">I. Background </HD>
                    <P>
                        In a final rule published in the 
                        <E T="04">Federal Register</E>
                         (66 FR 11546) on February 26, 2001, we announced a 60-day delay in the effective date of the January 19, 2001 final rule with comment period implementing Medicaid managed care provisions in the Balanced Budget Act of 1997 (BBA). This 60-day delay postponed the effective date of the final rule until June 18, 2001. This delay in effective date was necessary to give newly appointed Department officials the opportunity for review and consideration of the new regulations. During that review, we heard from key stakeholders in the Medicaid managed care program, including States, advocates for beneficiaries, and provider organizations. These parties expressed strong (sometimes opposing) views about the January 19, 2001 final rule. In particular, concerns were expressed about revisions made in the final rule that were based on public comments we received on the proposed rule. Other commenters raised concerns about how we chose to implement those provisions in the final rule without further opportunity for public comment. As a result of these comments, on June 18, 2001, we published another final rule in the 
                        <E T="04">Federal Register</E>
                         that delayed the effective date of the January 19, 2001 final rule an additional 60 days, from June 18, 2001 until August 17, 2001, (66 FR 32776) for further review and consideration on the most appropriate way to address the concerns expressed by key stakeholders. 
                    </P>
                    <P>
                        After careful consideration, we decided the best approach was to make some modifications to the January 19, 2001 final rule with comment period, and republish it as a proposed rule. This would enable the public the opportunity to comment on all of the provisions and revisions. Therefore, as noted above, on August 20, 2001 we published a new proposed rule in the 
                        <E T="04">Federal Register</E>
                         (66 FR 43613). In addition, in order to give us time to consider the public comments and take action on the new proposed rule, we also published an interim final rule with comment period on August 17, 2001 in the 
                        <E T="04">Federal Register</E>
                         (66 FR 43090) that further delayed until August 16, 2002, the effective date of the January 19, 2001 final rule with comment period. 
                    </P>
                    <P>
                        In response to those comments submitted on the August 20, 2001 proposed rule, we have published, elsewhere in this 
                        <E T="04">Federal Register</E>
                         issue, a final rule amending the Medicaid regulations to implement the managed care provisions of the BBA, and to establish new standards for prepaid health plans (PHPs), which are, under this new final rule, divided into two categories, prepaid inpatient health plans (PIHPs) and prepaid ambulatory health plans (PAHPs). In light of the publication of the superseding final rule, we are withdrawing the provisions of the January 19, 2001 final rule with comment period. 
                    </P>
                    <HD SOURCE="HD1">II. Analysis of and Response to Public Comments on the August 17, 2001 Interim Final Rule With Comment Period </HD>
                    <P>We received approximately 23 public comments expressing dissatisfaction with the delay in the effective date of the January 19, 2001 final rule with comment period. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters contended that “courts have held that the effective date of a regulation is a substantive term of the regulation itself, and the Administrative Procedure Act (APA) requires that the public be given prior notice and opportunity to comment before substantive terms of a regulation may be legally changed.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         None of these commenters cited the court cases upon which they purport to rely for the proposition that withdrawing a regulation that has never taken effect constitutes a change in the regulations. We are not aware of any case that suggests that an agency must go through notice and comment to delay the effective date of a regulation that has not taken effect (or to withdraw a regulation, as we are doing here). Under the APA, notice and comment generally is required to promulgate new rules or to change rules that are already in place. Currently, the Medicaid managed care regulations that are in effect are those set forth in part 434, because the regulations published on January 19, 2001 have not become effective. We would agree that notice and comment is required to change the Medicaid managed care regulations in part 434, and we have done so in the final rule responding to comments on the August 20, 2001 proposed rule. We do not agree, however, that notice and comment is required in order to delay the effective date of regulations that have been published in the 
                        <E T="04">Federal Register</E>
                         but have never taken effect. In that case, there is no “rule” in effect, just an announcement of a “future” rule. We do not believe that notice and comment was required to change the effective date of a “future rule.” Nor do we believe that notice and comment is required in order to withdraw a rule before it takes effect. We note that even if notice and comment were required, we have engaged in public notice and 
                        <PRTPAGE P="40989"/>
                        comment on the final rule that supersedes the rule we are withdrawing. 
                    </P>
                    <EXTRACT>
                        <FP>(Catalog of Federal Domestic Assistance Program No. 93.778, Medical Assistance Program) </FP>
                    </EXTRACT>
                    <SIG>
                        <DATED>Dated: April 17, 2002. </DATED>
                        <NAME>Thomas A. Scully, </NAME>
                        <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                    </SIG>
                    <SIG>
                        <APPR>Approved: May 14, 2002. </APPR>
                        <NAME>Tommy G. Thompson, </NAME>
                        <TITLE>Secretary. </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 02-14748 Filed 6-13-02; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
            </RULE>
            <RULE>
                <PREAMB>
                    <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                    <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                    <CFR>42 CFR Parts 400, 430, 431, 434, 435, 438, 440, and 447 </CFR>
                    <DEPDOC>[CMS-2104-F] </DEPDOC>
                    <RIN>RIN 0938-AK96 </RIN>
                    <SUBJECT>Medicaid Program; Medicaid Managed Care: New Provisions </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This final rule amends the Medicaid regulations to implement provisions of the Balanced Budget Act of 1997 (BBA) that allow the States greater flexibility by permitting them to amend their State plan to require certain categories of Medicaid beneficiaries to enroll in managed care entities without obtaining waivers if beneficiary choice is provided; establish new beneficiary protections in areas such as quality assurance, grievance rights, and coverage of emergency services; and eliminate certain requirements viewed by State agencies as impediments to the growth of managed care programs, such as, the enrollment composition requirement, the right to disenroll without cause at any time, and the prohibition against enrollee cost-sharing. </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                        <P>These regulations are effective on August 13, 2002. States will have until June 16, 2003, to bring all aspects of their State managed care program (that is, contracts, waivers, State plan amendments and State operations) into compliance with the final rule provisions. </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <FP SOURCE="FP-1">
                            <E T="03">Subparts A and B</E>
                            —Bruce Johnson, (410) 786-0615. 
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Subpart C</E>
                            —Kristin Fan, (410) 786-4581. 
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Subpart D</E>
                            —Deborah Larwood, (410) 786-9500. 
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Subpart F</E>
                            —Tim Roe, (410) 786-2006. 
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Subpart H</E>
                            —Donna Schmidt, (410) 786-5532. 
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Subpart I</E>
                            —Tim Roe, (410) 786-2006. 
                        </FP>
                        <FP SOURCE="FP-1">
                            <E T="03">Subpart J</E>
                            —Bruce Johnson, (410) 786-0615. 
                        </FP>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P SOURCE="NPAR">
                        <E T="03">Copies:</E>
                         To order copies of the 
                        <E T="04">Federal Register</E>
                         containing this document, send your request to: New Orders, Superintendent of Documents, PO Box 371954, Pittsburgh, PA 15250-7954. Specify the date of the issue requested and enclose a check or money order payable to the Superintendent of Documents, or enclose your Visa or Master Card number and expiration date. Credit card orders can also be placed by calling the order desk at (202) 512-1800 or by faxing to (202) 512-2250. The cost for each copy is $9. As an alternative, you can view and photocopy the 
                        <E T="04">Federal Register</E>
                         document at most libraries designated as Federal Depository Libraries and at many other public and academic libraries throughout the country that receive the 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                    <P>
                        This 
                        <E T="04">Federal Register</E>
                         document is also available from the 
                        <E T="04">Federal Register</E>
                         online database through GPO access, a service of the U.S. Government Printing Office. The Website address is 
                        <E T="03">http://www.access.gpo.gov/nara/index.html.</E>
                    </P>
                    <HD SOURCE="HD1">I. Background </HD>
                    <HD SOURCE="HD2">A. General </HD>
                    <P>In 1965, amendments to the Social Security Act (the Act) established the Medicaid program as a joint Federal and State program for providing financial assistance to individuals with low incomes to enable them to receive medical care. Under the Medicaid program, each State establishes its own eligibility standards, benefits packages, payment rates and program administration in accordance with certain Federal statutory and regulatory requirements. The provisions of each State's Medicaid program are described in the State's Medicaid “State plan” that we must approve. In addition to approving State plans and monitoring States for compliance with Federal Medicaid laws, the Federal role also includes providing matching funds to State agencies to pay for a portion of the costs of providing health care to Medicaid beneficiaries. Medicaid beneficiaries typically include low-income children and their families, pregnant women, individuals age 65 and older, and individuals with disabilities. (Throughout this preamble, we use the term “beneficiaries” to mean “individuals eligible for and receiving Medicaid benefits.” The term “recipients” in the regulations text has the same meaning as the term “beneficiary.”) </P>
                    <P>When the Medicaid program was created, coverage typically was provided through reimbursements by the State agency to health care providers who submitted claims for payment after they provided health care services to Medicaid beneficiaries. This reimbursement arrangement is referred to as “fee-for-service” (FFS) payment. Before 1982, 99 percent of Medicaid beneficiaries received Medicaid coverage through fee-for-service arrangements. Since 1982, State agencies increasingly have provided Medicaid coverage through contracts with managed care organizations (MCOs), such as health maintenance organizations (HMOs). Through these contracts an MCO is paid a fixed, prospective, monthly payment for each beneficiary enrolled with the entity for health coverage. This payment approach is referred to as “capitation.” Beneficiaries enrolled in capitated MCOs are required to receive health care services provided under the MCO's contract, through the MCO that receives the capitation payment. The Omnibus Budget Reconciliation Act (OBRA) of 1981 (Pub. L. 97-35 enacted on August 13, 1981) allowed State agencies to mandate that Medicaid beneficiaries enroll in MCOs, which increased the use of MCOs. In most States, mandatory enrollment takes place for at least certain categories of beneficiaries. To achieve this mandatory enrollment, before the enactment of the Balanced Budget Act (BBA) of 1997 (Pub. L. 105-33, enacted on August 5, 1997), States were required to obtain a waiver of a Medicaid statutory requirement for beneficiary “freedom of choice” of providers. (State programs that offered beneficiaries voluntary enrollment in MCOs do not require these waivers.) As a result, in 1997, just before the passage of the BBA, almost 8.5 million Medicaid beneficiaries, or 43 percent of all Medicaid beneficiaries, were enrolled in MCOs for a comprehensive array of Medicaid services. Some of these beneficiaries and additional Medicaid beneficiaries were enrolled in other organizations that received capitated payment for a limited array of services, such as behavioral health or dental services. These organizations that receive capitation payment for a limited array of services are referred to as “prepaid health plans (PHPs).” </P>
                    <P>
                        While the Act was further amended in the 1980s and in 1990 to address certain 
                        <PRTPAGE P="40990"/>
                        aspects of Medicaid managed care, the BBA represents the first comprehensive revision to Federal statutes governing Medicaid managed care in over a decade. In general, Chapter One (subtitle H) of the BBA significantly renovated the Medicaid managed care program by modifying Federal statute to: (1) Allow States to mandate the enrollment of certain Medicaid beneficiaries into MCOs without having to first seek a waiver of Federal statutory requirements; (2) eliminate requirements on the composition of enrollment in MCOs that had not been proven to be effective; (3) apply consumer protections that were receiving widespread acceptance in the commercial and Medicare marketplaces to Medicaid beneficiaries; for example, consumer information standards and standards for access to services; and (4) apply the advances and developments in health care quality improvement that are in widespread use in the private sector to Medicaid managed care programs. Specifically, sections 4701 through 4710 of the BBA provisions: (1) Reduce requirements for State agencies to obtain waivers to implement certain managed care programs; (2) eliminate enrollment composition requirements for managed care contracts; (3) increase beneficiary protections for enrollees in Medicaid managed care entities; (4) improve quality assurance; (5) establish solvency standards; (6) protect against fraud and abuse; (7) permit a period of guaranteed eligibility for Medicaid beneficiaries; and (8) improve certain administrative features of State managed care programs. 
                    </P>
                    <P>
                        We have already implemented provisions of the BBA that did not require regulations. CMS provided guidance on these provisions through the issuance of State Medicaid Director letters, which are listed below. These letters can be found on the CMS website at 
                        <E T="03">www.hcfa.gov/medicaid/letters/.</E>
                    </P>
                    <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,r100,xs90">
                        <TTITLE>State Medicaid Director Letters on Managed Care Provisions of the BBA </TTITLE>
                        <BOXHD>
                            <CHED H="1">Section of the Act issued </CHED>
                            <CHED H="1">Subject </CHED>
                            <CHED H="1">Date </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">1932(a)(1) </ENT>
                            <ENT>State Plan Option for Managed Care </ENT>
                            <ENT>December 17, 1997. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(b)(1) </ENT>
                            <ENT>Specification of Benefits </ENT>
                            <ENT>December 17, 1997. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(d)(2) </ENT>
                            <ENT>Marketing Restrictions </ENT>
                            <ENT>December 30, 1997. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(b)(6), 1128B(d)(1), 1124(a)(2)(A), 1932(d)(3), 1903(i), 1916(a)(2)(D), 1916(b)(2)(D), and 1903(m)(1)(C) </ENT>
                            <ENT>Miscellaneous Managed Care Provisions </ENT>
                            <ENT>December 30, 1997. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(a)(1)(B), 1932(a)(3), and 1903(m)(2)(A) </ENT>
                            <ENT>Definition of a managed care entity, Choice, Repeal of 75/25, and Approval Threshold </ENT>
                            <ENT>January 14, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(c)(2) and 1903(a)(3)(C) </ENT>
                            <ENT>External Quality Review </ENT>
                            <ENT>January 20, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(a)(4) </ENT>
                            <ENT>Enrollment, Termination, and Default Assignment </ENT>
                            <ENT>January 21, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1905(t) and 1905(a)(25) </ENT>
                            <ENT>PCCM Services Without Waiver </ENT>
                            <ENT>January 21, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(e) </ENT>
                            <ENT>Sanctions for Noncompliance </ENT>
                            <ENT>February 20, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(a)(5) BBA Section 4710(a) </ENT>
                            <ENT>Provision of Information &amp; Effective Dates </ENT>
                            <ENT>February 20, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(b)(2) </ENT>
                            <ENT>Emergency Services </ENT>
                            <ENT>February 20, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(b)(4) </ENT>
                            <ENT>Grievance Procedures </ENT>
                            <ENT>February 20, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(d)(1) </ENT>
                            <ENT>Debarred Individuals </ENT>
                            <ENT>February 20, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(b)(3), 1932(b)(7), and 1932(b)(5) </ENT>
                            <ENT>Enrollee-Provider Communications, Antidiscrimination of Providers, and Adequate Capacity </ENT>
                            <ENT>February 20, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(d)(2) </ENT>
                            <ENT>Effective Date of Marketing Restrictions </ENT>
                            <ENT>February 20, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1902(e)(2) </ENT>
                            <ENT>Guaranteed Eligibility </ENT>
                            <ENT>March 23, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">BBA Section 4710(c) </ENT>
                            <ENT>Application to Waivers </ENT>
                            <ENT>March 25, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(b)(2) </ENT>
                            <ENT>Prudent Layperson Standard </ENT>
                            <ENT>May 6, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(b)(2) </ENT>
                            <ENT>Post-Stabilization Services </ENT>
                            <ENT>August 5, 1998. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">1932(b) </ENT>
                            <ENT>Emergency Services </ENT>
                            <ENT>April 18, 2000. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD2">B. Statutory Basis </HD>
                    <P>Section 4701 of the BBA enacted section 1932 of the Act, changes terminology in title XIX of the Act (most significantly, the BBA uses the term “managed care organization” to refer to entities previously labeled “health maintenance organizations”, and amends section 1903(m) to require that MCOs and MCO contracts comply with applicable requirements in newly added section 1932 of the Act. Among other things, section 1932 of the Act permits States to require most groups of Medicaid beneficiaries to enroll in managed care arrangements without waiver authority granted under section 1915(b) or 1115(a) of the Act. Under the statute before the BBA, a State agency was required to obtain Federal authority to waive beneficiary free choice of providers in order to restrict their coverage to managed care arrangements. Section 1932 also defines the term “managed care entity” (MCE) to include MCOs and primary care case managers (PCCMs); establishes new requirements for managed care enrollment and choice of coverage; and requires MCEs and State agencies to provide specified information to enrollees and potential enrollees. </P>
                    <P>Section 4702 of the BBA amended section 1905 of the Act to provide for States to contract with primary care case managers without waiver authority. Instead, primary care case management services may be made available under a State's Medicaid plan as an optional service. </P>
                    <P>Section 4703 of the BBA eliminated a former statutory requirement that no more than 75 percent of the enrollees in an MCO be Medicaid or Medicare beneficiaries. </P>
                    <P>Section 4704 of the BBA created section 1932(b) of the Act to add increased protections for those enrolled in managed care arrangements. These protections include, the application of a “prudent layperson's” standard to determine whether emergency room use by a beneficiary was appropriate; criteria for showing adequate capacity and services; grievance procedures; and protections for enrollees against liability for payment of an organization's or provider's debts in the case of insolvency. </P>
                    <P>
                        Section 4705 of the BBA created section 1932(c) of the Act, which requires States to develop and implement quality assessment and improvement strategies for their managed care arrangements and to provide for external, independent review of managed care activities. 
                        <PRTPAGE P="40991"/>
                    </P>
                    <P>Section 4706 of the BBA provided that, with limited exceptions, an MCO must meet the same solvency standards set by States for private HMOs, or otherwise be licensed or certified by the State as a risk-bearing entity. </P>
                    <P>Section 4707 of the BBA enacted section 1932(d) of the Act to add protections against fraud and abuse, such as restrictions on marketing and sanctions for noncompliance. </P>
                    <P>Section 4708 of the BBA added a number of provisions to the Act to improve the administration of managed care arrangements. These include, provisions raising the threshold value of managed care contracts that require the Secretary's prior approval, and permitting the same copayments in MCOs as apply to fee-for-service arrangements. </P>
                    <P>Section 4709 of the BBA allows States the option to provide 6 months of guaranteed eligibility for all individuals enrolled in an MCE. Section 4710 of the BBA specifies the effective dates for all the provisions identified in sections 4701 through 4709 of the BBA, and specifies that these provisions do not apply to the extent they are inconsistent with the terms and conditions of waivers under section 1915(b) or section 1115 of the Act. </P>
                    <HD SOURCE="HD2">C. Federal Register Publications </HD>
                    <P>
                        On September 29, 1998, we published in the 
                        <E T="04">Federal Register</E>
                         (63 FR 52022) a proposed rule to implement the above provisions of the BBA. In that 1998 proposed rule, we also proposed to strengthen regulatory requirements of PHPs by incorporating regulatory requirements that would otherwise apply only to MCOs. We received over 300 comments on the 1998 proposed rule. The comments were extensive and generally addressed all sections of that proposed rule. On January 19, 2001, we published in the 
                        <E T="04">Federal Register</E>
                         (66 FR 6228) a final rule with comment period that summarized, and responded to the public comments we received on the proposed rule. It also contained additional provisions not included in the 1998 proposed rule. Among these were revisions eliminating the existing “upper payment limit” (UPL) on risk capitation payments in § 447.361, and replacing this limit with provisions in § 438.6(c) setting forth requirements designed to ensure that rates were actuarially sound. We invited comments only on these last two changes. 
                    </P>
                    <P>
                        In a 
                        <E T="04">Federal Register</E>
                         notice (66 FR 11546) published on February 26, 2001, we announced a 60-day delay in the effective date of the January 19, 2001 final rule with comment period. This 60-day delay postponed the effective date of the rule until June 18, 2001. This delay in effective date was necessary to give Department officials the opportunity for further review and consideration of the new regulations. During that review, we heard from key stakeholders in the Medicaid managed care program, including States, advocates for beneficiaries, and provider organizations. These parties expressed strong (sometimes opposing) views about the regulation. In particular, concerns were expressed about the revisions based on public comments we received on the proposed rule. Other commenters raised concerns about how we chose to implement those provisions in the final rule without further opportunity for public comment. 
                    </P>
                    <P>
                        As a result of these comments, on June 18, 2001, we published a final rule in the 
                        <E T="04">Federal Register</E>
                         that further delayed the effective date of the January 19, 2001 final rule with comment period an additional 60 days, from June 18, 2001 until August 17, 2001, (66 FR 32776) for further review and consideration on the most appropriate way to address the concerns expressed by key stakeholders. In response to these concerns, on August 20, 2001 we published a new proposed rule in the 
                        <E T="04">Federal Register</E>
                        . In addition, in order to give us the time to consider the public comments and take final action on the new proposed rule, we also published in the August 17, 2001 
                        <E T="04">Federal Register</E>
                         an interim final rule with comment period that further delayed until August 16, 2002, the effective date of the January 2001 final rule with comment period. 
                    </P>
                    <P>The new proposed rule was published to address the concerns that were expressed to the Department during our review. After careful consideration, we decided the best approach was to make some modifications to the January 19, 2001 final rule and republish it as a proposed rule. This would enable the public the opportunity to comment on all of the provisions and revisions. </P>
                    <P>
                        In developing the proposed rule, we were guided by several considerations. First, we gave serious attention to all the concerns that were communicated to us. Second, we tried to discern when a difference of opinion represented different goals or different methods of achieving the same goals. Finally, we believed that all commenters expressed the same goal, namely: Strong, viable, Medicaid managed care programs that deliver high quality health care to Medicaid beneficiaries. We note that we have published elsewhere in this 
                        <E T="04">Federal Register</E>
                         a final rule withdrawing the January 19, 2001 final rule with comment period. 
                    </P>
                    <P>We have drafted the provisions of this final rule in full recognition of the statutorily designed structure of the Medicaid program as a Federal-State partnership. States are assigned the responsibility of designing their State programs, and typically do so addressing local, as well as State needs. We have drafted this final rule to recognize the responsibilities of the States and the need to employ different approaches to achieving the same goal within their varying State marketplaces and health care delivery systems. </P>
                    <P>Finally, we appreciate that new advances and findings in health care, health care quality assessment and improvement, and health services research unfold on an almost daily basis. In many instances, States have been at the forefront of implementing these new developments and innovations. We have sought to standardize, through regulation, those practices that have been found to be necessary to the delivery of high quality health care. We simultaneously have sought to continue to allow States, in consultation with their State and local partners and customers (beneficiaries), to determine the best approach to implementing their managed care program when there is an absence of clear evidence about the superiority of a given approach. </P>
                    <P>
                        Overall, we recognize the great diversity and sometimes “special needs” of Medicaid beneficiaries. While the greatest numbers (54 percent) of Medicaid beneficiaries are children, 11 percent are age 65 or older. Medicaid also serves as a significant source of health care for individuals with disabilities and conditions that place them at risk of developing disabilities. In 1997, more than 6 million children and adults were eligible for Medicaid on the basis of a physical, mental, or cognitive disability. The Medicaid program insures more than half of all people with Acquired Immune Deficiency Syndrome (AIDS) in this country and up to 90 percent of children with AIDS. Medicaid also is a significant source of health care coverage for individuals with serious and persistent mental illness, and children in foster care. Our report to the Congress, “
                        <E T="03">Safeguards for Individuals with Special Health Care Needs Enrolled in Medicaid Managed Care</E>
                        ” (November 6, 2000), summarized existing evidence on effective practices in caring for individuals with special health care needs. 
                    </P>
                    <P>
                        The regulations in this final rule are mostly set forth as new provisions in part 438. All new managed care regulations created under the authority 
                        <PRTPAGE P="40992"/>
                        of the BBA, other sections of existing Medicaid regulations pertaining to managed care, and appropriate cross references will appear in this new part. By creating this new part, we aim to help users of the regulations to better understand the overall regulatory framework for managed care. 
                    </P>
                    <HD SOURCE="HD2">D. Overview of Medicaid Managed Care </HD>
                    <P>Medicaid managed care programs have been in existence almost since the inception of the Medicaid program in 1965. In New York State, Medicaid beneficiaries were enrolled in the Health Insurance Plan of Greater New York beginning in 1967. The State of Washington began contracting with Group Health of Puget Sound in 1970, and, by 1972, various regional operations of Kaiser-Permanente served Medicaid beneficiaries in three different States. Initially, there were no statutory or regulatory provisions specifically addressing the use of managed care by State agencies. </P>
                    <P>As a result of the increasing use of managed care in Medicaid, Medicare and the private sector, statutory provisions and regulations have since been adopted to specifically address Medicaid managed care. In 1976, the Health Maintenance Organization Act put forth the first specific Federal requirements for Medicaid contracts with HMOs or comparable organizations, by essentially requiring, with some exceptions, that contracts with entities to provide “comprehensive” specified services, be entered into only with Federally qualified HMOs. By 1981, little more than 1 percent of Medicaid beneficiaries were enrolled in managed care. Further legislative and regulatory changes made in 1981 and 1982 made possible more widespread use of managed care by State agencies but were also accompanied by increased requirements in some areas (For example, OBRA 1981 required that Medicaid enrollees be allowed to voluntarily disenroll without cause from HMOs. This was subsequently amended to permit a 6-month lock-in for individuals enrolled in federally qualified HMOs.) Until the enactment of the BBA, modification of the statutes and regulations governing Medicaid managed care after OBRA 1981 and the Tax Equity and Fiscal Responsibility Act of 1982 (TEFRA) (Pub. L. 97-248, enacted on September 3, 1982) has occurred in a piecemeal manner. The BBA represents the first major revision of the statutes governing Medicaid managed care in over a decade.</P>
                    <P>
                        The period from 1981 to the present has seen significant changes in Medicaid managed care programs. While only approximately 250,000 Medicaid beneficiaries were enrolled in managed care in 1981, by 1997 this number had increased to over 15 million. As of June 2000, approximately 56 percent of the entire Medicaid population received at least some services through an MCO, PHP, or a primary care case management arrangement. In the last decade, a number of studies and reports have documented that State agencies need both flexibility and assistance to implement new approaches and tools to effectively administer their contracts with MCOs. A 1997 General Accounting Office Report entitled, “
                        <E T="03">Medicaid Managed Care—Challenge of Holding Plans Accountable Requires Greater State Effort,</E>
                        ” indicated the need for priority attention to beneficiary information and education, and access to care and quality monitoring. 
                    </P>
                    <P>As noted above, Medicaid managed care contracts were originally entered into by some State agencies without any specific statutory provision for these arrangements. When the Congress acted to regulate managed care arrangements, it limited the applicability of these statutory requirements to contracts that were comprehensive in the services they covered. </P>
                    <P>Specifically, the statutory requirements enacted by the Congress in section 1903(m) of the Act have always applied to contracts for inpatient services plus any one of the other services specified in section 1903(m)(2)(A) of the Act, or for any three of the non-inpatient services specified in section 1903(m)(2)(A) of the Act. Managed care contracts that were less than comprehensive remained exempt from all statutory managed care requirements. In recognition of this fact, we have in the past exercised our authority under section 1902(a)(4) of the Act to specify “methods of administration” that were “necessary for proper and efficient administration” to impose regulatory requirements on entities that were exempt from the statutory requirements in section 1903(m), either because they provided less than comprehensive services or because they were specifically exempted by the Congress from complying with section 1903(m) requirements. These entities were called “prepaid health plans,” or “PHPs.” </P>
                    <P>The regulatory requirements we applied to PHPs were not as stringent in many areas as those under section 1903(m). For example, while PHPs were subject to an enrollment composition requirement like comprehensive HMO contractors, the PHP enrollment composition requirement could be waived by the State for “good cause.” PHPs also were not subject to the section 1903(m) requirement that beneficiaries have the right to disenroll without cause at any time, and beneficiaries enrolled in PHPs thus could have their ability to disenroll restricted under section 1915(b) waiver authority, (where the right to disenroll required under section 1903(m) could not be waived). </P>
                    <P>In part, because of the less stringent requirements that applied to PHPs, there has been a substantial growth in PHP enrollment. Some of these PHPs are single service managed care plans (for example, behavioral health plans) and their enrollees are also enrolled in other managed care plans for their routine primary and acute care. Other PHPs, such as the Health Insurance Plan (HIP) of New York, provide a full range of services, but were exempted by the Congress from the requirements in section 1903(m) of the Act. As discussed more fully below, certain PHPs are required to meet most of the provisions that apply to MCOs. </P>
                    <P>
                        Concurrent with the increasing size of, and need for, stronger Medicaid managed care programs, over the last decade we have been developing improved tools, techniques, and strategies that State agencies can use to strengthen their managed care programs. In 1991, we began the Quality Assurance Reform Initiative (QARI) to provide technical assistance tools and assistance to State agencies. In 1993, we produced a QARI guide entitled, “
                        <E T="03">A Health Care Quality Improvement System for Medicaid Managed Care—A Guide for States,</E>
                        ” which contained four areas of guidance for States: (1) A framework for quality improvement systems for Medicaid managed care programs; (2) guidelines for internal quality assurance programs of Medicaid HMOs and PHPs; (3) guidelines for clinical and health services focus areas and use of quality indicators and clinical practice guidelines; and (4) guidelines for the conduct of external quality reviews conducted under section 1902(a)(30)(C) of the Act. In 1995, we worked collaboratively with the National Committee for Quality Assurance (NCQA) and the American Public Human Services Association to produce a Medicaid version of the Health Plan Employer Data and Information Set (HEDIS). HEDIS is a standardized quality performance measurement system used by private sector purchasers of managed care services, which we modified for use by State agencies. We contracted with NCQA to develop “
                        <E T="03">
                            Health Care Quality 
                            <PRTPAGE P="40993"/>
                            Improvement Studies in Managed Care Settings: Design and Assessment—A Guide for State Medicaid Agencies
                        </E>
                        ”.
                    </P>
                    <P>In 1996, we undertook the Quality Improvement System for Managed Care (QISMC) initiative to accomplish several goals: (1) To update the 1993 QARI guidelines; (2) to develop coordinated Medicare and Medicaid quality standards that would reduce duplicative or conflicting efforts; (3) to make the most efficient and effective use of recent developments in the art and science of quality measurement, while allowing sufficient flexibility to incorporate developments in this rapidly evolving discipline; and (4) to assist the Federal government and State agencies in becoming more effective “value-based” purchasers of health care for vulnerable populations. In developing QISMC, we worked with representatives from, and with tools developed by, health plans, State agencies, advocacy organizations, and experts in quality measurement and improvement such as the NCQA, the Foundation for Accountability (FACCT) and the Joint Commission on the Accreditation of Healthcare Organizations. With the assistance of the experts and their products, we identified the approaches, tools, and techniques that we believed would most effectively measure and improve health care quality in managed care. The quality assurance provisions of this final rule espouse the same philosophy and goals for performance improvement as are reflected in QISMC, but have been modified based on recent developments in Medicaid, managed care, and quality assessment and improvement. For example, QISMC was written before our report to the Congress addressing individuals with special health care needs. </P>
                    <P>In 1997, the Agency for Health Care Policy and Research (AHCPR) (now, the Agency for Healthcare Research and Quality) produced a set of consumer survey instruments and measurement tools under the auspices of the Consumer Assessment of Health Plan Study (CAHPS). The CAHPS instruments include measures and tools specifically designed for use by State agencies. Also in 1997, the George Washington University Center for Health Policy Research published a compendium of provisions of State contracts with Medicaid managed care organizations. This nationwide study of Medicaid managed care contracts has provided valuable information that can be used by all State agencies in the design and management of their managed care contracts. </P>
                    <P>
                        More recently, in 1999, we produced a technical assistance manual for State agencies entitled, “
                        <E T="03">Writing and Designing Print Materials for Beneficiaries: A Guide for State Medicaid Agencies.</E>
                        ” This technical assistance tool for States was in direct response to the BBA statutory provisions calling for dissemination of information to Medicaid beneficiaries. A contract with FACCT produced a manual describing valid and reliable tools that State agencies can use to identify children and adults with special health care needs. In addition, a contract with the Center for Health Program Development and Management at the University of Maryland Baltimore County will develop a guidance manual for States that will describe various approaches to using health status-based risk adjustment in making payments to MCOs. 
                    </P>
                    <P>These and other tools we have in planning stages can be applied to the efforts of State agencies to become even more effective in purchasing managed care services for Medicaid beneficiaries. This final rule provides an opportunity to clarify for MCOs, beneficiaries, and State agencies, how these advances in the management and oversight of health care can be applied to Medicaid managed care programs. </P>
                    <P>Through these regulations, we promote uniform national application of knowledge and best practices learned from these initiatives. While we promote uniform best practice, the Medicaid statute has always given State agencies latitude to design their Medicaid programs, as long as they meet certain minimum Federal standards. Current Federal requirements in the Medicaid managed care area are imposed either as conditions for Federal matching funds to support contracts with MCOs, as conditions for receiving a waiver of freedom of choice under section 1915(b) of the Act, or as conditions for falling within the section 1932 exception to the freedom of choice requirement in section 1902(a)(23) of the Act. In the first case, failure to comply with section 1932 requirements could result in a disallowance of Federal financial participation (FFP) in contract payments. In the latter two cases, if the State fails to meet conditions for the section 1932 exception to the freedom-of-choice requirement in section 1902(a)(23), or has its section 1915(b) waiver nonrenewed or terminated for a failure to meet waiver conditions, the State agency would be out of compliance with the freedom of choice requirement in section 1902(a)(23), and the State agency would be subject to a compliance enforcement action under section 1904 of the Act. </P>
                    <P>Because the Medicaid program is a State-administered program subject to Federal guidance and rules, Medicaid regulations do not generally adopt the same approach to regulating managed care organizations as Federal Medicare regulations. Instead, Medicaid rules generally regulate State agencies and place requirements on their contracts with managed care organizations or managed care programs. This final rule adopts this direction in implementing the new requirements in the BBA. </P>
                    <P>Section 4710(c) of the BBA provided for a time-limited exemption from the requirements in sections 4701 through 4710 for approved waiver programs or demonstration projects under the authority of sections 1115 or 1915(b) of the Act. Specifically, the BBA in section 4710(c) provided that none of the provisions contained in sections 4701 through 4710 would affect the terms and conditions of any approved section 1915(b) waiver or demonstration project under section 1115, as the waiver or demonstration project was in effect on the date of the enactment of the BBA (that is, August 5, 1997.) We interpreted this “grandfather provision” to apply only for the period for which the waiver or demonstration project was approved as of August 5, 1997. Thus, at the expiration of any 2-year waiver period under section 1915(b), or at the end of the period for which a demonstration project was approved under section 1115, the grandfather provision in section 4710(c) would no longer apply. </P>
                    <P>In general, during the period approved as of August 5, 1997, any provision of a State's approved section 1115 or section 1915(b) waiver program that was specifically addressed in the State's waiver proposal, statutory waivers, special terms and conditions, operational protocol, or other official State policy or procedures approved by us, was not affected by the BBA provisions, even if it differed from the BBA managed care requirements. As long as the BBA provisions were addressed in the State's approved waiver materials, no determination needed to be made as to whether the State's policy or procedures meet or exceeded the BBA requirements. If the BBA provisions were not addressed, the State was required to meet the BBA requirements, except as specified below for newly submitted or amended waivers. </P>
                    <P>
                        As noted above, under our interpretation, the exemption from the BBA requirements applied to section 1915(b) waiver programs only until the date that the waiver authority approved or in effect as of August 5, 1997 expired, which in all cases occurred no later than 
                        <PRTPAGE P="40994"/>
                        1999. As of the date of the two year section 1915(b) waiver period approved on August 5, 1997 expired, the State was required to comply with all BBA requirements that in effect. 
                    </P>
                    <P>In the case of section 1115 demonstrations, while the “grandfather” provision in section 4710(c) only applies until the end of the period for which the demonstration project was approved as of August 5, 1997, if the demonstration project has been extended under the provisions in section 1115(e) of the Act, existing terms and conditions inconsistent with BBA requirements are extended for three years, nullifying the effect of the “expiration” of the grandfather provision in section 4710(c). Therefore, any exemptions from the BBA requirements to which these programs were entitled under the “grandfather provision” may continue during the period of the extended waiver authority. </P>
                    <P>The Medicare, Medicaid, and State Child Health Insurance Program Benefits Improvement and Protection Act of 2000 (BIPA), enacted on December 21, 2000 (Pub. L. 106-554) provided for additional extensions of section 1115 health care reform demonstrations, but did not include language extending the same terms and conditions through this period. Thus, we conclude that provisions of the BBA would apply to the demonstrations in these extension periods under BIPA as well as all other demonstrations in extensions under any authority other than section 1115(e)(2), unless the Secretary uses his discretionary authority to waive the requirements. </P>
                    <P>For newly submitted or amended section 1915(b) or section 1115 waivers, the Secretary retains the discretionary authority to waive the BBA managed care provisions. Generally, waivers are granted that allow States some flexibility in operating their Medicaid programs, while promoting the proper and efficient administration of a State's plan. In particular, for the BBA provisions related to increased beneficiary protections and quality assurance standards, we anticipate that the BBA provisions would apply unless a State can demonstrate that a waiver program beneficiary protection or quality standard would equal or exceed the BBA requirement.</P>
                    <HD SOURCE="HD1">II. Provisions of the Proposed Rule and Analysis of and Response to Public Comments </HD>
                    <P>We received comments from 387 States, national and State organizations, health plans, advocacy groups and other individuals on the August 20, 2001 proposed rule. The comments were extensive and generally pertained to the new rate-setting provisions, the quality requirements and the grievance system requirements contained in the proposed rule. We carefully reviewed all of the comments and revisited the policies contained in the proposed rule that related to the comments. This final rule responds to these comments. In the following discussion, we present a summary of the proposed provisions and our responses to the public comments. </P>
                    <P>In the proposed rule, we set forth the new organizational format for part 438 as follows: </P>
                    <FP SOURCE="FP-1">Subpart A—General Provisions </FP>
                    <FP SOURCE="FP-1">Subpart B—State Responsibilities </FP>
                    <FP SOURCE="FP-1">Subpart C—Enrollee Rights and Protections </FP>
                    <FP SOURCE="FP-1">Subpart D—Quality Assessment and Performance Improvement </FP>
                    <FP SOURCE="FP-1">Subpart E—[Reserved] </FP>
                    <FP SOURCE="FP-1">Subpart F—Grievance System </FP>
                    <FP SOURCE="FP-1">Subpart G [Reserved] </FP>
                    <FP SOURCE="FP-1">Subpart H—Certifications and Program Integrity</FP>
                    <FP SOURCE="FP-1">Subpart I—Sanctions </FP>
                    <FP SOURCE="FP-1">Subpart J—Conditions for Federal Financial Participation </FP>
                    <HD SOURCE="HD2">A. General Provisions (Subpart A) </HD>
                    <HD SOURCE="HD3">1. Basis and Scope (Proposed § 438.1) </HD>
                    <P>Section 438.1 of the proposed regulation set forth the basis and scope of part 438 including the fact that regulations in this part implement authority in sections 1902(a)(4), 1903(m), 1905(t), and 1932 of the Act. Proposed § 438.1 also briefly described these statutory provisions. </P>
                    <HD SOURCE="HD3">2. Definitions (Proposed §§ 400.203, 438.2, 430.5) </HD>
                    <P>Sections 400.203, 438.2 and 430.5 of the proposed rule included definitions of terms that would apply for purposes of proposed part 438. In reviewing the definitions in this section of the proposed rule, we recognized that the current definition of health insuring organization (HIO) is confusing, and not useful to the reader. The current definition encompasses entities that also meet the definition of managed care organization (MCO), and are subject to MCO requirements. This is because the language in section 1903(m)(2)(A) contemplates that there would be HIOs that are subject to the requirements in that section, including the requirement that the HIO meet the definition of MCO. (The introductory clause to the requirements in section 1903(m)(2)(A) includes the parenthetical “including a health insuring organization.”)</P>
                    <P>This language dates to a time when HIOs that arranged for care were exempt from the MCO requirements in section 1903(m)(2)(A). Specifically, the language was added in 1985 legislation (the Consolidated Omnibus Budget Reconciliation Act of 1985 (COBRA)) that “grandfathered” this exemption for HIOs operating before January 1, 1986. The parenthetical language was designed to make clear that other “HIOs” would be subject to 1903(m)(2)(A) requirements. Because one of the requirements of section 1903(m)(2)(A) is meeting the definition of MCO, any entity in this latter category would be covered by references in the regulations to MCOs. Thus, the term HIO has no legal significance for these entities. The term HIO is only relevant insofar as an exemption from section 1903(m)(2)(A) uses this term to refer to the exempt entity. </P>
                    <P>In the Omnibus Budget Reconciliation Act of 1990 (OBRA 90), the Congress again used the term HIO, in exempting certain county-operated entities in California from section 1903(m)(2)(A) requirements. After these amendments, the term HIO is only legally relevant for purposes of identifying this new group of exempt entities, and the entities grandfathered in COBRA. For this reason, and to avoid confusion, in this final rule, we are changing the definition of HIO to refer only to these section 1903(m)(2)(A)-exempt entities for which the term has continuing legal relevance. This change has no effect on any entities' rights or obligations. </P>
                    <P>Also among these definitions are new definitions of a “Prepaid Inpatient Health Plan” (PIHP) and a “Prepaid Ambulatory Health Plan” (PAHP). These new definitions divide the definition of “Prepaid Health Plan” (PHP) in the January 19, 2001 final rule into two subcategories of PHPs, to which different regulatory requirements would apply in this final rule. PIHPs are entities that provide some inpatient services, and would be subject to more requirements than PAHPs, which do not provide inpatient services. We received the following comments on the proposed definitions in the proposed rule, including the new proposed definitions of PIHP and PAHP. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern that the proposed definition of “provider” included in § 400.203 encompasses all entities and individuals engaged in, or arranging for, the delivery of a medical service in a managed care delivery system. The commenter believed that this broad definition creates a problem when applied in proposed § 438.214(b), which requires the credentialing of providers who participate with an MCO or PIHP. The commenter contended that including all 
                        <PRTPAGE P="40995"/>
                        ancillary and non-licensed providers under this credentialing requirement goes far beyond current industry standards that apply only to licensed health professionals such as physicians, psychologists, podiatrists, and mid-level practitioners. The commenter suggested limiting the scope of the requirements in § 438.214(b) to those health professionals that are engaged in the delivery of direct patient care and are licensed within their State. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The definition of “provider” as published in our proposed rule, mirrors the definition of provider used in the Medicare+Choice regulations. However, to further clarify the definition in the proposed rule, and to be consistent with the definition of “physician” used in section 1861(r)(1) of the Act, we revised the definition of “provider” to be “any individual or entity that is engaged in the delivery of health care services and is legally authorized to do so by the State in which it delivers the services.” We believe that the proposed definition is correct, and the requirements that States have a process for credentialing and recredentialing all individuals involved in the delivery of health care services is an appropriate beneficiary protection. There is no requirement that the process be the same for each provider type within a network, only that there be a process in place. Further, this definition provides States the flexibility to determine what State requirements any provider must meet (for example, licensure and certification requirements) in order to provide services under managed care arrangement, and allows States, at their option, to include licensure or certification requirements imposed by tribal governments. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that we add the definition of health care professional in § 438.102 to this section. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Proposed § 438.102(a) contains the statutory definition of health care professional found in section 1932(b)(3)(C) of the Act, which specifically applies to the provisions governing enrollee-provider communications. However, in light of the fact that this term is also used for other purposes throughout part 438, we agree with the commenter that the definition of health care professional in proposed § 438.102 should be moved to § 438.2, and have done so. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A large number of commenters opposed the separation of PHPs into PIHPs and PAHPs. Some felt that we had not provided sufficient reasons for making this distinction, that the primary purpose of the change was to exempt a broad catch-all category of PAHPs from regulatory standards, and argued that defining the entity and the level of regulation based on the scope of the services provided was not logical, and could deny beneficiaries needed protections. These commenters felt that this distinction could jeopardize the quality and consistency of health care, particularly for women, due to the PAHPs' exemption from anti-discrimination provisions, State quality strategies, adequate service and capacity requirements and grievance and appeal rights. The commenters further noted that the January 19, 2001 final rule would apply to all PHPs. Several commenters felt that the new definitions could lead to gaming by contractors and create an incentive for MCOs or PIHPs to carve out various services (for example, inpatient hospital services) in order to limit the degree to which they are regulated. One commenter suggested that the term PAHP be more clearly defined, or limited to a specific set of non-medical or non-health care services, in order to prevent such carve-outs. 
                    </P>
                    <P>Some commenters wanted to return to the original PHP definition and subject all PHPs to all MCO requirements, while others suggested keeping the current PHP definition but allowing for individual rules to be relaxed where they are inapplicable. </P>
                    <P>Other commenters supported making the distinction between types of PHPs and believed that basing this distinction on the scope of services is a useful way to distinguish between requirements that are relevant to each contracting arrangement, and to provide the flexibility needed to appropriately regulate each type of contractor. </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the distinction between types of PHPs established in the proposed rule is appropriate and we will maintain the separate definition of PIHP and PAHP in this final rule. There are clear differences in terms of the degree of financial risk, contractual obligation, scope of services, and capitation rates paid to these different types of entities. The distinction between PIHPs and PAHPs based upon the scope of services in their contract is modeled after the requirement in section 1903(m)(2)(A) of the Act, which defines the scope of contracted services that requires an MCO. This scope of services is set forth in § 438.2, which defines comprehensive risk contract as a risk contract that covers inpatient hospital services and any of the following services, or any three or more of the following services: (1) Outpatient hospital services; (2) Rural health clinic services; (3) FQHC services; (4) Other laboratory and X-ray services; (5) Nursing facility (NF) services; (6) Early and periodic screening diagnostic, and treatment (EPSDT) services; (7) Family planning services; (8) Physician services; or (9) Home health services. 
                    </P>
                    <P>PHPs were originally designated by regulation as entities that incurred risk for a lesser scope of services. Since that time, the PHP definition has been expanded to include a scope of services that would have required an MCO, except that their contracts covered only a portion of inpatient hospital services (for example, inpatient mental health services) rather than all inpatient hospital care. These entities incurred far greater risk, were obligated to provide a greater range of services, and have greater responsibility for the beneficiary care than the early PHPs, which were predominantly capitated primary care physicians and physician groups at risk for the cost of physician and one other outpatient Medicaid service. </P>
                    <P>Recognizing that the scope of contractual responsibility for these larger PHPs, now designated PIHPs, was far more like the responsibilities in MCO contracts, we have imposed most MCO requirements on these entities. The PAHP designation allows us to impose requirements on this smaller group that are more appropriate to the scope of services they are obligated to provide. Not only do we believe it is unnecessary to subject prepaid dental plans, transportation providers, and capitated primary care case managers to the same standards as MCOs and PIHPs, it is not logical to impose the same administrative burdens on contractors who receive a fraction of the amount in capitation rates that MCOs and PIHPs are paid. Further, for these types of entities, access to care could be negatively impacted by the imposition of inappropriate levels of administrative burdens. </P>
                    <P>Further, we do not believe it likely that MCOs and PIHPs that contract with States will arbitrarily reduce the benefit package they provide in order to limit the degree to which they are regulated. First, much of the savings to be achieved from managed care come from reductions in the cost of inpatient care for beneficiaries, and a contractor would not likely choose to carve-out the source of most of their potential savings. Neither is it to the State's advantage to permit such carve-outs, since the State would then be obligated to assume all responsibilities for coordination of care required under Subpart D that would otherwise be the contractor's responsibility. </P>
                    <P>
                        Finally, we believe that the distinction is clear between PIHPs and PAHPs and MCOs. If an entity has less-
                        <PRTPAGE P="40996"/>
                        than a comprehensive risk contract, but has any responsibility for an enrollee's inpatient hospital or institutional care, it is a PIHP and subject to all PIHP requirements. However, as discussed below, in § 438.8 we have expanded the requirements that apply to PAHPs, as described in that section. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters felt that many PHPs that provide a comprehensive range of services; (for example, outpatient services, including primary care, mental health care, reproductive health care, and/or HIV services), but do not provide inpatient care should not be exempt from the managed care requirements in the proposed rule. One commenter asked whether an entity responsible only for behavioral health services (inpatient and outpatient) is considered a PIHP. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In making the distinction between PIHPs and PAHPs, we have not changed current policy under which entities that contract for a subset of inpatient and outpatient care, as with behavioral health carve-outs, do not have comprehensive risk contracts subject to the statutory requirements that apply to MCOs. Thus, in answer to the commenters' question, such a behavioral health contractor is a PIHP (due to its provision of some inpatient services), not an MCO. Similarly, the definition of comprehensive risk contract in section 1903(m)(2)(A) of the Act has not changed, so that an entity that is at risk for inpatient hospital services generally, and any one of the other specified services, or three or more of the services identified in the definition of comprehensive risk contract, falls under the MCO requirements in section 1903(m)(2)(A). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters argued that ambulatory and community-based plans should not be exempt from essential protections, while others felt that these programs did not need to be included as PIHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are not expanding the PIHP definition to include these programs. If these programs are responsible for institutional care, they will be subject to PIHP requirements. Otherwise, we believe their scope of risk and operations for these programs are more like PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that the use of the terms PIHP and PAHP would permit States to mandate enrollment in PIHPs and PAHPs of populations who were exempted from mandatory enrollment in MCOs and PCCMs under the authority in section 1932(a). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The authority in section 1932(a)(1) of the Act and proposed § 438.50 permitting States to mandate managed care enrollment through a State plan amendment does not extend to certain specified groups of beneficiaries who are exempted from having managed care enrollment mandated under that provision. In addition, the authority in section 1932(a)(1) is limited to mandating enrollment in MCOs and PCCMs, and does not give States authority to mandate enrollment in either PIHPs or PAHPs, unless the PAHP qualifies as both a PCCM and a PAHP. But, this would still not permit the mandatory enrollment of the exempted groups under section 1932(a). However, the exemption of certain populations from mandatory enrollment under section 1932(a)(1) applies only to enrollment under the new authority in that section, and did not preclude the mandatory enrollment of these groups of beneficiaries in MCOs, PCCMs, PIHPs, or PAHPs under existing authority in sections 1115 or 1915(b) of the Act. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believes that the definition of “primary care” should include services provided by a Master of Social Work, psychologist, psychiatrist, physician assistant, advanced registered nurse practitioner, or other health care professional. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The definition of primary care in this section is taken from section 1905(t)(4) of the Act, which specifically identifies the services that the Congress intended to be included as primary care. We do not believe adding the services suggested by the commenter would be an appropriate extension of this section of the Act. We note, however, that States have the option of using physician assistants, certified nurse midwives, and nurse practitioners as primary care case managers, although the primary care services they provide would still be as defined in this section. 
                    </P>
                    <HD SOURCE="HD3">3. Contract Requirements (Proposed § 438.6) </HD>
                    <P>Proposed § 438.6 set forth rules governing contracts with MCOs, PIHPs, PAHPs and PCCMs. Paragraph (a) of proposed § 438.6 required the CMS Regional Office to review and approve all MCO, PIHP and PAHP contracts, including those that are not subject to the statutory prior approval requirement implemented in § 438.806. Paragraph (b) set forth the entities with which a State may enter into a comprehensive risk contract. Paragraph (c) proposed new rules governing payments under risk contracts, to replace the upper payment limit in § 447.361. Paragraph (d) contained requirements regarding enrollment; that enrollments be accepted in the order of application up to capacity limits, that enrollment be voluntary unless specified exceptions apply, and that beneficiaries not be discriminated against based on health status. Paragraph (e) provided that MCOs, PIHPs, and PAHPs can cover services for enrollees in addition to those covered under the State plan. Paragraph (f) required that contracts must meet the requirements in § 438.6. Paragraph (g) required that risk contracts provide that the State and HHS have access to financial records of contractors and subcontractors. Paragraph (h) required compliance with physician incentive plan requirements in §§ 422.208 and 422.210. Paragraph (i) required compliance with advance directive requirements. Paragraph (j) provided that with certain exceptions, HIOs are subject to MCO requirements. Paragraph (k) proposed new rules from section 1905(t)(3) of the Act that apply to contracts with primary care case managers. Paragraph (l) and (m) set forth existing requirements for subcontracts and enrollees' right to choice of health professional to the extent possible and appropriate, respectively. Because of the volume of comments we received on this section, we have grouped our comments and responses according to the paragraph designation. We note that we did not receive comments on paragraphs (a), (b), (d), (h) and (j) of this section and are therefore implementing those provisions as proposed. </P>
                    <HD SOURCE="HD3">• Payment Under Risk Contracts (Proposed § 438.6(c)) </HD>
                    <HD SOURCE="HD2">General Comments </HD>
                    <P>This section proposed new rules to replace the upper payment limit (UPL) for risk contracts in § 447.361, which is being repealed as part of this final rule. The new rules require actuarial certification of capitation rates; specify data elements that must be included in the methodology used to set capitation rates; require States to consider the costs for individuals with special health care needs or catastrophic claims in developing rates; require States to provide explanations of risk sharing or incentive methodologies; and impose special rules, including a limitation on the amount that can be paid in FFP under some of these arrangements. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Nearly all commenters expressed strong support for replacing the UPL with an actuarial process and methodology requirement. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support. We have been working for several years to move away from the UPL requirement for risk-based managed care contracts and appreciates the input it has received from a number of sources including States, managed 
                        <PRTPAGE P="40997"/>
                        care entities, actuaries, and various organizations in this process. There was a broad consensus among these parties to eliminate the UPL requirement. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters wanted us to allocate additional resources to ensure that the agency has the necessary expertise to review rates and to provide technical assistance to States in order to implement the new rate setting process. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have been providing training and tools to review payment rates under these rules to our regional office personnel who are responsible for the review all of the MCO, PIHP, and PAHP risk contracts using this new methodology. The rate review checklists to be used by our regional offices are available from CMS regional offices. Section 1903(k) of the Act specifically authorizes us to provide this assistance to States at no cost, although most States have currently elected to contract with their own actuaries. If States request this assistance as these new requirements are implemented, we will provide it. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked what appeals process is available for rate disputes. Another commenter recommended that we establish a mechanism to mediate disputes between MCOs and States over rates similar to the mediation process currently used in one State, involving: (1) Meetings between State and MCO actuaries where there is a dispute, during which the parties identify areas of continued disagreement; and (2) selection of a mutually acceptable independent actuary to mediate the dispute and make his/her (non-binding) findings available to the State and MCO. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Some States have formal processes for appeals or dispute resolution on payment rates, while in others there may be a more informal process for this purpose. While we support these mechanisms to emphasize the partnership between States and MCOs in Medicaid managed care, and believe they may help to sustain the viability of these programs, we do not believe it would be appropriate for the Federal government to impose specific requirements on States. Rather, we believe that a State should have the flexibility to provide for the processes that works best for that State. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters believed that State rate setting processes should be more open, and that States should be required to disclose core data assumptions regarding the State's rate setting methodology, utilization data for each rate category, and trend factors used. Several other commenters suggested that we require States (other than those using a competitive bidding process) to disclose sufficient information to permit MCOs to replicate the calculation of proposed rates, including the unit cost and utilization assumptions used and assumptions used in calculating administrative cost and retention factors. These commenters believe that this sharing of information will permit informed discussions between States and MCOs in the process and increase the continued viability of Medicaid managed care programs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that sharing information in a negotiated rate setting process to the extent possible is a good way to enhance the partnership between States and MCOs and to maintain the viability of a State's Medicaid managed care program. However, we recognize that this will not always be possible and may not be a preferred contracting approach in some markets, even where competitive bidding is not the rate setting mechanism used by a State. Consequently, we are not willing to impose a Federal requirement that certain information be shared, and continue to believe that MCOs, PIHPs, and PAHPs contracting with States on a risk basis must make their own independent judgments of proposed rates based on their own costs of doing business and their understanding of the population to be covered. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked how States would be required under the new rules to make payment adjustments to account for changes in trends or new administrative requirements that occur between legislative sessions or contract renewals.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Contracts may be of varying lengths, but any changes to the terms of a contract during that period require a contract amendment that must be reviewed and approved by us. FFP is available for such amended contracts only after both parties have agreed to the changes and CMS has approved the contract amendment. We will not require States to amend contracts due to changes in such things as trends in inflation rates, unless payment rates are changed as a result. However, we believe that changes in the services to be provided or the administrative requirements in a contract would warrant changes in payment rates to reflect the expected impact of the required change in services or administration. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter asked what would occur if a State refuses to pay rates that have been approved by CMS as actuarially sound. The commenter wanted to know how we would enforce these rates. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We only review the rates that are submitted by States as part of the contract review process. We believe it would be unlikely that States would submit capitation rates for contract approval, and then not pay the approved rates. In the event that this were to occur, and be documented, the State would be subject to a disallowance of FFP for failing to comply with the requirement in section 1903(m)(2)(A)(iii) that rates be actuarially sound. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned that eliminating the UPL and requiring actuarially sound capitation rates may increase the burden if States need to continue to calculate a UPL to determine cost effectiveness. Another commenter noted that we had indicated in the proposed rule that we would issue a revised methodology for determining the cost effectiveness of section 1915(b) waivers, and wanted to know (1) when waiver applications would be modified to contain the new methodology and (2) how States are to document cost effectiveness in the interim. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not wish to impose additional burden on States in moving from the UPL test to a rule that requires an actuarially sound methodology as set forth in this final rule. As the commenter noted, we are issuing new cost effectiveness requirements for section 1915(b) waiver applications for both new and existing waivers, which will more closely correspond to the principles in the new rate setting guidelines. We expect to issue new guidelines for cost effectiveness before the effective date of this regulation, and will attempt in these guidelines to reduce the burden on States in documenting the cost effectiveness of these waiver programs. Recognizing the difficulty in changing long-standing methodologies in both setting rates and documenting cost effectiveness, we will permit States to use either the current methodology with its FFS comparison, or the rate setting process in this regulation in the period between the effective date of these rules and the final implementation date. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked if we have any guidelines or regulations on the length of time FFS data must be retained, since these data still have some use in setting capitation rates. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that FFS data are one of the possible sources for establishing base year costs and utilization under this rule. However, one of the reasons for moving to the new rate setting rules, and away from the UPL requirement, is that FFS data loses its validity for this purpose as it becomes older. We are not establishing any rule as to the age of data used for rate setting purposes, since we would 
                        <PRTPAGE P="40998"/>
                        rely on an actuarial certification that the data used had sufficient validity for this purpose. For the retention of FFS data in general, § 433.32(b) and (c) require States to retain records, such as FFS data, for 3 years from the date of submission of a final expenditure report (or longer of audit findings have not been resolved). We believe that these data have value for rate setting purposes beyond the time period they are required to be retained under that regulation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that requirements for actuarial soundness extend to payment rates between MCOs and subcontracting providers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Except in the case of payments to FQHCs that subcontract with MCOs, which are governed by section 1903(m)(2)(A)(ix), we do not regulate the payment rates between MCOs and subcontracting providers. While section 1903(m)(2)(A)(iii) requires that payments to MCOs be actuarially sound, other than in the case of FQHCs, the Congress has not established any standards for payments to subcontractors. We believe that this is because one of the efficiencies of managed care is premised on an MCO's ability to negotiate favorable payment rates with network providers. MCOs must pay sufficient rates to guarantee that their networks meet the access requirements in subpart C of this final rule. We believe that payment rates are adequate to the extent the MCO has documented the adequacy of its network. 
                    </P>
                    <HD SOURCE="HD2">Definition of Actuarially Sound Capitation Rates </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters believed that CMS should go beyond simply defining an actuarially sound process, and instead should establish prescriptive standards for actuarial soundness. Some commenters believed that the definition of “actuarially sound capitation rates” should include the concept that rates be sufficient to cover the reasonable costs of the MCO. Other commenters suggested that we adopt the definition of actuarial soundness adopted by the Health Committee of the Actuarial Standards Board in the context of the small group market, which requires that payments “are adequate to provide for all expected costs, including health benefits, health benefit settlement expenses, marketing and administrative expenses, and the cost of capital. Another commenter believed the definition of actuarially sound rate setting should be replaced with language similar to the following: rates are determined using generally accepted actuarial methods based on analyses of historical State contractual rates and an MCO's experience in providing heath care for the eligible populations, and are paid based on legislative allocations for the Medicaid program. Several other commenters supported our proposed approach requiring that rates be developed using accepted actuarial principles and practices. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As discussed in detail below, we considered various approaches in defining actuarial soundness, but decided that basing the definition on a methodology that uses accepted actuarial principles and practices, and that is certified by a member of the American Academy of Actuaries, is the best approach in that it gives States and actuaries maximum flexibility while still ensuring that rates be certified as actuarially sound.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters wanted the actuarial soundness test at § 438.6(c)(1)(i) to be revised to require that payment rates be adequate to cover the actual cost of services to be provided, and wanted us to take a more active role in assuring the adequacy of rates, including; (1) Reviewing key components and underlying assumptions of the rates, rather than accepting an actuary's certification; (2) ensuring proper adjustment and enforcement of the payment rules; (3) disapproving rates determined to be inadequate; (4) requiring disclosure of rate calculation inputs; and (5) resolving rate calculation disputes between MCOs and States. In contrast, several other commenters believed that we had gone too far in establishing a standard for rate adequacy that would be difficult to administer and justify. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While, as indicated above, there was a consensus among commenters on the need to replace the UPL requirement, there were a wide variety of opinions among commenters on requirements to replace it. In the proposed rule, we sought to strike a balance between merely accepting State assurances on capitation rates in risk contracts on one hand, and requiring that the amounts of the capitation rates paid in each contract meet specific requirements for reasonableness and adequacy on the other. Under the former concept, we did not believe that we would meet our statutory responsibility to ensure that rates are actuarially sound as required under section 1903(m)(2)(A)(iii). Under the latter format, we would be establishing standards for reasonableness and adequacy of rates, which: (1) Would require that a determination be made on every rate cell in each risk contract submitted to us for review; (2) would require that we obtain sufficient actuarial expertise to review every risk contract in Medicaid managed care; and (3) would establish a new “reasonable and adequate” payment standard for Medicaid managed care when, in the BBA, the Congress amended title XIX to eliminate a similar requirement for Medicaid payments to institutional providers. 
                    </P>
                    <P>As a result of these considerations, we have established a requirement that payment rates in risk contracts be actuarially sound, that is, that they have been developed in accordance with generally accepted actuarial principles and practices, are appropriate for the populations and services under the contract, and have been certified by an actuary as meeting the requirements in this rule and the standards of the Actuarial Standards Board. This rule then sets forth the basic requirements that States must apply in setting capitation rates, and the documentation that States must provide to us to support their rate setting process. We believe that by reviewing the process used in setting the rates under a risk contract, we will fulfill our regulatory responsibilities to the fiscal integrity of the Medicaid program and will assure that States have considered all relevant factors in this process. We believe that MCOs, PIHPs, and PAHPs, that contract with States on a risk basis, are better able to determine whether rates are reasonable and adequate, and will do so in deciding whether or not to agree to contract or continue to contract with a State to provide services as part of a Medicaid managed care program. </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter believed that we should acknowledge that actuarially sound rates may vary between MCOs in the same service area. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge that rates may differ between MCOs in the same area for a variety of reasons, but most often when States utilize risk adjustment based upon health status or diagnosis. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked whether the actuarial soundness requirement applies only to capitation rates under an entire contract, or to each rate cell under the contract. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirement in proposed § 438.6(c)(2)(i) that 
                        <E T="03">all</E>
                         capitation rates paid under risk contracts and all risk sharing mechanisms in the contracts must be actuarially sound applies this requirement to all rate cells, as well as the entire contract, and all payments made under the contract. This is a change from the UPL requirement where individual rate cells within the contract 
                        <PRTPAGE P="40999"/>
                        could exceed the UPL as long as the entire contract did not exceed the UPL. In order to clarify that the requirement for actuarial soundness applies to 
                        <E T="03">all</E>
                         payments, we are replacing the phrase “capitation rates paid” in proposed § 438.6(c)(2)(i) with the word “payments.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that the requirement that rates be “appropriate” for the population and services to be covered under the contract to be too vague, and subject to being interpreted by some to mean covering the full cost of care at billed charges. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The term “appropriate” as used in this paragraph is merely intended to illustrate the requirements that follow in the remainder of § 438.6. “Appropriate for populations covered” means that the rates are based upon specific populations, by eligibility category, age, gender, locality, and other distinctions decided by the State. “Appropriate to the services to be covered” means that the rates must be based upon the State plan services to be provided under the contract. There is no stated or implied requirement that MCOs be reimbursed the full cost of care at billed charges. 
                    </P>
                    <HD SOURCE="HD2">Basic Requirements </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter wanted us to define the term “actuarial basis,” as used in § 438.06(c)(2)(ii), and provide sample contract language to implement this provision. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         “Actuarial basis” as used in § 438.06(c)(2)(ii) merely refers to the principles and assumptions used by the actuary in computing the rates in the contract. We do not believe it is necessary to define this term in the text of the regulation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned about meeting the requirements of § 438.6(c)(2)(ii), which provides that the contract must specify the capitation rates that are paid. Specifically, the commenter asked if States would be able to submit final rates in an addendum to the contract when the rates are developed after the rest of the contract is implemented. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In answer to the commenter's question, rates must be part of the contract that is approved by us as part of the contract approval process that is a pre-condition for FFP § 438.806 in the case of comprehensive risk contracts with MCOs. If rates are not yet agreed upon between the State and the contractor at the time the remainder of the contract is approved, the State could operate under the payment rates that were previously approved by us, although FFP would not be available in new payment rates until they are approved as well. If the contract is a renewal or extension of a previously approved contract, FFP could be claimed and payments made based the rates in the previously approved contract, until an addendum to that contract with new rates and the supporting documentation required by this section of the regulations is approved. 
                    </P>
                    <HD SOURCE="HD2">Requirements for Actuarially Sound Rates </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters believe that we should clarify that this provision does not preclude States from using additional elements, such as case-rate type payments (for pregnant women or others) and family-based rate cells as long as they are consistent with other requirements. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirements in this section are not meant to be all inclusive. States are required either to apply the elements in § 438.6(c)(3), or to explain why they are not applicable. Examples of reasons that these elements would not be applicable would include the State's use of case-rate type methodologies or other rate setting methods, that still meet the test for actuarial soundness, or where the rate cells broken down to this level are not large enough to be statistically valid. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters wanted us to require States to explain how they have taken into account: Potential data inaccuracy due to lack of historical Medicaid managed care data for a new population or service; potential data inaccuracy due to reasonably anticipated under-reporting; and other similar data shortcomings that may be reasonably foreseeable.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters that these are important factors in determining payment rates. The adjustments required to smooth data should include adjustments for incomplete data, whether due to incurred-but-not-reported expenditures, delays in claims submission, or other factors. In response to this comment, we are adding data completion factors to § 438.6(c)(3)(ii) as one of the required data smoothing adjustments. However, we believe that this is not the only mechanism that could be used to account for unexpected costs of new populations or services, and that these issues are better addressed through risk adjustment or risk sharing provisions in the contract. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters wanted us to require States to identify their method for compensating MCOs for changes in obligations imposed on the MCOs during a contract year, so that new requirements cannot be imposed while payment rates remain unchanged. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The terms of a contract must be agreed upon by both parties in order for the contract to be in effect, as required by § 438.802(a)(2). One option is for the contract to include a term providing for an increase in payment in the event there are changes in the MCO's obligation (for example, if the contract binds the MCO to cover all State plan services, and services are added to a State plan mid-year). Absent such a provision, the contract would have to be amended in order for payment to be increased to cover new obligations. Any such amendment would have to be approved by us. We will not review and approve those amendments unless both parties, that is, the State and the MCO, PIHP, or PAHP have agreed to the new terms. Thus, we believe that the issue of how changes in contractual obligations are addressed should be the subject of negotiation between the parties, who are in the best position to agree upon an approach that works in their situation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked whether States will have the flexibility to take into account their FFS budgets, and managed care budget authority, when developing actuarially sound rates. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We understand the fact that all Medicaid programs are subject to budgets set by the governor and/or the State legislature, and that this obviously must be taken into account in negotiating rates with MCOs, as well as in deciding whether the State can afford to do so. In some cases, there may be insufficient funding to begin or to continue a Medicaid managed care program. We are not in a position to determine if and when a State may have insufficient funding. The Medicaid agency may determine this in advance, or as the result of being unable to attract contractors who are willing to operate a managed care program for the payment rates that the State is able to pay. When contracts are submitted to us for review and approval, the determination of whether adequate funding is available has already been made, in that the State has an agreement with one or more managed care entities and has determined that these entities can meet the contractual obligations to be imposed on them. The managed care entities have determined that the rates they are to be paid are adequate to meet their obligations under the contract. We do not have the authority to change the way States budget for their Medicaid programs in this final rule. We will use our authority to review and approve rates in risk contracts based on the 
                        <PRTPAGE P="41000"/>
                        actuarial certification and the documentation provided showing that the requirements in this section are met. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked what sources we will accept as base utilization and cost data in determining actuarially sound rates (for example, FFS data, encounter data, MCO financial data) and most of these commenters believed that the rule should specify that these other sources are permissible. Another commenter asked who makes the determination as to whether “costs” are to be determined by FFS history, MCO experience, or other factors. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A State's FFS data would be the best source of baseline data, since they represent the most complete claims history available on the population to be covered under managed care, but only to the extent that the data are recent enough to be valid for this purpose. The fact that there is an increasing number of States that lack recent FFS data to use for rate setting is one of the main reasons that it has become necessary to repeal the UPL requirement. We agree that other sources, such as encounter data, need to be used for this purpose. However, we also recognize that not all States have even begun to collect encounter data, and that not all of those States that are collecting the data have yet developed mechanisms to ensure their validity. States without recent FFS history and no validated encounter data will need to develop other data sources for this purpose. States and their actuaries will have to decide which source of the data to use for this purpose, based on which source is determined to have the highest degree of reliability. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that experience data used to develop the base period medical cost should only be from the population being rated and categorized by the rate cells used.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In general, we agree with the commenter that the best source of base period data would be the population to be covered under the managed care contract, but as indicated above, this is not always possible. If the data are not available or usable, States must use other data for this purpose. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter wanted us to clarify that the phrase “derived from the Medicaid population” at § 438.6(c)(3)(i) means those Medicaid beneficiaries enrolled in MCOs. As set forth, this provision would permit the use of State FFS cost data, which may have understated cost assumptions, and inflation data, especially in the area of prescription drugs where MCOs are unable to negotiate prices comparable to those available to the States. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. The phrase “derived from the Medicaid population” means that the source of the base utilization and cost data is the historical utilization and cost data of the Medicaid eligibles to be covered under the managed care contract. These data may be derived from the FFS history, managed care history, or a combination of both. Regardless of the source, adjustments should be made to achieve a degree of predictability for the rates that are developed. The commenter's example of prescription drug costs represents one specific area where the new rate setting rules allow greater flexibility in rate setting than permitted previously. Under the UPL requirement, capitation rates in a contract could not exceed what would have been paid under FFS for the same services provided to a comparable population. For the prescription drug component of a capitation rate, this amount would have been net of the amount of drug rebates received by the State through its FFS system. Under the new rules, the component of the capitation rate for prescription drugs will not be limited by the UPL. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters wanted CMS to require States to provide information on base year costs by primary service category included in the contract, such as, pharmaceuticals, hospital, and physician services, and to clarify that these data will specifically include unit cost and utilization data as separate assumptions, in order to evaluate the adequacy of the rates. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States must report information on base year costs by the primary service category, at a minimum, for the primary services included in the contract. Further, we agree with the commenter that States should use separate assumptions with respect to unit cost and utilization data. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that the proposed regulation was unclear as to the adjustment factors to be used to make base period data comparable to the Medicaid population in cases in which data specific to the Medicaid population do not exist. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As discussed above, the best source of data for determining base period cost and utilization will have to be determined by the State and its actuaries, subject to CMS approval. States will also need to determine what adjustments are necessary to make data comparable to the Medicaid population if there are no usable Medicaid data available. We would expect these adjustments to be based upon a comparison of the population whose data are used to the State's Medicaid population in terms such as income, demographics, and historical medical costs. In instances where non-Medicaid data are used, the required actuarial certification will need to include an explanation of the adjustments used to make the data comparable. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters suggested that base year costs be trended forward by “medical” inflation, not just “inflation” as stated in the proposed rule, and that we should clarify this in the regulation text. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters, and in response to this comment have changed the regulation text at § 438.6(c)(3)(ii) accordingly. In making this change, we want to emphasize that the rate of medical inflation may be determined from such sources as the medical market basket or the State's historical Medicaid costs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters wanted the administrative adjustment to be expanded to require it to reflect an MCO's cost of complying with Medicaid managed care requirements in such areas as service delivery, reporting, and operational and accountability standards. These commenters argued that administrative costs would have to be significantly increased to comply with the quality provisions and other reporting requirements in this regulation, and that payment rates should reflect these costs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the capitation rate should include an administrative adjustment that recognizes administrative costs incurred by the contractor in providing the services to be delivered under the contract. However, we recognize that this adjustment may not necessarily fully compensate the contractor for its administrative costs under the contract, and potential contractors need to consider proposed payment rates in the aggregate, as to whether or not they will be sufficient to cover both the cost of services and the administrative costs it will incur under the terms of the contract. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked that we clarify how the limits in proposed § 438.6(c)(4)(ii) (regarding an assurance that all payment rates are based only upon services covered under the State plan) apply to the adjustments for inflation and administration in paragraph (c)(3)(ii), and whether we plan to issue guidelines on acceptable adjustment factors and any limits that will be in place. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The intent of this limitation in § 438.6(c)(4)(ii) is to prevent States from obtaining FFP for things such as State-funded services for which FFP would not ordinarily be available, by 
                        <PRTPAGE P="41001"/>
                        including them in an MCO, PIHP, or PAHP contract. This limitation is extended to the adjustments in paragraph (c)(3)(ii), so that the only administrative costs recognized are those associated with the MCO's, PIHP's, or PAHP's provision of State plan services to Medicaid enrollees. We do not intend to issue specific guidelines on these limits, as we believe that decisions will have to be made on a case-by-case basis. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters urged us to specify that risk or profit levels, along with an administrative component, should be included in actuarially sound rates, and that the adjustment requirement in § 438.6(c)(3)(ii) is not sufficient to achieve this purpose. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This is another area where we believe all MCOs, PIHPs, and PAHPs which intend to contract with States must consider proposed payment rates in the aggregate, as to whether or not the payments will be sufficient to cover the cost of all of their contractual obligations and their desired risk and profit levels as well. We do not believe it would be appropriate to establish standards for risk and profit levels. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that there are many other adjustments that should be applied beyond those listed in the proposed rule, such as adjustments for new procedures or technologies or the addition of new Medicaid benefits. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that there are other appropriate adjustments currently used by States in setting their capitation rates, and will approve those supported by the accompanying certification and documentation as contracts are reviewed and approved. However, we are not mandating any additional adjustments at this time. 
                    </P>
                    <P>For the addition of new Medicaid benefits, however, we believe that the inclusion of any additional Medicaid services during the term of a contract could either be handled through a contract amendment or a contract term that provides for the contingency, subject to CMS approval, subject to CMS approval.</P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters expressed concerns over the requirements in § 438.6(c)(3)(iii) that rate cells be specific to the enrolled population by eligibility category, age, gender, and locality or region. Some commenters asked whether this provision mandates the use of these specific breakouts in developing rate cells, and were concerned that requiring rate cells to be broken down to this level could result in rates in some small cells that are not actuarially sound in States with small populations. Other commenters wanted us to clarify that other types of rate cells, such as case rate or family-based cells are permissible.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It is our intent that, to the extent possible and practical, rate cells be broken down by these categories. The vast majority of capitation rates in Medicaid managed care contracts currently use these breakouts. However, we recognize that there are valid reasons why this breakout may not be appropriate or possible in a particular State—because of such factors as the size of the population, or because a decision has been made to use another methodology, which still complies with the overall requirement for actuarial soundness. For this reason, the introductory language in § 438.6(c)(3) requires States to apply the elements in setting their capitation rates, “or explain why they are not applicable.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters wanted us to specify the type of explanation it would accept for a State that does not use these adjustments, and quantify the burden on States to comply with this provision. One commenter asked whether the explanation could cover an entire managed care program, or whether the State had to separately justify every region or county where the program operates. One commenter wanted us to allow States to use an actuarially appropriate method that may include these cells as appropriate, without requiring the State to justify its approach during each rate-setting process. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the most obvious reason a State would not use rate cells broken out to this degree would be insufficient numbers of enrollees in any one category for the category to have statistical validity. Another example that would be accepted is the use of a different methodology such as case rates or family-based cells, provided the methodology still meets the other requirements of this section and has the required actuarial certification. These decisions will be made on a case-by-case basis, and we do not want to limit the flexibility States can have in developing new methodologies by specifying all allowable exceptions in this rule. On the other hand, these rate cells are the most commonly used breakouts in current Medicaid managed care contracts, and we believe that it is not unreasonable to require States to justify other methodologies if that is the approach they decide to use. 
                    </P>
                    <P>We disagree with the commenter that this requirement places any significant burden on States. Most States are already in compliance with the requirement. The remaining States should either be able to provide a simple justification for their alternative methodologies, or need to consider a different approach in setting their capitation rates. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter wanted us to add a requirement for rate cells by major category of service (that is, inpatient, outpatient, primary care specialist, pharmacy, medical supplies, ambulance and other). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that such a requirement would serve a useful purpose. It is important for contracting MCOs, PIHPs and PAHPs to know a payment amount per enrollee, but it is up to the contractor to determine how to allocate that amount at the provider (or service category) level. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters felt that the requirements in § 438.6(c)(3)(iv) were not clear. This provision required that there be payment mechanisms and assumptions recognizing higher than average medical costs for certain enrollees, for example, through risk adjustment, risk sharing, or other cost neutral methods. One commenter urged that we clarify that a rate setting method that uses utilization and cost data for populations that include individuals with chronic illness, disability, ongoing health care needs, or catastrophic claims already meets this requirement without additional adjustments, since the higher costs would be reflected in the enrollees' utilization. Another commenter questioned whether this rule requires health status or diagnosis-based risk adjustment, or other risk sharing methods. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The intent of this requirement is that contracts will have some mechanism selected to recognize the financial burden a contractor may incur as a result of enrollees who have much higher than normal health care costs, as a result of either a chronic or acute condition. The fact that the costs of these individuals are included in the aggregate data used for setting rates will not account for the costs to be incurred by a contractor that, due to adverse selection or other reasons, enrolls a disproportionately high number of these persons. Thus, we are requiring some mechanism for risk-sharing or risk adjustment to address this issue. Most MCO contracts currently use either stop-loss, risk corridors, reinsurance, health status-based risk adjusters, or some combination of these approaches. We have not mandated that any particular approach be adopted. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked how we define the terms “chronic illness”, “disability,” “ongoing health care 
                        <PRTPAGE P="41002"/>
                        needs,” and “catastrophic claims,” as used in § 438.6(c)(3)(iv), and whether these are the same individuals categorized as enrollees at risk of having special health care needs, as may be defined by States in § 438.208(b)(3).
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The individuals intended to be covered by this requirement would likely include those described as having special health care needs, but would not necessarily be limited to that group. This provision is also intended to address individuals for whom a contractor may incur short-term catastrophic claims, but who may not be defined by the State as having special health care needs. Further, the individuals referred to in this paragraph are identified by their medical costs, while the individuals referred to in § 438.208(b) are identified by their medical needs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked whether we intend to make risk adjustment by health status mandatory in the future, since we have indicated that risk adjustment is an appropriate smoothing factor for individuals with special health care needs, and has contracted to produce a guidance manual for States to use health-status risk adjustment. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenter is correct that we support the use of health status risk adjusters as one way of making capitation rates more predictable and accurate, and have contracted for technical assistance for States in developing and using payment systems that are risk adjusted based on health status or diagnosis, and will be providing a guidance manual for States to use for this purpose. However, each State will still need to determine whether it wishes to invest the extensive resources necessary to develop and utilize this type of risk adjustment system. We do not intend to mandate this requirement. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter wanted us to define the term “appropriate” as used in § 438.6(c)(3)(iv), which refers to appropriate payment mechanisms and utilization and cost assumptions. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As used both here and in the definition of actuarially sound rates, the term “appropriate” means specific to the population for which the payment rate, or in this instance risk sharing mechanism, is intended. This requirement applies to individuals who have health care costs that are much higher than the average. Appropriate for the populations covered means that the rates are based upon specific populations, by eligibility category, age, gender, locality, and other distinctions decided by the State. Appropriate to the services to be covered means that the rates must be based upon the State plan services to be provided under the contract. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters wanted us to define the term “cost neutral” as used at § 438.6(c)(1)(ii), and specify how this requirement will be measured. One commenter asked whether a risk sharing model, where the State shares a percentage of excess profits and losses with its MCO, would be considered cost neutral. Several commenters asked whether all of the mechanisms mentioned in § 438.6(c)(3)(iv) need to be cost neutral, and whether these mechanisms must be cost neutral over the entire Medicaid program, or just as applied to specific populations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In using the term “cost neutral,” we are requiring that risk sharing mechanisms recognize the fact that while some enrollees will have much higher than average health care costs, other will have much lower than average costs. Actuarially sound risk sharing methodologies will be cost neutral in that they will not merely add additional payments to the contractors' rates, but will have a negative impact on other rates, through offsets or reductions in capitation rates, so that there is no net aggregate impact across all payments. A risk corridor model, as described by the commenter, where the State and contractor share equal percentages of profits and losses beyond a threshold amount, would be cost neutral. In response to these commenters we have added a definition of “cost neutral” at § 438.6(c)(1)(iii). 
                    </P>
                    <P>In response to the other commenters, the cost neutrality requirement must apply to all mechanisms described in § 438.6(c)(3)(iv). The mechanism, as set forth in the rate setting methodology, should be cost neutral in the aggregate. How that is determined, however, will differ based on the type of mechanism that is used. A stop-loss mechanism will require an offset to all capitation rates under the contract, based on the amount of the stop-loss. Health status-based risk adjustment may require an adjustment to the capitation rate for all individuals categorized through the risk adjustment system, but the aggregate impact will still be neutral. We recognize that any of these mechanisms may result in actual payments that are not cost neutral, in that there could be changes in the case mix or relative health status of the enrolled population. As long as the risk sharing or risk adjustment system is designed to be cost neutral, it would meet this requirement regardless of unforeseen outcomes such as these resulting in higher actual payments. </P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters believed that an actuarial certification alone would not be sufficient to justify the payment rates. Some believed that the impact of the adequacy and timeliness of data and the State's budget process must be addressed as well. Other commenters wanted the certification to include enough information for another actuary to independently evaluate the results, including: Underlying data, its source and adjustments made; description of rate methodology; documentation of assumptions used; presentation of rates; and expected impact on each MCO's revenues. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We will be looking beyond the actuarial certification of the capitation rates in reviewing and approving rates in risk contracts. The certification is one part of the documentation that will be required, and as described elsewhere in § 438.6, there are a number of assurances and explanations that must accompany this certification in order for rates to be approved. We do not believe it is necessary, or in some cases appropriate, for other actuaries to be able to independently evaluate the results and assumptions in setting the rates (other than for our actuaries in cases where their assistance is required). As we stated above, we believe that MCOs, PIHPs, and PAHPs contracting with States on a risk basis must make their own independent judgments of proposed rates based on their own costs of doing business and their understanding of the population to be covered, not necessarily their actuaries' review of the State's actuaries' assumptions and process in setting the rates. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned that States or their contracted actuaries may be required to provide proprietary information to document the assumptions and methodology used to establish the capitation rates. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that States will be required to provide any information that is proprietary in nature in order to justify their capitation rates in risk contracts. However, if there are instances where actuaries believe that information their State is required to submit would represent trade secrets or proprietary information, as described in the Freedom of Information Act (FOIA) (5 U.S.C. 552(a)), the information should be identified as such and may be withheld from public disclosure under the provisions of the FOIA. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that additional documentation should be required, including: eligibility and enrollment trends; provider 
                        <PRTPAGE P="41003"/>
                        reimbursement at the Medicaid market level; utilization trends; pharmacy and ancillary costs; benefits in the contract period; and administration. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the documentation requirements in § 438.6(c)(4), along with the other provisions of this rule, will provide sufficient information on which to base decisions to approve or disapprove capitation rates in risk contracts. Thus, we do not believe that the additional documentation suggested by the commenter is necessary. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A large number of commenters expressed concern over the requirement in § 438.6(c)(4)(ii) that payment rates may only be based upon services covered under the State plan. Some of these commenters felt that MCOs need to maintain the flexibility to arrange for, and provide services in the most efficient manner that meets the needs of the individual, and these alternative services may not be in the State plan. The commenters asked whether this paragraph prohibits States and MCOs from offering additional services or providing services in alternative settings determined to be more appropriate, when these services are not in the State plan. Others asked whether MCOs can still receive payment for these services when they provide them. Some commenters wanted us to allow these costs to be incorporated into the rate calculations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         When a State agency decides to contract with an MCO or other type of managed care entity, it is arranging to have some or all of its State plan services provided to its Medicaid population through that entity. The State has not modified the services that are covered under its State plan, nor is it continuing to pay, on a FFS basis, for each and every service to be provided by the entity. Further, MCOs and other managed care contractors have the ability to do as suggested by the commenters—to provide services that are in the place of, or in addition to, the services covered under the State plan, in the most efficient manner that meets the needs of the individual enrollee. 
                    </P>
                    <P>These additional or alternative services do not affect the capitation rate paid to the MCO by the State. Neither do we believe that the capitation rate should be developed on the basis on these services. This requirement sets forth that principle—that the State determines the scope of State plan benefits to be covered under the managed care contract, and sets payment rates based on those services. This does not affect the MCOs right, however, to use these payments to provide alternative services to enrollees that would not be available under the State plan to beneficiaries not enrolled in the MCO. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked how the cost of non-State plan services, provided as cost-effective alternatives to State plan covered services, can be factored into the development of the capitation rates when a State uses MCO utilization and cost data in setting rates, if under § 438.6(c)(4)(ii) rates can only be based upon services covered under the State plan. These commenters believed that States need to be able to incorporate the cost of alternative services in rate calculations. Some commenters suggested that trade-offs should be incorporated into the rate calculation so that the cost of these services can be recognized. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that there must be a mechanism whereby States using MCO encounter data can base utilization costs of actuarially correct rates on non-FFS data. However, actuaries must adjust the data to reflect FFS State plan services only. States cannot use unilaterally contractually required or “suggested” services not part of the State plan (also known as “1915(b)(3) services”) to calculate actuarially sound rates. We are open to suggestions from States and their actuaries, but we will not modify the basic principle that rates be based only on services covered under the State plan. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked whether capitation rates can be adjusted to reflect additional requirements for services like EPSDT and other preventive care that may not have been provided under the State plan in FFS.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Another reason that we decided to replace the UPL requirement with the requirement for actuarially sound rate setting is to permit States to pay for the amount, duration and scope of State plan services that States expect to be delivered under a managed care contract. Thus, States may adjust the capitation rate to cover services such as EPSDT or prenatal care at the rate the State wants the service to be delivered to the enrolled population. States may use other mechanisms such as financial penalties if service delivery targets are not met, or incentives for when targets are met. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter asked if the requirement in § 438.6(c)(4)(ii) that payment rates based upon the cost of State plan covered services would prohibit payment for administration, profit, and contingencies, and what effect this would have on the FFP match. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As noted previously, we have clarified the language in § 438.6(c)(4)(ii) to indicate that payment may also be made for a contractor's administrative costs directly related to providing Medicaid services covered under the contract. In accordance with § 438.812, all costs under a risk contract are considered a medical assistance cost, so there is no impact on FFP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters raised questions regarding the requirement at § 438.6(c)(4)(iii) for a comparison of projected expenditures for a past year to actual expenditures for that year. Several commenters wanted to know what our purpose was in requiring the reporting of year-to-year expenditure differences when evaluating actuarial soundness. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The purpose of this requirement is to provide us with an indicator of the accuracy of prior year projections and the rate of growth in a State's expenditures under its managed care program, and to provide some direction to reviewers as to whether it may be necessary to look behind the assumptions used by the State in setting the rates. An increase in expenditures that far exceeds the inflation rate in the medical market basket for a given period may warrant further review, as may rates that have been unchanged through several contracting cycles. However, these are not factors that would, in and of themselves, result in the disapproval of proposed rates. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that we clarify whether the requirement for documentation is an annual requirement or if the information is to be submitted on some other basis. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This information, along with the rest of the documentation required by this rule, would have to be submitted with any new contract, or contract renewal or amendment that included new rates, as part of that required documentation. Thus, the information is not necessarily required to be submitted on an annual basis. States will need to submit the documentation of past and projected future expenditures in time for us to review the expenditure comparison as part of its review of new, renewed, or amended contracts (with revised rates). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked whether the comparison of expenditure data is intended to cover the State's entire Medicaid population, or only that portion which is to be enrolled in managed care during the contract year. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         These data should cover expenditures for all Medicaid eligible beneficiaries in areas where they are or could be enrolled in managed care. Thus, if all TANF eligibles in a part of the State are mandatorily enrolled in managed care, in either a PCCM or an 
                        <PRTPAGE P="41004"/>
                        MCO, they would be included in all of past expenditures data and future projections. Also, if SSI eligibles could voluntarily enroll in managed care, data on all SSI beneficiaries (whether the individuals are enrolled in managed care or not) should be included. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believed that we should clarify what is meant by the provision at § 438.6(c)(4)(iii), which requires “documenting” the prior year's expenditures as compared to the projected expenditures in the contract year, and asked what type of documentation would be required, and when it would be due. These commenters wanted to know whether we will issue guidelines on the process to be used to project the prior year's expenditures. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe the provision of these data is either a complex or burdensome process. We require that the State identify that portion of its expenditures in the most recent complete year that are attributable to populations who are or could be enrolled in managed care. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked what flexibility States will have in determining the methodology for making expenditure projections under this provision, and believed States should be able to provide these projections on the basis of either aggregate or per capita expenditures. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we are not prescribing the methodology for providing this information, we believe that per capita expenditures are the only valid means to provide the type of information that can be compared from year to year.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked what information States must submit to comply with the requirement at § 438.6(c)(4)(iv) to explain incentive arrangements, or stop-loss, reinsurance, or other risk sharing methodologies in MCO contracts. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         These risk sharing methodologies can sometimes be very complex. In order for the mechanism to be approved in the contract, the State or its actuary will need to provide enough information for our reviewer to understand both the operation and the financing of the risk sharing mechanism. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters raised questions regarding stop/loss and reinsurance coverage, and asked whether we will require MCOs to obtain stop-loss/reinsurance coverage. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Although a number of States require MCOs to obtain stop-loss or reinsurance coverage, there is no Federal requirement that they do so. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked whether, in cases where the State requires stop-loss insurance, we would require the State to provide a copy of a contract between the MCO and the re-insurer or stop-loss provider to us. Another commenter asked if we would require States to verify the actuarial soundness of MCO stop-loss/reinsurance contracts purchased commercially. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We will not review the actuarial soundness of commercially purchased stop-loss/reinsurance coverage. As mentioned above, there is no Federal requirement that MCOs obtain this coverage, and we will not generally require a copy of the stop-loss/reinsurance coverage contract. However, there are situations where this may be required, due to unusual circumstances, such as an MCO that is financially unstable. 
                    </P>
                    <HD SOURCE="HD2">Special Provisions </HD>
                    <P>A number of commenters expressed concerns about the limitation in § 438.814 on FFP in contracts with incentive arrangements or risk corridors. These comments are addressed in the portion of the preamble on that section. For purposes of clarity and in order to include these limitations on payment in the same subpart as the other rules governing payments in risk contracts we have moved these provisions from § 438.814 to § 438.6(c)(5)(ii) and (c)(5)(iii). We have also removed the phrase in § 438.6(c)(5)(i), which excepted risk corridors from the requirement for actuarial soundness, since it contradicted other provisions of the regulation. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters wanted us to define the terms “risk corridors” and “incentive arrangements” as used in § 438.6(c)(5)(ii) and § 438.814. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The term “incentive arrangements,” as used in this part, means any payment mechanism under which a contractor may receive additional funds over and above the capitation rates it was paid, for meeting targets specified in the contract. These targets may be for such things as delivery of services such as EPSDT at a specified rate (beyond the level envisioned in the capitation rate), or meeting certain quality improvement standards. Risk corridors are defined as a risk sharing mechanism in which States and MCOs share in both profits and losses under the contract outside of predetermined threshold amount. The amount of risk shared under this arrangement is usually graduated so that after an initial corridor in which the MCO is responsible for all losses or retains all profits, the State contributes a portion toward any additional losses, and receives a portion of any additional profits. In response to these commenters we have added definitions for “incentive arrangement” and “risk corridor” at § 438.6 in paragraphs (c)(1)(iv) and (c)(1)(v) respectively. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters questioned the provision in proposed § 438.6(c)(5)(iii)(C) that would have required the withholding of payments or other financial penalties in any contract with incentive arrangements, where the incentives are not met. These commenters stated that the requirement did not make sense, since these are two different types of provisions that act independently and serve different purposes. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter that this proposed provision was confusing and have deleted it from this final rule. Proposed § 438.6(c)(5)(iii)(D) has been recodified as § 438.6(c)(5)(iv)(C), with subsequent paragraphs similarly renamed. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter wanted us to clarify what is intended by the requirement in proposed § 438.6(c)(5)(iii)(E) (now § 436.6(c)(5)(iv)(D) in this final rule), that incentive payments cannot be conditioned on intergovernmental transfer agreements. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The purpose of this prohibition is to prevent incentive arrangements in managed care contracts from being used as funding mechanisms between State agencies or State and county agencies.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believes that the requirement in proposed § 438.6(c)(5)(iii)(F), (now § 436.6(c)(5)(iv)(E) in this final rule) that incentive arrangements be necessary for the specified activities and targets is unclear and a highly subjective determination. The commenter felt that the provision should either be deleted, or alternatively that responsibility for the determination of necessity be placed on the State. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that this provision is unclear or highly subjective. A State that decides to use incentive arrangements will have made a determination that they are needed in the contract, and we agree that this should be the State's determination. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters objected to the provision in proposed § 438.60 prohibiting direct payments to teaching hospitals for graduate medical education (GME) when the hospital's services are provided through managed care. Commenters indicated that this prohibition would disturb longstanding arrangements in many States. 
                        <PRTPAGE P="41005"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In response to the concerns raised by these commenters, we have modified that section to permit such payments to the extent the capitation rate has been adjusted to reflect the amount of the GME payment made directly to the hospital. We have added new § 438.6(c)(5)(v), which requires States making payments to providers for GME costs under an approved State plan, to adjust the actuarially sound capitation rates to account for the aggregate amount of GME payments to be made directly to hospitals on behalf of enrollees covered under the contract. This amount cannot exceed the aggregate amount that would have been paid under the approved state plan for FFS. We believe this approach addresses State concerns of preventing harm to teaching hospitals and Federal concerns of ensuring the fiscal accountability of these payments. As part of our larger strategy of improving the fiscal integrity of Medicaid payments, we also plan to study existing Medicaid GME payment arrangements and may issue additional policies in the future. 
                    </P>
                    <HD SOURCE="HD3">• Services That May Be Covered (Proposed § 438.6(e)) </HD>
                    <P>The proposed rule at § 438.6(e) provided that an MCO, PIHP, or PAHP, contract may cover, for enrollees, services that are in addition to those covered under the State plan. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was pleased that the proposed rule expressly provides for MCO contracts to cover services that are in addition to those covered under the State plan, because it will allow them to find new, innovative ways to more effectively treat health problems. A few commenters believed these non-State plan services will allow for cost-effective substitutions for State plan services. However, these commenters question why these non-State plan services cannot be used by the State in the development of payment rates under § 438.6(c). One commenter noted that if they are not paid for such non-State plan services it would stifle MCOs in the use of innovative treatment methodologies and technologies. Another commenter questioned how FFP is impacted for these additional services, since they are not allowed to be included in the rate setting methodology under § 438.6(c)(4)(ii). This commenter also asked whether we were requiring payments for these additional services to be actuarially sound and certified as required by § 438.6(c). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Those commenters who appear to believe that § 438.6(e) allows for payment for additional services that can be provided in lieu of State plan services are not correct. The additional services allowed under § 438.6(e) are not included in the calculation of capitation payments. These services may only be offered by an MCO, PIHP, or PAHP paid on a risk basis. This is because these entities would typically use “savings” (a portion of the risk payment not needed to cover State plan services) to cover the additional services in question. Additional services may also be provided for under section 1915(b)(3) waiver authority which allows a State to share savings resulting from the use of more cost-effective medical care with beneficiaries by providing them with additional services. In either case these services are additions to State plan services and are paid for by plans or through shared savings under the waiver program. Since payment is made by the plans or through shared savings, such payments do not have to be actuarially sound and certified. In order to clarify the confusion over this provision, we have added the phrase, “although the cost of the services cannot be included when determining the payment rates under § 438.6(c).” Further, for a discussion of the prohibition against including non-State plan services in setting capitation rates, see the preamble discussion of § 438.6(c)(4). 
                    </P>
                    <HD SOURCE="HD3">• Compliance With Contracting Rules (Proposed § 438.6(f)) </HD>
                    <P>This section requires all contracts under this subpart to comply with all Federal and State laws and regulations and meet all requirements of this section. </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received one comment supporting the provisions regarding compliance with applicable Federal and State laws and regulations found in § 438.6(f). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are retaining the provisions supported by the commenter in this final rule, and appreciate the commenter's supportive comments. 
                    </P>
                    <HD SOURCE="HD3">• Inspection and Audit of Financial Records (Proposed § 438.6(g)) </HD>
                    <P>This section of the proposed rule required that the financial records of contractors and subcontractors be available for audit and inspection. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter supported the explicit requirements of § 438.6(g). The commenter noted that without access to financial arrangements with subcontractors, it is difficult to track whether rates are sufficient to ensure that children have access. The commenter urged us to make this information publicly available. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are not imposing a requirement on States to make these financial data public, nor will we establish a mechanism to do so at the Federal level. However, under § 438.10(g) (3) enrollees are entitled to obtain information on the structure and operations of their MCO or PIHP, and for States with mandatory managed care under section 1932(a)(1), § 438.10(i)(3)(iv) provides that beneficiaries are entitled to receive quality and performance indicators on the MCOs and PIHPs available to them. We believe that this type of information has more value to Medicaid beneficiaries than the financial data required by this section. 
                    </P>
                    <HD SOURCE="HD3">• Advance Directives (Proposed § 438.6(i)) </HD>
                    <P>Proposed § 438.6(i) requires that all MCO and PIHP contracts comply with the requirements of § 422.128 (M+C rules) for maintaining written policies and procedures for advance directives, and reflect changes in State law within 90 days. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked for the definition of the term “advance directive” as used in § 438.6(i). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The provisions on advance directives are cross referenced to the more detailed M+C rules in § 422.128, which are further linked to the definition of the term in § 489.100. As defined in § 489.100, “advance directive” means a written instruction, such as a living will or durable power of attorney for health care, recognized under State law (whether statutory or as recognized by the courts of the State), relating to the provision of health care when the individual is incapacitated. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned that providing all adult enrollees with written information on advance directive policies, and including a description of applicable State law changes, will cause MCOs to duplicate information and develop documentation systems that will add unnecessary cost and an administrative burden, thereby reducing efficiency of providing health care. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Because section 1903(m)(1)(A) of the Act requires MCOs to provide information on advance directives to enrollees, we do not have the authority to eliminate or modify the advance directives provision for MCOs under § 438.6(i). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Another commenter believes the advance directive requirements should be expanded to all managed care enrollees and not just for those enrollees in MCOs and PIHPs. The commenter believes that beneficiaries have the same right to make informed 
                        <PRTPAGE P="41006"/>
                        choices about outpatient treatments as those beneficiaries do about inpatient treatments. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 489.102(a) identifies those providers required to comply with advance directive requirements. That section includes providers that could be participating in a PAHP network, including hospital outpatient providers and home health agencies. Therefore, we agree with the commenter that advance directives should apply to PAHPs if their network includes any of the providers that are listed in § 489.102(a). We have added a new § 438.6(i)(2) to include this requirement. 
                    </P>
                    <HD SOURCE="HD3">• Additional Rules for Contracts With PCCMs (Proposed § 438.6(k) </HD>
                    <P>This section proposed new rules found in section 1905(t)(3) of the Act which specify the requirements that must be included in contracts with primary care case managers. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter felt that the contract requirements for PCCMs were too minimal, and that patients in PCCM programs should have rights of access, coverage, information, and disclosure that are as strong as those that apply to MCOs, PIHPs, and PAHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The contract requirements for primary care case managers in proposed § 438.6(k) largely mirror the language set forth in section 1905(t)(3) of the Act, which was added by section 4702 of the BBA. The BBA is clear in setting forth which contracting requirements should be placed on primary care case managers, which should be placed on MCOs, and which apply to all MCOs, PHPs, or PCCMs. PCCM contracts must include those requirements set forth in section 1905(t)(3) as well as any additional requirements in section 1932 of the Act that apply to them. For example, a PCCM must meet the information requirements set forth in § 438.10 that apply to it. We also have applied access, coverage, and information requirements to primary care case managers where applicable. Where the BBA specifies that requirements apply to MCOs, such requirements are not applicable to PCCM contracts. However, where a PCCM is paid on a capitated basis, the PCCM would meet the definition of a PAHP and would also be subject, by regulation, to all PAHP requirements. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter is concerned that the requirement in § 438.6(k)(2) that “restricts enrollment to recipients who reside sufficiently near one of the manager's delivery sites to reach that site within a reasonable time using available and affordable modes of transportation” does not take into consideration the special circumstances and characteristics of frontier states. The commenter wanted us to clarify what is a “reasonable” time in frontier states where the nearest provider may be more than 100 miles from the beneficiary, and very few locations have any public or commercial transportation available. The commenter asked whether this prohibits a recipient from choosing a provider who is further away, which could result in decreased beneficiary satisfaction and choice. The commenter suggests a standard based on “normal and customary” practices that would allow for a frontier state to better serve its population. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that this requirement imposes any unreasonable burden on frontier states as suggested by the commenter. The requirement in proposed § 438.6(k)(2), that beneficiaries be able to access care within reasonable time using affordable modes of transportation, is derived from statutory language in section 1905(t)(3)(B) and cannot be changed. However, states have the flexibility to determine their own standards for reasonableness based on normal distance and travel times in the area, the needs of the beneficiaries, provider availability, and the geographic uniqueness of the State. One example, as noted in the preamble of the proposed rule, is the 30-minute travel time standard that many States have adopted for urban areas. Other States have established 10 to 30 mile distance standard, depending on specific circumstances within the area of the State to be served. We have consistently permitted States to develop their own standards, based upon customary treatment patterns in their unrestricted FFS programs, in the approval of section 1915(b) waiver programs. 
                    </P>
                    <P>While we require States to develop their PCCM programs so that enrollees should not have to travel an unreasonable distance beyond what is customary in the State's unrestricted FFS program, we encourage States, to the extent practical, to make exceptions for beneficiaries who request to travel further than the time and distance standards set by the State, for such reasons as a desire to maintain an ongoing relationship with a particular participating provider. Section 438.6(k)(2) would not prohibit such exceptions, provided the beneficiary was aware of his or her options and could make an informed choice of PCCM. </P>
                    <HD SOURCE="HD3">• Subcontracts (Proposed § 438.6(l)) </HD>
                    <P>This proposed rule requires all subcontractors to fulfill the requirements of § 438.6 that are appropriate to the services or activity delegated under the subcontract. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked for clarification about whether the CMS Regional Office must also review and approve all subcontracts since § 438.6(l) requires that all subcontracts must fulfill the requirements of § 438.6, and § 438.6(a) requires the CMS Regional Office to review and approve all MCO, PIHP, and PAHP contracts. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirement for Regional Office review of contracts in § 438.6(a) only pertains to contracts between States and MCOs, PIHPs, and PAHPs, but not to subcontracts between any of these entities and their subcontractors. As noted above, § 438.6(l) only requires compliance with provisions in § 438.6 that are “appropriate” to the service or activity covered under the subcontract, and we do not believe that such review would be appropriate to the services or activities delegated under the subcontracts, or a worthwhile expenditure of our resources. Our focus is on the contractual relationship between the State and the MCO, PIHP, or PAHP as the primary contractor, as required by section 1903(m) of the Act, with respect to MCOs. The primary contractor is the entity that is obligated to comply with all provisions of the contract, whether it uses subcontractors in order to do this or not. The use of subcontracts does not in any way alter the primary contractor's responsibilities, obligations, or authority under the contract. 
                    </P>
                    <HD SOURCE="HD3">• Choice of Health Professional (Proposed § 438.6(m)) </HD>
                    <P>This section sets forth the right of an MCO enrollee to choose his or her health professional to the extent possible and appropriate.</P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the regulations should specify that MCOs must let enrollees choose their primary care provider from among all qualified participating providers, including specialists. The commenter also suggested that when an enrollee is unable to be linked to their first choice of primary care provider, the MCO should have a mechanism for linking the enrollee to that provider when the provider becomes available. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.6(m) permits an enrollee to choose his or her health professional to the extent possible and appropriate. This would include the selection of primary care providers participating in the MCO, PIHP or PAHP network, unless they were already at capacity. We do not believe it is necessarily appropriate for specialist to act as primary care providers in every 
                        <PRTPAGE P="41007"/>
                        instance. Primary care is defined in § 438.2, and does not describe the range of services provided by many specialists. We believe that the decision on whether a specialist is the appropriate PCP for any enrollee should be left to the MCO, PIHP, PAHP, and/or the State to be determined on an individual basis. If an enrollee is unable to be placed with their first choice of primary care provider, they may continue to check on that provider's availability and change PCP when it becomes possible to do so. We do not believe this change is necessary in the regulation text. However, we are removing reference to MCOs, since this requirement applies to PIHPs and PAHPs as well under § 438.8. 
                    </P>
                    <HD SOURCE="HD3">4. Provisions That Apply to PIHPs and PAHPs (Proposed § 438.8) </HD>
                    <P>This section specifies which provisions of this rule apply to PIHPs and which apply to PAHPs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters believed that the same requirements should apply to both PIHPs and PAHPs, and several suggested that both types of PHPs should be subject to the same requirements as MCOs. These commenters argued that both types of entities cover an increasingly large portion of the Medicaid population, that requirements for an adequate and appropriate network are just as relevant and necessary for dental and transportation providers as for MCOs, that children with special health care needs require specialized care regardless of the scope of services their managed care contractor provides, and that any plans that provide any type of medical care should be required to comply with the protections in the BBA, such as network adequacy, credentialing, and grievance rights. 
                    </P>
                    <P>Several other commenters suggested that even plans providing non-medical services, such as transportation should be required to have an adequate network, provide services timely, and have a mechanism to resolve complaints. </P>
                    <P>Another commenter suggested returning to a single set of requirements for PHPs, but accommodating PHPs covering a more limited array of services by permitting them to deviate from standards that are not applicable to the entity or services it provides or allow additional time to come into compliance. </P>
                    <P>Other commenters expressed support for the distinction in requirements between PIHPs and PAHPs and the flexibility in the rule to determine how to most appropriately regulate PAHPs. </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated above in the discussion regarding definitions at § 438.2, we believe that there are clear differences in terms of the degree of financial risk, contractual obligations, scope of services, and capitation rates paid to these different types of entities, and that the scope of rules that apply to these entities under this regulation should reflect these distinct differences. However, in considering the provisions of the proposed rule and the issues raised by commenters, we agree that there are additional provisions of this regulation that should apply to PAHPs and have modified the requirements of the final rule to implement these changes. In § 438.8(b), we have added the following requirements to PAHPs: Advance directives where a PAHP has a network of providers that includes either hospital outpatient departments or home health agencies (see the response to comments on § 438.6(i) advance directives), all of subpart C on Enrollee Rights, and designated portions of subpart D on Quality Assessment and Performance Improvement. We have added new information requirements specific to PAHPs in a new paragraph (h) in § 438.10 (with the existing paragraph (h) renamed paragraph (i)). Finally, at § 438.6(b)(7), we have reaffirmed a PAHP enrollee's right to a fair hearing under § 431.220. We believe that with these changes, we have maintained an appropriate level of regulatory requirements for these entities and provided the necessary degree of flexibility for States to implement these programs and impose any additional requirements States determine to be necessary. In addition, we believe we have provided the necessary level of beneficiary protections for these programs, including network adequacy (where applicable), provider credentialing, and appeal rights. We do not believe that applying additional provisions to PAHPs would be appropriate based on the scope of services they provide and the capitation rates they are paid in comparison to PIHPs and MCOs.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters raised specific concerns about PAHP rules governing prepaid dental plans. Some commenters indicated that Medicaid dental patients need patient protections like MCO enrollees, since oral and systemic health are both integral to overall health, and should have the same patient protections. Another commenter asked whether MCO or PAHP rules apply to MCOs that subcontract for dental care. Several commenters were concerned that dental services are provided as part of MCO contracts and FFS as well as by prepaid dental plans, and PAHP dental enrollees should have the same protections as MCO enrollees receiving dental care. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters regarding the importance of dental health and that beneficiary protections are an important requirement for dental PAHPs, particularly the requirement for network adequacy. One reason that States use prepaid dental plans is because of the lack of dental providers who provide care under FFS. Guaranteeing an adequate network in a dental PAHP will provide Medicaid beneficiaries access to dental care that is often otherwise unavailable. 
                    </P>
                    <P>The determination as to which rules apply to any service or delivery system is the identity of the entity that contracts with the State. Thus, in situations where an MCO has a contract with a State, MCO rules apply to services furnished by the MCO or its sub-contractors, including a subcontracting pre-paid dental plan. Where a PIHP or PAHP contracts with the State, PIHP or PAHP rules apply respectively. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters objected to the requirements imposed on PIHPs. They believed that the proposed requirements were unclear, ambiguous, and burdensome, and would require the State to spend money on administrative expenses rather than patient care. These commenters felt that the proposed requirements were targeted to a medical model and did not take into account behavioral health services, such as mental health and substance abuse or rehabilitation models. They pointed out that PIHPs only authorize and pay for community psychiatric hospital beds and not all inpatient hospital care, and thus should not be subject to MCO requirements. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge that this rule will impose many new requirements on PIHPs, just as it imposes new requirements on MCOs and PAHPs. Most of the new rules imposed on MCOs were derived from the BBA. Prior to the BBA, PHPs were subject, under Part 434, to most of the rules governing Medicaid-contracting HMOs. We believe that the Congress determined that additional costs and administrative burden were justified in order to provide sufficient protections for beneficiaries enrolled in MCOs. We believe that these same considerations apply to PHPs that provide inpatient services. In addition, we believe that beneficiaries in need of mental health and substance abuse services may be particularly vulnerable, and need these 
                        <PRTPAGE P="41008"/>
                        protections more than some other healthier Medicaid beneficiaries. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter apparently believed that while PCCMs covering some or all of the following services were subject to PCCM requirements (case management, durable medical equipment, EPSDT, family planning, hearing, home health care, immunizations, laboratory, outpatient hospital, pharmacy, physician, transportation, vision, and x-ray) a managed care plans covering a subset of theses services would be exempt from all enrollee safeguards and quality and integrity requirements. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It is true that the referenced services can be furnished through a PCCM arrangement, under which the primary care case manager provides physician services and case management, and has the responsibility to refer or prior authorize these other services for their enrollees. It is also true, that in such a case, the PCCM requirements, and any requirement that applies to a “managed care entity” (both MCOs and PCCMs) would apply in this case. However, it is also true that a managed care plan that provides a subset of these services would be subject to enrollee safeguards and quality and integrity requirements, as an MCO or a PAHP. An entity that was at risk for the full scope of services described by the commenter (or any subset of three or more of the services described in § 438.2 in the definition of comprehensive risk contract) would be considered an MCO, even though inpatient services were not being provided. If the “subset of services” did not trigger the definition of comprehensive risk contract, the entity would still be regulated as a PAHP, and PAHPs are not exempt from 
                        <E T="03">all</E>
                         enrollee safeguards and quality provisions. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters wanted us to impose PIHP requirements on prepaid providers of home and community-based services (under a section 1915(c) waiver) in order to assure that beneficiaries in programs that maximize community-based care and minimize the need for institutionalization will have sufficient protections. One commenter contended that the Supreme Court's decision in 
                        <E T="03">Olmstead</E>
                         v. 
                        <E T="03">L.C.,</E>
                         and the President's New Freedom Initiative, dictate that all provisions in the proposed rule that would improve or ensure access to care must be provided to those who need community-based care in order to reside outside of institutions. Other commenters believed that PIHP rules should not apply to home and community-based services, since the rules could discourage participation of these needed providers, and take away State and local discretion to impose, waive, or adjust requirements as best determined at that level. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Home and community based service providers by definition do not provide “inpatient” care, and accordingly would not meet the definition of PIHP. In light of our decision, discussed above, to impose additional requirements on PAHPs, we believe that we have provided sufficient beneficiary protections for PAHPs that provide home and community based services, while at the same time accommodating the latter commenter's concern about requirements discouraging participation. In so doing, we believe that we are helping to implement the 
                        <E T="03">Olmstead</E>
                         v. 
                        <E T="03">L.C.</E>
                         decision and the President's New Freedom Initiative, and to ensure access to community-based care with appropriate enrollee protections and quality assurance. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter felt that all PIHPs and PAHPs should be subject to sanctions if they do not comply with the regulations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The sanction authority enacted by the Congress in the BBA is limited to MCOs. We do not believe we have authority, by regulation, to authorize States to impose civil money penalties on PAHPs or PIHPs. However, States may cover PIHPs and PAHPs under their own State sanction laws, and we encourage States to do so whenever they believe it is necessary. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter wanted us to add a provision to exempt MCOs with less than 500 members from the same requirements from which PAHPs are exempt. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Because PIHP and PAHP requirements are based on broad on the authority in section 1902(a)(4) of the Act, we have the discretion to impose those requirements on PIHPs and PAHPs that we determine to be appropriate through regulations. However, requirements for MCOs are specified in sections 1903(m) and 1932 of the Act, and are not subject to modification by regulation on the basis of the number of an MCO's enrollees. 
                    </P>
                    <HD SOURCE="HD3">5. Information Requirements (Proposed § 438.10) </HD>
                    <P>Proposed § 438.10 set forth the requirements that apply to States, MCOs, PIHPs, PAHPs, PCCMs, and enrollment brokers concerning the provision of information to enrollees and potential enrollees. Paragraph (a) defined the terms used in this section. Paragraph (b) set forth the basic rule that all information provided must be in a manner and format that may be easily understood. Paragraph (c) established rules regarding language. Paragraph (d) specified the format for information and that alternative formats must be available. Paragraph (e) described information requirements for potential enrollees. Paragraph (f) set forth the general information requirements for enrollees of all MCOs, PIHPs, PAHPs, and PCCMs. Paragraph (g) contained specific information requirements for MCO and PIHP enrollees. And paragraph (h) set forth the special rules required of States with mandatory enrollment under the State plan authority in § 438.50.</P>
                    <HD SOURCE="HD2">General Comments on § 438.10 </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters appreciated the clarity and content of this section, and stated that they did not believe the provisions were too prescriptive. By contrast, another commenter contended that the requirements were too prescriptive, and would be difficult to meet even for a non-Medicaid population. This commenter believed this section as a whole did not take into consideration the nature of frontier States. The commenter recommended reducing the Federal role in the provision of information to beneficiaries, and letting States have the discretion to determine what is most appropriate. 
                    </P>
                    <P>Finally, one commenter believed that the proposed rule did not ensure that enrollees would receive adequate information to understand their rights and responsibilities, and that it failed to provide potential enrollees with enough information to make an appropriate decision. The commenter believed this is especially true for individuals with chronic health conditions, who often see numerous medical professionals. The commenter asserted that these beneficiaries must have adequate information to make the best decision to ensure that their health needs can be met within a plan's network. </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the proposed rule achieves an appropriate balance between ensuring potential enrollees and enrollees have sufficient information, and giving the State flexibility in implementing the regulation. We appreciate the comments in support of the clarity of the proposed rule, and the comment that it contains an appropriate level of prescriptiveness. For frontier areas, enrollees there also need a minimum set of information to navigate a managed care program. We believe the regulations are flexible enough to accommodate the unique circumstances of rural and frontier areas, and have identified specific instances in our responses to 
                        <PRTPAGE P="41009"/>
                        subsequent comments. Finally, we believe the minimum information required in the proposed rule is sufficient for all potential enrollees and enrollees, even those with disabilities or chronic illnesses. There are areas where information that might be especially useful for this population is available upon request instead of provided automatically (for example § 438.10(d) on alternative formats, § 438.10(e)(2)(ii)(D) on summary provider information, and § 438.10(g) on information on plan structure and operations), but the final rule makes clear that these enrollees and potential enrollees must be informed of how and where to get this information. 
                    </P>
                    <HD SOURCE="HD2">Definitions (Proposed § 438.10(a)) </HD>
                    <P>Proposed paragraph (a) set forth definitions of “potential enrollee” and “enrollee.” </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter supported the definitions of “potential enrollee” and “enrollee.” Another commenter, however, felt that the regulation needs to clarify who an enrollee is in the case of a specialty plan. For example, in the commenter's State, all Medicaid recipients are required to receive mental health services from certain plans, but the State does not give information about mental health services until an individual actually receives services. This commenter recommended the State or plan should provide minimum general information about the plan and what services are provided at the time of initial enrollment in the plan, and provide more detailed information when the beneficiary first contacts the plan to inquire about services available. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the definition of enrollee is appropriate for any managed care program, including mental health managed care. We believe that the regulation's flexibility on providing certain information in summary format meets the commenter's first suggestion. We disagree with the suggestion to delay providing the full set of required enrollee information to the point in time when an enrollee requests services. This fails to provide adequate information to enrollees, and could be a barrier to care for enrollees who are unsure of what services the plan provides and how to access those services. We acknowledge that this will result in increased burden for States such as those in which the commenter resides where there is a single PIHP per service area in which every beneficiary is automatically enrolled upon determination of Medicaid eligibility. Some of the anticipated burden could be reduced by providing the required potential enrollee and enrollee information at the same time. 
                    </P>
                    <HD SOURCE="HD2">Mechanism To Assist Understanding (Proposed § 438.10(b)) </HD>
                    <P>As noted above, proposed paragraph (b) set forth the basic rule that all information provided must be in a manner and format that may be easily understood. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters believed that the proposed basic rule at § 438.10(b) failed to require States to have a mechanism to help enrollees and potential enrollees understand the managed care program, and failed to require MCOs, PIHPs, and PAHPs to have a mechanism for enrollees and potential enrollees to understand the requirements and benefits of the plan. Several argued that beneficiaries need to have the ability to get information from a variety of resources, not just written material. They felt that a mechanism was needed to ensure that enrollees and potential enrollees have information necessary for informed decisions. Some commenters believed that the lack of such a source of assistance would have a harmful impact on persons with disabilities, especially mental retardation and other cognitive impairments. One commenter urged that such a mechanism be family-friendly. Several commenters noted that such a mechanism was included in the Bipartisan Patient Protection Act (HR 2653), CMS' Report to the Congress entitled “Safeguards for Individuals with Special Health Care Needs Enrolled in Medicaid Managed Care,” and the President's Advisory Commission on Consumer Protection and Quality in the Healthcare Industry. 
                    </P>
                    <P>The commenters recommended requiring States to have a mechanism for potential enrollees and enrollees to understand the State's managed care program. Examples included a toll-free hotline, ombudsman, and other types of consumer assistance. Many of the commenters further recommended requiring that MCOs, PIHPs, and PAHPs have a mechanism to help potential enrollees and enrollees understand the requirements and benefits of the specific plan. Two commenters recommended the plan's mechanism need only be provided for enrollees, not potential enrollees. </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with commenters that written information may not be sufficient for potential enrollees and enrollees to understand a managed care program. In response to these comments, we have amended § 438.10(b), by adding paragraphs (b)(1) and (b)(2) to require that States, MCOs and PIHPs have mechanisms in place to help beneficiaries that need such help to understand the managed care program, and plan requirements and plan benefits. We believe that it is not necessary to separately require PAHPs and PCCMs to have such mechanisms, as information on such plans could be addressed by the State's mechanism. We will require the mechanism to be available to both potential enrollees and enrollees, especially given that much of the required potential enrollee information need only be provided in summary format. We believe, however, that the State and plans should be given the discretion and flexibility to provide the mechanism most appropriate to their situation, so we are not specifying the type of mechanism that must be in place. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that health plans be made aware of their responsibility to respond to a beneficiary's questions in a timely manner. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that plans should respond in a timely manner, and expect them to do so. However, we do not believe that it is necessary to specifically provide for this in regulation text. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters noted that the basic rule requires that only certain information be presented in a manner and format that is easily understood. They objected that this did not appropriately safeguard the rights of beneficiaries. The commenters believed that limiting the requirement to only certain material fails to give beneficiaries with limited English proficiency sufficient information. Some expressed concern that this could also violate section 1932(a)(5)(A) of the Act, which the preamble to the proposed rule characterized as requiring “all written information be provided in an easily understood language and format.” Commenters recommended expanding the requirement to include “all” materials. On the other hand, there was one commenter who agreed with the limitations on which materials must meet the criteria. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we share the commenters concern that all material should be in a manner and format that is easily understood, this section of the regulations is derived from section 1932(a)(5)(A) of the Act which specifically requires that responsible parties “provide all enrollment notices and information and instructional materials * * * in a manner and format which may be easily understood.” Thus, notwithstanding the unqualified language in the preamble, section 1932(a)(5)(A) of the Act limits the type of information covered by its provisions. 
                        <PRTPAGE P="41010"/>
                        However, in addition to the specific requirements that apply to enrollment notices and information and instructional materials contained in this section, provisions of the regulation governing information on enrollee rights, provider enrollee communications, marketing, grievances and appeals, and termination of MCOs and PCCMs all reference the requirements of this section. We believe that this extends the requirements for an easily understood language and format to virtually all written material provided to potential enrollees and enrollees. Thus, we do not agree that it is necessary to revise the regulation in response to this comment. 
                    </P>
                    <HD SOURCE="HD2">Clarifying Responsible Entity (Proposed Rules § 438.10(b) and § 438.10(f)) </HD>
                    <P>As noted above, paragraph (b) sets forth the basic principle that information must be provided in a form that is easily understood. However, it does not set forth which entities are obligated to provide what specific information. This also is the case with respect to one paragraph in paragraph (f), which sets forth the general information requirements for enrollees of all MCOs, PIHPs, PAHPs, and PCCMs. The introductory paragraph to paragraph (f) refers to information being made “available.” </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters objected to the fact that the text of the “basic rule” in § 438.10(b) does not identify who is responsible for providing information to potential enrollees and enrollees. One commenter asserted it is not enough for § 438.10(f) to require only that information be made “available” to enrollees, because this creates what the commenter believed to be a needless barrier to ensuring beneficiaries have the information they need. Finally, many commenters expressed concern that § 438.10(f)(6) (regarding required information for enrollees) did not specify who was responsible for providing required information to enrollees. Some of these commenters recommended clarifying that the State is responsible for providing required information to enrollees, and that the State can delegate this responsibility to the health plan. Other commenters suggested clarifying that the plan is responsible for providing required information, and that the State is responsible for ensuring compliance. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While the text in § 438.10(b) setting forth the “basic rule” does not itself identify who is responsible for providing what information to potential enrollees and enrollees, we believe that other provisions of the regulations text make this clear. Specifically, § 438.10(e)(1) specifies that the State or its contracted entity is responsible for providing required information to potential enrollees; § 438.10(f), with one exception discussed below, specifies which entity or entities is responsible for providing specified information; § 438.10(g) specifies that MCOs and PIHPs are responsible for providing information specific to those types of programs; § 438.10(h) specifies that the State or a PAHP must provide information on PAHPs; and § 438.10(i); specifies the State is responsible for providing certain information required under a State plan amendment. 
                    </P>
                    <P>
                        Within § 438.10(f), each of the paragraphs specifies a responsible party, except, as commenters note, paragraph (f)(6). While § 438.10(f)(3) specifies who is responsible for providing the information in § 438.10(f)(6), we agree that § 438.10(f)(6)—read alone—is unclear. We are revising § 438.10(f)(6) to specify the State or at its discretion, its contracted entity, the MCO, PIHP, PAHP, or PCCM, is responsible for providing required information to enrollees. We will also conform the language identifying responsible parties in § 438.10(f)(4) and § 438.10(g) with the language used in other paragraphs. Finally, while each paragraph in § 438.10(f) requires the 
                        <E T="03">provision</E>
                         of certain information, in response to this comment, and for consistency, we are revising the introductory paragraph to replace “made available” with “provide.”
                    </P>
                    <HD SOURCE="HD2">Prevalent Languages (Proposed § 438.10(c)) </HD>
                    <P>Proposed paragraph (c) required that information be made available in prevalent languages. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter supported basing the determination of whether a language is prevalent in the potential enrollee and enrollee population, rather than the State's population as a whole. The commenter stated this more appropriately targets those who would use information being translated. 
                    </P>
                    <P>By contrast, a few commenters noted that proposed rule only requires States to identify prevalent languages, not all languages spoken by potential enrollees and enrollees. They asserted this is a weak standard, and disproportionately harms community health centers, which serve a disproportionate share of people with limited English proficiency. The commenters recommended the State be required to identify all languages spoken in State, not just prevalent languages. </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the first commenter that the proposed rule's focus on the enrollee and potential enrollee population in the state is most effective. We disagree with the latter commenters that the proposed “prevalent languages” standard is weak. The proposed rule conforms with the Office for Civil Rights' “Policy Guidance title VI Prohibition Against National Origin Discrimination As It Affects Persons With Limited English Proficiency.” Specifically, that Guidance suggested that written material should be translated into regularly encountered languages other than English spoken by a significant number or percentage of the population eligible to be served. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that there is generic (versus plan-specific) information in § 438.10(f)(6) that must be translated into prevalent languages. The commenter believed it would be wasteful and inefficient to require each plan to translate it, and any variation in this generic language across plans would be confusing to beneficiaries. The commenter recommended requiring States to make translations of generic information available to plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Nothing in the proposed rule would prohibit the State from translating material that is not plan specific. However, we believe States should have flexibility on whether to adopt this approach. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that the proposed regulatory provisions placed sole responsibility for identifying prevalent languages on the State. In the commenter's State, there is a model in which plans are required to identify the prevalent languages spoken by their enrollees, and forward that data to the State. The commenter stated this allows the plan to concentrate on the language needs of their membership; the State then combines its data with plans' data for a more accurate picture of non-English languages spoken. The commenter recommended flexibility in this area so that the maximum amount of prevalent language data can be collected at all levels of contact with the enrollee. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the proposed rule provides the flexibility this commenter seeks. Specifically, § 438.10(c)(1) requires the State to “establish a methodology,” but gives States the discretion on what the actual methodology is. It would not preclude the methodology described by the commenter. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters expressed concern that the definition of “prevalent” at § 438.10(c)(1) was based on prevalence among the enrollee and 
                        <PRTPAGE P="41011"/>
                        prospective enrollee population at a Statewide level, not a service area level. They observed that if beneficiaries with limited English proficiency are concentrated in a few areas, there may not be enough to meet statewide prevalence threshold. One commenter stated this was especially an issue in more populated States. 
                    </P>
                    <P>The commenters recommended basing prevalence on service area, not a statewide threshold. One recommended it be based on geographic area, as stated in the preamble to the proposed rule. Another commenter recommended the rule define service area. Still others urged the rule go further, and specify a threshold of 5 percent within localized area. A few proposed the rule set a threshold of 10 percent or 3,000 in a service area, with additional specifications if there are 5 percent or less, as well as under 100 potential enrollees or enrollees. Finally, a commenter suggested that if the State does not identify prevalent languages by service area, that plans be required to do so. </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' point regarding languages that may be prevalent at a service area level but not meet a statewide threshold. However, we believe the proposed rule takes this into account. Specifically, § 438.10(c)(2) requires the State to “Provide written information in each prevalent non-English language.” However, § 438.10(c)(3) requires each MCO, PIHP, PAHP, and PCCM to make its written information available in the prevalent non-English languages in its particular service area. For potential enrollees and enrollees who primarily speak a non-English language that is not prevalent, the mechanism we are requiring in response to a comment on § 438.10(b) will provide them an avenue for obtaining needed information. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter contended that requiring States to identify prevalent languages is administratively burdensome and costly. Another commenter found the language requirements problematic, especially for rural States, and believed they would create additional costs for State and plans. Finally, a commenter noted the difficulty of consistently producing materials in prevalent non-English languages in a timely fashion. On the other hand, numerous commenters supported the proposed rule requiring a methodology to identify prevalent non-English languages, and provision of written information in those languages. 
                    </P>
                    <P>Commenters who had concerns about the prescriptiveness of the proposed language requirements recommended more flexibility in the language requirements, including allowing States the flexibility to determine if additional language versions of written information are necessary. </P>
                    <P>
                        <E T="03">Response:</E>
                         The OCR Guidance we referenced in our earlier response makes clear that all entities that receive Federal financial assistance from the Department of Health and Human Services, either directly or indirectly, must provide meaningful access to its services for beneficiaries with limited English proficiency. This includes providing translated versions of vital documents into non-English languages regularly encountered in the eligible population. The Guidance provides suggested methodologies for identifying prevalent languages, which may be of use to States that do not yet have a methodology in place. It may be that in a rural State, there are no non-English languages that would meet a prevalence test. In those instances, States must still arrange for oral interpretation and have a mechanism (see comment and response on § 438.10(b)) to assist non-English speaking beneficiaries to understand written materials that are not translated. 
                    </P>
                    <P>We believe the proposed rule gives considerable discretion to States in what methodology they use. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed support of the proposed rule's reinforcement of existing language requirements under title VI of Civil Rights Act of 1964. Others suggested specifically referencing in the rule guidance issued by the Office for Civil Rights, since it applies to States and plans receiving Federal funding under Medicaid. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support on this issue. We have disseminated the Guidance to States via a State Medicaid Director letter dated August 31, 2000, and it is also available on our website. We do not believe it necessary to specifically reference the OCR Guidance in the regulation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters noted that the definition of “prevalent” does not define what constitutes a “significant number or percentage.” They believe this is not sufficient guidance, and that there is no compelling need for States to have discretion. On the other hand, a few commenters expressed support for giving States the discretion to define prevalent. 
                    </P>
                    <P>The commenters concerned about lack of guidance uniformly recommended the final rule establish a minimum threshold. Recommendations included defining prevalent as 10 percent or 3,000; incorporating OCR guidance on “safe harbors,” and using a threshold of 5 percent in a localized area and a Statewide level of 5 percent as well. </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the language and format requirements are essential elements for ensuring that enrollees and potential enrollees receive the information necessary to make an informed choice and access benefits. While we believe they are essential elements, we also continue to believe that the best methodology for determining the prevalent language spoken by a population in a service area may differ from State to State and therefore we will not be modifying the regulation to mandate a specific methodology. We also note that the OCR policy guidance referenced above gives further examples and guidance on meeting individuals' language needs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that § 438.10(c)(2) requires States to 
                        <E T="03">provide</E>
                         written information in each prevalent language, but § 438.10(c)(3) only requires plans to make translated written material 
                        <E T="03">available.</E>
                         The commenter believes that this seems to suggest that unlike plans, States cannot simply respond to a request and instead must actually ensure it distributes translated materials to each beneficiary with limited English proficiency. The commenter stated this would be an onerous requirement, and recommended instead that latitude be given to States to respond to an inquiry. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the wording could be construed to required different levels of effort between the State and plans. In response to this comment, we are revising § 438.10(c)(2) to clarify that States need only make translated materials available. We note that § 438.10(c)(5) still requires States and plans to notify enrollees and potential enrollees that translated materials are available and how to obtain them. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that the proposed rule required States and plans to identify beneficiaries with limited English proficiency. However, the commenter believed that individuals with limited English proficiency should be able to self-identify and receive appropriate written and oral communication. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that beneficiaries with limited English proficiency should be able to self-identify and receive appropriate written and oral communication, and believe the regulation does allow this. First, anyone who self-identifies as having limited English proficiency would at that point be identified as such by the State as well as a result. Secondly, § 438.10(c)(5) requires States and plans to notify 
                        <PRTPAGE P="41012"/>
                        potential enrollees and enrollees about the availability of oral interpretation, written information in prevalent languages, and how to access those services. Those services are available regardless of whether the State or plan identifies the beneficiary as having limited English proficiency, or the beneficiary self-identifies as such. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter concurred with the requirement in § 438.10(c)(3) on making translated material available, and limiting it to written information. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenter's support for this clarification. 
                    </P>
                    <HD SOURCE="HD2">Oral Interpretation (Proposed § 438.10(c)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters noted that sign language was not specifically referenced in the proposed rule, and that interpretation for persons with hearing impairments is required by the Americans with Disabilities Act and title VI of the Civil Rights Act. One commenter suggested that clarification of this point in the regulation text would avoid confusion about the applicability of ADA requirements. The commenters recommended specifically including sign language and other interpreter services for beneficiaries with hearing impairments. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that sign language interpretation should be available for potential enrollees and enrollees with hearing impairments. However, § 438.6(f) specifically requires MCOs, PIHPs, PAHPs, and PCCMs to comply with the Americans with Disabilities Act and other applicable Federal statutes. We do not believe it would be necessary or appropriate to restate all of the specific requirements of that law in this section of the regulation text. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters supported the availability of interpretation services, but believed it would be extremely difficult for most office-based physicians to set up and finance these services. They noted there is little coverage of these services by States, and the cost would be substantial for office-based physicians, often exceeding their reimbursement for the office visit itself. The commenters felt it was critical that we require States to create and fund systems to ensure appropriate interpretation services Statewide. They further stipulated that the services should be funded separately, not bundled into provider or capitation payments. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we believe that it is appropriate and necessary to require that interpretation and translation services be available for all potential enrollees and enrollees, we also believes that the States should be afforded the flexibility to determine how these translation services are provided and paid for. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter contended that the requirement in § 438.10(c)(4) to make oral interpretation available for all non-English languages does not take into consideration special circumstances and characteristics of frontier States. To expect a State with a small population to have someone available to speak any possible language would be unreasonable in this commenter's view. This view was based on the commenter's belief that the increased cost and could result in decreased access if providers drop their participation in Medicaid. Another commenter argued that requiring oral interpretation for all languages was administratively burdensome and costly. The commenters recommended allowing State flexibility to determine if oral interpretation was necessary. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the difficulties in arranging for oral interpretation for languages that are less frequently encountered. However, we believe the proposed rule does not create any new requirements, but rather clarifies that existing requirements under title VI of the Civil Rights Act apply to Medicaid managed care programs. The OCR guidance reinforces this, but allows for flexibility in how oral interpretation is arranged. For example, it acknowledges that on-site interpretation may not always be realistic, in which case other options such as telephone language lines may be used.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters supported the requirement for provision of oral interpretation. One commenter specifically supported the provision that it be available free of charge to each potential enrollee and enrollee, but believed the requirement should be strengthened. The commenter suggested adding language stipulating that oral interpretation be provided when needed, and in a manner convenient to the beneficiary. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support of this provision. We believe that some flexibility is appropriate, as noted in the OCR guidance, which sets forth a variety of factors to take into consideration when determining how to provide meaningful translation. 
                    </P>
                    <HD SOURCE="HD2">Alternative Formats (Proposed § 438.10(d)(2)) </HD>
                    <P>As noted above, proposed paragraph (d) specified the format for information, and that alternative formats must be available for those with special needs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters supported the requirement that written material be available in alternative formats, but objected to the fact that the proposed rule did not expressly identify who was responsible for providing them. They believed that specifying responsibility was essential to ensuring that the information is transmitted in a timely manner. The commenters recommended that the final regulation specify that both the State and health plans have responsibility for making available their respective written materials in alternative formats. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the proposed rule makes clear that written material must be available in alternative formats. We believe that as drafted, it is clear that this requirement applies to whomever is providing the written material at issue to potential enrollees and enrollees. Therefore, we believe it is unnecessary to list each party in the regulations text. 
                    </P>
                    <HD SOURCE="HD2">Required Information — General (Proposed § 438.10 (e) Through (g)) </HD>
                    <P>As noted above, proposed paragraph (e) described information requirements for potential enrollees; paragraph (f) set forth the general information requirements for enrollees of MCOs, PIHPs, PAHPs, and PCCMs, and paragraph (g) contained specific information requirements for MCO and PIHP enrollees. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that requiring specific information for potential enrollees and enrollees would require additional State and contractor financial and staff resources. The commenter believed this would lead to increased costs of production and distribution for both State and plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate that additional resources may be needed to compile, produce, and disseminate the required information. However, we believe this information is critical for potential enrollees to make informed decisions, and enrollees to understand how to access services. 
                    </P>
                    <HD SOURCE="HD2">Information for Potential Enrollees (Proposed § 438.10(e)(1)(i)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters believed the proposed rule would result in a delay in potential enrollees receiving information. The commenters noted that as proposed, the rule would require information be given to potential enrollees when they become eligible to voluntarily enroll in managed care, or face mandated enrollment in managed care. They were concerned this could delay when beneficiaries receive the information, reducing the amount of time they have to digest it. Some 
                        <PRTPAGE P="41013"/>
                        commenters proposed that an additional option should be added, 
                        <E T="03">i.e.,</E>
                         the time when the potential enrollee first becomes eligible for Medicaid. Others recommended adding the following language to § 438.10(e)(1)(i): “When eligible to choose among MCOs, PIHPs, PAHPs, or PCCMs in a voluntary program.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the proposed rule ensures that potential enrollees are provided required information at the earliest appropriate time. We acknowledge that a beneficiary may become Medicaid eligible first, and only later be eligible to enroll in a voluntary program, or required to enroll in a mandatory program. However, we are concerned that the provision of information for which the beneficiary has no immediate use will result in the information being disregarded. In the majority of cases, a beneficiary becomes a “potential enrollee” immediately upon Medicaid eligibility determination, and in these instances will get the information at the time suggested by commenters. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that the proposed rule does not expressly require the State to provide the required information on a plan to all potential enrollees in the plan's service area. The commenter recommended adding this language. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The proposed rule requires the State to provide the required information to all potential enrollees, which already would include all potential enrollees in a particular plan's service area. Therefore, we believe it unnecessary to add the recommended language on ensuring that the information must be provided to all potential enrollees in a plan's service area. 
                    </P>
                    <HD SOURCE="HD2">Summary Information for Potential Enrollees (Proposed § 438.10(e)(2)(ii)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters supported proposed § 438.10(e)(2)(ii), which provided that States need only provide summary information specific to each plan, with detailed information to be provided upon request. They believe this flexibility allowed States and plans to make better use of their resources by giving specific information only where it is needed to make informed choices, without broadly disseminating voluminous information that will generally receive little attention. 
                    </P>
                    <P>Another commenter was concerned that the requirement for States to provide only summary information—versus providing detailed information—would mean that many potential enrollees may not receive basic information on service areas, cost-sharing, benefits covered, provider information (including family planning), and other benefits not covered under contract. The commenter believed the burden in providing more detailed information is minimal, so the final rule should require the State to provide detailed information to all potential enrollees, not just upon request. </P>
                    <P>Numerous commenters specifically objected to proposed § 438.10(e)(2)(ii)(E), which required the State to provide to potential enrollees only summary information on State plan services not covered by the contract. They believed this provision eliminated one way potential enrollees learn about the full range of what is available under the State plan. Some commenters were especially concerned that it was important for access to reproductive health services, which plans may not offer. Some commenters were concerned that the delay caused by needing to ask for the information could result in a beneficiary being defaulted into such a plan. Finally, there were commenters who asserted summary information was not adequate to allow potential enrollees to make an informed decision. </P>
                    <P>Many of the commenters recommended that the final regulation require detailed—not summary—information on all items specific to each MCO, PIHP, and PAHP. Others also suggested the final rule require health plans to refer enrollees to a State sponsored, toll-free number that informs beneficiaries about how and where to access services plan the plan does not provide. They further suggested that this information be provided on an annual basis and at the point of service. </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the proposed rule strikes the proper balance between providing needed information and ensuring the information is useful rather than overwhelming. The proposed rule does not preclude a State from providing detailed information. However, if it opts to provide summary information, then it must under § 438.10(e)(12)(ii) ensure potential enrollees and enrollees are informed that more detailed information is available upon request, and how to request it. Lists of Participating Providers (§ 438.10(e)(2)(ii)(D) and § 438.10(f)(6)(i)) 
                    </P>
                    <P>These proposed sections required the provision of a list of participating providers, including the name, phone number address, non-English languages spoken, and other information. </P>
                    <P>
                        <E T="03">Comment:</E>
                         For potential enrollees, one commenter suggested limiting the list of providers on whom information is provided to hospital and primary care. The commenter believed that providing a full specialty provider directory may create confusion on how to navigate the plan's referral process, giving the impression that referrals or authorization are not needed. The commenter recommended potential enrollees who want the specialty network information be directed to call the plan or enrollment broker. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Although we acknowledge that including information on specialists adds to the volume of information and further complicates the process of keeping information current, we do believe that a significant number of potential enrollees rely on this information and therefore continue to believe that, at a minimum, information on provider networks should include information on primary care physicians, specialists, and hospitals.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that even in summary format, provider information would be too voluminous, and its value for potential enrollees is highly questionable. In the commenter's view, based on experience with managed care, people are more likely to read mailings that contain simple, limited information focusing only on the most important issues. The commenter suggested the requirement be limited to informing potential enrollees how they can obtain this information. 
                    </P>
                    <P>Another commenter was unclear how provider network information could be summarized. Even a summary could be voluminous, especially if it has to be kept up to date. The commenter asserted that States need flexibility to determine the most efficient method that will get accurate information to beneficiaries via the easiest media. The commenter suggested making this information available upon request, with assistance available from both State and plans. </P>
                    <P>
                        <E T="03">Response:</E>
                         For many potential enrollees, a decisive factor in selecting a plan is whether their current primary care provider is in the network. For beneficiaries with disabilities or chronic illnesses, participating specialists can carry the same weight. We believe the flexibility to summarize provider information will allow States to minimize the volume. For example, clinics or group practices could be identified in lieu of listing individual physicians. States and their contractors must highlight to potential enrollees how to obtain detailed listings or to inquire whether a specific provider is participating. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter pointed out that identifying non-English languages spoken by providers—as required in 
                        <PRTPAGE P="41014"/>
                        § 438.10(e)(2)(ii)(D) and § 438.10(f)(6)(i)—is an example of how the proposed rule would impose requirements on managed care programs which are not required in Medicaid FFS programs. In the commenter's view, it would be problematic to obtain this information, and the State could place itself at risk if it is construed that it is in some way “certifying” their ability to speak the language. Another commenter noted that maintaining information on non-English languages spoken by specialists and hospitals is extremely difficult due to the frequency with which it changes. The commenter recommended this only be required for PCPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge that this information may be problematic to obtain and keep current. However, it is our belief that potential enrollees and enrollees need this information to make informed choices. We encourage States and plans to highlight to potential enrollees and enrollees that it is important to verify through a phone call or other means that the information is current. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters felt that it would be difficult to keep information on which providers are accepting new enrollees current—as required in § 438.10(f)(6)(i)—especially in a printed format. One of the commenters suggested clarifying that plans may state in their materials that potential enrollees must contact the plan for oral updates of this information, or that they be required to keep the printed information reasonably up to date. Another commenter suggested that the final rule be revised to require the plan to prominently display a toll-free number to get this information. Another recommended the rule be clarified to provide that a plan's best effort would be sufficient, or allow for a phone number to be available to provide the information. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge that this information is time sensitive; however, it is our belief that beneficiaries need this information to make an informed selection. Therefore, we encourage States and their contractors to highlight to potential enrollees and enrollees that it is important to verify through a phone call, or other means, that the information is still current. We also expect that States and their contractors will provide updates to provider directories within a reasonable time frame, although the exact time is left to the State to determine. 
                    </P>
                    <HD SOURCE="HD2">Required Information—General (Proposed § 438.10(e) through (f)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter observed that some of the information required before and after enrollment is duplicative. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the requirement to provide information on benefits, cost sharing, service area, and participating providers required for potential enrollees in § 438.10(e)(2)(ii) duplicates required information for enrollees in § 438.10(f)(6). However, we would note that for potential enrollees, States may provide summary information, with detailed information provided upon request. For enrollees, detailed information is necessary to understand the services for which they are covered and how to access them. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believes that all the required information for both potential enrollees and enrollees should be in writing, and should also be available to enrollees through a toll-free telephone number established by the State. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we expect that the required information will be provided in writing, we do not want to preclude other formats. We note that the “mechanism” for assisting enrollee understanding that we are requiring in response to comments on proposed § 438.10(b) will provide another source of information, though as noted above, we believe States and plans are in the best position to determine the most effective mechanism to be used. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters believed that a core patient protection is access to information on the quality of health plan and providers. This conforms with the President's Advisory Commission on Consumer Protection and Quality in the Health Care Industry. The commenters recommended requiring MCOs and PIHPs to provide to potential enrollees and enrollees, upon request, (1) information on licensure, certification and accreditation status of MCOs and health care facilities; (2) information on education, licensure, Board certification and recertification; (3) a description of cost-control procedures; (4) summary descriptions of methods of compensation for physicians; and (5) information on the financial condition of the plan, including the most recent audit. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the provision in § 438.10(g)(4), which requires MCOs and PIHPs to provide certain information upon request to enrollees, including information on the structure and operation of the plan, is sufficient to cover the bulk of the information the commenters specifically mentioned. As a result, we are not revising the regulations text to add additional references. 
                    </P>
                    <HD SOURCE="HD2">Notice of Disenrollment (Proposed § 438.10(f)(1)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested modifying the requirement for annual disenrollment notice to not apply when there is no lock-in, while several other commenters supported the requirement for States to notify enrollees of their disenrollment rights at least annually, and at least 60 days prior to each open enrollment period. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the proposed rule as written would be awkward for a program with no lock-in provision. However, we believe it important for enrollees to be notified annually of their disenrollment rights under § 438.56, even in a program with no lock-in, and therefore are not eliminating this provision. 
                    </P>
                    <P>Traditionally, States with no lock-in program could still delay the effective date of disenrollment to the beginning of the subsequent month, leading to a de facto lock-in of 1 month. Section 1932(a)(4) of the Act did not eliminate this scenario, but did permit States to lock-in enrollees for up to a year. The Act also provides that if there is a lock-in, enrollees can disenroll without cause for the first 90 days of enrollment in an MCO, which assumes that a lock-in period will be at least 90 days long. Finally, the statute provides that if States have a lock-in, they must notify enrollees at least 60 days prior to each annual enrollment opportunity of the right to disenroll. We are revising the regulation to clarify that the 60-day timeframe for notifying enrollees of the right to disenroll applies solely to programs with lock-ins of 90 days or greater. </P>
                    <HD SOURCE="HD2">Annual Notice (Proposed § 438.10(f)(2) and § 438.10(g)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters objected to the fact that the annual notice requirement in § 438.10(f)(2) need only notify enrollees of the availability of required enrollee information (that is, that they may receive it upon request) rather than requiring that the information be furnished to all enrollees. Many commenters believed that the result would be that many enrollees would not receive information for many years, and would be unaware of their rights, because they did not bother to specifically ask for the information. Some commenters found this especially problematic in light of the fact that some services may not be provided because of the conscience clause. One commenter 
                        <PRTPAGE P="41015"/>
                        noted that an annual mailing of a full set of information typically is sent to enrollees in private health plans, and believed that Medicaid enrollees deserve no less. Another commenter argued that by actually furnishing all required information yearly, rather than only upon request, enrollees are ensured timely information about their rights, as well as a complete compilation of the previous year's changes or amendments to services provided. Finally, a commenter expressed the view that the information in question is critical for enrollees deciding to remain with a particular plan or switch during an open enrollment season. 
                    </P>
                    <P>On a related issue, numerous commenters supported the MCO and PIHP-specific provisions in § 438.10(g), but recommended the annual notice in § 438.10(f)(2) be amended to require the information be provided in full on an annual basis. </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the arguments for ensuring enrollees have up-to-date information on the managed care plans with which they are enrolled. However, we believe the proposed rule achieves a balance. The rule ensures enrollees receive detailed information upon enrollment. In § 438.10(f)(4), we require plans to give each enrollee written notice of significant changes at least 30 days prior to the effective date of the change. To ensure that they are updated on all required information, we are adding a requirement at § 438.10(f)(2) and (f)(3) that enrollees be updated on changes to required information in § 438.10(g), regarding MCO- or PIHP-specific information. 
                    </P>
                    <HD SOURCE="HD2">Timing of Information to Enrollees (Proposed § 438.10(f)(3) Through (f)(5)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern about the requirement that plans send specified information to enrollees within a reasonable time after plans receive notice of enrollment. The commenter noted that in some cases, notice of enrollment precedes the effective date by a wide enough margin that it will be confusing to send the information that early. The commenter suggested revising the language in the proposed rule to read “a reasonable time after the MCO received the notice of the recipient's enrollment or the effective date of enrollment, whichever is later.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation requires that the information be provided within a “reasonable time after it receives, from the State or the enrollment broker, notice of the recipient's enrollment.” We believe that the State is in the best position to define this specific time requirement (
                        <E T="03">i.e.,</E>
                         what is “reasonable”) for providing this information. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that the requirement in § 438.10(f)(4) for 30 days written notice of any significant change, as defined by the State, is not always possible to comply with, since States do not always have 30 days notice of such changes. However, numerous other commenters supported the provision to require plans to give 30 days prior notice of significant changes. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we understand that there may be instances in which plans receive less than 30 days notice of a change, we believe this would be the rare exception, and that a general rule for 30 days notice would generally be possible to meet. We believe that where it is possible, this timeframe should be satisfied, since we believe that it is needed in order to give enrollees adequate notice of significant changes that could affect their care. As a result, we are not changing this provision. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned that the provision in § 438.10(f)(5) requiring 15 days notice to enrollees of their provider's termination from the plan's network was not enough to ensure continuity of care. The commenter recommended requiring 60 days notice, with prior approval by the State. The commenter further suggested that if 60 days notice is not given, the plan should pay for enrollee care from the terminating provider for 60 days or until the enrollee transfers to another plan. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize a more stringent threshold would likely further promote continuity of care, and we believe the proposed rule provides States with the discretion to do so. However, we also recognize the reality that providers often give little notice of their plans to terminate participation in a network. We believe the proposed rule provides a realistic threshold that protects enrollees' interests. 
                    </P>
                    <HD SOURCE="HD2">Required Information for All Enrollees (Proposed § 438.10(f)(6)) </HD>
                    <P>Paragraph (f)(6) sets forth information that must be provided to all enrollees. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter found that the requirement in § 438.10(f)(6)(i), to provide the names and other information for hospital and specialists, would be impractical for a PCCM program, since all Medicaid-participating providers are eligible. The commenter observed that specialists also move, change offices, etc., making maintenance of such a list impractical. In addition, the commenter noted that identifying all participating PCCMs for enrollees does not seem necessary or reasonable. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter, and in response to this comment are conforming the language in § 438.10(f)(6)(i) to the language in § 438.10(e)(2)(ii)(D), which clarifies that information on specialists and hospitals is only required for MCOs, PIHPs, and PAHPs. We are also clarifying the State need only identify participating PCCMs in an enrollee's service area. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters supported the statement in the preamble to the proposed rule that information provided must (1) clearly indicate which providers are available under any subnetworks with which a plan contracts, and (2) explain the procedures under which an enrollee may request a referral to an affiliated provider not in the subnetwork. These commenters believed that compliance with this requirement was especially important for women who may be obtaining services from a subnetwork that limits access to reproductive health services. The commenters recommended including an explicit requirement in the regulation text, specifically in § 438.10(f)(6)(ii). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we do not believe it would be appropriate to dictate permissible contracting entities for plans, we do require under § 438.10(e)(2)(iii) that if there are restrictions within a network, the beneficiary be informed of these restrictions as part of the information that they receive. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters noted that the preamble to the proposed rule specifically discussed the provision of information on pharmaceuticals, mental health and substance abuse benefits. H.R. 2564, as passed by the House, and supported by the President, specifically requires disclosure of prescription drug benefits. If the intent is for plans to disclose this information, the commenters believed that § 438.10(f)(6)(v) should explicitly list them. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the language in § 438.10(f)(6)(v) already ensures full disclosure of information on all benefits, including prescription drug coverage and mental health benefits. It requires information on the “amount, duration, and scope of benefits available under the contract in sufficient detail to ensure that enrollees understand the benefits to which they are entitled.” Since this applies to all contracted benefits, it is unnecessary to single out specific benefits in the regulation text. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters noted that proposed § 438.62 would require States to ensure continued services to beneficiaries who are transitioning, out of an MCO, PIHP, PAHP, or PCCM, but did not require 
                        <PRTPAGE P="41016"/>
                        that enrollees be provided with information on how to obtain benefits during such a transition. The commenters recommended adding this as required information for enrollees. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The proposed rule requires the State agency to actively arrange for continued services to beneficiaries transitioning in and out of a managed care system. We believe States should be given discretion as to how they fulfill that responsibility. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the requirement in § 438.10(f)(6)(vii) to specify the ability to access family planning providers out of network. They recommended clarifying that this requirement applies to all plans, not just those with conscience clauses. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that it is clear that the language in the proposed rule applies to all managed care programs (unless this obligation were ever waived under a section 1115 demonstration), and are not making further revisions. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         With respect to § 438.10(f)(viii)(C), one commenter noted that in some frontier and rural States, 911 is not yet operational throughout the State. The commenter stated that printing and updating materials specific to the system in each locale would increase costs and burden. The commenter observed that this would also lead to another situation in which managed care requirements would be greater than those in fee-for-service. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirement for providing information on how to use the 911 service is limited, implicitly, to areas where this service exists to use. For areas that have not yet implemented a 911 system, it would be acceptable for the State to generally instruct the enrollee to call their local emergency number without specifying the actual phone number. We believe that it is important, however, to include information on using 911 wherever this service is available. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked why the requirements in § 438.10(f)(6)(viii)(D) through (f)(6)(viii)(E) concerning the provision of information on emergency services applied to PCCM programs. The commenter believed that in PCCM programs, there were no additional restrictions on which emergency settings PCCM enrollees can use. The commenter believed there was no difference between PCCMs and regular FFS Medicaid on this point. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While enrollees must be able to access emergency care at any hospital setting, MCOs, PIHPs, and PAHPs also often contract with specific hospitals for these services; in those instances, these contracted providers need to be identified. We acknowledge that the only contracted providers in PCCM programs are PCPs. For PCCM programs, it will be sufficient for the State to direct enrollees to the nearest emergency room. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters supported the requirement in § 438.10(f)(6)(viii) through (f)(6)(ix) that MCOs and PIHPs make certain information available to enrollees regarding how emergency services are covered, and the process for accessing these services. Some of the commenters, however, suggested that plans also be required to send required enrollee information on emergency care to affected providers and hospitals. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Since an enrollee must be able to access emergency services at any hospital setting, it would be virtually impossible for plans to send the information to all such providers. For hospitals and providers with which plans contract to provide emergency services, § 438.230(b)(2)(ii) requires that a subcontract “[s]pecifies the activities * * * delegated to the subcontractor,” so this would ensure that at least these providers would be aware of procedures regarding emergency services. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters believed there was a gap in proposed § 438.10(f)(xii) with respect to how enrollees would be informed of where and how to obtain counseling or referral services that plans do not provide on the grounds of moral or religious objection. As written, these commenters asserted that the proposed rule does not require plans to provide information, nor refer enrollees to a source of information concerning these services. They acknowledged that States are required to provide this information, but did not feel that it should be up to the enrollee to figure this out. Some commenters argued that requiring enrollees to go to two places to obtain information about how and where to access family planning services is confusing, constitutes a barrier to care, and could delay care unnecessarily. These commenters believed this would permit discrimination against women, ignoring their health care needs. Another commenter noted that remedying this problem would reduce State burden in complying with the requirements. A few commenters felt that as written, the proposed rule would permit plans to create “gag rules” against physicians and other health providers, who can be barred from even discussing how to find information about certain services. Finally, some commenters believed that this provision violated section 1932(b)(3)(B)(ii) of the Act, which requires plans to inform enrollees about services not covered because of moral or religious objections. 
                    </P>
                    <P>Several commenters recommended that plans be required to refer enrollees to where they can obtain the information addressed in section 438.10(f)(xii). Some commenters suggested that plans specifically provide referral to toll-free line—which States should be responsible for maintaining—that tells beneficiaries how and where to access services the health plan does not provide. A few also suggested that such a toll-free line be used to inform enrollees about the extent to which they can access out of network providers, including family planning (per § 438.10(f)(6)(vii)), and services available under the State plan but not under the contract (per § 438.10(f)(6)(xii)). Other commenters suggested that plans be required to inform beneficiaries of all State plan services not available in the plan but otherwise available in Medicaid, and that this information be provided at point of service and annually. </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe it would be inappropriate, and inconsistent with the intent of the conscience clause provision, to require a health plan that morally objects to a service to provide information on how and where to access the service. This is why we provided in the regulations that the State should be responsible for doing so. We believe the proposed rule was clear, in stating that information must be “furnished” by the State, that the State had the responsibility of providing beneficiaries with this information, not merely making it available to them. It appears, however, that at least some commenters have inferred some lesser level of State responsibility from the fact that the word “furnish” was used instead of “provide,” which is used elsewhere in the regulation text. While we believe these words to be interchangeable, the commenter seems to believe that furnish, as used here, means only that the materials must be furnished upon request (that is, “made available”). In order to avoid any such inferences, and to make it clear that States are required actually to provide this information to enrollees, we are revising the text of § 438.10(e)(2)(ii)(E) and § 438.10(f)(6)(xii) to use the word “provide” instead of “furnish” in describing the State's responsibility. We are also revising § 438.102(d) to clarify the State is responsible for providing the required information not only for potential enrollees, but for enrollees as well. We believe States should be given 
                        <PRTPAGE P="41017"/>
                        discretion as to how they fulfill that responsibility.
                    </P>
                    <HD SOURCE="HD2">MCO/PIHP Specific Information (Proposed § 438.10(g)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter urged that it be made clear how grievances and appeals work, not only within the health plans, but within State government as well. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.10(g)(1)(i) requires that plans provide information on the State fair hearing process, as well as their own grievance procedures. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended that the required information for MCOs and PIHPs should also apply to PAHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The information requirements in § 438.10(g) of the proposed rule reflect requirements elsewhere in the regulation that apply only to MCOs and PIHPs. However, in response to a comment on § 438.2 and 438.8, two additional provisions on which information is required in § 438.10(g) are being imposed on PAHPs. First, under § 438.8(b)(1)(ii), the advance directives requirement in § 438.6(i)(2) now applies to the extent that the PAHP includes any of the providers listed in § 489.102(a). Second, PAHP enrollees are entitled to an affirmation of their right to a State Fair Hearing. In response to this comment, and as noted above, we are adding a new paragraph (h) for PAHP-specific requirements (with proposed paragraph (h) renamed paragraph (i)), and including a reference to it in appropriate parts of § 438.10(f). Finally, § 438.6(h) and 438.8(b) of the proposed rule already extended the Physician Incentive Plan requirements of 434.70 to PAHPs. We are adding in the new paragraph (h) of § 438.10, that this information be provided upon request. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was unclear as to why the information on provider appeal rights required by proposed § 438.10(g)(1)(vii) was critical for enrollees. In the commenter's view, enrollees already feel that the amount of information they currently receive is too much, or borders on it. The commenter suggested requiring plans to send notices of provider appeal rights to network providers rather than enrollees. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirement in § 438.10(g)(1)(vii) simply reflects the statutory requirement in section 1932(a)(5)(B)(iii) of the Act that information on “procedures available to * * * a health care provider to challenge or appeal the failure of the organization to cover a service.” This should not be interpreted as creating a new right in Medicaid for providers to file an appeal. However, should the State, MCO, or PIHP provide for such a right, they must inform enrollees of its availability. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters noted that under the grievance and appeals rules in proposed subpart F of part 438, enrollees have the right to representation. These commenters were believed that grievances and appeals are complicated proceedings involving difficult to understand rules, and that enrollees should be made aware they have the option to obtain assistance. In addition, the commenters believed that enrollees should be protected against retaliation for filing an appeal or grievance, and provided with information on this right as well, so they will not forgo appeals out of fear of retaliation. The commenters recommended requiring health plans to inform enrollees they have a right to representation, and that they will not suffer from retaliation for filing an appeal or grievance. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that enrollees need to understand the grievance system for it to be effective. However, we note the proposed rule at § 438.10(g)(1)(iv) already stipulates that enrollees must be informed of the “availability of assistance in the filing process.” We believe this is sufficient to ensure enrollees understand the ability to obtain assistance, and are not adding the suggested clarification. We also disagree with the commenter that it is necessary to include an explicit statement that the beneficiary will not face retaliation for appealing. We do not believe that beneficiaries would assume that they would face retaliation in such a case. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters questioned the provision of complex information such the information on physician incentive plans provided under proposed § 438.10(g)(3)(B). These commenters believed that many enrollees would not want such information, and may have difficulty understanding it, making its automatic provision counterproductive. The commenters recommended making it available upon request. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that requiring the provision of detailed information on physician incentive plans may be counterproductive. We are revising the regulation to provide at § 438.10(g)(3)(B) to require MCOs and PIHPs to inform enrollees it is available upon request. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters objected to the lack of a requirement for plans to notify enrollees of their ability to obtain, upon request, information on requirements for accessing services, including factors such as physical accessibility. These commenters believed that if plans did not furnish this information, the enrollee would have to contact numerous providers to obtain such information. In an emergency, the commenters were concerned that this could delay lifesaving care. One commenter referenced the need for TTY's service. Commenters also specifically noted that the 14th recommendation in CMS' Report to Congress on Special Needs addressed ensuring that plans and providers are physically accessible to those they will serve. Other commenters asserted that this was a requirement of the Americans with Disabilities Act. The commenters urged that plans be required to notify enrollees that this information is available upon request, and that this also be included in the annual notice. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the overall requirements of this section, in particular the new requirement for a mechanism to assist beneficiaries understand the managed care program and their own plans requirements and benefits, will fulfill the needs identified by the commenters. Further, § 438.6(f) specifically requires MCOs, PIHPs, PAHPs and PCCMs to comply with the provisions of the Americans with Disabilities Act and other anti-discrimination statutes. We do not believe any additional changes to the regulations text are necessary. 
                    </P>
                    <HD SOURCE="HD2">Comparative Information Under the State Plan Option (Proposed § 438.10(h)—Current § 438.10(i)) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that there is a common understanding that quality and performance indicators are still evolving. This commenter believed that the reliability of such indicators for comparing plans varies for reasons such as difficulty in adjusting for factors not within the plan's control; reporting inconsistencies; or lack of statistical validity due to small plan size. The commenter recommended requiring States to address these issues as they determine which measures to include, and how the information is presented, explained, and qualified. In addition, the commenter recommended that the final rule advise States whether there are circumstances in which reporting data that is not statistically valid would be misleading. 
                    </P>
                    <P>
                        A few commenters urged that MCO information be consistent with HEDIS standards, and be based on the MCO's overall performance. Another commenter suggested giving States the latitude to develop and apply regional standards for comparative information. Finally, a commenter contended that disenrollment rates are not valid 
                        <PRTPAGE P="41018"/>
                        indicators when auto-assignment is used. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that States are aware of the evolving nature of quality indicators. The proposed rule includes the statutory discretion in section 1932(a)(5)(c)(iii) to provide quality indicators “to the extent available.” We believe States are in the best position to determine which quality indicators to use, and that there is no impediment to regional standards for comparative information. With respect to disenrollment rates, we agree that there are valid concerns with respect to their use in a situation with auto-assignment. We note that disenrollment rates were not included in Medicaid HEDIS because of methodological problems, including the fact that most were related to loss of Medicaid eligibility. As a result, in response to this comment, we are revising the regulation at § 438.10(i)(3)(iv) to delete the reference to disenrollment rates. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that the type, scope, nature, and format of the comparative information that must be furnished in the case of the State plan option would be extremely costly. Another commenter argued that charting this information for individual PCCM providers would unduly complicate comparisons for enrollees, and be confusing for many service areas. This commenter believed that collection and maintenance would be cumbersome and costly to the State. The commenter suggested deleting this requirement for PCCMs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize these requirements will result in some additional costs, but do not believe compliance will be as onerous as the commenter believes. The information on benefits, cost-sharing, and service area are already available to the State. We do not have any flexibility on the requirement that information be presented in a comparative chart-like format, since this is specifically required by section 1932(a)(5)(C) of the Act. We also do not have flexibility on the applicability of this requirement to PCCMs under section 1932(a)(1) authority, as this is also required under section 1932(A)(5). (Section 1932(a)(5) requires the provision of information on “managed care entities,” which includes MCOs and PCCMs.) 
                    </P>
                    <P>There is flexibility for States to provide certain information that is identical across plans or PCCMs only once. For example, the State may provide a list of services provided or coordinated by all entities, and only identify and compare variations such as additional services provided, or services not provided because of the entity's religious or moral objections. The quality indicators are only required “to the extent available.” </P>
                    <P>We are, however, clarifying that the State need only provide comparative information on MCOs and PCCMs on a service area basis, to ensure that enrollees do not receive information on entities with which they cannot enroll. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that it did not make sense to require the comparative information to be provided to potential enrollees at least once a year. The commenter assumed this was an error. The commenter suggested making this information available to enrollees and potential enrollees, rather than furnishing it. The commenter further suggested that States be required to provide the information prior to enrollment or anytime upon request. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenter is correct that we made an error. The error, however, was not the fact that the information be provided, rather than merely being made available upon request. Rather, the error was in omitting a reference to enrollees in what is now § 438.10(i)(3). Section 1932(a)(5)(C) provides that “A State that requires individuals to enroll with managed care entities under paragraph (1)(A) shall 
                        <E T="03">annually</E>
                         (and upon request) 
                        <E T="03">provide,</E>
                         directly or through the managed care entity, to such individuals * * *.” The statute thus requires that information be provided to all potential enrollees 
                        <E T="03">and</E>
                         enrollees, and contrary to the commenter's suggestion that information only be made available upon request, it requires that this information be “provid[ed]” annually. Thus, in this respect, the regulation is not in error. We are making the needed correction to conform § 438.10(i)(3) in this final rule with the statute. Specifically, we are clarifying that the information needs to be provided to potential enrollees in the timeframe required in § 438.10(e)(1) (since enrollment is mandated for potential enrollees under section 1932(a)(1), these individuals would be enrollees when the obligation to provide information after one year occurs), and that enrollees should receive it annually and upon request. Further, we are acknowledging in § 438.10(i) that the comparative information required in this paragraph may duplicate what is required in § 438.10(e) for potential enrollees and § 438.10(f)(6) for enrollees. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters supported the idea that access to comparative information on health plans is essential to allow Medicaid beneficiaries to make informed choices. The commenters believed that exempting PIHPs and PAHPs from this requirement would undermine true competition among plans. The commenters recommended including PIHPs and PAHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirements in § 438.10(i) (proposed § 438.10(h) apply only to managed care programs operated under State plan amendment, as authorized by Section 1932(a)(1) of the BBA. States may only use this authority for mandatory MCO and PCCM programs; mandatory PIHP and PAHP programs cannot be operated under this authority. Thus, § 438.10(i) applies, PIHPs and PAHPs that are not also PCCMs (if they wee, they would be included as such) would not be among the plans from which beneficiaries could choose. As a result, we are not extending the requirement for comparative information to PIHPs and PAHPs as the commenter suggests. 
                    </P>
                    <HD SOURCE="HD2">Technical Corrections </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters noted areas where technical corrections are needed. In the introductory paragraph of § 438.10(g), the reference should be to “438.10(f)” instead of “§ 438.10(e).” In § 438.10(h)(1), they noted the correct reference was “(h)(3),” not “(g)(3).” In § 438.10(h)(3), they recommended changing “paragraph (d)” to “paragraph (e),” and changing “paragraph (g)(2)” to “paragraph (h)(2).” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters pointing out the errors, and are making the recommended corrections. In addition, we are correcting a drafting error in § 438.10(a), in the definition of “potential enrollee.” Specifically, we are deleting the words “in a” in the phrase “* * * not yet an enrollee of a specific in a MCO * * *” 
                    </P>
                    <HD SOURCE="HD3">6. Provider Discrimination (Proposed § 438.12) </HD>
                    <P>
                        Proposed 438.12 would implement the prohibition on provider discrimination in section 1932(b)(7) of the Act. The intent of these requirements is to ensure that an MCO does not discriminate against providers, with respect to participation, reimbursement, or indemnification, solely on the basis of their licensure or certification. We extended this requirement to PIHPs and PAHPs in proposed § 438.12. These requirements do not prohibit an MCO, PIHP or PAHP from including providers only to the extent necessary to meet their needs. Further, the requirements do not preclude an MCO, PIHP or PAHP from establishing different payment rates for different specialties, and do not preclude an MCO, PIHP or PAHP from establishing measures designed to maintain the quality of services and 
                        <PRTPAGE P="41019"/>
                        control costs, consistent with its responsibilities. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter agreed that health plans should be prohibited from excluding providers from their networks for reasons that are inconsistent with public policy, such as discrimination against providers serving a high need population or retaliation against providers who advocate on behalf of their patients. However, the commenter stated that the vast majority of health plans' decisions are wholly unrelated to these concerns. The commenter noted that the issuance of a written notice is unlikely to prevent the few cases of improper conduct. The commenter believed that the written notice provision would impose an unnecessary administrative burden and cost on health plans without substantially protecting providers, and therefore should be eliminated. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We continue to believe that such notice is important to help enforce the anti-discrimination requirements in section 1932(b)(7) of the Act and § 438.12. The notice will provide reasons why providers were not included in the MCO's, PIHP's, or PAHP's network and may be used by States in its monitoring efforts. Further, we estimate that it will take one hour to draft and furnish any given notice and on average each MCO, PIHP, and PAHP will only need to produce 10 notices per year. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter strongly disagreed with this provision, as the commenter believed it was intervening with the ability of the MCO to contract and develop networks without undue restraint. The commenter specified that in a managed care business model, selection of networks is made on the basis of quality and market need and that States should be given the latitude to address these issues as part of their network analysis. The commenter also argued that this provision would handicap MCOs in requiring all providers be credentialed. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. Section 438.12, implementing section 1932(b)(7) of the Act, provides sufficient latitude for MCOs, PIHPs and PAHPs with respect to network selection. This provision does not require MCOs, PIHPs and PAHPs to contract with providers beyond the number necessary to meet the needs of its enrollees. Further, this provision does not preclude these entities from establishing measures for provider selection that are designed to maintain quality of services and control costs and are consistent with its responsibilities to enrollees. Finally, this provision does not require entities to contract with any willing provider. We also would not have the discretion to eliminate this provision even if we agreed with the commenter, as it is set forth in the statute. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter urged CMS to clarify in this section that Medicaid managed care entities may not prohibit or limit fully licensed physicians, such as psychiatrists from providing services within their scope of practice. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirements in § 438.12 are intended to ensure that an MCO, PIHP or PAHP does not discriminate against providers with respect to participation, reimbursement or indemnification solely on the basis of their licensure or certification. We do not believe it is appropriate to include the suggested statement, as this requirement does not pertain to scope of practice. Section 438.214 addresses provider selection and credentialing requirements. 
                    </P>
                    <HD SOURCE="HD2">B. State Responsibilities (Subpart B) </HD>
                    <P>Proposed subpart B set forth the State option to implement mandatory managed care through a State plan amendment, as well as other State responsibilities in connection with managed care, such as beneficiary choice, provisions for disenrollment, continuity of care, conflict of interest standards, limits on payment, and monitoring. </P>
                    <HD SOURCE="HD3">1. State Plan Requirements (Proposed § 438.50) </HD>
                    <P>Proposed § 438.50 permits State agencies to enroll most Medicaid beneficiaries in MCOs or PCCMs on a mandatory basis without a waiver under sections 1915(b) or 1115 of the Act, and without being out of compliance with the provisions in section 1902 of the Act for Statewideness, comparability, or freedom of choice. Paragraphs (b) and (c) set forth the requirements for these programs and the assurances that States must provide. Paragraphs (d) and (e) identified populations that cannot be mandatorily enrolled in an MCO or PCCM and address the requirements for a default enrollment mechanism. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters viewed proposed § 438.50(b)(2) as a first step in better understanding how managed care organizations pay physicians and recognize that payment to providers in managed care is controlled by the managed care organizations. The commenters recommended that CMS also require managed care plans to specify the manner in which increases in Medicaid payment for services will be passed through to intended physicians. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.50(b)(2) is a general requirement that a State plan amendment under this authority specify the payment arrangement between the State and its managed care contractor. This section does not require the submission of any information regarding payment mechanisms or amounts between MCOs and their subcontracting providers. CMS does not review these subcontracts. We do not believe that it is necessary to impose these requirements beyond requiring that payments to providers be sufficient to encourage sufficient provider participation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the provisions for public involvement in the design and implementation of the State plan amendment and on-going public participation after implementation of the State plan amendment as proposed in § 438(b)(4). One commenter opposed the requirements for public involvement citing that this requirement is not applied to any other State plan amendment and requires additional State resources. The commenter suggested that latitude be given to States with history of public appearance. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While not all State plan amendments require public involvement, this language is consistent with the public notice requirements of the State Children's Health Insurance Program and reflects the requirements under the section 1115 of the Act demonstration authority. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters suggested adding PIHPs and PAHPs, as well as MCOs and PCCMs, to the introductory clause in § 438.50(d), which describes populations that cannot be mandatorily enrolled in an MCO or PCCM under the authority in section 1932(a) of the Act and § 438.50(a). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(a)(1) prohibits States from mandatorily enrolling specified groups of beneficiaries in MCOs and PCCMs under the authority in that section, which is implemented in § 438.50. This section of the statute and regulations only permit States to enroll beneficiaries in MCOs and PCCMs, even if the beneficiaries are not in an exempted group. Since this provision is an exception to authority that only permits enrollments in MCOs or PCCMs, it is not appropriate to reference PIHPs or PAHPs in this provision. Unless the PAHP also qualifies as a PCCM, and thus, would already be covered by this latter term, enrollment in a PIHP or PAHP may only be mandated under waiver authority in sections 1915(b) or 1115(a) of the Act. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received several comments on the enrollment by default 
                        <PRTPAGE P="41020"/>
                        in proposed § 438.50(f) with one commenter applauding CMS' effort to maintain existing relations that recipients may have with providers. Another commenter recommended that CMS delete the specific requirements to take relationships with existing providers into account. Two commenters believe that the default enrollment process discourages health plans and providers who have not traditionally served Medicaid beneficiaries. Another commenter inquired as to how the default enrollment process should function if the individual's provider is part of more than one MCO network. One commenter recommended that the default enrollment process consider geographic location, family relations and special needs of the individual. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(a)(4)(D) of the Act clearly states that the default mechanism must consider existing relationships or “relationships with providers that have traditionally served beneficiaries under this title.” We believe that the States should have the flexibility to consider other factors in the design of a default enrollment process that best meets the needs of the individual, including factors suggested by the commenter. Therefore, we have not added any new requirements to § 438.50(f). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters requested clarification of the phrase in proposed § 438.50(f)(2), “must distribute the recipients equitably.” One commenter recommended that the regulation be restated to explicitly grant States the right to determine what is an equitable distribution. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This provision requires States to have a process whereby they can assign beneficiaries to MCOs or PCCMs, if the beneficiary does not exercise his or her right to choose. When the State is unable to make an assignment based on an existing provider-recipient relationship or a relationship with a provider that has traditionally serviced the Medicaid population, it must do so by distributing “the recipients equitably among qualified MCOs and PCCMs available to enroll them.” The State is the only party that can determine when it is unable to make an assignment based on its records of an existing relationship or traditional service to the Medicaid population. Further, we agree with the commenter that the State is best suited to determine how to make an equitable distribution of default-assigned beneficiaries. This may be done through a specific assignment algorithm or as a simple distribution among all qualified providers up to any limits established. We have added language to the text of § 438.50(f)(2) to clarify this. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         To help ensure the best quality of care, one commenter recommended that the proposed requirement for “existing provider-recipient relations” in § 438.50(f)(3) be based on the provider being the main source of Medicaid services for the recipient in the last 2 years. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that a 1-year period allowed in § 438.50(f)(3) is sufficiently long to identify an existing provider-recipient relationship. This provision only applies to the default assignment of individuals who did not take the opportunity to choose their MCO or PCCM, and we would assume that most individuals would make this selection if their relationship with a particular provider is important to them. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concerns that these provisions in § 438.50 do not directly address the importance of ensuring that families are able to choose among health plans and health care providers when enrolling in mandatory managed care plan. The commenter believes that the process of auto-assigning can cause problems with the assignment of different family members of the same family to numerous providers and the assignment of certain individuals to providers many miles away and recommended that States be required to make every effort to ensure that families make their own selections. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Through a mandatory assignment under § 438.50(f), or any mandatory managed care arrangement under a waiver authority, it is possible that individuals in a family may be assigned to different providers. We do not believe that this should be prohibited, since the arrangement may be in the best interest of the individuals in the family based on their specific health care needs. If this assignment is problematic, all enrollees are free to disenroll without cause during the first 90 days of their enrollment period. Consequently, we do not believe any changes are warranted in this provision. 
                    </P>
                    <HD SOURCE="HD3">2. Choice of MCOs, PIHPs, PAHPs, and PCCMs (Proposed § 438.52) </HD>
                    <P>Proposed § 438.52 implements the requirement in section 1932(a)(3) of the Act that States must permit an individual to choose from at least two MCOs or PCCMs, but would have permitted States to offer a single MCO in a rural area under certain conditions, and to offer a single HIO in certain counties. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters were concerned about the impact of these regulations on States with a single carve-out PIHP contract, such as a mental health carve-out in a non-rural area, because the requirement for choice in this section would appear to prohibit this type of program. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Although we are extending the choice requirement in § 438.52 to PIHPs and PAHPs under the authority of this regulation, the Secretary will continue to have the discretionary authority to grant waivers for the operation of managed care programs contracting with single PIHPs or PAHPs on a case-by-case basis. 
                    </P>
                    <P>As under current provisions, these entities can operate under waivers of the freedom of choice requirement in section 1902(a)(23) of the Act, which permits a State to establish or continue a program. For the purposes of PIHPs and PAHPs, this waiver could extend to the requirement for choice in section 1932(a)(3) of the Act. All requirements that apply to PIHPs and PAHPs, including the choice requirement, are based only upon the regulatory authority for the existence of these entities, which is derived from section 1902(a)(4) of the Act, which can be waived under section 1915(b). The waiver would not be possible for MCOs or PCCMs since this section of the Act cannot be waived under section 1915(b). </P>
                    <P>Therefore, under these rules, as before, CMS can grant States a waiver to operate a program with a single PIHP or PAHP, in a rural or non-rural area. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter pointed out that a State could not restrict enrollment in one plan as a sanction in non-rural areas where only two plans exist, because the State would not be in compliance with this requirement for choice. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenter is correct that a State cannot impose a sanction that would leave only one plan available in a non-rural area unless the State then offers fee-for-service as an alternative. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters suggested there should be no exception to allow a State to limit choice in rural areas. Another commenter felt that allowing a choice in a rural area of two primary care providers as opposed to two managed care systems, would limit choices that might in fact be otherwise available to an enrollee. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The exception allowing a State agency to restrict choice of coverage to a single MCO or PCCM system in rural areas is specified in section 1932(a)(3)(B) of the Act and cannot be revoked by this regulation. Even without the rural exception to the choice requirement permitted by section 1932(a)(3)(B), a State may limit a beneficiary's freedom of choice of providers in a rural or any other area 
                        <PRTPAGE P="41021"/>
                        through a waiver under section 1115 or 1915(b) of the Act, or a State plan amendment under section 1932(a)(1) of the Act. Both these waivers and the exception permitted under this rule may have the impact of limiting beneficiary choices, which would otherwise be available, as suggested by the commenter. However, the limitation in this rule is specifically authorized by section 1932(a)(3) of the Act. 
                    </P>
                    <P>We have specified conditions that must be met in order for this exception to be implemented. These include the requirement in § 438.52(b)(2) that a beneficiary in a rural area who has been receiving services from a provider that is not part of the managed care network can receive out-of-plan treatment from that provider on a limited basis, as specified in that paragraph. Thus, we believe that the statute and this final rule contain sufficient beneficiary protections when the choice of managed care entity is restricted in rural areas. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned that rural area PIHPs and PAHPs that do not include primary care services would not qualify for a rural exception because of the requirement to permit beneficiaries to choose from at least two physicians or case managers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         If either of these entities operating in a rural area do not include primary care services, then the requirement would not apply to them. These primary care services would be available through another source. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned about what the commenter saw as a contradiction in the preamble in the statement that, allowing beneficiaries in a single rural plan to choose another primary care provider in the network would make it unnecessary for a State agency to operate a parallel fee-for-service system for those individuals who disenroll for cause. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenter is correct that this statement is misleading, and a State may not always be able to be relieved from operating a fee-for-service system in this situation. The State may be obligated to cover out-of-network services on a FFS basis in the situations described in § 438.52(2)(b)(ii)(A) through (b)(ii)(D). Further, enrollees in a program operated under the rural exception to the choice requirement, have the right to disenroll from their primary care providers, but not necessarily from the single entity providing health care in the rural area (except for instances when the enrollee moves out of the entity's service area). When the enrollee no longer resides in the rural area served by the single entity, he or she may be required to re-enroll in a managed care entity serving his or her new area of residence. 
                    </P>
                    <P>However, the commenter is correct that there may always be individual instances when States must maintain the ability to make FFS payments to providers even if an entire parallel FFS system is no longer necessary. </P>
                    <P>
                        <E T="03">Comment:</E>
                         There were several commenters who appreciated requiring MCOs to solicit enrollment of providers who are the source of service to a new enrollee, and to transition the enrollee within 60 days to other providers in the MCO network if the provider chooses not to participate. These commenters were concerned that rural area enrollees would otherwise remain out-of-network indefinitely. One commenter suggested a transition period shorter than 60 days and a few suggested a longer period. Many commenters felt that it was not appropriate to require a rural provider to join an MCO in order to continue to serve a patient with whom there was a prior relationship, particularly for pregnant women. They indicated belief that rural providers would choose not to enroll and, therefore, enrollees' choices would be severely restricted. Some commenters questioned if this section meets the requirement of section 1396u-2(a)(3)(B)(ii) U.S.C. to allow for consideration of when using an out-of-plan provider is “appropriate.” Some commenters opposed requiring MCOs to offer contracts to “any willing provider” because it would prevent MCOs from building networks that are the correct composition for their enrollees and would undermine the financial viability of MCO networks. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that in establishing the “appropriate circumstances” for allowing an enrollee to go out of network when there is a rural exception to choice, we need to balance the needs of enrollees with supporting good managed care practices. By requiring an MCO to offer a contract to any qualified provider who is the main source of service to the recipient, we prohibit the MCO from barring the client's access to that provider. The 60-day period provides sufficient time to assure that a provider has the option to continue to serve an enrollee with whom they have an existing relationship. Allowing a recipient to continue indefinitely (that is, as long as an acute medical condition exists) to see a non-participating provider could encourage providers to not contract with MCOs and not continue their participation in the Medicaid program. We especially want to encourage, rather than discourage, the continued participation of providers who treat pregnant women, and we believe that this provision helps to accomplish that goal. 
                    </P>
                    <P>We disagree with the commenter that this provision requires MCOs to offer contracts to “any willing provider.” Section 438.52(b)(2)(ii)(B)(2) specifically recognizes that a provider “may not meet the qualification requirements to join” the managed care network. If this is the case, there is no requirement that the provider be offered a contract, and the beneficiary must be transitioned into the managed care network. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters were concerned that the definition of “rural” at § 438.52(b)(3) does not recognize that a Metropolitan Statistical Area may be largely rural although it has a large city, and due to the rural nature outside the city it would be appropriate for an exemption to the choice of two MCOs requirement. They suggested that the State should apply its own definition of “rural” subject to approval of CMS. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We initially proposed three possible definitions of rural, and asked for comments. There was no clear consensus among the comments we received at that time, and CMS decided to use the single definition of rural based on being outside of an MSA. We believe that this definition best assures that States can use the exemption when appropriate but it reasonably limits the extent to which an area is considered rural, and is consistent with the Medicare definition for the purpose of defining rural hospitals. 
                    </P>
                    <HD SOURCE="HD3">3. Enrollment and Disenrollment (Proposed § 438.56) </HD>
                    <P>Proposed § 438.56 implements the provision in section 1932(a)(4) of the Act, and sets forth a number of requirements relating to enrollment and disenrollment in Medicaid managed care programs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter questioned the authority to apply the provisions of this section to voluntary managed care programs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(a)(4) of the Act contains new requirements that apply to the enrollment and disenrollment of beneficiaries in MCOs and PCCMs. In addition to applying directly to the mandatory programs under section 1932(a)(1)(A) of the Act, these requirements are incorporated under section 1903(m)(2)(A) of the Act for MCOs and section 1905(t) of the Act for PCCMs. In addition, through this regulation we are extending these provisions to PIHPs and PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters were pleased that the proposed § 438.56(b) was consistent with the Medicare+Choice requirements restricting disenrollment by a plan. One 
                        <PRTPAGE P="41022"/>
                        commenter was concerned that there was no guidance as to what would constitute acceptable grounds for disenrollment. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that § 438.56(b)(2) clearly identifies the reasons an MCO, PIHP, PAHP, or PCCM may 
                        <E T="03">not</E>
                         request disenrollment of a beneficiary. We have not provided other limits as long as beneficiaries are not disenrolled for these reasons. States may wish to establish specific instances in which entities may request disenrollment of a beneficiary in their contract provisions. 
                    </P>
                    <P>However, we note that § 438.56(b)(2) as set forth in the proposed rule omitted the word “adverse,” describing a change in an enrollee's health status, as contained in the prior section governing disenrollment by the plan in § 434.27(a)(2). We inadvertently omitted this term, and we have inserted “adverse” in the final rule to clarify that the prohibition on requests for disenrollment under this section applies only to adverse changes in health status, not where an enrollee's health status has improved. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed concern that the ability to disenroll without cause during the 90 days following initial enrollment would disrupt continuity of care and was contrary to HEDIS reporting timeframes. Several other commenters were concerned that 90 days was not enough time and there should be more flexibility to change without cause. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Under section 1932(a)(4)(A) of the Act, beneficiaries must be able to disenroll without cause from an MCO or PCCM within the first 90 days of initial enrollment. We have no authority to modify this requirement by this regulation, but we believe that represents a reasonable time period for enrollees to decide whether the managed care entity in which they are enrolled will best meet their needs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that all States with ongoing programs should be required to provide a right to disenroll without cause, immediately upon implementation of these regulations. The commenter also suggested that disenrollments for cause should be applied retroactively. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Nearly every State (that is not operating under the authority of a section 1115 demonstration) has already implemented the BBA rules regarding enrollment and disenrollment in accordance with the guidance contained in the letter to all State Medicaid Directors letter dated January 21, 1998. As discussed elsewhere, provisions of this rule will become effective 60 days following publication of this final rule and must be implemented by 1 year from the effective date of this final rule. 
                    </P>
                    <P>We believe that an automatic disenrollment without cause for all of the over 25 million Medicaid managed care enrollees upon implementation of the regulation would create a chaotic situation disrupting current patterns of care, and is not justified by any evidence of problems in States' existing Medicaid managed care programs. We do not understand how the commenter envisions implementing retroactive disenrollments for cause, but we do not believe there is any justification for the suggested provision. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters suggested that homelessness or being a migrant worker should be added as a cause for disenrollment at any time. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe it is necessary to add these conditions as a cause for disenrollment. A beneficiary in one of these circumstances, like all other Medicaid enrollees, is entitled to disenroll, without cause for the first 90 days of enrollment in an MCO, PIHP, PAHP, or PCCM. Further, he or she may still disenroll for cause after that date, if one of the conditions in § 438.56(d)(2) listed is met. Section 438.56(d)(2)(i) specifies that an enrollee's movement out of an MCO, PIHP, PAHP, or PCCM service area is one of the required examples of cause for disenrollment. We believe that this option will often be available to migrant workers. In addition, a State may include additional reasons, such as homelessness as a cause for disenrollment under § 438.56(d)(2)(iv). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was supportive of the reasons allowed for disenrollment with cause. Another commenter was concerned that the broad definition of cause for other reasons at §§ 438.56(d)(2)(iv) was too broad and could lead to disenrollment on demand, particularly if MCOs may approve disenrollment through the grievance process. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS has specified three specific circumstances where cause for disenrollment exists and permitted States to develop other reasons, including but limited to, the examples in § 438.56(d)(iv). It is not our intent in this provision to permit disenrollment on demand. States will make determinations on request for disenrollment based on these requirements and any others they select, and beyond these limited requirements, have the flexibility to implement this provision as best serves their beneficiaries and the Medicaid program. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the timeframe for processing disenrollments should be more flexible to accommodate situations where more time is needed to make a determination. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the fixed timeframe will assure that all information is properly collected and evaluated in a timely fashion. Making the timeframe flexible could create an incentive to delay in accumulating necessary information. This timeframe reflects the time permitted for the determinations previously, and we do not believe it was problematic. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the requirement in §§ 438.56(f)(1), that enrollees be given written notice of their disenrollment rights at least 60 days before the end of each enrollment period, would confuse enrollees and seem to encourage disenrollment. The commenter suggested that including disenrollment rights in enrollment materials, and providing information through the enrollment broker should be sufficient. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(a)(4) requires an annual notice at least 60 days before the beginning of an individual's annual opportunity to disenroll. We believe that this information will be provided to enrollees along with all other enrollment materials that must be provided in this time frame. The purpose of this requirement is to ensure that enrollees have sufficient information in order to make a decision whether or not to continue enrollment in their current MCO, PIHP, PAHP, or PCCM within the time allotted for a change in enrollment. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter applauded the requirement to automatically reenroll a recipient who was disenrolled solely because he or she lost Medicaid eligibility for a period of 2 months or less. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' support. 
                    </P>
                    <HD SOURCE="HD3">4. Conflict of Interest Safeguards (§ 438.58) </HD>
                    <P>Proposed § 438.58 requires as a condition for contracting with MCOs that States establish conflict of interest safeguards at least as effective as those specified in section 27 of the Office of Federal Procurement Policy Act. We received no comments on this section. </P>
                    <HD SOURCE="HD3">5. Limit on Payment to Other Providers (Proposed § 438.60) </HD>
                    <P>Proposed § 438.60 prohibits direct payments to providers for services available under a contract with an MCO, PIHP, or PAHP. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters asked what type of payments to providers are exempt from this prohibition on direct payments, based on exceptions in title XIX of the Act or Federal regulations, 
                        <PRTPAGE P="41023"/>
                        and whether this exemption applies to graduate medical education (GME) payments to teaching hospitals, requiring GME payments to be included in capitation rates. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The exemption in proposed § 438.60 applies to two types of providers—disproportionate share hospitals (DSH) and Federally qualified health centers (FQHCs). Section 1902(a)(13) of the Act specifically requires direct payments to these providers when they are part of an MCO provider network. The proposed provision would prohibit States from making direct payments to teaching hospitals for GME when their Medicaid patients are enrolled in, and their services are provided under a contract between the State and an MCO or PIHP. Proposed § 438.60 would require any GME payments to be included in the capitation rates paid the MCO or PIHP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters opposed this limitation on GME payments in managed care arrangements, arguing that States should be permitted to maintain their current payment methodology for GME. A number of these commenters stated that this prohibition on GME is directly contradictory to the Medicare managed care requirements, for GME be carved out and paid directly to the teaching hospitals, and asked for CMS' rationale for this inconsistency. 
                    </P>
                    <P>Many commenters stated that this requirement would adversely impact teaching hospitals and discourage them from participating in managed care. Others indicated that including GME payments in capitation rates would not work since payments vary widely by provider and therefore by MCO network. They added that including GME in capitation rates would take away States' control over whether and to what extent teaching hospitals receive payments intended to go to them. </P>
                    <P>Most commenters suggested that approved GME payments should be made an exception to this provision, like DSH and FQHC payments. </P>
                    <P>
                        <E T="03">Response:</E>
                         The intent of proposed § 438.60 was to prevent duplicate and inappropriate supplemental payments to providers. Under the new rules governing payments under risk contracts in § 438.6(c), States are expected to make actuarially sound payments to MCOs, PIHPs, and PAHPs that include amounts for all services covered under the contract. In most instances, we do not believe there should be a need for payments directly from the State to providers who are delivering all of their services to Medicaid MCO enrollees. The Congress has made a statutory exception to require States to pay directly to the two types of providers identified above, when their services are delivered through a Medicaid-contracting MCO. As some commenters pointed out, the Congress also made an exception for Medicare GME, where amounts are required to be carved out of Medicare managed care payments and paid directly to teaching hospitals. A rationale for treating GME differently in Medicaid would be that the Medicare statute specifically authorizes payment of GME, while the Medicaid statute does not contain a similar provision. 
                    </P>
                    <P>However, we recognize that GME payments have become a common payment practice in State Medicaid programs. In response to the concerns raised, we are amending § 438.60 to allow an exception to this prohibition on direct payment to providers, “where the State agency has adjusted the actuarially sound capitation rates paid under the contract in accordance with § 438.6(c)(5)(v), to make payments for graduate medical education.” The aggregate amount of allowable payments under this exception would be limited to the total amount that would have been paid under the approved state plan for FFS. We believe that this is an equitable approach that mirrors the requirements in Medicare managed care and addresses State concerns of preventing harm to teaching hospitals and Federal concerns of ensuring the fiscal accountability of these payments. As part of our larger strategy of improving the fiscal integrity of Medicaid payments, we also plan to study existing Medicaid GME payment arrangements and may issue additional policies in the future. </P>
                    <HD SOURCE="HD3">6. Continued Service to Recipients (Proposed § 438.62) </HD>
                    <P>Proposed § 438.62 requires States to arrange for continued services to beneficiaries who were enrolled in an MCO, PIHP, PAHP, or PCCM whose contract was terminated, or for any enrollee who is disenrolled for any reason other than ineligibility for Medicaid. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended adding provisions to require mechanisms to assure continued access for enrollees with ongoing health care needs who move from FFS to managed care, between one managed care entity and another, or from managed care to FFS. These commenters wanted the requirements to apply to all special needs children, beneficiaries over age 65, pregnant women, and other groups identified by the State and include procedures for notification regarding the State's transition mechanisms and assurances that enrollees' ongoing health care needs would be met. 
                    </P>
                    <P>These commenters felt that enrollees may not understand how to access continued services during transition and this could be dangerous for those with special health care needs for which continuity of care is necessary. For example, an enrollee who requires home health services may find himself unable to receive care while being transferred from one MCO to another. </P>
                    <P>Another commenter stated that it was important to have some type of mechanism to insure that individuals may be treated by their current provider for a reasonable period of time. One commenter also suggested requiring a period of up to 60 days for beneficiaries going through one of these transitions, during which they could continue an ongoing course of treatment with a nonparticipating health care provider. </P>
                    <P>Several commenters supported the proposed provision. </P>
                    <P>
                        <E T="03">Response:</E>
                         The goal of our proposed rule is to ensure that there are adequate protections for managed care enrollees, while providing flexibility to States to determine how to best implement these protections. Most States, in their waiver programs under sections 1115 or 1915(b) of the Act already have mechanisms in place to transition enrollees into managed care from fee-for-service (FFS) and from one MCO to another. Further, we are concerned that it would be very difficult to enforce the requirement when a recipient moves from managed care to FFS as there are few mechanisms in the FFS delivery system for care coordination and follow-up. 
                    </P>
                    <HD SOURCE="HD3">7. Monitoring Procedures (Proposed § 438.66) </HD>
                    <P>Proposed § 438.66 is a redesignation of § 434.63, with non-substantive revisions and appropriate changes in terminology, and requires States to have in place procedures for monitoring MCOs, PIHPs, and PAHPs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that since Medicaid provides care to many low income children, monitoring should include a focus on pediatric services. A recent General Accounting Office report (
                        <E T="03">GAO-01-749,</E>
                         published July 2001) found that States have done a poor job in complying with EPSDT requirements, particularly in the area of managed care. The commenter urged CMS to implement the GAO recommendations to work with States to develop a timetable for improving their compliance, and for highlighting best practices. 
                        <PRTPAGE P="41024"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have initiated a number of projects that address the GAO recommendations, and are working to improve our monitoring of States as well as identifying and providing needed technical assistance to them. 
                    </P>
                    <HD SOURCE="HD2">C. Enrollee Rights and Protections (Subpart C) </HD>
                    <P>Proposed subpart C set forth a variety of enrollee protections, including enrollee rights (proposed § 438.100), protection of provider-enrollee communications (proposed § 438.102), limits on marketing activities (proposed § 438.104), limits on enrollee liability for payment (proposed § 438.106) and cost-sharing (proposed § 438.108), rights in connection with emergency and post-stabilization services (proposed § 438.114), and solvency standards (proposed § 438.116). </P>
                    <HD SOURCE="HD3">1. Enrollee Rights (Proposed § 438.100) </HD>
                    <P>As part of these standards, proposed § 438.100, required that each MCO and PIHP have written policies with respect to enrollee rights, and that each MCO, PIHP, PAHP, and PCCM ensure compliance with Federal and State laws affecting the rights of enrollees, and ensure that its staff and affiliated providers take these rights into account when furnishing services. Under proposed § 438.100(b), States were required to ensure that each enrollee of an MCO, PIHP, PAHP, or PCCM has the right to (1) receive information regarding his or her health care; (2) be treated with respect and with due consideration for enrollee dignity and privacy; (3) receive information on available treatment options and alternatives that is presented in a manner appropriate to the enrollee's condition and ability to understand; (4) participate in decisions regarding his or her health care, including the right to refuse treatment; and (5) be free from any form of restraint or seclusion used as a means of coercion, discipline, convenience, or retaliation. Further, enrollees of MCOs or PIHPs were given the right to (1) be furnished health care services in accordance with proposed §§ 438.206 through 438.210; (2) obtain a second opinion from an appropriately qualified health care professional; (3) request and receive a copy of his or her medical records, and to request that they be amended or corrected. The State also had to ensure that each enrollee is free to exercise his or her rights, and that the exercise of those rights does not adversely affect the way the MCO, PIHP, PAHP, or PCCM and its providers or the State agency treat the enrollee. Proposed § 438.100(d) required that States ensure compliance with various civil rights laws. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters provided support for the enrollee rights provisions as proposed. Several other commenters felt that all of the rights in this section should apply to PAHPs as well as PIHPs, or that the differences between these two types of plans should be narrower. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In response to the latter comments, we have expanded the enrollee rights to be provided for PAHP enrollees. We have clarified that PAHP enrollees have the right to request and receive a copy of their medical records, and to request that they be amended, as specified in 45 CFR part 164. Further, we have revised § 438.100(b)(3) to provide that PAHP enrollees, consistent with the scope of the PAHP's contracted services, have the right to be furnished health care services in accordance with §§ 438.206 through 438.210. We also removed from the regulation text the language referring to the right to obtain a second opinion from an appropriately qualified health care professional in accordance with § 438.206(b)(3) to avoid duplication. Please note, this language was only removed to avoid duplication, we did not remove the right to a second opinion, as it is subsumed within § 438.100(b)(3) as one of the health care services enrollees of MCOs, PIHPs and PAHPs have the right to be furnished under § 438.206. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that CMS should consider HIPAA privacy rules before finalizing this rule to ensure that there is no conflict. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Health Insurance Portability and Accountability Act of 1996 (HIPAA) included comprehensive health privacy legislation. HHS published the final privacy rule on December 28, 2000 (65 FR 82462). The final rule took effect on April 14, 2001 and applies to covered entities as that term is defined at 45 CFR 160.103. Most health plans and providers must comply with the new requirements by April 14, 2003. Enforcement of the privacy rule requirements will not occur until April 2003. The compliance date for small health plans is April 14, 2004. The privacy rule gives patients greater access to their own medical records and more control over how their personal health information is used. Specifically, the privacy rule gives patients the right to access their records, request a change or challenge a particular part of the medical record, and have that challenge be included in the permanent records. The privacy rule also covers permissible uses and disclosures of protected health information and requires that appropriate safeguards are used to ensure against misuse of such information. This final rule neither conflicts with the privacy rule, nor does it impose any privacy provisions of its own. Moreover, nothing in this final rule affects a State's or any other covered entity's responsibilities under the privacy rule. We reference the privacy rule at §§ 438.100(b)(2)(vi), 438.208(b)(4), and 438.224, to the extent that it is applicable. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern that proposed § 438.100(a)(2) specifies that all MCOs and PCCMs must comply with any applicable Federal and State laws that pertain to enrollees rights. The commenter was concerned that State laws on enrollee rights might be in conflict with this section. The commenter expressed the concern that requiring MCOs to comply with two sets of regulations addressing the same operational areas is unnecessarily confusing and burdensome for MCOs and for managed care enrollees. The commenter requested that this provision be restated such that if State law on enrollee rights is consistent with section 1932(b) of the Act, CMS does not have the authority to impose additional regulation. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As Federal law supercedes State law, all States must conform with Federal regulations for Medicaid managed care enrollees, so there would not be a situation in which two conflicting sets of requirements would apply, and this concern of the commenter is not valid. We proposed these standards because interpersonal aspects of care are highly important to most patients and closely related to quality of care. Enrollees' interactions with the organization and its providers can have an important bearing on their willingness and ability to understand and comply with recommended treatments and hence on outcomes and costs. While many States have requirements in place that would assure these rights, not all States do. We believe that these minimum standards are justified for all Medicaid beneficiaries. We accordingly do not accept the commenter's suggestion that we defer totally to State law with respect to enrollee rights. However, we note that these Federal regulations set a floor for the level of enrollee standards. States may establish more stringent standards that are not inconsistent with these requirements. 
                    </P>
                    <HD SOURCE="HD3">2. Provider-Enrollee Communications (Proposed § 438.102)</HD>
                    <P>
                        Medicaid beneficiaries are entitled to receive from their health care providers the full range of medical advice and counseling that is appropriate for their 
                        <PRTPAGE P="41025"/>
                        condition. Section 1932(b)(3)(A), added by the BBA, clarifies and expands on this basic right by expressly precluding an MCO from establishing restrictions that interfere with enrollee-provider communications, and expressly ensuring the right of a health care professional to give medical advice, without regard to whether the course of treatment advised is covered under the MCO's plan. In § 438.102 of the proposed rule, we provided a definition of the term “health care professional” (as discussed above, in this final rule, the definition is located at § 438.2), and outlined the general rule prohibiting interference with provider-enrollee communications. We also included language reflecting the provision in section 1932(b)(3)(B) specifying that the requirements in section 1932(b)(3)(A) should not be construed to require the MCO cover, furnish or pay for a particular counseling or referral service if the MCO objects to the provision of that service on moral or religious grounds, and provides information to the State, prospective enrollees, and to current enrollees within 90 days after adopting the policy with respect to objections of any particular service. In proposed § 438.102, under the authority in section 1902(a)(4), we extended both the explicit right to give advice in section 1932(b)(3)(A) and the moral or religious objection exception in section 1932(b)(3)(B) to PIHPs and PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believe that enrollees should receive information from their providers about treatment options in a culturally competent manner so that enrollees can better understand information about their health care. One commenter suggested that if information about treatment options is not delivered in a culturally sensitive way, it could affect patient compliance with medical advice, and trigger health conditions and medical care episodes that escalate the cost of care. The commenter also felt that this would adversely affect not only patients' health status, and ultimately health plans, but States' and CMS' combined efforts to eliminate ethnic and racial health disparities. Another commenter pointed out that many enrollees who have disabilities come from another country and do not speak English, or have a low education level that limits their ability to understand their medical care and insurance. In other instances enrollees have disabilities that can be a barrier to engaging a health care provider. The commenter believes that this could be true for people with mental disabilities, making it difficult for certain enrollees to get the health care that they need. Several of the commenters recommended that we include a provision, which mirrors a Medicare+Choice requirement, to require that MCOs, PIHPs, and PAHPs take steps to ensure that health professionals furnish information about treatment options (including option of no treatment) in a culturally competent manner, and ensure that enrollees with disabilities have effective communication in making decisions with respect to treatment options. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe it is important for enrollees to receive information in a culturally competent manner, however, we do not agree that additional regulatory provisions are necessary. The regulation already requires, at § 438.206(c)(2), that each MCO and PIHP participate in the State's efforts to promote the delivery of services in a culturally competent manner to all enrollees, including those with limited English proficiency and diverse cultural and ethnic backgrounds. It is up to each State to design its own cultural competency efforts to fit its individual needs and place responsibilities on its providers. In addition, we require at § 438.10(b) that information be provided to all enrollees in a manner and format that may be easily understood, taking into consideration cultural and linguistic needs and disabilities of enrollees. Finally, at § 438.100(b)(2)(iv), MCO, PIHP, and PAHP enrollees have the right to participate in decisions regarding his or her care, including the right to refuse treatment. We believe these provisions address the commenters' concerns. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that § 438.102 make clear that States have the affirmative responsibility to provide race, ethnicity, and language data to health plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It is not clear why the commenter believes that such a requirement would belong in the section dealing with provider-enrollee communications. In any event, § 438.204(b)(2) already requires that the State quality strategy identify the race, ethnicity and primary language spoken of each Medicaid enrollee, and that States provide this information to MCOs and PIHPs for each Medicaid enrollee at the time of enrollment. We therefore do not believe it is necessary to include additional regulatory requirements in this section of the regulations. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received numerous comments on the definition of health care professional. One commenter recommended that language be added that would permit expansion of the disciplines based on recognition of new medical providers/additional licensed individuals offering services. Others recommended a more general definition, that does not rely on identifying specific disciplines, or at a minimum adding “and any other health care professional identified by the State” at the end of the definition. Commenters were concerned that the definition in the proposed rule did not include all health care professionals authorized to provide care in all States, and that as the health care industry continues to evolve, the list will become outdated. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the commenters' concerns, however we will not be making any changes to the definition, as section 1932(b)(3)(C) of the Act provides an exact list of professions that are covered under this provision. As noted above, we have moved the definition of health care professional to § 438.2. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters noted that the provisions in paragraphs (c)(1), (c)(1)(ii)(B) and (c)(2) of § 438.102 make references to a paragraph (b)(3), which does not exist. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate these comments and have corrected the erroneous references. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters raised concerns about the fact that under proposed § 438.102(b)(2), health plans that exclude coverage of certain counseling or referral services on moral or religious grounds are not required to provide information on how and where to obtain information about the service. One commenter believes that any responsibility to provide information to beneficiaries eliminates what the commenter saw as the crucial means for women to access information at the point of service. The commenter felt that this provision discounts the moral and religious beliefs, and health care needs, of female Medicaid beneficiaries. Another commenter pointed out that the proposed rule transfers the responsibility for providing information on services the MCO declines to cover under § 438.102(b)(2) to the State, with no mention on how the State would provide that information to enrollees on a timely basis. The commenter urged that health plans be required to inform enrollees that it does not provide certain services on moral or religious grounds, and at a minimum, provide a referral to a State-sponsored toll-free number that informs beneficiaries about how and where to access these services. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Ultimately, it is the State's responsibility to deliver information on, and furnish, these services. As discussed above in section A., § 438.10(e) requires that information on each MCO, PIHP, or PAHP, be provided 
                        <PRTPAGE P="41026"/>
                        to potential enrollees (at the time the potential enrollee is first required to enroll in a mandatory enrollment program and within a timeframe that enables the potential enrollee to use the information in choosing among available MCOs, PIHPs, or PAHPs), including the benefits covered by the MCO, PIHP, or PAHP and the benefits available under the State plan, but not covered under the MCO's, PIHP's, or PAHP's contract. In addition, § 438.10(f) provides that for a counseling or referral service not covered because of moral or religious reasons, the State must furnish information about how and where to obtain the services. Section 438.102(b) requires the MCO, PIHP or PAHP to notify potential enrollees of services it does not cover because of moral or religious reasons. Further, this provision does not preclude health providers from providing information on how and where to obtain services, if they so choose. In addition, we do not believe that these provisions compromise the needs of female Medicaid beneficiaries, as the Medicaid statute guarantees freedom of choice for family planning services. An enrollee may seek family planning services out-of-network. We also permit enrollees to disenroll if services are not covered because of moral or religious objections, though because of the freedom of choice provisions, disenrollment is not necessary in order to access family planning services. 
                    </P>
                    <HD SOURCE="HD3">3. Marketing Activities (Proposed § 438.104) </HD>
                    <P>Consistent with the rules in section 1932(d)(2) of the Act that apply to MCOs and PCCMs, and in part under our authority in section 1902(a)(4), proposed § 438.104 set forth requirements for, and restrictions on, marketing activities by MCOs, PIHPs, PAHPs and PCCMs. Proposed § 438.104 included definitions of “cold-call marketing,” “marketing,” and “marketing materials.” It also set forth requirements and prohibitions for MCO, PIHP, PAHP or PCCM contracts, specifically: (1) The entity must not distribute any marketing materials without first obtaining State approval; (2) the entity must distribute the materials to its entire service area as indicated in the contract; (3) the entity complies with the information requirements of § 438.10 to ensure that before enrolling, the beneficiary receives from the entity or State, the accurate oral and written information he or she needs to make an informed decision on whether to enroll; (4) the entity does not seek to influence enrollment in conjunction with the sale or offering of any other insurance; and (5) the entity does not, directly or indirectly, engage in door-to-door, telephone, or other cold-call marketing activities. Proposed § 438.104(b)(2) requires that MCOs, PIHPs, PAHPs, and PCCMs specify the methods by which the entity assures the State agency that marketing plans and materials are accurate and do not mislead, confuse, or defraud the beneficiaries or State agency. Finally, § 438.104(c) proposed to require the State to consult with a Medical Care Advisory Committee or an advisory committee with similar membership in reviewing marketing materials. </P>
                    <HD SOURCE="HD2">General Comments </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believe that proposed § 438.104 should apply to current enrollees rather than just potential enrollees, and that the fact that it does not do so is inconsistent with the marketing requirements in the BBA. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have defined marketing as any communication, from an MCO, PIHP, PAHP, or PCCM to a Medicaid beneficiary who is not enrolled in that entity, that can reasonably be interpreted as intended to influence the beneficiary to enroll in that MCO, PIHP, PAHP, or PCCM, or either to not enroll in, or to disenroll from, another MCO's, PIHP's, PAHP's, or PCCM's Medicaid product. We believe that MCOs, PIHPs, PAHPs, and PCCMs are not engaged in marketing for the purposes of influencing enrollment or disenrollment when communicating with current enrollees. We do not believe this is a violation of the BBA marketing provisions in section 1932(d)(2), as this section does not address to whom the marketing covered by its provisions is directed. We believe that our interpretation of the word marketing is reasonable, and consistent with section 1932(d)(2). 
                    </P>
                    <HD SOURCE="HD2">Cold-Call Marketing </HD>
                    <P>Proposed § 438.104(a) defines cold-call marketing as any unsolicited personal contact by the MCO, PIHP, PAHP, or PCCM with a potential enrollee for the purpose of influencing the individual to enroll in that particular MCO, PIHP, PAHP, or PCCM. Cold-call marketing includes door-to-door, telephone or other related marketing activities performed by MCOs, PIHPs, PAHPs, or PCCMs and their employees (that is, direct marketing) or by agents, affiliated providers, or contractors (that is, indirect marketing). In the preamble to the proposed rule, we noted that cold-call marketing included such activities as a physician, other member of the medical staff, a salesperson, other MCO, PIHP, PAHP, or PCCM employees, or independent contractors approaching a beneficiary in order to influence his or her decision to enroll with a particular MCO, PIHP, PAHP, or PCCM. In proposed § 438.104(b)(1)(v), we expressly prohibited MCOs, PIHPs, PAHPs, or PCCMs from directly or indirectly engaging in door-to-door, telephone, or other cold-call marketing activities. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters stated that the definition of cold-call marketing is too broad and might impede legitimate marketing efforts. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The prohibition on cold-call marketing only applies to unsolicited contact by the MCO, PIHP, PAHP, or PCCM. For example, if a beneficiary attends a health fair or similar event, he or she would be seeking out information about health care and, therefore, the contact between the MCO, PIHP, PAHP, or PCCM and the beneficiary would not be considered unsolicited. We note, however, that MCO, PIHP, PAHP, or PCCM participation in health fairs and other community activities is considered marketing and, therefore, must have State approval. 
                    </P>
                    <P>Section 1932(d)(2)(E) of the Act prohibits direct or indirect door-to-door, telephonic, or other cold-call marketing of enrollment. Our interpretation of Congressional intent is that the statutory language was meant to minimize the potential for abusive marketing practices in both voluntary and mandatory programs. There are several other types of marketing that are permitted under section 1932(d) and this regulation. For example, States may permit the use of billboards, newspaper, television, and other media to advertise MCOs, PIHPs, PAHPs, or PCCMs. Mailings are also permitted as long as they are distributed to the MCO's, PIHP's, PAHP's, or PCCM's entire service area covered by the contact. States may also provide marketing materials on behalf of MCOs, PIHPs, PAHPs, and PCCMs. </P>
                    <P>
                        This regulation does not prohibit educational activities on the part of MCOs, PIHPs, PAHPs, or PCCMs. However, any contacts other than patient counseling by any MCO, PIHP, PAHP, or PCCM staff or representative, would be considered marketing subject to State oversight. The regulation does not prohibit States from permitting MCOs, PIHPs, PAHPs, or PCCMs to market to groups in schools, churches, day care centers, etc. States are responsible for approving and monitoring these types of presentations and ensuring that beneficiaries attend 
                        <PRTPAGE P="41027"/>
                        voluntarily with knowledge that they are attending a marketing presentation. 
                    </P>
                    <P>States may permit and establish rules for marketing in public places. However, States may not permit uninvited personal solicitations in public places such as eligibility offices and supermarkets. Some States allow representatives of available MCOs, PIHPs, PAHPs, and PCCMs to be in eligibility offices or other locations on certain days or on a rotating basis to answer questions and provide information to beneficiaries. In these situations, there should be provisions to monitor contacts to ensure that unbiased information is available about all options and that beneficiaries are not coerced. However, marketing or other MCO, PIHP, PAHP, or PCCM representatives who approach beneficiaries as they enter or exit eligibility offices or other public places, call at residences uninvited, etc., are considered cold-call contacts and are not permitted.</P>
                    <P>We believe the regulation gives States broad authority to determine what marketing activities are permitted, with the exception of unsolicited personal contacts by MCOs, PIHPs, PAHPs, and PCCMs or their representatives. States are free to use MCOs, PIHPs, PAHPs, and PCCMs in community-based efforts. However, those efforts are considered marketing; therefore the materials (activities, materials, presentations, etc.) are subject to State review and approval. </P>
                    <HD SOURCE="HD2">Service Area </HD>
                    <P>Proposed § 438.104(b)(1)(ii) required that marketing materials be distributed to the entire service area as indicated in the contract. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters believe that the proposed requirement was unnecessary, unduly burdensome and costly. One commenter suggested that MCOs should not have to distribute marketing materials to areas they already serve and should be allowed to limit distribution to new areas only. Another commenter thought it reasonable to require materials be sent only to those who are eligible or potentially eligible for Medicaid in a given service area and recommended that we require MCOs, PIHPs, PAHPs, and PCCMs to distribute materials to all eligible enrollees in a specified county or region to avoid confusion to those in a particular sector in which the marketing materials do not apply. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(d)(2)(B) of the Act requires that marketing materials be distributed to the entire service area. The intent of this provision is to prohibit marketing practices that favor certain geographic areas over those thought to produce more costly enrollees. Section 438.104(b)(1)(ii) requires that each MCO, PIHP, PAHP, and PCCM contract must provide that the entity “distributes the materials to its entire service area 
                        <E T="03">as indicated in the contract.</E>
                        ” (Emphasis added.) The phrase “as indicated in the contract” is intended to provide States and MCOs, PIHPs, PAHPs, and PCCMs with some flexibility in designing and implementing marketing plans and in developing marketing materials. We expect that when States review MCO, PIHP, PAHP, and PCCM marketing and informing practices, they will not only consider accuracy of information, but also factors such as language, reading level, understandability, cultural sensitivity, and diversity. In addition, State review should ensure that MCOs, PIHPs, PAHPs, and PCCMs do not target or avoid populations based on their perceived health status, cost, or for other discriminatory reasons. 
                    </P>
                    <P>For example, a State may permit distribution of materials customized for a Hispanic population group as long as the materials are comparable to those distributed to the English speaking population. While the presentation and formats of the information may be varied based on the culture and distinct needs of the population, the information conveyed should be the same, in accordance with § 438.10. In the above example, the materials for the Hispanic population group must be distributed to all those Medicaid eligibles or enrollees who require or request Hispanic-related materials. States that use this flexibility to allow selective marketing may permit distribution by zip code, county, or other criteria within a service area if the information to be distributed pertains to a local event such as a health fair, or provider, such as a hospital or clinic. However, States must ensure that health fairs are not held only in areas known to have or perceived as having a more desirable population. We have chosen not to limit the distribution requirement only to mailings because broadcast advertising and other marketing activities can also be done selectively. All marketing activities should be conducted in a manner that provides for equitable distribution of materials and without bias toward or against any group. </P>
                    <HD SOURCE="HD2">Sale of Other Insurance </HD>
                    <P>Proposed § 438.104(b)(1)(iv) requires MCO, PIHP, PAHP, and PCCM contracts to assure that the entity does not seek to influence enrollment in conjunction with the sale or offering of any other insurance. We interpreted this provision to mean that MCOs, PIHPs, PAHPs, and PCCMs may not entice a potential enrollee to join the MCO, PIHP, PAHP, or PCCM by selling or offering any other type of insurance as a bonus for enrollment. However, we invited comment on this provision, because we did not have any legislative history to consider when developing our interpretation. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters strongly recommended that CMS clarify that this provision does not apply to Medicaid enrollees who are eligible for Medicare. As it is worded, commenters believe that this section precludes a Medicare sales representative from telling a potential enrollee eligible for Medicare and Medicaid services about Medicare. Another commenter indicated that this section could impede coordination efforts between Medicare and Medicaid programs. Another commenter stated that the section should not apply to Medicare, since the Medicare program is subject to marketing regulations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters that the proposed regulatory text could impede the interaction of marketing to dual eligibles by MCOs, PIHPs, PAHPs or PCCMs. We have clarified the regulation text at § 438.104(b)(1)(iv) by adding language clarifying that this provision applies to the sale or offering of any private insurance. This would not preclude a Medicare sales representative from telling a dually eligible beneficiary about the health plan's Medicare+Choice benefits. Rather, it is intended to apply to such types of insurance as burial insurance. 
                    </P>
                    <HD SOURCE="HD2">State Agency Review </HD>
                    <P>
                        Proposed § 438.104(c) provides that, in reviewing the marketing materials submitted by MCOs, PIHPs, PAHPs, and PCCMs, the State must consult with its Medical Care Advisory Committee (MCAC) or an advisory committee with similar membership. Section 431.12, of existing rules, sets forth the requirements for establishment of an MCAC. The MCAC must include Board-certified physicians and other representatives of the health professions who are familiar with the medical needs of low-income populations and with the resources available and required for their care. The MCAC must also include the Director of the Public Welfare Department or the Public Health Department, whichever does not head the Medicaid agency, as well as members of consumer groups including Medicaid beneficiaries and consumer organizations such as labor unions, cooperatives, and consumer-sponsored prepaid group practice plans. 
                        <PRTPAGE P="41028"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters felt that the MCAC review of marketing materials would be cumbersome, an administrative burden to the States, and may create delays in distributing marketing information to potential enrollees. The commenters indicated that States should consult the MCAC on marketing policy, regulations, and guidelines, rather than review each piece of marketing materials submitted. One commenter felt that if the MCAC were to review pieces of marketing material, then it should be done in a timely manner. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We did not intend to require that the committee itself review and approve marketing materials. Rather, we intend to reflect section 1932(d)(2)(A)(ii) of the Act, which requires the State to 
                        <E T="03">consult</E>
                         with the committee during the State's own process of review and approval. The State is not required to obtain the committee's approval of, or consensus on, the materials. The State has flexibility in determining how to consult with the committee. A State may elect to require the committee to review the actual marketing materials. If so, in order to expedite the total review time, the State could permit the committee members to conduct their review concurrently with the State's review. 
                    </P>
                    <P>States may also consult with the committee in the development of standardized guidelines or protocols that are intended to facilitate State review. States may consult with the committee to develop suggested language and deem approval of an MCO's, PIHP's, PAHP's, or PCCM's materials if that language is used. MCOs, PIHPs, PAHPs, and PCCMs could also use some of the suggested language and then identify areas where different language has been used, and States could then limit review and/or consultation to that particular portion of the materials. </P>
                    <HD SOURCE="HD3">4. Liability for Payment (Proposed § 438.106) </HD>
                    <P>Proposed § 438.106, consistent with section 1932(b)(6) of the Act, requires MCOs, PIHPs, and PAHPs to provide that their Medicaid enrollees will not be held liable for (a) the debts of the MCO, PIHP, or PAHP in the event of insolvency; (b) covered services provided to the enrollee for which the State does not pay the MCO, PIHP, or PAHP; or (c) payments for covered services furnished under a contract, referral, or other arrangement, to the extent that those payments are in excess of the amount that the enrollees would owe if the MCO, PIHP, or PAHP provided the services directly. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed support for this provision. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge and thank the commenter for their support. 
                    </P>
                    <HD SOURCE="HD3">5. Cost Sharing (Proposed § 438.108) </HD>
                    <P>Prior to the enactment of the BBA, MCOs were prohibited from imposing cost sharing on enrollees. The BBA eliminated this prohibition, and provided that copayments for services furnished by MCOs may be imposed in the same manner as they are under fee-for-service. In § 438.108, we proposed that the contract must provide that any cost sharing imposed on Medicaid enrollees is in accordance with § 447.50 through § 447.58 of the existing regulations. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters supported this provision. One commenter expressed concern about the inappropriate use of hospital emergency rooms. The commenter recommended that we allow and encourage States to charge beneficiaries a $25 copayment per visit for inappropriate use of the emergency room. Under the commenter's recommended approach, MCOs would require that hospitals collect the copayment at the time of the visit; provided, however, that enrollees would not be denied care because of inability to pay the copayment. Under the commenter's suggested policy, if it was determined that a true emergency existed, the copayment would be refunded. The commenter believes that this would serve as an incentive to enrollees to seek care in the appropriate setting, at the appropriate time and would allow the primary care physician to establish a medical relationship with the beneficiary. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Under § 447.53(b)(4), emergency services are exempt from cost sharing. Specifically, copayments may not be imposed on “[s]ervices provided in a hospital, clinic, office, or other facility that is equipped to furnish the required care, after the sudden onset of a medical condition manifesting itself by acute symptoms of sufficient severity (including severe pain) that the absence of immediate medical attention could reasonably be expected to result in—(i) Placing the patient's health in serious jeopardy; (ii) serious impairment to bodily functions; or (iii) serious dysfunction of any bodily organ or part.” We emphasize that as long as the enrollee seeks emergency services that could reasonably be expected to have the above effects, a copayment may not be imposed, even if the condition was determined not to be an emergency.
                    </P>
                    <P>We believe that allowing the collection of an “upfront” copayment in a hospital emergency room as the commenter suggested violate § 447.53(b)(4), and be inconsistent with the enrollee's right to coverage of emergency services when a “prudent layperson” would reasonably believe that an emergency exists (see discussion above). However, enrollees should be aware that if they seek services in an emergency room when it is clear that the standard in § 447.53(b)(4) is not met, coverage of these services may be denied entirely. </P>
                    <HD SOURCE="HD3">6. Emergency and Post-Stabilization Services (Proposed § 438.114) </HD>
                    <P>
                        Section 4704(a) of the BBA added section 1932(b)(2) to the Act to assure that Medicaid managed care beneficiaries have the right to immediately obtain emergency care and services, and the right to post-stabilization services following an emergency medical condition under certain circumstances. (Post-stabilization services are medically necessary services related to an emergency medical condition that are received at the site at which the patient is treated for an emergency medical condition, after the individual's condition is sufficiently stabilized that he or she could alternatively be safely discharged or transferred to another facility.) Each contract with an MCO and PCCM must require the organization to provide for coverage of emergency services and post-stabilization services as described below. In section 1932(b)(2)(A)(i) of the Act, while the Congress required MCOs and PCCMs to provide coverage of emergency services, it did not define the word “coverage,” even though these health care models generally do not cover emergency services in the same manner. In proposed § 438.114, we interpreted the obligation in section 1932(b)(2)(A)(i) of the Act to provide for coverage of emergency services to mean that an MCO or State (as payer in the case of a PCCM) that pays for hospital services generally, must pay for the cost of emergency services obtained by Medicaid managed care enrollees. We interpreted coverage in the PCCM context to mean that the PCCM must allow direct access to emergency services without prior authorization. We applied different meanings to the word “coverage” because while PCCMs are individuals paid on a fee-for-service basis, they receive a State payment to manage an enrollee's care. Unlike MCOs, PCCMs would not likely be involved in a payment dispute involving emergency services, though 
                        <PRTPAGE P="41029"/>
                        they could be involved in an authorization dispute over whether a self-referral to an emergency room is authorized without prior approval of the PCCM. Accordingly, in proposed § 438.114(c)(2), we provided that enrollees of PCCMs are entitled to the same emergency services coverage without prior authorization that is available to MCO enrollees under section 1932(b)(2) of the Act. 
                    </P>
                    <P>Section 1932(b)(2)(A)(i) stipulates that emergency services must be covered without regard to prior authorization, or the emergency care provider's contractual relationship with the organization. This assures a Medicaid enrollee of the right to immediately obtain emergency services at the nearest provider when and where the need arises. </P>
                    <P>Section 1932(b)(2)(B) of the Act defines emergency services as covered inpatient or outpatient services that are furnished by a provider qualified to furnish these services under Medicaid that are needed to evaluate or stabilize an “emergency medical condition.” An “emergency medical condition” is in turn defined in section 1932(b)(2)(C) of the Act as a medical condition manifesting itself by acute symptoms of sufficient severity (including severe pain) that a prudent layperson, who possesses an average knowledge of health and medicine, could reasonably expect the absence of immediate medical attention to result in placing the health of the individual (or for a pregnant woman, the health of the woman or her unborn child) in serious jeopardy, serious impairment to body functions, or serious dysfunction of any bodily organ or part. While this standard encompasses clinical emergencies, it also clearly requires MCOs to base coverage decisions for emergency services on the apparent severity of the symptoms at the time of presentation, and to cover examinations when the presenting symptoms are of sufficient severity to constitute an emergency medical condition in the judgment of a prudent layperson. The above definitions are set forth in proposed § 438.114(a). </P>
                    <P>In some cases, the “emergency” services required to diagnose or treat an “emergency medical condition” may fall within the scope of services that a PIHP, or even a PAHP, is required to cover under its contract. In this case, we believe that enrollees should have the same rights to have these services covered without delay, and “out of plan” as in the case of services covered by an MCO or through a PCCM. Accordingly, through our authority in section 1902(a)(4) of the Act, we provided in proposed § 438.114(f) that the requirements in § 438.114 apply to PIHPs and PAHPs to the extent that the services required to treat the emergency medical condition, or the required post-stabilization services in question, fall within the scope of the services for which the PIHP or PAHP is responsible. </P>
                    <P>Proposed § 438.114(b) requires that MCOs, PIHPs, PAHPs (to the extent applicable), at-risk PCCMs, or the State agency pay for emergency and certain post-stabilization services without prior authorization (other than the pre-approval of post-stabilization services no later than within one hour of a request for approval). </P>
                    <P>Proposed § 438.114(c)(1)(i) provides that an MCO or, to the extent applicable, a PIHP or PAHP, must pay for emergency services regardless of whether the entity that furnishes the services has a contract with the MCO, PIHP, or PAHP. In proposed § 438.114(c)(1)(ii), MCOs, PIHPs, or PAHPs may not deny payments if, on the basis of symptoms identified by the enrollee, he or she appeared to have an emergency medical condition, but turned out not to have a condition in which the absence of immediate medical care would have resulted in serious jeopardy to the health of the individual or, in the case of a pregnant woman, the health of her unborn child, serious impairment of bodily function, or serious dysfunction of any bodily organ or part. Likewise, the MCO, PIHP, PAHP, or PCCM cannot deny payment if the enrollee obtained services based on instructions of a practitioner or other representative of the MCO, PIHP, or PAHP. Proposed § 438.114(c)(2) provides that if a PCCM contract is a risk contract that covers the services, a PCCM system must allow enrollees to obtain emergency services outside of the PCCM system.</P>
                    <P>Proposed § 438.114(d) further clarified financial responsibility. Proposed § 438.114(d)(1) provided that MCOs, PIHPs and PAHPs (to the extent applicable), at-risk PCCMs, or States may not limit what constitutes an emergency medical condition through lists of symptoms or final diagnoses/conditions and may not refuse to process a claim because it does not contain the primary care provider's authorization number. Proposed § 438.114(d)(2) provided that an enrollee who, based on the treating emergency provider's determination, has an emergency medical condition, may not be held liable for payment concerning the screening and treatment of that condition necessary to stabilize the enrollee. Proposed § 438.114(d)(3) provided that the attending physician or practitioner actually treating the enrollee determines when the enrollee is sufficiently stabilized for transfer or discharge, and that this determination is binding on the MCO, PIHP, or PAHP for coverage purposes. </P>
                    <P>Section 1932(b)(2)(A)(ii) of the Act also provides MCO and PCCM enrollees with the right, under certain circumstances, to coverage of “post-stabilization” services after they have been “stabilized” (that is, they no longer have an emergency medical condition, and could be safely discharged or transferred to another facility) following an admission for an emergency medical condition. Specifically, the services that must be covered are those that must be covered under Medicare rules implementing section 1852(d)(2) of the Act, in the same manner as these rules apply to M+C plans offered under Part C of Title XVIII. In section 1932(b)(2)(A) of the Act, this requirement was effective 30 days after the Medicare rules were established, which was August 26, 1998. The Medicare+Choice post-stabilization requirements referenced by section 1932(b)(2)(A)(ii) of the Act are set forth in proposed § 438.114(e), which referenced § 422.113(c) of the Medicare+Choice final regulation. Post-stabilization care means covered services, related to an emergency medical condition, that are provided after an enrollee is stabilized in order to maintain the stabilized condition, and under the circumstances described in paragraph § 422.113(c)(2)(iii), to improve or resolve the enrollee's condition. Under these latter circumstances, either the health plan has authorized post-stabilization services in the facility in question, or there has been no authorization and (1) the hospital was unable to reach the health plan; or (2) the hospital reached the health plan, but did not get instructions within an hour of a request. </P>
                    <P>The above emergency provisions are consistent with most of the emergency services provisions in the Medicare+Choice regulations. However, these regulations deviate from Medicare in two ways. First, the Medicare statute has specific provisions for non-emergency, but urgently needed services, while the Medicaid statute does not contain any similar references. Second, the PCCM, PIHP, and PAHP models are delivery systems unique to Medicaid; and there is no Medicare counterpart to the special rules described above that apply to PCCM enrollees. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter urged that the applicable definitions, including an emergency medical condition and post-
                        <PRTPAGE P="41030"/>
                        stabilization services, be set forth in § 438.114, rather than simply referencing § 422.113. The commenter felt this would make the Medicaid regulations easier to understand. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree. In response to this comment, we have set forth the full definitions of emergency medical condition, emergency services and post-stabilization services in § 438.114. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters noted that the Emergency Treatment and Active Labor Act (EMTALA) requires hospitals and emergency providers to screen and treat those Medicaid enrollees that present at the emergency room, and argued that managed care organizations (MCOs) and States should have to cover costs that EMTALA mandates. A few commenters expressed the view that EMTALA was being enforced on hospitals with more vigilance than the prudent layperson standard is on MCOs, PIHPs, and States. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While MCOs, PIHPs, and States are responsible for covering emergency medical conditions, this is not the same mandate as the services that must be covered under EMTALA. For example, if a prudent layperson would not reasonably believe that an emergency medical condition existed, MCOs, PIHPs, or States would not be liable for costs when the individual presents at an emergency room without prior authorization. Under EMTALA, however, obligations to at least perform screening exist regardless of the condition of the presenting individual. Hence, the scope of a hospital's obligations under EMTALA is broader than the scope of an MCO's or State's obligation under section 1932(b)(2) (or, by extension under this regulation, a PIHP where applicable). However, we agree that the mandates under each rule overlap significantly in most cases. We encourage parties who have concerns about violations or enforcement to contact either the State or CMS regional office responsible for the area in question. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that we remove the provision which precludes an MCO, PIHP or State from refusing to cover services without the primary care provider's (PCP) authorization number. The commenter was concerned that without such a number, there was not a practical mechanism to alert a State or health plan that its enrollee had presented to the emergency room. The commenter also said that its computer system would have to be reconfigured in order to leave out this information, costing a significant amount of money. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Originally, we added this requirement because we were concerned that MCOs, PIHPs, and States could attempt to avoid their obligations under § 438.114 by refusing to pay claims based on technicalities concerning the submission of claims. However, we agree with the commenter that there is a vested interest in MCOs, PIHPs, and States tracking individual enrollees' emergency room presentation rates. Therefore, we are allowing MCOs, PIHPs, and States to require the PCP number to be on a claim before it will be processed for payments. However, we have provided in § 438.114(d)(1)(ii) that MCO, PIHPs, and States must provide hospitals, emergency room providers, or their fiscal intermediaries, when applicable, a minimum of 10 business days to notify the primary care provider or other designated contact before a payment may be denied for a failure to provide notice. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned about the prohibition against denying claims based on lists of symptoms or final diagnosis codes. A number of States require MCOs to pay a screening fee even if there was no emergency, but do not require them to pay for the service based on their emergency services fee schedule. The commenter wanted to know if there was a conflict with the regulation. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is no conflict in this situation if the determination was made taking into account the presenting symptoms rather than the final diagnosis. We prohibit the use of codes (either symptoms or final diagnosis) for denying claims because there is no way a list can capture every scenario that could indicate an emergency medical condition as required in the BBA. An MCO, PIHP, or State may pay claims using those lists and require coverage of screens even if no emergency medical condition exists. However, we do not require coverage of a screen if it reveals no emergency medical condition (as opposed to EMTALA requirements on Medicare participating hospitals). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters were concerned that the Federal rules provide little State flexibility when it comes to setting State rules involving claims coverage, or educating enrollees about emergency room use. One commenter was concerned that, if read literally, the rule prohibits denial of a claim for any reason other than not meeting the prudent layperson standard. The commenter stated that under the proposed rule, reasons for denial could include claims not submitted in a timely manner, claims that are not clean, or claims submitted by providers who refuse to sign provider agreements.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We never intended this rule to prevent States from setting reasonable claim filing deadlines, asking for charts or other information before making a decision, or covering claims submitted by providers refusing to sign provider agreements. The purpose of the rule is to ensure that enrollees have unfettered emergency room access for emergency medical conditions, and that hospitals receive payment for those claims meeting that definition without having to navigate through unreasonable administrative loopholes. However, as long as filing deadlines specifically outlined for an appeals process are not used to deny initial claims, a State may set its own filing timeframes and other administrative rules (as long as it is not contrary to specific Federal provisions such as the 10 business day post-notification minimum timeframe requirement). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned about the application of proposed § 438.114 to situations involving mental health emergencies. The commenter felt that the present definition cannot be readily understood in the context of emergencies related to mental disorders. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the present definition is primarily designed to cover physical rather than mental health. However, since the definition comes directly from the BBA, we do not have the legal authority to expand or change it. The present definition does apply to mental health as well when its standards are met (for example
                        <E T="03">,</E>
                         “placing the health of the individual in serious jeopardy”). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters believe that the one-hour rule for MCOs to notify hospitals before post-stabilization services may be performed is too short a timeframe, and is contrary to their own State rules. One commenter indicated that it follows a 2-hour timeframe before post-stabilization services may be performed, finding it much more reasonable in order to give MCOs and PCPs an opportunity to coordinate an enrollee's non-emergent care. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(b)(2)(a)(ii) of the Act requires MCOs and PCCMs to comply with guidelines established under section 1852(d)(2) of the Act regarding coordination of post-stabilization care in the same manner as the guidelines apply to Medicare+Choice plans under Part C of title XVIII. Therefore, according to statute, we must follow the rules that apply under the Medicare+Choice program. In this case, that is a 1-hour timeframe for MCOs or PCCMs to notify a hospital before post-stabilization services may begin. 
                        <PRTPAGE P="41031"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters pointed out that proposed § 438.114(c)(1) contains an error by referring to entities identified in subparagraph (c) when it should refer to paragraph (b). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The commenters are correct. We have made the change in the final rule. 
                    </P>
                    <HD SOURCE="HD3">7. Solvency Standards (Proposed § 438.116) </HD>
                    <P>Section 4706 of the BBA added new solvency standards to section 1903(m)(1) of the Act, requiring that an MCO's provision against the risk of insolvency meet the requirements of a new section 1903(m)(1)(C)(i), unless exceptions in section 1903(m)(1)(C)(ii) apply. Under section 1903(m)(1)(C)(i), the organization must meet “solvency standards established by the State for private health maintenance organizations” (or be “licensed or certified by the State as a risk-bearing entity.”) The exceptions to this new requirement in section 1903(m)(1)(C)(ii) apply if the MCO, (1) is not responsible for inpatient services, (2) is a public entity, (3) has its solvency guaranteed by the State, or (4) is, or is controlled by FQHCs, and meets standards the State applies to FQHCs. Section 4710(b)(4) of the BBA provided that the new solvency standards applied to contracts entered into or renewed on or after October 1, 1998. Proposed § 438.116 reflects these statutory provisions. We received no comments on this section and are implementing it as proposed.</P>
                    <HD SOURCE="HD2">D. Quality Assessment and Performance Improvement (Subpart D)—Background </HD>
                    <P>Section 4705 of the BBA added section 1932(c) to the Act. Section 1932(c)(1) requires State agencies that contract with Medicaid MCOs under section 1903(m) of the Act to develop and implement quality assessment and improvement strategies that are consistent with standards established by the Secretary. Subpart D would implement this provision. We proposed that the requirements be applied to PIHPs and, in some cases, to PAHPs. </P>
                    <HD SOURCE="HD3">1. Scope (Proposed § 438.200) </HD>
                    <P>Proposed § 438.200 set forth the scope of subpart D. Proposed subpart D would implement section 1932(c)(1) by setting forth specifications for quality assessment and performance improvement strategies that States must implement. Subpart D also proposed standards that would apply to States, MCOs, Prepaid Inpatient Health Plans (PIHPs), and in some cases, Prepaid Ambulatory Health Plans (PAHPs). </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that the provisions of subpart D were appropriate overall but that more flexibility is needed for smaller States and MCOs because their administrative burden is greater. Many commenters supported the approach taken in the August 2001 proposed rule and the balance struck between requirements and flexibility. They stated their belief that subpart D avoids the imposition of requirements with administrative burden and serves the interest of beneficiaries. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that § 438.204 provides the structure for State quality strategies consistent with the intent of the Congress when it addressed quality in section 4705(a) of the BBA. We also believe that we have provided sufficient flexibility for States to design and implement quality strategies that will best meet their needs. We do not relax the requirements for smaller States or MCOs because we do not believe that quality should be compromised due to the size of an organization. However, we do not believe the burden on States is excessive, even for smaller States, and we believe that States may impose the appropriate activities on MCOs and PIHPs. For example, a State might require less in the way of quality assessment and performance improvement activities for smaller plans. The State also might contract with an organization that does external quality review for the State pursuant to section 1932(c)(2) of the Act, to calculate performance measures or design quality improvement projects. (See 64 FR 67223, December 1, 1999 for the proposed rules that would govern “External Quality Review Organizations,” or “EQROs.”) 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters stated that the provisions of subpart D should apply to PAHPs, including dental plans, as well as to MCOs and PIHPs. They believe that all capitated programs, including those that provide transportation, should be subject to the quality provisions. Other commenters stated that exempting “mental health carve out” plans from the quality requirements is inconsistent with the findings of the General Accounting Office (GAO) report of September, 1999 on mental health carve out programs in Medicaid managed care. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter. Therefore, in this final rule, we have applied additional sections of the regulation to PAHPs. (See § 438.8(b).) In subpart D, we now apply the provisions of §§ 438.206, 438.207, 438.208, 438.210, 438.214, 438.230, and 438.236 to PAHPs. These sections address access to care and the provision of quality care. We believe that the protections of these sections should be extended to enrollees in PAHPs. We do not apply the other provisions of subpart D related to a quality strategy and quality improvement activities, as we believe these requirements would impose a burden on States and PAHPs that is unreasonable given the scope of PAHP activities. 
                    </P>
                    <P>The terms “mental health carve out program” or “behavioral health carve out program” refer to prepaid plans that provide only mental health services. Under a waiver, a State Medicaid managed care program can contract with such a program. The GAO Report issued on September 17, 1999, indicated that CMS needs to oversee mental health carveouts more systematically, and noted approvingly that we were developing a rule that would include a requirement for annual external quality reviews. Mental health carve out programs that provide hospital as well as ambulatory care are PIHPs, and are subject to all the subpart D requirements. We believe that most of the large mental health carve out programs fall into this category, and that this final rule is therefore consistent with the intent of the September 1999 GAO report. </P>
                    <HD SOURCE="HD3">2. State Responsibilities (Proposed § 438.202) </HD>
                    <P>Proposed § 438.202 set forth the State's responsibilities in implementing its quality strategy. Specifically, proposed § 438.202 required that each State (1) have a written strategy for assessing and improving the quality of managed care services, (2) provide input by stakeholders into the strategy, (3) ensure compliance with State-established standards, (4) periodically review the strategy for its effectiveness and update as needed, and (5) submit to CMS a copy of the initial and revised strategies and regular reports on their implementation and effectiveness. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that in § 438.202 “strategy” be replaced with “policy.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(c)(1) of the Act requires a State to develop and implement a quality assessment and improvement strategy if it contracts with an MCO. Therefore, we retain the term “strategy” in § 438.202 of the final rule to be consistent with the term used in the statute. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believes that the provisions regarding a State quality strategy are heavy handed, over controlling, and result in CMS substituting its judgment regarding quality for the State's. 
                        <PRTPAGE P="41032"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the regulation provides a balance between an appropriate amount of detail needed to ensure that States develop and implement sound quality strategies and flexibility for States to determine the best approach for developing these strategies. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that the State's quality strategy should clearly outline the relationship between the MCO and PIHP quality requirements and the strategy components. Each MCO and PIHP requirement should clearly support a component of the strategy. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The MCO and PIHP quality requirements of subpart D (§§ 438.206 through 438.242) are incorporated as an element of the State's quality strategy (§ 438.204(g)). Specifically, § 438.204(g) requires that the State quality strategy include information on how the State plans to make MCOs and PIHPs comply with State access standards, structural and operational standards, and measurement and improvement standards. We do not believe we need to revise § 438.204 to provide clarifying language to show the relationship between the quality strategy and the MCO and PIHP quality requirements under § 438.240. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters stated that the requirement in proposed § 438.208(c) and (d) (now § 438.208 (b) and (c)) for States to assess the quality and appropriateness of care and services furnished to all Medicaid enrollees, including those with special health care needs, is ambiguous. Commenters believe it can be read to mean that the overall population must be measured, including special needs populations, rather than that the quality for special needs populations be measured separately. They see this as a problem because the results may yield no specific information about persons with special health care needs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our intent for the proposed provision was to have States assess the quality and appropriateness of care and services to all Medicaid enrollees as well as to assess separately the quality and appropriateness of care and services for individuals with special health care needs. For clarification purposes, we have revised § 438.208(b) and (c). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter objected to the inclusion of the word “all” in § 438.204(b) because States do not have the budgets or staffs to assess the needs of all Medicaid enrollees. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.204(b) requires the State to identify in the quality strategy how it plans to implement procedures to assess the quality and appropriateness of care and services furnished to all Medicaid beneficiaries. We disagree with the commenter because States have the flexibility to determine the methods and timeframes that will work best to assess the quality and appropriateness of care and services to all Medicaid beneficiaries. There are a variety of options States can choose from to meet this requirement. For example, States can use findings from performance measures collected, performance improvement projects conducted, reviews for compliance with State standards, consumer surveys, or the analysis of grievance and appeal information. States can conduct these activities, use a State contractor to conduct these activities, and/or use findings from MCO and PIHP quality assessment and performance improvement programs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter questioned if there are specific quality measures for individuals with special health care needs, other than surveys, that can be used to meet the requirement of the regulation that States assess the appropriateness of care of these enrollees. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated above, there are numerous activities that can be conducted to assess the appropriateness and quality of care and services provided to beneficiaries. When targeting an assessment of individuals with special health care needs States can stratify the data by identified categories or conduct activities specifically targeted to a specified population. For example, a State could conduct or have their MCOs and PIHPs conduct a performance improvement project on access to care for individuals needing substance abuse services. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters suggested that proposed § 438.208(b) (now § 438.208(c)) should require States to provide information to MCOs and PHPs about Medicaid enrollees known by the agency to have special needs, as this step is crucial to assessing the quality and appropriateness of care provided to these beneficiaries. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters. Therefore, we have revised § 438.208(c) to require that States implement mechanisms that identify individuals with special health care needs. The State or its enrollment broker may determine which individuals have special needs, and then inform the MCO, or the State may require that the MCO, PIHP, or PAHP apply the mechanisms to identify these individuals. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters expressed support for the requirement that State quality strategies be in writing. One commenter mistakenly believed that the proposed rule did not include the requirement that the strategy be in writing and asked that this requirement be included. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters and we will retain the requirements in § 438.202(a). We believe it important that the quality strategy be in writing to provide a document for stakeholders to react to, as well as, for the States to assess on a regular basis and update as necessary. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that the regulation appears to contemplate a formal solicitation of public input to the quality strategy. A formal public process is costly and administratively burdensome. One commenter said that they have found a public process to solicit input ineffective. The commenter asked that we clarify in text or preamble language that a less formal process is permissible. Another urged its deletion. Several commenters supported the requirement for public input into the State quality strategy. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Our intent is that there be a formal process to obtain input from beneficiaries and other program stakeholders in the development of the State quality strategy. We leave it to the State to define this process. We believe public input provides for the integration of various perspectives and priorities and will facilitate a more useful end product. Therefore, we retain the requirement in § 438.202(b) of this final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern that the regulation will require a continual process of formal comments on a State's quality strategy because it will change frequently as new quality tools become available, laws and regulations change, and CMS places conditions on States when approving waivers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated above, we intend for States to obtain public comments on updated quality strategies when significant changes are made. We do not expect States to obtain public comments when modifications are made to the strategy that are not considered significant, as defined by the State. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters believe that CMS should specify a timeframe for States to update their quality strategies, such as annually or every 3 years. They believe that “periodic” is insufficient, as the term is not defined. One commenter stated that the review should be conducted annually, the review should identify the degree to which the MCO or PIHP interventions continue to support the goals of the strategy, and the findings should be reported annually to CMS and to the public. 
                        <PRTPAGE P="41033"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that we should require a specific time period for States to update their quality strategies. We have provided States with the flexibility to determine these timeframes. We believe that a State's review and evaluation of the effectiveness of the strategy will guide the State's decision as to when and how the strategy should be revised. Therefore, we retain the requirement in § 438.202(d). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that the requirement that States submit their quality strategies to CMS implied a role for CMS in approving the strategy. Another commenter requested a provision stating that CMS' review will be limited to verification that each required element is addressed. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As part of the CMS regional office review of Medicaid managed care programs, regional office staff will assess State quality strategies to ensure compliance with this rule. We have not yet determined the scope of review activities that regional office staff will undertake. As we develop this process, we will work in collaboration with States and other stakeholders. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that a provision be included to require States to review health plans' quality strategies at least every 3 years. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         MCOs and PIHPs are not required to develop quality strategies. MCOs and PIHPs are required to have a quality assessment and performance improvement program as specified under § 438.240. The State is required to review this program annually to determine the impact and effectiveness of the program. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that progress toward goals in the quality strategy should be shared by States with their MCOs and PIHPs to reinforce collaboration, monitor progress, and make needed revisions.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We encourage States to share findings of the effectiveness of the State quality strategy with MCOs and PIHPs. We are not requiring this, however, in regulation. 
                    </P>
                    <HD SOURCE="HD3">3. Elements of State Quality Strategies (Proposed § 438.204) </HD>
                    <P>Proposed § 438.204 set forth the elements of a State quality strategy, including, in § 438.204(a), contract provisions that incorporate the standards specified in this subpart. Section 438.204(b) required that the State strategy must include procedures that (1) assess the quality and appropriateness of care and services furnished to all Medicaid enrollees, including those enrollees with special health needs; (2) identify and provide to MCOs and PIHPs information on the race, ethnicity, and primary language spoken of each Medicaid enrollee; and (3) monitor and evaluate the compliance of MCOs and PIHPs with these standards. </P>
                    <P>Section 438.204(c) provided that the State quality strategy must include any performance measures and levels developed by CMS in consultation with States and other stakeholders. “Performance measures” or “measures” refer to how often a desired action or result is achieved or produced, such as the percent of two-year olds who are immunized. “Levels” refers to a specified percentage to be achieved or a measure. </P>
                    <P>Section 438.204(d) required an annual, external independent review of the quality outcomes and timeliness of, and access to, the services covered by the MCO or PIHP contract. </P>
                    <P>Section 438.204(e), (f), and (g) required that State strategies use intermediate sanctions; include an information system to support the operation and review of the strategy; and include standards for access to care, structure and operations, and quality measurement and improvement, all consistent with the requirements of other sections of this subpart. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that States be required to use the definition of children with special health care needs established by the Bureau of Maternal and Child Health and, through monitoring the use of services, identify children who received subspecialty care. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There are numerous definitions for individuals with special health care needs. However, health services research is still in the process of developing conceptual models, screening tools, and approaches to identifying these individuals. We, therefore, do not agree that this regulation should require States to use a particular definition. We provide States with the flexibility to define individuals with special health care needs. This regulation requires that States identify procedures to assess the quality and appropriateness of care provided to individuals with special health care needs and that States conduct reviews to evaluate the effectiveness of the strategy, including quality activities targeting individuals with special health care needs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters strongly supported the provision that States be required to identify the race, ethnicity, and primary language spoken of each Medicaid enrollee and provide this to the MCO or PIHP upon enrollment. This supports the HHS goal of eradicating racial and ethnic disparities in health care by the year 2010. It also ensures that MCOs and PIHPs have the information necessary to comply with title VI of the Civil Rights Act of 1964. They allege that it has been long recognized that effective recording and reporting of data is the basis used to determine that Federal fund recipients are in compliance with the law. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         To ensure that Medicaid services are provided in a manner that meets the needs of beneficiaries, we retain the provision in § 438.204(b)(2) in the final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter urged that the regulation permit the collection of information on race, ethnicity, and primary language at both the State and MCO and PIHP level. They note that State data is not always accurate. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In addition to the information provided to MCOs and PIHPs by the States, MCOs and PIHPs have the option to collect information on race, ethnicity and primary language. We are not requiring this in regulation but we note that States may do so. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked for clarification on the level of specificity that would be required to meet the requirement to collect data on ethnicity. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are providing States with the flexibility to determine how they would like to define and categorize ethnicity. Ethnicity information is collected for census purposes and we encourage States to consider using standard categories used by the Bureau of the Census. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that race data in State eligibility systems is not always accurate and that identifying primary language will cost money to make required systems changes. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize that some States will need to modify their Medicaid Management Information Systems (MMIS) to collect data on primary language. We will allow States sufficient time to modify their systems to capture these data. We also recognize that the race data collected by States may not always be accurate and that it will always be subject to omission due to a variety of factors including beneficiary unwillingness to provide the information. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that information on race, ethnicity, and primary language is not available from the Social Security Administration (SSA) for Supplemental Security Income (SSI) beneficiaries or that States do not control what information SSA collects. States should not be required to provide this information to MCOs unless it is available from SSA. 
                        <PRTPAGE P="41034"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Information on race is available from SSA on SSI beneficiaries and is available to States through the State Data Exchange (SDX) file. Information on ethnicity and primary language, however, is not available from SSA. We encourage States to pursue methods to collect information on ethnicity and primary language spoken for these beneficiaries. The information may be available in files of other State programs. We recognize that this information may not be complete for a variety of reasons. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that the State has no legitimate interest in the primary language spoken by beneficiaries, as this does not indicate that use of English presents a barrier. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. We believe that the primary language spoken by a beneficiary indicates that there could be a potential barrier to appropriate use of health care services. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters said that data on race, ethnicity, and primary language are difficult to collect and unreliable due to the reliance on self-reporting. One commenter noted that undocumented parents may be reluctant to apply for benefits if this question is asked. The commenter further suggested that this provision be deleted or not required. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Self-report data are used for numerous purposes including consumer satisfaction surveys and initial screening of beneficiary needs. There are methodological pros and cons to using any types of data, including self-report data. While we realize that self-report data about race, ethnicity, and language will not always be completely reliable, we believe that collecting it will allow MCOs, PIHPs, and PAHPs to take into account the cultural barriers that may undermine the delivery of health care to particular populations enrolled in the MCO. We do not believe that collection of this information will discourage undocumented parents from applying for benefits for eligible children because the question will be in reference to the children. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that requiring beneficiaries to disclose race or ethnicity constitutes a potential violation of the Civil Rights Act. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This rule does not require beneficiaries to disclose race or ethnicity. It requires States to make an effort to identify this information. In addition, the Civil Rights Act of 1964 does not prohibit a State or any other Federally assisted entity from asking a beneficiary to disclose his or her race or ethnicity. The failure to disclose the requested information, however, cannot be used as a basis to deny services or benefits to the beneficiary. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters noted that the requirement for States to collect information on race, ethnicity, and primary language would require systems modifications and training of intake staff. The commenter expressed the hope that CMS, when conducting compliance reviews, would be sensitive to the time it will take for States to fully implement this provision. Another commenter suggested that States may need technical assistance. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize that some States will need to modify their MMIS systems to capture these data, although we believe most States are already capturing data on race and ethnicity. We will allow States sufficient time to modify their systems to capture these data. We also recognize that training of intake staff may need to occur and that technical assistance to State may need to be provided. We plan to conduct training pertaining to the implementation of the provisions in this rule shortly after its publication. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the regulation require States to furnish MCOs and PIHPs with the age of children being enrolled along with information on race, ethnicity, and primary language spoken. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The purpose of requiring States to identify race, ethnicity, and primary language is to facilitate the appropriate delivery of health care services. We believe that MCOs and PIHPs can adequately obtain age information from the enrollee and are, therefore, not requiring that the age of enrolled children be provided. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter appreciated that we are permitting States to develop strategies for identifying race, ethnicity, and primary language, rather than requiring States to identify these factors. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe the commenter misunderstood the provision. The regulation 
                        <E T="03">requires</E>
                         States to identify the race, ethnicity, and primary language of enrollees. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that States be required to provide the date of redetermination for new enrollees to MCOs and PIHPs. This would allow MCOs and PIHPs to outreach to enrollees to ensure that eligible beneficiaries continue to receive services. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that this regulation should require States to provide the date of redetermination for new enrollees to MCOs and PIHPs. If MCOs and PIHPs would find this information useful to provide continuity of services and do not currently receive it, we suggest that they raise this issue with their State. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that the requirement in proposed § 438.204(b)(3) for “continuous” monitoring be changed to “periodic” monitoring as continuous means nonstop, and this is an unreasonable requirement. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter and have revised § 438.204(b)(3) of the regulation text to provide for regular monitoring, as opposed to continuous monitoring. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters applauded the provision that performance measures and levels be identified and developed by CMS in consultation with States and other stakeholders. Some recommended that beneficiaries and groups that represent them should be among the stakeholders consulted. One commenter suggested that CMS ask the American Association of Health Plans (AAHP) to obtain recommendations and comments about proposed measures from MCOs. Others urged that performance measures be implemented in a way that allows MCOs to meet a realistic schedule. They further recommended that CMS take into consideration nationally demonstrated performance levels in both MCOs and in State fee-for-service (FFS) programs. One commenter recommended that any new measures be tested for one year to assess the data and results before States, MCOs and PIHPs are considered out of compliance. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We anticipate that States, beneficiary advocacy groups, and MCOs and PIHPs would all be invited by CMS to participate in the process to develop standard measures. The implementation process would be discussed at this time and would include issues such as measure specifications, testing of measures, and measure reporting. States would need to ensure that their contracting MCOs and PIHPs collect any measures specified by CMS. We would encourage States to also use standard measures in their FFS programs. If CMS prescribes any national performance measures, it will consider a testing phase. Finally, should CMS consider setting levels for performance measures, we would consider levels used in both managed care and FFS programs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the number of national measures be limited so as not to unnecessarily increase costs or burden or interfere with State efforts. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that national measures should be limited in number. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that quality improvement initiatives must be recognized as long-term efforts 
                        <PRTPAGE P="41035"/>
                        and that States and MCOs must partner to identify meaningful topics that should be measured, and track these over time. Continual, capricious changes to quality initiatives are not conducive to meaningful study and improvement. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter and acknowledge that a quality improvement initiative (the process of measuring performance, implementing interventions to respond to identified quality problems, and then remeasuring performance) needs sufficient time to be implemented and for findings to be made available. We do not prescribe the duration in which performance improvement projects must be completed. We expect States to require that a project be completed in a reasonable time period and that information be provided on the project's progress annually. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested detailed standards to ensure that Medicaid children are receiving the care to which they are entitled. Specifically, the commenter recommended the regulation include standards for accreditation of MCOs and PIHPs, consumer satisfaction and quality of care “report cards,” and use of criteria consistent with national standards for assessing outcomes of care of children. In addition, the commenter suggested that CMS work with states to develop criteria and a timetable for improving the reporting of early and periodic, screening, diagnosis and treatment (EPSDT) services. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The provisions under subpart D provide for access standards, structural and operational standards, and measurement and improvement standards. These standards apply regardless of the composition of the Medicaid population that is provided health care services through a State Medicaid managed care program. A review of these standards will be conducted as specified in the forthcoming final External Quality Review (EQR) regulation (64 FR 67223). As part of EQR, we have proposed that States may contract with external quality review organizations (EQROs) to conduct consumer surveys and validate and calculate performance measures and obtain a 75 percent enhanced Federal matching rate. Alternatively, States can have a contractor that is not an EQRO conduct these activities, and obtain the 50 percent administrative matching rate. States, the EQROs they contract with, or other State contractors will be able to extract information obtained from these quality measurement activities in a way that allows them to look at the quality of care of specified populations, including children. Regarding the comment about EPSDT, we do not believe that this is within the scope of this regulation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters suggested that only non-medical PHPs (that is, transportation and dental) be excluded from the requirement for EQR and that a State audit substitute for the EQR for these entities. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have proposed to exclude all PAHPs, including transportation and dental PAHPs, from the EQR requirements. We believe that requiring EQR for PAHPs would impose an unreasonable burden given the limited scope of their services. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that many States conduct extensive quality reviews, either though another State agency or through an accreditation organization. These reviews, the commenter contended, are similar to or more rigorous than the CMS required external review and he suggested that, if a review is done by another State agency or an accreditation organization, that the MCO or PIHP be exempt from the EQR.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We plan to address when an MCO or PIHP can be exempt from certain EQR activities or from EQR in its entirety in the final EQR regulation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked if it will be permissible to contract with State medical and allied health professional schools for EQR. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We plan to address who is qualified to be an EQRO in the final EQR regulation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter mistakenly believed that we deleted the EQR requirement from the quality strategy and was in agreement with this deletion arguing that the requirement was excessive and costly. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(c)(2) of the Act requires an EQR of managed care activities. While we have included the EQR requirement as part of the quality strategy under this subpart, specific requirements regarding compliance with the EQR provision were published in a separate EQR Notice of Proposed Rulemaking on December 1, 1999 (64 FR 67223). The final EQR rule is forthcoming. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that some PIHPs have enrollments of less than 200 and serve fewer than 10 beneficiaries a year. The commenter is concerned that for these PIHPs the cost of an EQR could exceed the costs of providing health care services. The commenter suggested that for PIHPs include an option for Section 1115 and 1915(b) waiver programs allowing the use of the independent assessment of the waiver program in lieu of an EQR. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The independent assessment requirement only applies to programs operated under section 1915(b) waivers, and if the assessment is found to be acceptable, is generally required for only the first two waiver periods. It does not apply to a managed care program conducted under section 1932(a) or section 1115 of the Act or one that enrolls beneficiaries in managed care on a voluntary basis. We therefore do not agree that this option is a suitable replacement for the EQR requirement. If a PIHP contracts with a State to provide services to Medicaid beneficiaries it will be required to comply with the provisions in this rule including the EQR requirements. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended that § 438.204(e), which requires the use of intermediate sanctions, be amended to indicate that it is applicable to MCOs only and not to PIHPs because subpart I does not apply to PIHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter and have deleted the reference to PIHPs under § 438.204(e). In addition, to clarify the applicability of § 438.204(c), we have included language that clarifies that this provision applies to both MCOs and PIHPs. 
                    </P>
                    <HD SOURCE="HD3">4. Availability of Services (Proposed § 438.206) </HD>
                    <P>Section 1932(c)(1)(A)(i) of the Act, as added by section 4705 of the BBA, requires each State that contracts with MCOs under section 1903(m) of the Act to develop and implement standards for access to care under its quality assessment and improvement strategy. Section 438.206 of the proposed rule established standards for access to care. Paragraph (a) required that States ensure that all covered services are available and accessible to enrollees. Paragraph (b) proposed new requirements for the delivery networks of MCOs and PIHPs. These requirements would be imposed on State agencies, which in turn would enforce these requirements on MCOs and PIHPs through contract provisions. </P>
                    <P>
                        Specifically, paragraph (b)(1) proposed that all MCOs and PIHPs maintain and monitor a network of appropriate providers that is supported by written arrangements and is sufficient to provide adequate access to covered services. In establishing and maintaining such a network, the proposed rule required MCOs and PIHPs to consider (1) anticipated enrollment; (2) the expected utilization of services, considering enrollee characteristics and health care needs; (3) the numbers and types of network providers required to furnish contract 
                        <PRTPAGE P="41036"/>
                        services; (4) the number of network providers who are not accepting new patients; and (5) the geographic location of providers and enrollees, considering distance, travel time, the means of transportation normally used by enrollees, and whether the location provides physical access for enrollees with disabilities. 
                    </P>
                    <P>In § 438.206(b)(2) we proposed that the State be required to ensure that MCOs and PIHPs allow women direct access to a woman's health specialist for women's routine and preventative services. Proposed § 438.206(b)(3) required that MCOs and PIHPs provide for a second opinion from a qualified health care professional within the network, or arrange for the enrollee to obtain one outside the network, at no cost to the enrollee. In paragraph (4), we proposed that the MCO or PIHP must cover medically necessary services for enrollees obtained outside the network if, and for as long as, they cannot be obtained from within the network. Paragraph (5) of the proposed rule required out-of-network providers to coordinate with the MCO and PIHP with respect to payment and ensure that the cost to the enrollee is no more than it would be if the services were provided within the network. In paragraph (6), we proposed that MCOs and PIHPs demonstrate that their providers are credentialed in accordance with § 438.214(b). </P>
                    <P>Paragraph (c)(1) required MCOs and PIHPs to meet State standards for timely access to services and to require that their providers also meet these standards. It also required MCOs and PIHPs to (1) ensure that network providers offer hours of operation that are no less than the hours of operation offered to commercial enrollees or comparable Medicaid fee-for-service, if the provider serves only Medicaid enrollees; (2) make services available 24 hours a day, 7 days a week, when medically necessary; (3) establish mechanisms to ensure compliance with these requirements; (4) monitor for compliance continuously; and (5) take corrective action if there is a failure to comply. </P>
                    <P>Paragraph (c)(2) required that the State ensure that each MCO and PIHP participate in State efforts to promote the delivery of services in a culturally competent manner to all enrollees with limited English proficiency and diverse cultural and ethnic backgrounds. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters said that the provisions in proposed § 438.206 should apply to all PHPs because PAHPs should have the same requirements for an adequate provider network as applies to MCOs and PIHPs. One commenter said that this section should apply to dental plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters that the availability of services provisions should apply to PAHPs. Therefore, in § 438.206 of the final rule, we have added “PAHP” in each instance in which the terms “MCO or PIHP” appeared in the proposed rule. Therefore, these requirements will now apply to dental PAHPs. We note that the types of providers that a PAHP must include in its network is limited to those needed to provide the services under its contract. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the provisions at § 438.206(a) requiring that all covered services be available and accessible. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters and believe that these provisions are consistent with the intent of the Congress concerning the development and implementation of standards for access to care. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters said that proposed § 438.206(b) fails to provide for direct accountability by States in that it provides only that States ensure compliance 
                        <E T="03">through their contracts.</E>
                         These commenters believe that this wording does not require States to ensure that the contract provisions are carried out in practice. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter. We now specify in the regulation that § 438.206 be reflected in contracts with MCOs, PIHPs, and PAHPs, because it is essential that these requirements be included in the contract to be enforceable by the State. The regulation also requires, at § 438.204(b)(3), that States “monitor and evaluate the MCO, PIHP, and PAHP compliance with the standards”. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that a requirement that MCOs have a network “sufficient to provide adequate access to all services under the contract” is a significant departure from 1902(a)(30)(A) of the Act that requires the State to establish methods, procedures, and payments “sufficient to enlist enough providers so that care and services are available under the plan at least to the extent that such care and services are available to the general population in a geographic area”. The commenter is concerned that the language in the proposed regulation obligates the State to guarantee that all covered services are available at all times, which may be beyond the ability of the State due to shortages of service providers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1902(a)(30)(A) is a requirement that applies to the State's fee-for-service program, operated pursuant to the State plan. The provision that specifically governs the availability of services under a State's managed care program is section 1932(c)(1)(A)(i) of the Act, which requires that services be available “in a manner that ensures continuity of care and adequate primary and specialized services capacity.” We believe that the provisions of § 438.206(b)(1) carry out the intent of the Congress under section 1932 to provide access standards that will ensure the availability of care in MCOs, PIHPs and PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed support for the provision requiring networks to have experienced providers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that it is important that MCOs, PIHPs, and PAHPs have experienced providers in order to provide quality care to Medicaid enrollees. This is especially true for enrollees with special health care needs, whose needs may be sufficiently rare or complex due to multiple conditions that a provider, even one who is a specialist, may have little or no experience in treating the enrollee's condition or conditions. Accordingly, in section 438.206(b)(1)(iii) we specify that the MCO, PIHP, or PAHP must consider the training, experience, and specialization of providers. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended adding language to require MCOs and PIHPs that serve children with special health care needs to include appropriately trained physicians in their network, including pediatric specialty and subspecialty physicians. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe it necessary to include an explicit requirement for specific specialty and subspecialty physicians for particular groups of enrollees. The general requirement that a network be adequate to provide access to all services under the contract, taking into account the anticipated enrollment and the expected utilization, is sufficient to ensure that the network will be adequate to meet all needs. Inclusion of language related to particular groups may even be detrimental in that it would be impossible to list the particular requirements of all groups. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that we add an explicit requirement that MCOs and PHPs pay particular attention to the needs of enrollees with disabilities when developing and maintaining networks. Without such a provision, the commenter is concerned that specialized psychiatric treatment for children and adults with severe mental illness may not be available. The commenter believes that the inclusion of such a requirement has the potential 
                        <PRTPAGE P="41037"/>
                        to bring psychiatrists who refuse to treat FFS Medicaid beneficiaries into the program because MCOs would use their market power to recruit these providers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated above, we do not agree that we should address the special needs of particular groups of enrollees for specialty providers. We believe that the requirement of the regulation for adequate provider networks will cause the States to include appropriate requirements in their contracts with MCOs, PIHPs, and PAHPs and that the assurances of adequate capacity and services, provided under § 438.207 of this regulation, will further ensure that provider networks include the range of providers necessary to meet the needs of their enrollees. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters suggested that the regulation include a provision that MCOs and PIHPs pay particular attention to pregnant women and individuals with special health care needs because MCO and PIHPs may interpret a general requirement to require only an overall survey of enrollees, rather than a targeted assessment of the needs of the most vulnerable and ill patients. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         For the reasons stated above, we do not agree that the regulation should include a specific provision for these groups. We believe that the intent of this regulation is clear, that is, that the needs of all enrollees must be met through the provider network. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that the regulation should require States to ensure that MCOs and PIHPs consider and address existing underutilization problems when establishing and monitoring their service networks. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation places an affirmative obligation on States and MCOs, PIHPs, and PAHPs to consider the needs of their anticipated enrollees and provide an adequate provider network to meet those needs. We believe that this requirement makes it unnecessary to include a provision to address existing underutilization problems. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters said that the regulation should require MCOs and PIHPs that seek to expand their service areas to demonstrate that they have sufficient numbers and types of providers to meet the anticipated volume and types of services enrollees in those areas will require. Failure to include this provision could violate sections 1902(a)(19) and 1932(b)(5) of the Act which require State plans to provide safeguards to assure that services be provided, and MCOs to provide assurances that they have the capacity to serve the expected enrollment, respectively. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that it is necessary for the regulation to specifically require that MCOs, PIHPs, and PAHPs that seek to expand their service areas have sufficient numbers and types of providers to meet the expected increased enrollee volume. The general requirement that MCOs, PIHPs, and PAHPs have adequate networks applies whatever the service area. Furthermore, § 438.207(c) requires that MCOs, PIHPs, and PAHPs submit documentation to the State at any time there has been a significant change in their operation, including changes to the geographic service area. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters asked that a provision be included in the regulation to require States to make available all services included in the State plan and make information available to beneficiaries on how to access these benefits. The commenter is concerned that without this requirement important community services that many State plans include through the Rehabilitation Option, such as services that are part of the assertive community treatment model, will not be accessed by beneficiaries. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States are required to make available to all beneficiaries all services covered in the State plan. States may use voluntary or mandatory managed care to provide some or all of these services. If the beneficiary is enrolled in an MCO that does not provide all Medicaid services, or is enrolled in a PIHP or PAHP (which, by definition, is not a comprehensive risk contract), the State remains responsible for making available all Medicaid services not covered in the contract. The regulation provides that both potential enrollees and current enrollees be informed about the services not covered under the contract and how and where they can be obtained. See § 438.10(e)(2)(ii)(E) and (f)(6)(xii). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters said that the rule should require States to notify enrollees how and where to obtain services, including transportation, for services covered by the State plan but not included in the MCO, PHP, or PCCM contract. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.10(f)(6) requires the State, it's contracted representative, or the MCO, PIHP, PAHP, or PCCM to notify enrollees annually of their right to request this information. In addition, § 438.10(e)(2)(i)(E) requires that this information be provided to potential enrollees at the time the potential enrollee first becomes eligible to enroll in a voluntary program or is first required to enroll in a mandatory program. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern that use of a distance standard for urban enrollees could force travel to outlying suburban areas or neighboring counties. The commenter would like the final rule to include language to protect urban enrollees from needing to make lengthy trips to obtain services. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation provides that the State must ensure through its contracts that the provider network is accessible to enrollees, taking into account several factors related to geographic location of providers and enrollees. Depending on State and local circumstances, we believe that the significance of the factors listed—distance, travel time, and means of transportation ordinarily used by Medicaid enrollees—will differ. For urban enrollees, States may find that the latter two factors are more important considerations than distance. When using distance for enrollees in urban areas, we believe that States will factor in the other elements and select a distance criterion that meets the overall intent of the regulation. We believe that the State is in the best position to determine how these criteria should be applied in each of its service areas. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters applauded the use of the term “women's health care specialist” because they believe that it recognizes the important role played by a variety of health care professionals in addition to physicians. These commenters asked that “routine and preventative” be defined in order to ensure that MCOs and PIHPs do not place barriers to impede women's access to women's health specialists. According to the commenters, the definition should include initial and follow up visits for prenatal care, mammograms, pap tests, family planning, and treatment of vaginal and urinary tract infections and sexually transmitted diseases. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the use of the words “routine and preventative” in the regulation is sufficient to categorize the types of services that women can access directly through a women's health specialist. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter seeks inclusion of a requirement that children have direct access to pediatricians, including specialists. The commenter noted that the regulation provides for direct access to women's health specialists and that the patient's rights legislation endorsed by the Administration provides for direct access to pediatricians. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that it is appropriate to require direct access to 
                        <PRTPAGE P="41038"/>
                        pediatricians. While we believe that most children enrolled in Medicaid managed care will have pediatricians as their primary care physicians, pediatricians are not locally available in all areas of the country, and some children will use other physicians, such as family physicians, as their source of primary care. We believe that direct access should generally be to the primary care physician. For women's routine and preventative care we make an exception to this rule because we think it appropriate that women have the choice to see a women's health specialist for routine and preventative care rather than a generalist or other specialty physician.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that the regulation should require direct access to psychiatrists. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that the regulation should provide direct access to psychiatrists. We are concerned about coordination of care and believe that States should have the option to require that patients be referred to psychiatrists by their primary care physician. This helps to ensure that the primary care physician is cognizant of both the physical and mental health needs of patients and has the information needed to coordinate the care needed by patients. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that we retain the provision for out-of-network second opinions from health care professionals, which are not currently available. The commenter stated that a second opinion for a denied service from an in-network provider is a meaningless right. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. The proposed rule provided for a second opinion from a provider in the network, if one is available, and from a provider outside the network only if there is not another qualified provider within the network. We believe that it is important to provide an enrollee with the right to a second opinion, but we believe that this does not require access to a second opinion from a provider who is out of the network. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believe that second opinions should be given by participating physicians when one in the specialty is available. Enrollees would then only be allowed to go out of network when no qualified alternative exists with the network. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in the previous response, the proposed and final rule provide enrollees the right to a second opinion from a provider within the network if a qualified health care professional within the network is available to provide the second opinion. When a qualified health care professional is not available within the network to give a second opinion, the enrollee may obtain it from a health care professional who is not in the network. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the regulation require that second opinions regarding care for a child be provided by physicians with appropriate pediatric education and training. This would be consistent with the pending patient's bill of rights. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The rule specifies that the health care professional giving the second opinion must be qualified to do so. We leave to the States the responsibility for determining the qualifications to be used. States best know their health care markets and are responsible for setting provider qualifications and, therefore, are in the best position to make this decision. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the regulation limit second opinions from out-of-State providers to instances in which a qualified professional is not available within the State. In addition, the commenter asked that the regulation require that the nearest out-of-State provider be used. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation provides that second opinions be obtained from a provider in the network if such a qualified provider is available. This limitation applies when the desired out-of-network provider is within or outside of the State. We have not added other requirements to this provision, as recommended by the commenter. This allows States to decide, or to allow MCOs, PIHPs, and PAHPs to decide, who is to provide a second opinion when one is to be obtained from an out-of-network provider. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believes that CMS should conduct studies to determine if second opinions routinely result in a change of treatment plan and in better outcomes. Unless it can be established that second opinions result in better outcomes, they do not warrant the extra cost. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree that CMS should study if second opinions result in a change of treatment plan or in better outcomes to document their benefit before establishing them as an enrollee right. Second opinions are widely used and accepted in both FFS and managed care service delivery systems. In FFS, Medicaid beneficiaries can freely access a second opinion by simply seeing another physician. Likewise, in FFS, insurance companies often require confirmatory second opinions before authorizing certain services or procedures. We believe that second opinions are well established in the practice of medicine in this country and should be available to Medicaid managed care enrollees. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters asked that the regulation limit payment to non-participating providers to the Medicaid FFS fee schedule. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not require that non-participating providers be paid according to the Medicaid FFS fee schedule. We believe that States are in the best position to determine whether payment limits should apply to out-of-network providers or if the MCO, PIHP, and PAHP should be free to negotiate rates. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that we retain the requirement that MCO and PIHPs pay for services received out of network when they are not available in the network because this will lead to less disenrollment. Another commenter supported inclusion of this provision. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that it is the responsibility of the MCO, PIHP, or PAHP to pay for services, covered under their contracts, received out of network when they are not available from within the network. The MCO, PIHP, or PAHP must arrange for all services needed by their enrollees. We agree that establishing this as an MCO, PIHP, and PAHP responsibility will decrease enrollee disenrollments. We retain this provision in the final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported the provision that services received out of network may not result in costs to the enrollee greater than would have been within the network. One commenter asked that the wording be revised so that MCOs and PIHPs would not be responsible for actions by out-of-network providers in relation to fees charged to enrollees. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that it is important that Medicaid enrollees not be placed at a financial disadvantage should their MCO, PIHP, or PAHP refer them to an out-of-network provider for a covered service because a qualified provider is not available in the network. The MCO, PIHP, or PAHP must negotiate the amount they will pay the provider and, as part of this negotiation, can best ensure that the enrollee does not incur out-of-pocket costs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed the opinion that the hours of operation offered commercial enrollees is not relevant to the Medicaid contract. He believes that this requirement is impossible to oversee or enforce and could result in a decrease in the number of providers available to serve Medicaid beneficiaries. Another commenter believes that it is not realistic for Medicaid to achieve this standard because Medicaid reimburses providers significantly less than commercial 
                        <PRTPAGE P="41039"/>
                        plans. And another commenter said that it is not usual practice for States to track providers' hours of operation if they do not treat Medicaid patients. One commenter said that the requirement should be that services are available and accessible to the same extent that they are for FFS beneficiaries or the general public. Another commenter supported the provision as written. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In the final rule we have retained the provision related to hours of operation as proposed. The purpose of this requirement is to make certain that Medicaid enrollees have the same access to providers as do enrollees of other payers. We believe that the provision is appropriate and is enforceable by MCOs, PIHPs, and PAHPs through their contracts with providers. Access can be monitored by the State or the MCO, PIHP, or PAHP by reviewing patient appointments or by monitoring enrollee grievances. The commenter who stated that States do not track providers' hours of operation if they do not treat Medicaid patients misunderstood the provision. It applies only to providers in Medicaid managed care networks. For those providers who serve only Medicaid patients, we set the hours of operation for FFS Medicaid patients as the standard that must also be applied to managed care enrollees. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that proposed § 438.204(b)(3) should not require States to “continuously” monitor hours of operation, as this represents an increased burden on States. Rather the regulation should require that States monitor for this requirement “regularly''. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the use of the term “continuously” may be confusing and that “regularly” better conveys our intent. We have revised § 438.204(b)(3) of the regulation to reflect this change. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters said that the requirement that MCOs participate in States' efforts to promote the delivery of care in a culturally competent manner is not sufficient. They believe that systems of care must be designed to be respectful of and responsive to cultural and linguistic needs in order to provide equal access to quality health care. Failure to provide information about treatment options in a culturally sensitive way could affect patient compliance, lead to declines in the patient's health, and escalate costs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that health care needs to be delivered in a culturally competent manner for it to be most effective. However, in the final regulation we have retained the provision of the proposed rule, that MCOs, PIHPs, and PAHPs participate in State efforts to promote the delivery of care in a culturally competent manner, because we believe that it is through this requirement that MCOs, PIHPs, and PAHPs, will gain the knowledge and experience to provide culturally competent care. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the approach taken in the NPRM regarding cultural competency and believe that the State is in the best position to lead initiatives on cultural competency. This allows States to advance initiatives crossing FFS and managed care. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters and have retained this provision in the final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters said that MCOs, all PHPs, and PCCMs should be required to provide services in a culturally competent manner because, as recipients of Federal funds, they are all required to do this. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This regulation requires MCOs, PIHPs, and PAHPs to participate in State efforts to promote cultural competency in order to comply with the requirements of section 1932 of the Act. It does not address requirements of other statutes that might also apply. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter objected to the Medicaid rule having what he viewed as weaker requirements relating to cultural competency than the Medicare+Choice rule. He noted that in the preamble to that rule CMS stated that the M+C provisions are consistent with title VI of the Civil Rights Act, recommendations from the President's Race Initiative, and the President's Advisory Commission on Consumer Protection and Quality in the Health Care Industry. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Medicaid is a State/Federal program and States retain responsibility for much of the program and operational policy of their programs. We believe that States can best decide how to advance cultural competency in their managed care programs. We are working with the Medicare program to develop tools for managed care organizations to use to improve the delivery of culturally competent health care. When these tools are available, we will share them with States so that they can use them at their option. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the new standards developed by the Office of Minority Health (National Standards on Culturally and Linguistically Appropriate Services) be referenced as a more detailed document that clarifies the regulatory provision. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that these guidelines are a valuable tool and we encourage States to review them and consider their use. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters suggested the addition of a provision to prohibit discrimination by providers toward Medicaid enrollees. One commenter noted that the President's Commission on Consumer Protection and Quality in the Health Care Industry opposed discrimination on the basis of source of payment. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have decided not to include a provision in the regulation to prohibit providers from discriminating against Medicaid enrollees. We do not believe that this provision is needed in this regulation. States remain responsible for ensuring Medicaid enrollees adequate access to providers and are in the best position to choose the mechanisms they believe will be effective to ensure this result. We also have a provision in the regulation that requires that network providers offer Medicaid enrollees the same hours of operation offered to commercial enrollees. We believe that this requirement will help ensure equal access for Medicaid enrollees to providers. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended inclusion of a provision to require States that limit freedom of choice to comply with the requirements of § 438.52. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirements related to freedom of choice at § 438.52 apply in accordance with the provisions of that section. It is unnecessary to reiterate or cross reference those requirements in this section. 
                    </P>
                    <HD SOURCE="HD3">5. Assurances of Adequate Capacity and Services (Proposed § 438.207) </HD>
                    <P>Under the authority of section 1932(b)(5) of the Act, proposed § 438.207(a) required that the MCO and PIHP provide the State with adequate assurances that the MCO or PIHP has the capacity to serve the expected enrollment in the service area. Proposed § 438.207(b) required that documentation submitted to the State must be in a format set by the State and acceptable to CMS and must demonstrate that the MCO or PIHP offers an appropriate range of services, including preventative services, primary care services, and specialty services. The MCO and PIHP was also required to document that it maintains a network of providers sufficient in number, mix, and geographic distribution. </P>
                    <P>
                        Section § 438.207(c) specified when documentation must be provided including (1) at the time the MCO or PIHP enters into a contract with the State, and (2) whenever there has been a significant change in the MCO's or PIHP's operations that would affect adequate capacity and services such as 
                        <PRTPAGE P="41040"/>
                        changes in services provided, benefits, geographic service areas, payments, or enrollment of a new population. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended that this section apply to dental plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that it is important for PAHPs, including dental plans, as well as MCOs and PIHPs to have adequate provider networks and to provide the State with assurances as to the adequacy of their networks. Therefore, in the final rule, we extend the provisions of this section to PAHPs. We note that the provider network for PIHPs and PAHPs need only include provider types necessary to provide the services included in their contracts. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that MCOs and PIHPs need to contract with the appropriate number and mix of pediatric-trained specialists and tertiary care centers for children in order to ensure that they have adequate capacity to serve their expected enrollment. If a plan fails to contract with an adequate number of these providers, the plan should be required to provide these services out of network at no additional cost. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we stated earlier in this preamble, we have chosen not to specify types of specialists or other providers that health plans must contract with in order to meet the requirements of the regulation. Rather, in § 438.206(b)(1), we retain the general requirement that provider networks must be adequate to provide adequate access to all services covered under the contract. In § 438.206(b)(4), we provide that necessary medical services not available within the network, must be covered by the MCO, PIHP, or PAHP out of network. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that this provision be revised to require the State to ensure, through its contracts, that MCOs provide a full range of psychiatric services and have a sufficient number of psychiatrists participating in the plan. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated above, in the final rule we are not specifying specific provider types needed by MCOs, PIHPs, and PAHPs, but rather providing a general requirement that the networks be sufficient to provide adequate access to covered services to all enrollees. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter disagreed with CMS' decision to interpret “adequate assurances” to require extensive documentation suggested in the preamble. The commenter believes that extensive and detailed data are often of little use in determining the adequacy of the provider network and that network deficiencies are often found when an enrollee changes primary care physicians, calls enrollee services, or files a grievance.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We continue to believe that it is necessary and appropriate for the regulation to require that each MCO, PIHP, and PAHP document that it has adequate provider capacity to provide necessary medical services. The heading for section 1932(b)(5) of the Act is “Demonstration of Adequate Capacity and Services.” We believe that the MCO, PIHP or PAHP cannot demonstrate that it has the capacity to serve its expected enrollment without providing documentation. In addition, we require that the State have documentation to support its certification to the Secretary under § 438.207(d). This documentation is required prospectively to avoid problems that may otherwise not be detected until an enrollee complains or takes other steps to address a situation caused by the lack of an adequate provider network. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters objected to the omission of a provision to require MCOs and PIHPs to have in place policies and procedures to respond to situations in which there is an unanticipated need for providers with particular types of expertise or an unanticipated limitation on the availability of such providers. The commenters believe that such a provision is necessary to meet the statutory requirement for a quality strategy that includes access standards to ensure that covered services are available within reasonable timeframes and in a manner that ensures continuity of care and adequate primary care and specialty care. Another commenter supported the omission of such a provision. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have not included a provision in the final rule to require MCOs, PIHPs, and PAHPs to have policies and procedures in place to respond to situations in which there is an unanticipated need for providers or a limitation on the availability of needed providers. We again rely on the requirement in § 438.206(b)(1) and § 438.206(b)(4) that MCOs, PIHPs, and PAHPs must have adequate provider networks or, if the MCO, PIHP, or PAHP is unable to provide them, must adequately and timely provide these services out of network. 
                    </P>
                    <HD SOURCE="HD3">6. Coordination and Continuity of Care (Proposed § 438.208) </HD>
                    <P>Proposed § 438.208 contained provisions specifying how the care of Medicaid beneficiaries enrolled in MCOs and PIHPs is to be provided in order to promote coordination and continuity of care, especially with respect to individuals with special health care needs. In proposed paragraph (a) we allowed for two exceptions to some of these coordination and continuity of care provisions. In the first instance, provisions pertaining to some screening, assessment and primary care requirements would apply to PIHPs as the state determines appropriate, based on the scope of the PIHP's contracted services and the way the state has organized the delivery of managed care services. In the second instance, for Medicaid-contracting MCOs that serve certain Medicaid enrollees also enrolled in Medicare+Choice plans and receiving Medicare benefits, the State similarly determines, based on the services it requires the MCO to furnish to dually eligible enrollees, the extent to which the MCO must meet certain screening, assessment, referral, treatment planning, primary care and care coordination requirements. In proposed paragraph (b) we put forth requirements for the state Medicaid agency to identify certain enrollees with special health care needs and to further identify these enrollees to its enrollment broker, if applicable, and contracting MCOs and PIHPs. In proposed paragraph (c) we specified requirements for the screening and assessment of individuals with special health care needs. In proposed paragraph (d) we specified requirements for referrals and treatment plans for MCO and PIHP enrollees determined to have ongoing special conditions that require a course of treatment or regular care monitoring. These requirements addressed access to specialists and the development of treatment plans. In proposed paragraph (e) we specified requirements pertaining to MCO and PIHP care coordination programs, including requirements that these programs: provide each enrollee with an ongoing source of primary care, coordinate each enrollee's health care services, appropriately share with other MCOs and PIHPs the results of any screenings or assessments in order to prevent unnecessary burden on the enrollee, and protect enrollee privacy and confidentiality. </P>
                    <P>
                        One commenter heartily endorsed § 438.208 of the proposed rule and urged CMS to preserve it in the final rule and monitor for compliance with it. However, many other commenters recommended that this section of the regulation include more specific or stronger requirements for States and managed care entities, particularly with respect to the care of individuals with special health care needs. Most commenters offered specific 
                        <PRTPAGE P="41041"/>
                        recommendations for changing this section of the regulation. We agree with these comments and have revised § 438.208 as discussed below, in response to these comments. 
                    </P>
                    <HD SOURCE="HD2">Identification of “At Risk” Individuals </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended that we require States to identify individuals “at risk” of having special health care needs. Many of these commenters identified these individuals as: children and adults who receive SSI benefits; children in foster care; enrollees over the age of 65; enrollees in relevant, state-established, risk-adjusted, higher-cost payment categories; and any other category of recipients identified by CMS. A few commenters recommended that we allow States to use additional State-identified categories of people who are “at risk” for having special health care needs. One commenter stated that children under age 2 and pregnant women should be identified as being “at risk” of having special health care needs. Another commenter stated that children enrolled in a State's Title V program for children with special health care needs should be included in a regulatory definition of persons “at risk” of having special health care needs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The proposed rule at § 438.208(b) required States to identify individuals “with” (as opposed to individuals “at risk of having”) special health care needs. For several reasons, we believe it is appropriate to retain this distinction in this final rule, and not additionally require States to identify individuals “at risk of having” special health care needs. First, States already well appreciate the increased risk that certain populations (for example, children and adults who receive SSI benefits; children in foster care; enrollees over the age of 65; and enrollees in relevant, state-established, risk-adjusted, higher-cost payment categories) have for needing special services or high levels of service. States can also readily identify these individuals. We do not believe that regulations are necessary to call States' attention to these individuals or that States need encouragement or assistance in identifying these individuals. To additionally require States to create a new administrative mechanism in order to categorize as “at-risk” those individuals who are already well-known to State Medicaid agencies and can be easily identified, would dilute the attention paid to individuals who actually have special health care needs. Instead, in § 438.208(c) of this final regulation we require States to focus their attention more closely on identifying individuals who actually have special health care needs. Second, the concept of “at risk” of having special health care needs (beyond the categorical groups discussed above) is widely recognized as difficult to put into operation. Well-known researchers in this field have explicitly declined to address the concept of “at risk” when developing screening tools to identify children and adults with special health care needs. Because the science in this area is still elementary, we believe it is premature to ask States to implement this concept at this time. Finally, we note that commenters did not agree among themselves on which populations should be included in a category of “at risk of having” special health care needs. For these reasons, in this final rule we do not require States to identify individuals “at risk” of having special health care needs. 
                    </P>
                    <HD SOURCE="HD2">Definition of Individuals With Special Health Care Needs </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended that proposed § 438.208(b) should specify certain groups of individuals as “having” special health care needs. Many of the recommended groups were identical to the groups identified by other commenters as individuals who should be considered “at risk” of having special health care needs. Specifically, the following groups were recommended by many commenters: children and adults who are receiving SSI benefits; children in foster care; enrollees over the age of 65; enrollees in relevant, state-established, risk-adjusted, higher-cost payment categories; and any other category of recipients identified by CMS. Many commenters also identified children under age 2 and other enrollees known by the State to be pregnant or having other special health care needs as categories of persons requiring special attention and about whom the State should notify the MCO/PIHP of their having a special health care need. 
                    </P>
                    <P>Other commenters stated that proposed § 438.208(b) should specify a threshold or minimum definition of persons with special health care needs. One commenter stated that the definition should be as follows, “Individuals with special health care needs include adults and children who daily face physical, mental, or environmental challenges that place at risk their health and ability to fully function in society (for example, individuals with mental retardation or serious chronic illnesses, pregnant women, children under the age of 7, children in foster care or out-of-home placement, and individuals over age 65).” Other commenters stated that children with special health care needs should be defined consistent with the Department's Maternal and Child Health Bureau's definition which reads, “Children with special health care needs are those who have or are at elevated risk for chronic physical, developmental, behavioral, or emotional conditions and who also require health and related services of a type or amount not usually required by children.” </P>
                    <P>In contrast, several commenters expressed support for allowing States to define which populations need to be identified and how to identify them. One commenter asked us to confirm that the proposed rule would allow States the flexibility to define “individuals with special health care needs.” Another commenter stated that the requirement for States to identify enrollees with special health care needs and identify these enrollees to its enrollment broker (if applicable) and MCOs should be eliminated. The commenter stated that this requirement is neither feasible nor practical because (1) the State does not have a mechanism to identify persons with special health care needs—other than individuals who receive SSI; (2) enrollees may not choose to reveal information about their health, which should be held between the enrollee and his or her provider, and possibly the health plans; and (3) the appropriate mechanism for identifying a person with a special health care need is through an assessment which is required elsewhere in the regulation. </P>
                    <P>
                        <E T="03">Response:</E>
                         In our report to the Congress, Safeguards for Individuals with Special Health Care Needs Enrolled in Medicaid Managed Care, dated November 6, 2000, we identified, “the presence or increased risk of disability,” as a shared characteristic of populations with special health care needs. We identified 6 populations as examples of groups that had an increased prevalence or risk of disability: (1) Children with special health care needs; (2) children in foster care; (3) individuals with serious and persistent mental illness and/or substance abuse; (4) individuals who are homeless; (5) older adults with disabilities; and (6) non-elderly adults who are disabled or chronically ill with physical or mental disabilities. However, this same report, while calling these groups to the attention of States, recognized the difficulty that States face in identifying not just population 
                        <E T="03">groups</E>
                         that have an increased prevalence or risk of disability, but in identifying 
                        <E T="03">individuals</E>
                         who actually have a special health care need. Because of this, we entered into a contract with 
                        <PRTPAGE P="41042"/>
                        the Foundation for Accountability (FACCT) to produce a reference manual for State Medicaid agencies and other interested parties. The manual will present and discuss reliable and valid approaches to identifying individuals who have special health care needs. In addition, we asked FACCT to develop a new screening tool that can be used to help identify adults with special health care needs. This adult screener has now been developed and tested. It, along with other valid and reliable approaches to identifying adults and children with special health care needs, will be included in the reference manual for States. Because this research conducted for us by FACCT has documented that there are different ways (with varying degrees of sensitivity, specificity, and resource implications) to identify individuals with special health care needs, we do not believe it appropriate to require one approach, and thereby one definition. Rather, we encourage States to review these different approaches, in conjunction with beneficiaries and stakeholders, as a part of their State quality strategy developed under § 438.204, and select the approach or approaches to identifying individuals with special health care needs that best complements the design of the State's Medicaid program and managed care initiatives. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended that States also be required to identify enrollees with special health care needs to PAHPs and PCCMs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters and we have revised § 438.208(c) to include PAHPs. However, we have not applied these provisions to PCCMs because, as noted elsewhere in this preamble, the statutory provisions of the BBA, which authorized these quality requirements, apply only to prepaid, capitated forms of managed care. 
                    </P>
                    <HD SOURCE="HD2">Screening and Assessment </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters expressed confusion over the use of the words “screening” and “assessment” in § 438.208(c) of the proposed rule. One commenter erroneously stated that the provisions for screening and assessment of special needs individuals were not contained in the proposed regulation. Many commenters stated that the proposed rule did not differentiate between the words, “screening” and “assessment.” One commenter urged us to specify that an initial screen must be sufficient to identify individuals with special health care needs and facilities that can meet those needs, and that a health assessment must be comprehensive and include a physical examination. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that the proposed rule provisions at §§ 438.208(b) and (c) respectively calling for “State responsibility to identify certain enrollees with special health care needs,” and “Screening and assessment” are confusing, in part because of some redundancy. The proposed rule intended to convey that identification of individuals with special health care needs should be accomplished through some form of screening. Therefore, we have revised § 438.208(c) and replaced the word “screening” with the words, “mechanisms to identify.” This change is supported by information from several experts in screening who reminded us that screening tools by their very nature are not perfect, and that subsequent follow-up through a more intensive assessment is needed in order to better determine if an individual's special health care needs actually require a course of therapy or monitoring. We also made other changes to the organization of this section in order to better distinguish the identification activity from the assessment function. 
                    </P>
                    <P>However, we did not, as requested by one commenter, specify that an initial screen (identification mechanism) must be sufficient to identify facilities that can meet an individual's special needs. We believe that determining appropriate facilities, when care in a facility is needed, should not be based on the results of a screen or identification mechanism, but upon an assessment and ongoing communication between the patient and his or her health care provider(s). We further did not explicitly state in § 438.208(c)(2) that the enrollee's health assessment must be comprehensive because we believe that “comprehensive” is subject to varying interpretations, and therefore is not readily able to be reliably monitored or consistently enforced by CMS. Further, the provisions in § 438.208(c)(2) already require assessments to “identify any ongoing special conditions of the enrollee that require a course of treatment or regular care monitoring” and that the assessment mechanisms must use appropriate health care professionals. We also have not required that the assessment include a physical examination, because we believe that for some individuals, a course of treatment or regular care monitoring might be determined to be unnecessary without a physical examination. We therefore defer to States to set further standards for assessment, noting that these standards for identification and assessment are included as part of a State's quality strategies under § 438.204. Therefore, any State standards for assessment will be developed with the input of Medicaid beneficiaries and other stakeholders. We believe that any greater specificity in requirements pertaining to assessments should be developed as a part of this process. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that proposed § 438.208(c) failed to quantify what will be substantial burden associated with the requirements for screening and assessment. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It would be very difficult to more accurately quantify the overall impact and burden of this provision of the regulation because of the variation in State programs and how States will choose to implement these provisions. In § 438.208(c) of the final rule we have retained State flexibility in identification, assessment, treatment planning for individuals with special health care needs, and with respect to how provisions will be applied to MCOs, PIHPs, and PAHPs that serve dually eligible enrollees. Because of our desire to allow States to have this flexibility, and the variations in practice that currently exist within the managed care industry, it is not possible to more accurately quantify the burden of these provisions. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that it could not comply with the requirement stated in the preamble to proposed § 438.208 that in instances when an MCO is not able to meet requirements for screening or assessment for an individual enrollee, because, for example, it is not possible to contact the enrollee or the enrollee refused to respond to the MCO, that the MCO ensure that the reason why the enrollee could not be screened or assessed be documented in the enrollee's medical record. The commenter stated that it does not own its contracted providers and does not have the ability to enforce the requirement. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. We believe that MCOs can include this as a requirement in their written agreements with participating providers. However, the commenter is incorrect in indicating that we have required this in the preamble. Rather, the preamble states that an MCO or PIHP “should” take steps to ensure that this information is documented. 
                    </P>
                    <HD SOURCE="HD2">Identification </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked us to clarify CMS's goal with respect to individuals with special health care needs given the commenter's 
                        <PRTPAGE P="41043"/>
                        observation that these individuals will have great variability in the coverage and care they will receive between States. One commenter stated that § 438.208(b) of the proposed rules did not emphasize clearly the importance of identifying all persons with special health care needs. A few commenters expressed concern that the proposed rule did not contain provisions that would require the State to have a strategy to identify enrollees with special health care needs. One commenter stated that the regulation does not contain requirements that MCOs have procedures in place to identify individual enrollees with serious and multiple medical conditions, “whether they be physical-health, mental health, or substance-abuse related in nature.” The commenter maintained that CMS must include these provisions. A few commenters stated their support for a requirement that MCOs must screen all enrollees to detect special health care needs. A few commenters also stated that each MCO and PHP should be required to implement a mechanism to identify enrollees who develop special health care needs after they enroll in the MCO or PIHP. One commenter asked if CMS would be monitoring States with respect to the requirement in § 438.208(b) pertaining to State's responsibility to identify certain enrollees with special health care needs, and if so, if the monitoring will use a tool that has been developed for CMS by FACCT. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have revised § 438.208(c)(1) and (c)(2) to clarify our goals with respect to individuals with special health care needs and emphasize the importance of identifying the individuals. We did not, as one commenter directed, require MCOs to have procedures in place to identify individual enrollees with serious and multiple medical conditions, “whether they be physical-health, mental health, or substance-abuse related in nature,” because we believe that the State should be the one to consider the issues as it develops its mechanism to identify individuals with special health care needs, as part of its quality strategy, and with the input of Medicaid recipients and other stakeholders. In our revisions, we also did not require each MCO and PIHP to implement a mechanism to identify enrollees who develop special health care needs after they enroll in the MCO or PIHP. We believe that the extent to which this should occur should be considered by the States in the context of the States' overall strategy and mechanism for identifying individuals with special health care needs. Finally, we affirm that CMS will be monitoring States with respect to the requirement to identify enrollees with special health care needs. However, we note that the tool that has been developed for CMS by FACCT is a screening tool, not a monitoring tool. Additionally, it is one of several screening tools that will be shared with States for their discretionary use. Therefore, the FACCT tool is not likely to be used by CMS for monitoring activities. 
                    </P>
                    <HD SOURCE="HD2">Assessment </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that the proposed rule does not contain provisions that MCOs assess the condition of individual enrollees with serious and multiple medical conditions. The commenter maintained that CMS must include these provisions. Another commenter stated that the regulation should specify groups of beneficiaries for whom special health assessments should be required so that there will not be significant variation in access and quality of care among the various state Medicaid programs. In contrast, other commenters expressed support for the provisions of the regulation pertaining to assessment of people with special health care needs and for allowing states and plans to develop timelines and procedures that meet the needs of their enrolled population. Still other commenters further expressed support for allowing States to determine how to assess individuals with special health care needs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The final regulation contains requirements that MCOs (and also PIHPs and PAHPs at the discretion of the State) assess individual enrollees with special health care needs. We believe that individuals with “serious and multiple medical conditions” are included in the concept of special health care needs, and intend that States' mechanisms to identify individuals with special health care needs will identify individuals with serious and multiple medical conditions. However, in § 438.208(c)(1) we allow States the discretion of determining how to identify individuals with special health care needs, and therefore how to implement this concept. Consistent with this position, we do not believe that we should specify groups of beneficiaries for whom special health assessments should be required. 
                    </P>
                    <HD SOURCE="HD2">Initial Assessments </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern that the proposed regulation does not require MCOs or PHPs to conduct initial assessments of all new Medicaid enrollees, noting that Medicare+Choice plans are required to conduct the assessments. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We used the term “initial assessment” in a Medicaid proposed rule published on September 29, 1998 (63 FR 52022) to implement these same statutory provisions. Since that time, we have received numerous and ongoing comments that the purpose and scope of an “initial” assessment has not been well understood. The words “initial assessment” do not appear in widespread use in the private sector or in health services research or policy studies. We have attempted to address this problem in subsequent versions of the regulation, and in § 438.208(c)(1) and (c)(2) of this final regulation, by dropping the terminology “initial assessment” and separating out what we believe are the two essential activities; that is, identifying individuals who have special health care needs, and assessing their needs. We do not believe it necessary to further specify the need for primary care providers operating under the auspices of an MCO, PIHP, or PAHP to assess the health of their patients, because we believe this to be a well-established component of primary health care. 
                    </P>
                    <HD SOURCE="HD2">Timeframes </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that the regulation must ensure that people with identifiable risks for having special health care needs receive an expedited review of their health care needs. Many commenters stated that the final rules should include a health assessment soon after enrollment to identify pregnant women's health care needs and course of treatment. Many other commenters stated that the regulation should specify timeframes for managed care entities to screen and assess individuals with special health care needs, individuals “
                        <E T="03">at risk</E>
                        ” of special health care needs, and other enrollees. Many of these commenters recommended a variety of specific timeframes as follows. MCOs and PHPs should be required to: (1) Screen enrollees identified as “
                        <E T="03">at risk</E>
                        ” by the State within 30 days of the enrollees being so identified; (2) screen all other enrollees within 90 days of enrollment to determine whether the enrollee is pregnant or has a special health care need; (3) for any screened enrollee identified as being pregnant or having special health care needs, provide a comprehensive health assessment as expeditiously as the enrollee's health condition requires, but no later than 30 days from the date of the identification; 
                        <PRTPAGE P="41044"/>
                        (4) for enrollees identified by the State as being pregnant, or who have self-identified as being pregnant or having special health care needs, provide a comprehensive health assessment within 30 days without needing an initial screen. Other commenters stated that screening should be performed on enrollees identified by the State as having special health care needs within 30 days after having been so identified by the State. One commenter stated that the regulation should require initial assessment of each pregnant woman by her MCO as soon as possible, but always within 30 days of enrollment. The commenter also stated that standards for individuals with complex and serious medical conditions should be similarly revised. Another commenter recommended that each MCO and PHP be required to make a best effort to screen the following individuals within 30 days of their being identified: Children and adults who receive SSI, children in Title IV-E foster care, enrollees over the age of 65, and enrollees in relevant, state-established, risk-adjusted, higher cost payment categories, and other categories identified by CMS. This commenter also recommended that each MCO and PHP be required to make a best effort to assess individuals who are pregnant or who have a special health care need within 30 days of their being identified. Another commenter recommend that disabled children and adults, foster children, enrollees over the age of 65, pregnant enrollees and infants and toddlers be screened by their MCOs within 30 days; other MCO enrollees should be screened within 90 days. Several other commenters, however, did not recommend a specific timeline. One commenter stated that timelines should be specified in advance by the State and approved in advance by CMS.
                    </P>
                    <P>In contrast, one commenter stated that proposed § 438.208(c) and (d) that pertain to assessment and treatment of people with special health care needs are realistic and allow States and plans to develop timelines and procedures that meet the needs of their enrolled population. Another commenter expressed support for allowing States the authority to determine workable timeframes for their individual programs. </P>
                    <P>
                        <E T="03">Response:</E>
                         We have carefully reviewed all the suggestions, and we do not believe it best for the Federal government, rather than the States, to establish timeframes specifying when all managed care entities are to screen and assess individuals with special health care needs, individuals “at risk” of special health care needs, and other enrollees. We believe that it would be more appropriate and effective for screening and assessment timelines to be established by the State agency, in consultation with beneficiaries and other stakeholders, taking into consideration access and availability standards set by the State, the definitions and mechanisms chosen by the State agency to identify individuals with special health care needs, the character of the state's managed care marketplace, and State and/or local standards in both the public and private marketplace. With respect to the comment that timelines should be specified in advance by the State and approved in advance by CMS, we note that because we believe that any necessary timelines should be established by the State based on State considerations, CMS would not likely have more relevant information than the State, on existing access and availability standards set by the State, definitions and mechanisms chosen by the State agency to identify individuals with special health care needs, the character of the State's managed care marketplace, and State and/or local standards in both the public and private marketplace. We therefore decline to require prior Federal approval of State timelines. 
                    </P>
                    <HD SOURCE="HD2">Treatment Plan </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported our proposed § 438.208(d) that pertains to a treatment plan for enrollees with special health care needs, but disagreed with the provision in § 438.208(d)(2) that states that the decision is left to the discretion of the enrollee's MCO/PHP of whether or not an individual with special health care needs would receive a treatment plan. Many commenters further stated that the regulation should indicate the individuals for whom health plans must develop and implement treatment plans, including individuals with special health care needs and pregnant women, particularly those pregnant women at high risk such as those with gestational diabetes or with a history of miscarriages. 
                    </P>
                    <P>Many commenters also suggested a number of additional provisions be added to the requirements for a treatment plan; specifically, that treatment plans: (1) Be appropriate to the enrollee's identified and assessed conditions and needs; (2) be for a specific period of time and updated periodically; (3) specify a standing referral or an adequate number of direct access visits to specialists; (4) ensure adequate coordination of care among providers; (5) be developed with enrollee participation and (6) ensure periodic reassessment of each enrollee as his or her health condition requires. A few commenters stated that the treatment plan should be required to be appropriate to the standard of care for the enrollee's condition and identified needs. Other commenters noted that the Medicare+Choice regulations require a treatment plan for all enrollees with serious medical conditions. One commenter stated that the regulation should add a new provision requiring that, “the MCO or PHP must continue the existing treatment plan of an enrollee until an initial assessment of that enrollee occurs.” The commenter stated that this provision would address the adverse effects that individuals can experience when there is an interruption in the ongoing clinical treatment of their illness or health condition. One commenter recommended the inclusion of requirements that treatment plans include direct access to specialists as required by the treatment plan and that the treatment plan be updated periodically by the physician responsible for the overall coordination of the enrollee's health. </P>
                    <P>In contrast, a few other commenters supported the provisions of the regulation pertaining to assessment and treatment of people with special health care needs, stating that the provisions are realistic and reasonable and allow states and plans to develop timelines and procedures that meet the needs of their enrolled population. One commenter stated that the enrollee, provider, and MCO clinical staff should determine the provisions that need to be included in a member's treatment plan. One commenter expressed support for allowing states to determine the extent to which MCOs must put in place mechanisms to allow enrollees to participate in the development of the treatment plan. One commenter recommended that an additional exemption be created in paragraph (a) with respect to the requirement that there be consultation with the primary care provider in the development of the treatment plans. The commenter noted that in his or her State, fee-for-service primary care providers are not a part of the specialty managed care network, and are not responsible for coordinating their primary care with mental health professionals. The commenter recommended that a new exception be added as section 438.208-(a)(2) (iii) “to consult with the enrollee's primary care provider in the development of a treatment plan as specified in paragraph (d)(2) of this section.” </P>
                    <P>
                        <E T="03">Response:</E>
                         We have revised § 438.208(c)(2) of this regulation, that 
                        <PRTPAGE P="41045"/>
                        left the decision of whether or not an individual with special health care needs receives a treatment plan up to the discretion of the enrollee's MCO, PIHP, or PAHP. We agree with many of the commenters that this decision should not be left up to the MCO, PIHP, or PAHP and have revised the regulation to give States the authority to determine the extent to which treatment plans would be required. States will be required to address this as a component of their quality strategy and to develop these standards with input from Medicaid recipients and other stakeholders. 
                    </P>
                    <P>
                        For a variety of reasons, we disagree with commenters that we should add certain other requirements for treatment plans; that is that treatment plans be required to: (1) Be appropriate to the enrollee's identified and assessed conditions and needs; (2) be for a specific period of time and updated periodically; (3) ensure periodic reassessment of each enrollee as his or her health condition requires; and (4) be required to be appropriate to the standard of care for the enrollee's condition and identified needs. We found a number of these requirements to be vague and therefore difficult to monitor and enforce, and not providing significant benefit to beneficiaries; for example, “be for a specific period of time and updated periodically,” “appropriate to * * * conditions and needs” and “appropriate to the standard of care for the enrollee's condition and identified needs.” In addition, we note that two of these proposed additions to treatment plan requirements are more strongly addressed elsewhere in this section. The recommended requirement that the treatment plan specify a standing referral or an adequate number of direct access visits to specialists is addressed in paragraph (c)(4), Direct Access to Specialists, which states that, “For enrollees determined through assessment to need a course of treatment or regular care monitoring, each MCO, PIHP, and PAHP must have a mechanism in place to allow enrollees to directly access a specialist (for example, through a standing referral or an approved number of visits) as appropriate for the enrollee's condition and identified needs.” The recommended requirement that the treatment plan ensure adequate coordination of care among providers is addressed in paragraph (b), 
                        <E T="03">Primary care and coordination of health care services for all MCO, PIHP, and PAHP enrollees.</E>
                         We also did not add a requirement that, “The MCO or PHP must continue the existing treatment plan of an enrollee until an initial assessment of that enrollee occurs.” We believe that the situation, which the commenter has identified, is addressed by the provisions at § 438.208(b) pertaining to primary care and coordination of health care services. 
                    </P>
                    <HD SOURCE="HD2">Direct Access to Specialists </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that proposed § 438.208(d) that pertains to direct access to specialists should be clarified that direct access to a specialist should be a determination made in concert with the primary care physician, health plan, patient, and specialist based on each patient's specific circumstances, not made through a screening instrument that identifies an individual as having special health care needs. Another commenter expressed support for the regulatory provisions allowing States to determine MCOs mechanisms through which Medicaid enrollees with special health care needs will have direct access to specialists. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that a decision about access to specialists should not be based on the results of screening. In § 438.208(c)(4) of the final rule, we clarify that access to specialists should be made as a result of a more detailed assessment using (consistent with § 438.208(c)(2)) “appropriate health care professionals.” We believe appropriate health care professionals include the enrollee's primary care provider, but not necessarily the MCO or a specialist. Participation of the enrollee in this decision is guaranteed under the provisions in § 438.100 (b)(2)(iv) pertaining to the enrollee's right to participate in decisions regarding his or her health care. 
                    </P>
                    <HD SOURCE="HD2">Exemptions </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed support for the exemption allowing State Medicaid agencies to determine to what extent any MCO that serves enrollees who are also enrolled in a M+C plan and receive Medicare benefits must meet the screening and assessment, referral and treatment plan, and primary care and coordination requirements of proposed § 438.208(c), (d), and (e)(1) (now § 438.208(b) and (c)). The commenter recommended that dual eligible enrollees receive one screening and assessment that satisfies requirements for Medicare+Choice. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate and agree with the commenter's support for the provision in § 438.208(b) and (c) that allow State Medicaid agencies to determine to what extent any MCO that serves enrollees who are also enrolled in a M+C plan and receive Medicare benefits must meet requirements pertaining to coordination, identification, assessment, and treatment planning. We agree that it is desirable for dual eligible enrollees to receive one screening and assessment that satisfies requirements for both Medicaid and Medicare+Choice, but we are not imposing this requirement at this time, in recognition of the operational and policy issues that first must be addressed in order to accomplish this and because it may not be feasible in all instances. 
                    </P>
                    <HD SOURCE="HD2">Patient Confidentiality and Sharing of Information </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern about the provision of proposed § 438.208(e)(3) which would require MCOs and PIHPs to share with other MCOs and PIHPs serving an enrollee, the results of its screening and assessments so that those activities need not be duplicated. The commenter understood of the intent of the provision but expressed concern over possible effects on patient confidentiality. The commenter offered no specific recommendation to address these competing concerns. Another commenter noted that the requirements might present concerns about patient confidentiality if MCOs are not able to obtain enrollee consent for the sharing of information. One commenter supported the proposed regulation's provision in § 438.208(e)(4) pertaining to the protection of enrollee privacy. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We also share commenters' concerns about protecting the privacy of patient information. For this reason, we have retained the provision, now at § 438.208(b)(4), that states that, “* * * in the process of coordinating care, each enrollee's privacy is protected in accordance with the privacy requirements in 45 CFR parts 160 and 164, subparts A and E, to the extent that they are applicable. 
                    </P>
                    <HD SOURCE="HD2">Primary Care and Coordination Program </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that the proposed regulations in § 438.208(e) allowed primary care coordination to be conducted by “a person or entity.” The commenter stated that it is inappropriate to allow MCOs or PHPs to delegate management of an enrollee's health care to an unlicensed or non-credentialed person or entity. The commenter recommended that primary care coordination be performed by a health care professional, as that term is defined in proposed § 438.102. One commenter recommended that CMS should describe in the regulation necessary coordination efforts and include specific references and examples. 
                        <PRTPAGE P="41046"/>
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have retained the wording, “a person or entity” in this final rule to acknowledge that sometimes care coordination might be performed by an organization, such as a Federally Qualified Health Center (FQHC), as opposed to an individual. We have not described in the regulation necessary coordination efforts and specific references and examples because we believe that there are more appropriate vehicles than this regulation for disseminating best practices, reference materials and examples of care coordination. 
                    </P>
                    <HD SOURCE="HD2">Monitoring </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended that CMS: (1) Closely monitor State agency and managed care entity procedures to identify any problems or disruptions in the continued treatment of patients with mental illness, including a substance abuse disorder; (2) provide direction to the State or State agency to facilitate effective solutions; and (3) use CMS resources to assure that continuity and coordination is maintained. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We will closely monitor State agencies and their managed care initiatives to identify any problems or disruptions in the services or treatment of all Medicaid enrollees, including enrollees with special health care needs such as mental illness and/or substance abuse. When deficiencies are found, we typically direct the State agency to undertake solutions and use our resources to assure that the solutions are effective. 
                    </P>
                    <HD SOURCE="HD2">Factors That Hinder Access </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended an addition to MCO/PIHP coordination provisions at proposed § 438.208(e) to require plans to have in effect procedures to address factors, such as lack of transportation, that may hinder enrollee access to health care treatments or regimens. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree with this recommendation. We know that many States and MCOs, PIHPs, and PAHPs in the absence of federal regulations, have in effect procedures to address factors, such as lack of transportation, that may hinder enrollee access to health care treatments or regimens. However, we believe that the extent to which these procedures should be the responsibility of the MCO, PIHP, or PAHP in contrast to the State agency or other agent of the State, is a decision best made by the State agency. 
                    </P>
                    <HD SOURCE="HD2">Maintenance of Health Records </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended that a provision be added to require each MCO and PHP to ensure that its providers have the information necessary for effective and continuous patient care and quality improvement, consistent with certain confidentiality and accuracy requirements. Many commenters also recommended that each MCO and PHP be required to ensure that each provider maintains health records that meet professional standards and that there is appropriate and confidential sharing of information among providers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that both of these issues are already addressed in other sections of the regulation. Section 438.242, 
                        <E T="03">Health Information Systems,</E>
                         requires the MCO and PIHP to maintain a health information system that “collects, analyzes, integrates, and reports data and can achieve the objectives of this subpart” and “ensures that data received from providers is accurate and complete.” We believe that this requirement is a stronger and more effective standard than a requirement that each provider maintain health records that meet professional standards. In addition, § 438.224, 
                        <E T="03">Confidentiality,</E>
                         requires each MCO and PIHP to establish and implement procedures in accordance with confidentiality requirements in 45 CFR parts 160 and 164. We believe these provisions more strongly address confidential sharing of information among providers. 
                    </P>
                    <HD SOURCE="HD3">7. Coverage and Authorization of Services (Proposed § 438.210) </HD>
                    <P>Proposed § 438.210 set forth requirements to ensure that each contract with an MCO or PIHP identifies all services offered under the contract, and that the MCO or PIHP establishes and follows written policies and procedures for processing requests for services in a manner that ensures appropriate beneficiary access to these services. Further, the proposed requirements would ensure that utilization management activities are not structured in a manner that is detrimental to enrollees. These standards implement sections 1932(b)(1) and (b)(4) of the Act.</P>
                    <P>In § 438.210(a) we proposed that the State, in its contracts with MCOs and PIHPs, identify, define, and specify the amount, duration, and scope of all Medicaid benefits that the MCO or PIHP must furnish. Furthermore, the contract must specify what constitutes medically necessary services to the extent they are described in the State plan, and provide that the MCO or PIHP furnish the services in accordance with that provision. We believe that it is important for enrollees and providers to know that the contract includes specific information on all services available under the contract and how the State applies its medical necessity criteria. We also required that the contract be clear on coverage of services related to (1) the prevention, diagnosis, and treatment of health impairments; (2) the ability to achieve age appropriate growth; and (3) the ability to attain, maintain, or regain functional capacity. </P>
                    <P>In § 438.210(b) we required that MCOs and PIHPs, and their subcontractors, have in place and follow written policies and procedures for initial and continuing authorization of services. We also required that MCOs and PIHPs consistently apply review criteria when authorizing services; consult with the requesting provider, when appropriate; and that decisions to deny requests for authorizations, or authorize a service in an amount, duration, or scope that is less than was requested, must be made by a health care professional who has the appropriate clinical expertise in treating the enrollee's condition or disease. </P>
                    <P>In paragraph (c), we proposed that MCO and PIHP contracts provide that written notice of decisions to deny a service authorization request or to authorize the request in an amount, duration, or scope that is less than what was requested be provided to the enrollee and the provider. The notice to the enrollee must be in writing. </P>
                    <P>In paragraph (d), we proposed timeframes for decisions to authorize services. For standard authorization decisions, the notice must be provided as expeditiously as the enrollee's health condition requires and within State-established timeframes that do not exceed 14 calendar days following the request for service. A 14 calendar-day extension would apply at the enrollee's or provider's request or if the MCO or PIHP justifies a need for additional information and how the extension is in the enrollee's interest. We believe that an extension would be in the enrollee's interest when more information is needed for the MCO or PIHP to authorize the service and failure to extend the timeframe would result in a denial of the authorization. </P>
                    <P>For expedited authorization decisions, we proposed that the MCO or PIHP have a maximum of 3 working days after receipt of the request to make a decision. This period could be extended for 14 days under the same circumstances as apply for standard decisions. </P>
                    <P>
                        In proposed § 438.210(e), we required that each MCO and PIHP contract must provide, consistent with § 438.6(g) and § 438.210(a)(2), that compensation to 
                        <PRTPAGE P="41047"/>
                        individuals and entities that conduct utilization management activities not be structured so as to provide incentives to deny, limit, or discontinue medically necessary services to enrollees. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed the opinion that § 438.210 should apply to dental plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter. We decided to extend the provisions of § 438.210 to include PAHPs as well as MCOs and PIHPs because we believe that enrollees of PAHPs need the protections provided under this section. This includes dental plans as well as other PAHPs. We note that the services included in the plans are limited to those provided for under the contract and that the provisions are not always applicable to certain PAHPs, for example, transportation PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended a Federal definition of medical necessity be included in the regulation that includes access to habilitative services. One commenter said that habilitative services are important for children and adults with severe mental impairments. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that the regulation should include a Federal definition of medical necessity. There currently exists no widely accepted national definition and at present States are allowed, under § 440.230(d), to “place appropriate limits on a service based on such criteria as medical necessity or on utilization control procedures,” and have great flexibility in defining those criteria. Therefore, we do not believe it is appropriate to promulgate a national definition. However, we believe it is necessary to provide some specific guidance regarding what State contracts must include. In particular, we believe that whatever a State's fee-for-service Medicaid program uses as medical necessity criteria should not be further restricted by Medicaid MCOs, PIHPs, and PAHPs. Making this clear to all parties should decrease the potential for dispute. If the State's fee-for-service medical necessity criteria address whether a service is needed “to attain, maintain or regain functional capacity,” the regulation requires the contract with the MCO, PIHP, or PAHP to address this as well. We believe this would address the extent to which habilitative services are considered medically necessary. While we are not mandating that specific services must be covered to meet these goals, the contract must clearly address the extent of each MCO's, PIHP's, and PAHP's responsibility to provide such services. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that the words “enrollee's ability to attain, maintain, or regain maximum function * * * could be jeopardized” should be deleted from the definition of medical necessity, as this definition is so broad that it could be applied to nearly all medical necessity determinations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         These words are not part of a definition of medical necessity. Rather, they make clear that State policies related to medical necessity under fee-for-service address any of the items listed in § 438.210(a)(4)(ii), then the State's contract with an MCO, PIHP or PAHP must also address these items. We believe this greater clarity will decrease the potential for disputes, among beneficiaries, the State and MCOs, PIHPs, and PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern that the proposed rule allows MCOs and PIHPs to limit services on the basis of the medical necessity definition and utilization controls. This commenter noted that the EPSDT provision of the Medicaid statute ensures children the full range of needed health care services and recommended specific language in the regulation to ensure this end. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Under § 440.230(d) States already have the authority to “place limits on a service based on such criteria as medical necessity or on utilization control procedures” and have great flexibility in defining those criteria. This provision also applies to services provided through the EPSDT program. 
                    </P>
                    <P>This managed care regulation does not affect any of the pre-existing EPSDT regulations. Furthermore, some States may choose to provide EPSDT services outside of the managed care contract. We believe it is redundant and unnecessary to repeat all existing requirements in this regulation, which focuses on managed care programs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern that an MCO should not be “placed in the middle of a decision” by a provider to deny a service based on “field experience and clinical documentation”. The commenter said that their State has consumer safeguards in place, both in the coverage and authorization process and grievance and appeal process, to protect enrollees. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(b)(4) of the Act requires that MCOs have internal grievance procedures for enrollees. Therefore, we must provide for such a process in the regulation and the MCO or PIHP must approve or disapprove a provider's decision. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked that the notice of action and right to appeal be removed in the case of a physician who denies a request for service, as this is not a realistic requirement and would trigger service continuation requirements. The commenter stated that there is no practical way for an MCO to know that a physician counseled against a medical service. Also, the requirement is unduly burdensome, particularly as it relates to modified requests for service authorizations that are agreed to by the requesting provider. One commenter said that this requirement is inconsistent with industry and Medicaid practice. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We acknowledge that it is difficult for an MCO or PIHP to know when a physician counseled against a service and that it would be burdensome to require physicians to provide notice of denial to enrollees or to inform the MCO or PIHP that a requested service was not provided. To address this issue, in the final rule, at § 438.404(b)(1), we have revised the regulation to specify that the enrollee has the right to appeal a denial by the MCO or PIHP. The physician's decision to provide a service does not trigger an appeal right. This will require the enrollee who wishes to receive a service that the physician will not provide to contact the MCO or PIHP to request approval of the service. A denial of the service at that point by the MCO or PIHP will constitute an action that may be appealed by the enrollee. In response to the comment related to service continuation, we note that services must be continued only if they have been approved in advance by the MCO or PIHP, or by a provider acting on behalf of the MCO or PIHP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked for clarification that § 438.210 applies to provider requests for authorization and not when a beneficiary requests a service that the provider does not find to be medically necessary. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As explained in the previous response, we specify in the final rule that the appeal right is triggered when an action is taken by the MCO or PIHP to deny a requested service or authorize it in an amount, duration, or scope that is less than was requested by the enrollee. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked if the regulation intends to require that a “clinical peer” within the MCO be used to deny a service authorization. If so, the commenter stated that this would impose an additional requirement beyond what is required in State law (which permits any licensed physician to deny an authorization). This would require a significant change in operation for MCOs in that State. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not use the term “clinical peer” to describe the qualifications of the health care 
                        <PRTPAGE P="41048"/>
                        professional who must make a service authorization decision. Rather we say that the health care professional must have “appropriate clinical expertise in treating the enrollee's condition or disease”. We believe that this criterion provides States latitude to specify what clinical experience will be required for individuals making authorization decisions. We also do not specify that the health care professional must be employed by the MCO or PIHP. This permits MCOs and PIHPs to contract for the services of health care professionals if they choose and the State approves. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believes that the standard set by the regulation, that prior authorization decisions be made by a health care professional who has appropriate clinical expertise, is unclear and may lead to unnecessary litigation. The commenter also noted that this standard is not imposed in FFS, nor is this expertise required at a State fair hearing. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that it is important that individuals who make authorization decisions for MCOs and PIHPs have appropriate medical knowledge and clinical experience when making these decisions. This supports the credibility of decisions and may be a factor in the enrollee's decision to appeal. In FFS and State fair hearings the situation is different, but in both cases, professional clinical judgments are available. In FFS, the beneficiary has an option to seek out another provider should a physician not agree to provide requested services. For State fair hearings, beneficiaries may present medical evidence in support of their claims. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested changing “treating” to “assessing” or “evaluating” in regard to the health care professional who must deny or limit a service authorization request. This would allow clinicians some latitude to determine if their level of expertise is appropriate for the review. The State in which the commenter resides holds licensed physician professionals accountable for consulting with appropriate specialists for each decision to deny care. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We continue to believe that the requirement should be that health care professionals have clinical experience in treating the condition or disease under review. As noted above, we believe that the requirement provides some latitude for States to determine what experience is appropriate. We do not think it appropriate for a health care professional without clinical treatment experience to make judgments regarding treatment. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that the lack of a definition of “appropriate” in § 438.210(b)(3) is problematic. This relates to health care professionals with the expertise to deny a service authorization request. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the word “appropriate” conveys a responsibility to the State to specify further criteria to meet the intent of this provision. We do not believe that Federal regulations should provide greater detail as we are not able to address all medical situations or local conditions. We believe this responsibility should rest with the States. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the health care professional denying a request for services should be required to see the patient.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that a health care professional denying a request should be required to see the patient. We include a requirement under § 438.210(b)(2)(ii) that the MCO or PIHP policies and procedures include consultation with the requesting provider, when appropriate. We believe that this requirement will ensure that the MCO or PIHP has the information needed to make an informed decision. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that we add “or who has considered advice from a health care professional with clinical expertise in treating the enrollee's condition or disease” at the end of § 438.210(b)(3). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that it is sufficient for the decision maker to rely on information gained through consultation with a clinical expert. We believe that the decision maker must be capable of rendering a decision based on his or her own expertise. Therefore, we have not revised the regulation as requested by the commenter. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked how we define “standard decisions,” as no definition is provided in the regulation. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A standard decision is one that does not meet the criteria for an expedited decision. These criteria are specified in § 438.210(d)(2) and again at § 438.410(a). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters urged that expedited authorizations be required to be made within 72 hours rather than in 3 working days. A 72-hour standard would ensure that decisions are made in a timeframe consistent with the urgent medical needs of the case. This would also apply to Medicaid enrollees the same protections that apply to other private and public health programs and are consistent with the provision of the patient's bill of rights. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In § 438.210(d)(2), we have retained the maximum timeframe for expedited decisions at 3 working days because this provides a State flexibility to set a timeframe that it believes appropriate while protecting beneficiaries by stipulating a maximum timeframe. The regulation also requires that the decision be made “as expeditiously as the enrollee's health care condition requires.” This provides beneficiaries further protection when a quicker decision is necessary because the timeframes set by the State would seriously jeopardize the enrollee's life or health. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters disagreed with the provision that would allow MCOs and PIHPs to extend the timeframe for expedited authorization decisions by 14 days when the extension is in the interest of the enrollee. The commenters believe that this provision undermines the strength of the shorter timeframe for expedited decisions and lessens the likelihood that the expedited timeframe will be met in practice. They also note that the provision is inconsistent with the Employee Retirement Income Security Act (ERISA) rules governing employer-sponsored groups and the patients' rights legislation supported by the Administration. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We retain the provision that allows the MCO or PIHP to extend the decision period by up to 14 days when the extension is in the best interest of the enrollee. We believe this protects the enrollee in situations in which sufficient information is not available to authorize a service at the end of the 3-day period. Without this provision, the enrollee would be denied the service and would need to appeal the denial to pursue the request. With this provision, the MCO or PIHP can continue to pursue the outstanding information and, ultimately, approve the request, if appropriate. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that the timeframe for authorization should begin when all information necessary to make a decision is received by the MCO and not when the enrollee's request is first denied. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have not accepted this comment because this would require a separate decision that all information needed to make a decision has been received. The authorization decision is generally made when information sufficient to make a decision is reviewed by the deciding health care professional. We believe that it is an important protection for the enrollee that the timeframe begin when the request for service is denied. It also provides an incentive for the MCO or 
                        <PRTPAGE P="41049"/>
                        PIHP to promptly gather information needed for a decision. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that the 14-day extension should not apply when MCOs and PIHPs make late requests for additional information. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It would be difficult to assess when a request for information is late, as the deciding health care professional may find a need for additional information when reviewing the information associated with the request. Therefore, we do not believe that this is an appropriate standard to use. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that the regulation not provide a national timeframe for authorization decisions. Rather, States should be required to set standards based on community norms. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We note that the timeframe provided in the regulation is a maximum timeframe; States may set shorter timeframes if they choose. We continue to believe that it is appropriate to set a maximum national timeframe as an important protection to Medicaid managed care enrollees. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked for a provision to prohibit requests for authorizations from having unnecessary or unduly burdensome information requirements for enrollees or providers. The commenters believe that such a provision is necessary to prohibit MCOs and PIHPs from increasing the “hassle factor” on physicians as a means of cutting costs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         It is not possible or reasonable to regulate against unnecessary or burdensome information requirements. States have other tools to ensure that MCOs and PIHPs with which they contract are not deliberately making it difficult for enrollees to access services. These include monitoring grievances and appeals by enrollees; requirements for adequate provider networks, as providers are unlikely to contract with MCOs or PIHPs that make it difficult for them to provide services; and other monitoring by the State. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters asked that the regulation include a provision to require that MCO and PIHP policies and procedures for decisions on coverage and authorization of services reflect current standards of medical practice. One commenter believes that omission of such a provision suggests that providers would be permitted to have policies and procedures that do not reflect current medical practice standards. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that such a provision is unnecessary as the requirement related to medical necessity will ensure that coverage and authorization decisions reflect current standards of medical practice. The omission of this as a requirement in no way implies that States or CMS sanction or permit practitioners to have policies and procedures contrary to current standards of medical practice. On the contrary, the provision on practice guidelines at § 438.236 requires that MCOs, PIHPs, and PAHPs (where appropriate) adopt and disseminate practice guidelines to their contracting providers to ensure that enrollees' care is consistent with the latest and most effective clinical practices. 
                    </P>
                    <HD SOURCE="HD3">8. Provider Selection (Proposed § 438.214) </HD>
                    <P>Proposed § 438.214 required State Medicaid agencies to ensure that contracted MCOs and PIHPs have written policies and procedures for the selection and retention of providers and a documented process for the initial credentialing and recredentialing of providers. It also required that MCOs and PIHPs not discriminate against providers who serve high-risk populations or specialize in conditions that require costly treatment. Finally, it prohibited MCOs and PIHPs from contracting with providers excluded from participation in Medicare and State health care programs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that language be added under § 438.214(b) to say “state-licensed providers” and add “of primary care, including at a minimum, physicians, psychologists, physician assistants, midwives, and nurse practitioners”. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The definition of provider, at § 400.203, as amended by this regulation, requires that the individual or entity be legally authorized by the State to deliver health care services. Therefore, it is not necessary to say “state-licensed providers.” In addition, it is not necessary to specifically list types of providers, as the definition of provider is broad enough to encompass these types of individuals or entities.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended that we apply the Medicare+Choice credentialing rules to Medicaid MCOs, PIHPs, and PAHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have decided not to apply the Medicare+Choice credentialing rules. Since each State Medicaid managed care program is unique, we do not believe that it would be appropriate to create detailed national standards. The regulation was written to promote State flexibility to manage their programs. However, we agree that there should be a uniform State standard for credentialing and recredentialing and have revised § 438.214(b) to require the State to set this standard policy. These policies and procedures must, at a minimum, include a documented process for credentialing and recredentialing, not discriminate against providers that serve high-risk populations or specialize in conditions that require costly treatment, and may not employ or contract with providers excluded from participation in Federal health care programs. We also revised § 438.214 to apply it to PAHPs, based on general comments requesting that all the provision of subpart D apply to PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed approval of not including specific requirements in the regulation but asked that CMS require States to use a process consistent with the credentialing guidelines of the National Committee on Quality Assurance (NCQA). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have decided not to require States to use a process consistent with NCQA's credentialing guidelines. It is up to each State to decide if they want to use these guidelines. Our regulation only requires MCOs, PIHPs, and PAHPs to implement written policies for the selection and retention of providers. However, we do require that each State set a uniform credentialing policy for all of its MCOs, PIHPs, and PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter seeks clarification that MCOs not be required to credential non-physician providers of licensed health facilities under contract to the plan if the facility itself credentials its providers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not address this level of specificity in the final rule. This provision speaks to the credentialing of providers and does not make a distinction between non-physician and physician providers or who does the credentialing. At a minimum, each MCO, PIHP, and PAHP must follow a documented process for credentialing and recredentialing providers who have signed contracts or participation agreements with the MCO, PIHP, or PAHP. Further, a provider in Medicaid managed care is defined as any individual or entity who is engaged in the delivery of health care services and is legally authorized to do so by the State in which he or she delivers the services. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that in the absence of a credentialing regulation, in many States, providers would set their own standards. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This final rule does not allow individual providers to establish their own credentialing standards. Section 438.214(b) requires States to set uniform credentialing policies and each MCO, PIHP, and PAHP must follow this policy for credentialing providers. 
                        <PRTPAGE P="41050"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed the opinion that a lack of specific credentialing requirements is an open door for States to lower standards for doctors who see Medicaid beneficiaries. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that States will establish lower standards for doctors who serve Medicaid beneficiaries. We allow States the flexibility to determine the credentialing policy that best fits their State's needs. The providers being credentialed must be legally authorized to deliver services in the State. Further, States must ensure that each MCO, PIHP, and PAHP maintains a network of providers that is appropriate to meet the needs of its enrolled population. 
                    </P>
                    <HD SOURCE="HD3">9. Enrollee Information (Proposed § 438.218) </HD>
                    <P>This section provided that the information requirements under § 438.10 are part of a State's quality strategy. We received no comments on this section and have retained it as in the proposed rule. </P>
                    <HD SOURCE="HD3">10. Confidentiality (Proposed § 438.224) </HD>
                    <P>This section of the proposed rule required that States must ensure that MCOs and PIHPs meet the privacy requirements of subpart F of part 431 of this chapter and 45 CFR parts 160 and 164. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters suggested that we strengthen the regulation to make clear that monitoring and oversight do not end with inclusion of contract language. The commenters suggested the addition of the following language “The State must ensure, through its contracts 
                        <E T="03">and by monitoring compliance with those contracts,</E>
                         that etc.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that monitoring and oversight require more than the inclusion of contract language. However, we provide for monitoring and oversight within the regulation. Under § 438.204(b)(3), the State quality strategy must include procedures to regularly monitor and evaluate MCO and PIHP compliance with the contract standards. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked if State confidentiality laws that are stricter than Federal privacy laws will continue to apply. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The Federal privacy laws do not pre-empt State confidentiality laws, to the extent that State laws are stricter. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that the privacy regulation cross referenced in this rule does not take effect until April 14, 2003. Assuming this regulation takes effect prior to that date, the commenter asked whether the privacy rules take effect earlier for Medicaid managed care MCOs and PIHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The privacy rule became effective on April 14, 2001. Most health plans and providers that are covered by the new rule must comply with the new requirements by April 14, 2003. Enforcement of the privacy rule will not occur until April, 2003. This final rule does not alter these dates, nor does it impose privacy requirements in addition to those of the privacy final rule that became effective on April 14, 2001 (65 FR 82462). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters requested that the regulation make clear that the confidentiality provisions extend to minors who seek health services through Medicaid. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.224, as a whole, was intended to ensure that MCOs and PIHPs have procedures to protect the confidentiality of all enrollees. We intend the term “enrollee” to encompass all enrollees, regardless of age. Further, the privacy rule provides all individuals with certain rights with respect to their personal health information, including the right to obtain access to, and request amendment of, health information about themselves. The privacy rule also has specific requirements regarding a minor and the minor's personal representative and their control over the minor's health care information (See 45 CFR 164.502(g)). 
                    </P>
                    <HD SOURCE="HD3">11. Enrollment and Disenrollment (Proposed § 438.226) </HD>
                    <P>This section of the proposed rule provided that each MCO and PIHP contact must comply with the enrollment and disenrollment requirements and limitations set forth in § 438.56. We received no comments on this section and have retained it as proposed. </P>
                    <HD SOURCE="HD3">12. Grievance Systems (Proposed § 438.228) </HD>
                    <P>Proposed § 438.228(a) required that the State ensure through its contracts with MCOs and PIHPs that they have grievance systems that met the requirements of subpart F. Paragraph (b) required States that delegate to the MCO or PIHP responsibility for notifying enrollees of an adverse action to conduct random reviews of the MCO, PIHP, and their providers to ensure that notices are provided in a timely manner. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters urged that the provisions of subpart F on grievances and appeals be applied to PAHPs. They believe that enrollees of these plans should have equal rights to grieve and appeal and that States should have access to data on grievances and appeals to monitor PAHPs for quality. Another commenter said that enrollees of PAHPs should have access to grievances and appeals because managed care, by its nature, includes conflicts of interest between the plans and their enrollees. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that the grievance system required under Federal regulation should apply to PAHPs. The services provided by PAHPs are generally of a much more limited scope than those provided by MCOs and PIHPs. We note that States may extend the grievance system requirements to PAHPs, or may require another grievance and appeals process. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters suggested that the State should be required to review quality of care grievances at the request of the enrollee. Without a provision for quality of care grievances no external record exists of MCOs and PIHPs that consistently fail to adhere to basic quality standards. Another commenter stated his opposition to inclusion of a category of grievance for quality of care. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The final regulation does not include a category of grievance for those related to quality of care. Rather, grievances related to quality of care fall into the general grievance category. We agree that data on grievances and appeals provide States with important information about the quality of care delivered by MCOs and PIHPs. For this reason, in § 438.416, we require that States must require MCOs and PIHPs to maintain records of grievances and appeals and review that information as part of the State quality strategy. While we do not require that States review quality of care grievances, we believe that States are responsive to issues raised by enrollees related to quality and will generally review these grievances when requested. 
                    </P>
                    <HD SOURCE="HD3">13. Subcontractual Relationships and Delegation (Proposed § 438.230) </HD>
                    <P>
                        Proposed § 438.230(a) set forth requirements specifying that an MCO or PIHP that contracts with the State retains full accountability for any activities under its contract that it delegates to a subcontractor. Paragraph (b) required that before an MCO or PIHP delegates responsibility to a subcontractor it must (1) evaluate the prospective contractor's ability to perform the functions to be delegated, and (2) have a written agreement that specifies the activities and report responsibilities of the subcontractor and provides for revoking the delegation or imposing sanctions if the subcontractor's performance is 
                        <PRTPAGE P="41051"/>
                        inadequate. Paragraph (c) required that the MCO or PIHP monitor the performance of the subcontractor and conduct periodic formal reviews on a schedule established by the State. 
                    </P>
                    <P>We received no comments on this section and we have retained § 438.230 as proposed. </P>
                    <HD SOURCE="HD3">14. Practice Guidelines (Proposed § 438.236) </HD>
                    <P>Proposed § 438.236 required that States ensure that each MCO and PIHP adopt practice guidelines that (1) are based on valid and reliable clinical evidence or a consensus of health care professionals in the particular field, (2) consider the needs of the MCO's or PIHP's enrollees, (3) are adopted in consultation with contracting health care professionals, and (4) are reviewed and updated periodically as appropriate. We also proposed that MCOs and PIHPs disseminate the guidelines to all affected providers and, upon request, to enrollees and potential enrollees. Finally, we specified that decisions with respect to utilization management, enrollee education, coverage of services, and other areas to which the guidelines apply must be consistent with the guidelines. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter said that § 438.236 should apply to dental plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter. This section should apply to PAHPs, including dental plans, as well as to MCOs and PIHPs, and we have revised § 438.236 accordingly. We note that the scope of services in the PAHP contract will determine the areas in which practice guidelines are appropriate. For example, dental guidelines would only be appropriate for plans that are responsible for providing dental services. Likewise, a clinical practice guideline is incompatible with transportation services, making this section inapplicable to transportation PAHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter recommended that the regulation require MCOs and PIHPs to use practice guidelines developed and/or endorsed by the American Academy of Pediatrics. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are not specifying what guidelines MCOs and PIHPs must adopt but rather are establishing criteria to be used by MCOs and PIHPs in adopting guidelines. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters objected to the requirement that MCOs and PIHPs adopt practice guidelines. One commenter said that guideline adoption should not be required because nationally accepted standards are not available for all clinical areas, for example, for rehabilitative mental health services. Another commenter objected to this provision because he believes that to require use of clinical practice guidelines substitutes the judgment of CMS, the States, and MCOs and PIHPs for the judgment of health care professionals. Other commenters supported the provision but suggested that reference be made to HIV/AIDS guidelines or that the provision also require the use of clinical review criteria that are directed specifically to meeting the needs of at-risk populations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We continue to believe that States should require MCOs, PIHPs, and PAHPs (where appropriate) to adopt clinical practice guidelines in order to ensure the highest quality of care to enrollees. We are aware that clinical practice guidelines are not available for all areas of clinical practice. However, we believe that it is important to promote the use of guidelines based on clinical evidence. Guidelines are being developed by a variety of organizations in a variety of areas and will increasingly become available for use. This is why we have set criteria for MCOs, PIHPs, and PAHPs to use when adopting guidelines rather than specifying particular guidelines to be used. We do not agree that requiring the use of practice guidelines substitutes the judgement of CMS, States, or health plans for the judgement of health care professionals. Rather, guidelines assist health care professionals to apply the best evidenced-based practice to clinical care. Guidelines are developed to assist the health care professional, not to dictate a specific course of action. We require that MCOs, PIHPs, and PAHPs consult with their contracting health care professionals when adopting practice guidelines to ensure that the health care professionals have input into these decisions. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that the regulation should require MCOs to consult with organizations that develop practice guidelines. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that it is necessary or practical to require MCOs, PIHPs, and PAHPs to consult with organizations that develop practice guidelines. What we believe is important is that the guidelines are valid and reliable, are relevant to the enrollee population, are adopted in consultation with the contracting health care providers, and are reviewed and updated periodically to ensure that they continue to reflect the most recent evidence. Therefore, these are the criteria we specify in the regulation for MCOs, PIHPs, and PAHPs to use when adopting practice guidelines. 
                    </P>
                    <HD SOURCE="HD3">15. Quality Assessment and Performance Improvement Program (Proposed § 438.240) </HD>
                    <P>This section sets forth the State's responsibility to ensure that each MCO and PIHP with which it contracts have in place a quality assessment and performance improvement program for the services it furnishes to Medicaid enrollees. In the NPRM we proposed that States must require that each MCO and PIHP include the following basic elements in its quality assessment and performance improvement program: (1) Conduct performance improvement projects, (2) have in effect mechanisms to detect both underutilization and overutilization of services, and (3) have in effect mechanisms to assess the quality and appropriateness of care furnished to enrollees with special health care needs. </P>
                    <P>In our proposed rule we specified that CMS, in consultation with States, and other stakeholders, may specify standardized quality measures and topics for performance improvement projects to be required by States in their contracts with MCOs and PIHPs. We proposed that MCOs and PIHPs measure performance using standardized measures annually, and implement performance improvement projects that address clinical and non-clinical areas. We also proposed that States review, at least annually, the impact and effectiveness of their quality assessment and performance improvement programs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters supported the quality assessment and performance improvement provisions. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We retain the provisions in § 438.240 in the final rule with certain revisions, discussed below. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter supported the provision that CMS will consult with States and other stakeholders if we decide to exercise our authority to specify quality measures or topics for performance improvement projects that we would require States to include in their contracts with MCOs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe it is important to include all stakeholders in any discussions that would lead to specifying performance measures or topics for performance improvement projects that we would require States to include in their contracts with MCOs and PIHPs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters were concerned that measures identified and developed by CMS, in consultation with States and other stakeholders, would be measures that are not routinely collected nor applicable to the unique circumstances of States and MCOs/
                        <PRTPAGE P="41052"/>
                        PIHPs and that the standardized performance measures would impose additional burden. The commenters suggested this requirement be removed. One commenter agreed that some standardization of performance measures is appropriate but believes the specifications for the measures should be determined by the MCO or PIHP. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We hope that by including all stakeholders in discussions about performance measures that we will reach agreement about measures that are important to a wide range of stakeholders and to CMS. We recognize that each State and MCO and PIHP will have unique program circumstances and that the national measures chosen will not meet all these needs. However, the requirement to use standard measures does not preclude States, MCOs, and PIHPs from also using performance measures that they find useful. We believe we should have the ability to specify standard measures and topics for performance improvement projects to provide comparability across States for some measures and to establish national priority areas for performance improvement projects. Therefore, we retain this provision in the final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters requested that we permit exceptions or deviations from the standard measures required by us. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As we stated in the preamble to the proposed rule, we believe we should have the ability to specify standard measures and that we will be working in consultation with States and other stakeholders to agree upon standard measures. Policy regarding the implementation of the measures, including whether any exceptions should apply, will also be determined in consultation with stakeholders. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters disagreed with our proposal to allow CMS to specify topics for performance improvement projects. One commenter stated that States are in the best position to identify State health priorities and how to allocate their resources and suggested that this provision be removed. Several commenters encouraged us to defer to States in determining the number and type of studies to be performed. One commenter agreed that the identification of standard performance improvement project topics is appropriate but believes that the intervention and measurement specifications should be left up to the MCOs/PIHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in the preamble of the August 2001 proposed rule, we believe that as the art of quality improvement and measurement advances, we should have the ability to specify standard measures and topics for performance improvement projects. We retain this provision in the final rule. As in the proposed rule, in the final rule, we do not specify the number or types of quality improvement projects nor do we specify improvement interventions that MCOs and PIHPs must implement. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters expressed concern that requiring performance improvement projects to achieve demonstrable and sustained improvement is not always feasible. Commenters said that this requirement could have a negative impact on quality improvement activities because it may impact the willingness of MCOs and PIHPs to take on difficult projects. One commenter suggested that the language in this section be changed to reflect that these projects have the goal of achieving demonstrable and sustained improvement as opposed to requiring the projects to achieve this improvement. Another commenter suggested deeming MCOs/PIHPs as having satisfied the quality assurance requirements found in this subpart if the MCO or PIHP is accredited by a private accreditation organization. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters that achieving demonstrable improvement is not always feasible. We have revised § 438.240(b)(1) to require that performance improvement projects be designed to achieve significant improvement sustained over time. This language is consistent with Medicare requirements that define demonstrable improvement as “significant improvement sustained over time.” We plan to address deeming of MCO and PIHP quality initiatives in the EQR final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that we allow States discretion to require demonstrable improvement or not. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As indicated in the response to the previous comment, we are no longer requiring that performance improvement projects achieve demonstrable improvement. We are requiring that these projects be designed to achieve significant improvement sustained over time. States will have the discretion to define what is to be considered significant improvement. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters argued that MCOs and PIHPs should be required to meet minimum performance levels established by the States as part of their quality assessment and performance improvement program. The commenters recommended that this requirement be added under § 438.240(b). One commenter supported that we did not propose to require MCOs and PIHPs to meet minimum performance standards. The commenter argued that it is difficult to identify reasonable performance levels when taking into consideration the variation of local conditions, beneficiaries, and unique program characteristics. This commenter recommended that the provision for standard quality measures be modified to allow States to recommend modification to the standards on a regional or State basis. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that we should require States to establish minimum performance levels that MCOs and PIHPs must meet as an element of the quality assessment and improvement program. States have the option to establish such levels, whether they are State standards or regional standards. We agree that performance measures should be included as an element of the quality assessment and performance improvement program. This was our original intent. We have changed § 438.240(b)(2) to add calculation of performance measures as a basic element of quality assessment and performance improvement programs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that States require that the information obtained from assessments of underutilization and overutilization and of the quality and appropriateness of care to enrollees with special health care needs be reported by age, race, and ethnicity of Medicaid enrollees. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that this regulation should specify that information obtained on underutilization and overutilization of services or the quality and appropriateness of care furnished to enrollees with special health care needs should be reported according to age, race, and ethnicity. We believe that each State should specify how the information should be reported based upon individual State needs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter agreed with the requirement that MCOs and PIHPs annually measure performance using standard measures required by the State and report this information to the State. The commenter believes that this provision maintains MCO and PIHP accountability while providing critical flexibility in the manner in which the requirements are carried out. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter and we have retained the provision in § 438.240(c) of the final rule. We also take this opportunity to clarify that the State performance measures described in § 438.240(c) must 
                        <PRTPAGE P="41053"/>
                        reflect any national performance measures that may be prescribed by the Secretary, consistent with § 438.204(c) and § 438.240(a)(2). 
                    </P>
                    <P>We also have taken the opportunity to recognize an additional approach to producing performance measures that maintains MCO and PIHP accountability while providing flexibility in the manner in which provisions at § 438.240(c) pertaining to performance measurement are met. Specifically, we have been reminded of a practice used by a growing number of States in which State agencies calculate measures of the performance of their MCOs or PIHPs using encounter and claims data transmitted by the MCO or PIHP to the State. We believe this is an acceptable practice that can reduce burden on MCOs and PIHPs, especially when MCOs or PIHPs are already transmitting encounter data to the State. Therefore, we have revised § 438.240(c) to indicate that there are three acceptable ways for States to obtain performance measures for each MCO and PIHP: (1) The MCO or PIHP could calculate the measures according to the States' specifications; (2) the State could calculate the measures using encounter or similar data submitted to the State by the MCO or PIHP; and (3) a State could obtain performance measures using a combination of these two approaches. We authorize States to determine the best approach or approaches to be used in its State, recognizing that a State may decide to use different approaches for individual MCOs or PIHPs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters agreed with the limited detail included in this regulation related to performance improvement projects. The commenters argued that the regulation sufficiently describes Federal standards while allowing States and MCOs and PIHPs the flexibility to develop processes that work best to fit their programs. One commenter requested that we work with MCOs and PIHPs and other stakeholders to develop guidance related to the final regulation that will further explain our expectations for implementing performance improvement projects (for example, challenges inherent in efforts to positively affect quality of care and outcomes given eligibility status, changes of enrollees, small populations, etc.). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We retain § 438.240(d) in our final rule. We have developed guidance for States on implementing performance improvement projects. As part of the development of the EQR regulation, we were statutorily mandated to contract with a national accreditation organization to develop protocols to be used in EQR. We awarded a contract to the Joint Commission on Accreditation of Healthcare Organizations (JCAHO) to develop these protocols. The JCAHO, as part of this effort, convened an expert panel composed of State agencies, MCOs, experts on quality improvement activities, and other stakeholders to provide us feedback on the development of the protocols. Two protocols address performance improvement projects. One protocol provides guidance on how to conduct performance improvement projects and one provides guidance on how to validate performance improvement projects. These protocols can be found on our web site at 
                        <E T="03">http://www.hcfa.gov/medicaid/mceqrhmp.htm.</E>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked us to clarify under § 438.240(d)(2) what is meant by the “new information on quality of care every year” that we are requiring be reported by the MCO or PIHP on each project upon request by the State. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The MCO or PIHP should provide to the State new information from performance improvement projects underway or information on projects that had been initiated since the previous annual report. For example, a project recently initiated by the MCO or PIHP may only be able to describe the topic selected and methodology to be used at the time of the first report. In year two, the intervention may have been implemented, but there may not yet be data to report. In year three, base line data may be collected, and in year four, there may be a repeat measurement. As projects progress, different information will be available to report. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters argued that our final rule should include more specific requirements related to performance improvement projects that include more specificity such as (1) that the MCOs/PIHPs include objective, clearly and unambiguously defined measures based on current clinical knowledge or health services research (2) that the measures measure outcomes such as change in health status, functional status, enrollees satisfaction, or proxies of these outcomes, and (3) that over time, MCOs/PIHPs vary projects to focus on a full spectrum of services rather than repeatedly monitoring areas that are easy to measure and improve. One commenter was concerned that the lack of specificity in the NPRM will result in MCOs and PIHPs developing quality measures that may be irrelevant to patient care and projects that may not protect patients. Another commenter was concerned that the lack of specificity relieves States and MCOs from developing and monitoring performance measures for specific conditions such as mental illness and other severe disabilities. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that this regulation should provide more detail on performance improvement projects or on the indicators used to measure performance. We believe the final regulation creates a balance between an appropriate amount of detail needed to ensure that States implement interventions to improve quality, while at the same time, provides States with the flexibility to determine the measures and levels they want to require of their contracting MCOs and PIHPs. We believe that States and MCOs and PIHPs will use performance measures and performance improvement projects that reflect important areas. These activities are costly and time-consuming and we believe that States and MCOs/PIHPs will target the investments in financial and staffing resources required for these activities to topics that will benefit from program improvement. 
                    </P>
                    <P>Section 438.240 requires, as a basic element of a quality assessment and performance improvement program, that MCOs and PIHPs have in effect mechanisms to assess the quality and appropriateness of care furnished to enrollees with special health care needs. This includes beneficiaries with conditions such as mental illness and other severe disabilities. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters argued that MCOs and PHPs should be required to conduct performance improvement projects on topics specified by the State and that MCOs and PIHPs should be required to participate in at least one statewide project. The commenters recommended that we incorporate these requirements in our final rule. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that this rule should require that States have their MCOs and PIHPs participate in statewide projects. We reserve the right to set performance improvement project topics in the future as specified in § 438.240(a)(2). A State, at its discretion, however, may choose to specify topics for MCOs or PIHPs improvement projects or to mandate participation in statewide projects. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter encouraged us to recognize the long-term nature of quality initiatives, that improvement in quality is incremental. The commenter was concerned that the short-term commitment to initiatives that is usually the perspective of States does not provide a paradigm for studying and understanding what works in managed care. The commenter argued 
                        <PRTPAGE P="41054"/>
                        that quality initiatives should not change capriciously from year to year. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter and acknowledge that quality improvement initiatives need a sufficient amount of time to be implemented and for findings to be determined. We do not prescribe the duration in which performance improvement projects must be completed. We only require that a project be completed in a reasonable time period and that information be provided on the project's progress annually. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked for clarification on how the program review by States will be coordinated with the EQR regulations. Several commenters suggested that we coordinate these efforts to avoid duplication of efforts. For example, one commenter suggested that we permit MCOs and PIHPs that are certified by an accreditation agency or who are reviewed by another State agency to be exempt from Medicaid reviews and EQR. One commenter suggested that we provide a cross reference to the EQR regulation and that we provide States sufficient discretion to define and modify their external review activities. Another commenter suggested that we amend the regulation to allow a State to use the EQR to meet the program review by the State requirements under § 438.240(e). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States at their option may use EQR findings to meet the program review requirements under § 438.240(e)(1). The final EQR rule addresses the circumstances under which an MCO or PIHP may be exempt from quality initiatives and what types of quality initiatives we consider to be EQR activities. We are not providing a cross reference to the EQR provisions or amending this rule to stipulate that EQR can be used to meet this requirement. We are providing States with the flexibility to decide if they want to use EQR or some other activity to meet these requirements. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter agreed with the requirement that States review the MCO's and PIHP's performance on standard measures on which MCOs and PIHPs are required to report. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In the final rule, we retain § 438.240(e)(1) as proposed. 
                    </P>
                    <HD SOURCE="HD3">16. Health Information Systems (Proposed § 438.242) </HD>
                    <P>Section 1932(c)(1)(iii) of the Act requires States that contract with MCOs to develop a quality assessment and improvement strategy that includes procedures for monitoring and evaluating the quality and appropriateness of care and services to enrollees. It also provides that MCOs provide quality assurance data to the State using the data and information set specified by the Secretary for the Medicare+Choice program or other data specified by the Secretary in consultation with States. Section 438.242 proposed that States require that MCOs and PIHPs have health information systems sufficient to provide data to States and CMS. </P>
                    <P>Paragraph (a) required that States must ensure that MCOs and PIHPs maintain data systems that collect, analyze, integrate, and report data to achieve the objectives of subpart D. It required that the system must provide information on utilization, grievances, and disenrollments (other than those that result from ineligibility for Medicaid). Paragraph (b) provided that the State must require MCOs and PIHPs to collect data on enrollee and provider characteristics and on services furnished to enrollees, and to ensure the accuracy and completeness of data received from providers by (1) verifying its accuracy and completeness; (2) screening the data for completeness, logic, and consistency; and (3) collecting service information in standard formats to the extent feasible and appropriate. </P>
                    <P>Paragraph(c) required MCOs and PIHPs to make all data available, as required in this subpart, to the State and, on request, to CMS. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter urged CMS to establish national data collection standards for collection of encounter data, EPSDT information, and network information by States, using standards established under the Health Insurance Portability and Accountability Act (HIPAA) where possible. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree that CMS should establish national data collection standards as part of this regulation. Under HIPAA, the Secretary is establishing standards for the electronic transfer of health data, including encounter data. The HIPAA regulations also specify the entities to which the standards apply. Medicaid MCOs and PIHPs, as well as State Medicaid agencies, will need to comply with the HIPAA regulations to the extent they apply. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that MCO and PIHPs can only supply data to States to the extent they are provided data by providers. This commenter suggested that this regulation require that providers give data to health plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This regulation is directed to States and, by placing requirements on States for their contracts with MCOs, PIHPs, PAHPs, and PCCMs, on these other entities. The regulation does not address the relationships of MCOs and PIHPs and their providers. Therefore, we are not including a provision to require data reporting by providers. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that it is important for States to negotiate price discounts with hardware and software vendors that can be passed on to providers and to develop guidance materials for practices preparing to install hardware and software. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States are in the best position to identify means to assist providers with the electronic submission of data. We do not believe that this issue should be addressed in Federal regulations. We revised § 438.242(a) by adding the words “and appeals” after “grievances”. This change was made to be consistent with § 438.416, which requires States to review information collected by MCOs and PIHPs as part of the State quality strategy. 
                    </P>
                    <HD SOURCE="HD2">E. Grievance System (Subpart F) </HD>
                    <P>Proposed subpart F is based on section 1902(a)(3) of the Act, (which requires a State plan to provide an opportunity for a fair hearing to any person whose request for assistance is denied or not acted upon promptly), section 1902(a)(4) of the Act, (which authorizes the Secretary to specify methods of administration that are “necessary” for “proper and efficient administration”), and section 1932(b)(4) of the Act, (which requires that MCOs have an internal grievance procedure under which a Medicaid enrollee, or a provider on behalf of an enrollee, may challenge the denial of coverage of, or payment by, the MCO). </P>
                    <P>In this subpart, we proposed regulations that lay out the elements of the grievance system required under section 1932(b)(4) of the Act, and how it interfaces with the State fair hearing requirements in section 1902(a)(3). We defined terms, described what constitutes a notice of action, and addressed how grievances and appeals must be handled, including timeframes for taking action. We included a process for expedited resolution of appeals in specific circumstances; addressed the requirement for continuation of benefits; and laid out the requirements relating to record keeping, monitoring and effectuation of reversed appeal resolutions. </P>
                    <P>
                        We proposed conforming amendments to part 431 to reflect changes in terminology and other new provisions enacted in the BBA. We also made conforming changes to the fair hearing regulations in subpart E of part 
                        <PRTPAGE P="41055"/>
                        431, to reflect the MCO grievance and appeals process in subpart F of part 438. We note that we revised § 431.244(f)(3) to require State approval for direct access to an expedited State fair hearing for MCO and PIHP enrollees. Due to the close relationship of the subject matter with subpart F, comments and responses regarding part 431 are addressed in this subpart. 
                    </P>
                    <HD SOURCE="HD3">1. Statutory Basis and Definitions (Proposed § 438.400) </HD>
                    <P>Definitions of terms used in proposed subpart F are found in proposed § 438.400 and have the following meanings: </P>
                    <P>
                        <E T="03">Action</E>
                         means, in the case of an MCO or PIHP or any of its providers, 
                    </P>
                    <P>• The denial or limited authorization of a requested service, including the type or level of service; </P>
                    <P>• The reduction, suspension, or termination of a previously authorized service; </P>
                    <P>• The denial, in whole or in part, of payment for a service; or </P>
                    <P>• For a resident of a rural area with only one MCO or PIHP, the denial of a Medicaid enrollee's request to exercise his or her right to obtain services outside the network. </P>
                    <P>
                        <E T="03">Appeal</E>
                         means a request for review of an action, as “action” is defined in this subpart. 
                    </P>
                    <P>
                        <E T="03">Grievance</E>
                         is defined as an expression of dissatisfaction about any matter other than an action. This term can also be used to refer to the overall system that includes grievances and appeals handled at the MCO or PIHP level and access to the State fair hearing Process. Possible subjects for grievances include, but are not limited to, the quality of care or services provided, aspects of interpersonal relationships such as rudeness of a provider or employee, or failure to respect the enrollee's rights. 
                    </P>
                    <P>Proposed § 438.400 contained the definition of a “governing body.” We, however, had not proposed regulatory requirements for a governing body. Therefore, we are removing the definition of a governing body in the final rule. </P>
                    <P>We received the following comments on these definitions. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter felt that having several potentially conflicting Federal statutes and State laws related to a health care plan's grievance system is troubling for the plans. They asked that, if a Patients' Bill of Rights is enacted, CMS review the provisions of this regulation to make it consistent with the mandate under that legislation, as well as ERISA rules. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter. If a Patients' Bill of Rights is enacted, we of course would be required to conform to the new statute if it applied to Medicaid, but even if it did not, we would review the provisions and consider making changes if it is appropriate for the Medicaid program. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters believe that the definition of “action” must include the failure to furnish services in a timely manner, the failure to resolve an appeal in a timely manner, or the denial of an enrollee's request to disenroll. They argued that if a plan delays furnishing services or adjudicating a claim in a timely manner, no “action” is triggered. Therefore, the enrollee would be denied his or her right under section 1902(a)(3) to a fair hearing if a claim medical assistance is “not acted upon with reasonable promptness.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that section 1902(a)(3) of the Act requires access to a State fair hearing for those requests not acted upon in a timely manner, and therefore, in § 438.400(b) we have modified the definition of “action” to include unreasonable delays in services, or appeals not acted upon within the timeframes provided in § 438.408(b). However, we disagree that a denial of a request to disenroll constitutes an “action,” as it addresses an issue separate from those specific denials, limitations, reductions, or suspensions of services that trigger fair hearing requirements. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters believe that the grievance and appeals provisions should apply to PAHPs as well as to MCOs and PIHPs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that PAHP enrollees should have the right to appeal denials, but believe that direct access to the existing fee-for-service fair hearing process is the more appropriate vehicle for this in the case of PAHPs. Therefore, in response to this comment, we have revised the fair hearing regulations in subpart E of part 431 to expressly reference PAHP enrollees as having a right to a fair hearing under those provisions in the case of an “action.” In general, we believe that the State should decide how best to address grievances involving PAHPs that do not involve an action, since they are often individual physicians or small group practices and cannot be expected to have the administrative structure to support a grievance process. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters disagreed that the independent professional judgment of providers should automatically trigger an action in the same manner as a denial from an MCO or PIHP. They believed that it is sometimes impossible for the MCO or PIHP to know when a provider has denied a service, or offered an alternative form of treatment that may or may not be a denial. They requested that providers be removed from the “action” definition. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters. Since a provider is making independent professional judgments as to the care and treatment of enrollees, his or her denial of a particular request, or the suggestion of an alternative should not automatically trigger a formal notice of appeal rights from the MCO or PIHP. We have removed “or any of its providers” from the definition of an “action.” However, anytime an enrollee challenges the decision of a provider to the MCO or PIHP, an action is triggered if the MCO or PIHP affirms the provider's decision, triggering a notice from the MCO or PIHP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters wanted the regulations to provide expressly for a “quality of care” grievance in cases in which the enrollee believed that any aspect of his or her care was substandard, or could have caused them harm. These commenters recommended that the State be required to review any such “quality” grievance that was not disposed of to the enrollee's satisfaction. Some commenters wanted these grievances to be reviewable by a State fair hearing. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that those enrollee complaints not meeting the standard of an appeal should be treated uniformly under Federal statute. The definition of “grievance” includes “quality of care” and it should be up to the State to decide whether or not a review, or a mechanism allowing State review, is necessary. We also believe that an enrollee only has the right to a State fair hearing under section 1902(a)(3) in cases that involve an “action,” since section 1902(a)(3) refers to a denial of medical assistance, or a case in which a claim for assistance is “not acted upon,” and not a case in which there are concerns about the quality of the assistance. We believe that the quality assurance requirements in subpart D of part 438 address the commenter's concerns. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter felt that appeal rights should be extended to providers in managed care systems. They argued that this is notable considering the appeal rights extended to MCOs in the right to pre-termination hearings. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The grievance and appeal rights in this subpart implement statutory provisions that grant rights to Medicaid beneficiaries, not providers. The right to a fair hearing in section 1902(a)(3) applies to an “individual” whose claim for medical assistance is 
                        <PRTPAGE P="41056"/>
                        denied or not acted upon. The statutory requirement in section 1932(b)(4) that MCOs have grievance procedures similarly applies to “an enrollee* * *or a provider 
                        <E T="03">on behalf of an enrollee.</E>
                         * * *” (Emphasis added.) While it is true that the statute provides for the right to a hearing before an MCO contract is terminated, there is no statutory provision for an appeal right for providers subcontracting with managed care plans. While States are free to provide such rights, and information must be provided about such rights where they exist (see section A. above), there are no such rights under Federal statute. We defer to congressional intent on this issue, and have not provided for any subcontracting provider appeal rights in this final rule. 
                    </P>
                    <HD SOURCE="HD3">2. General Requirements (Proposed § 438.402) </HD>
                    <P>Proposed § 438.402 required each MCO and PIHP to have a grievance system in place for enrollees that includes a grievance process, an appeal process, and access to the State's fair hearing system. </P>
                    <P>Proposed § 438.402(b)(1) specified that an enrollee may file a grievance or an MCO or PIHP level appeal, and may request a State fair hearing. In addition, as provided in section 1932(b)(4), the proposed rule provides that a provider, acting on behalf of an enrollee (with the enrollee's written consent) may file an appeal of a “denial of coverage of or payment for” assistance, or an “action.” However, under proposed § 438.402(b)(1)(ii), the provider could not file a grievance or request a State fair hearing on behalf of the enrollee. </P>
                    <P>Under § 438.402(b)(2), we proposed timeframes within which the enrollee or provider (on the enrollee's behalf) may file an appeal. Our intent was to mirror the filing timeframes for a State fair hearing, that is, a reasonable amount of time up to 90 days. In addition, we incorporated the longstanding policy at section 2901.3 of the State Medicaid Manual that beneficiaries be given a minimum of 20 days to file an appeal. We believe that this policy gives beneficiaries a reasonable amount of time to file an appeal. Therefore, the proposed regulation required that the State specifies a timeframe for filing an appeal that is no less than 20 days or more than 90 days from the date of the MCO's or PIHP's notice of action. Within this timeframe, the enrollee (or the provider on his or her behalf) may file an appeal, and in a State that does not require exhaustion of the MCO and PIHP level appeals, the enrollee may request a State fair hearing. </P>
                    <P>In proposed § 438.402(b)(3), we specified the manner in which enrollees may file grievances, and enrollees (or a provider on the enrollee's behalf) may file an appeal. For grievances, the enrollee may file either orally or in writing, either with the State or the MCO or PIHP, as determined by the State. The enrollee (or the provider on the enrollee's behalf) was permitted to file an appeal either orally or in writing, and unless he or she requests expedited resolution, was required to follow an oral filing with a written, signed, appeal. While enrollees were permitted to start the appeal clock with an oral request, under the proposed rule, they were required under the proposed rule to follow it with a written request, as we determined that a written appeal best documents the issue being appealed. In expedited situations, the proposed rule provided that the enrollee was not required to put the appeal in writing. </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters believed that permitting States to require the exhaustion of internal MCO or PIHP appeals procedures was unwarranted, and favored appeal rights administered by a state agency using the Federal fair hearing regulations. Other commenters believed that since MCOs are responsible for coordinating care and making coverage decisions, enrollees should be required to utilize their internal appeals process first before filing for a State fair hearing. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with both sets of commenters. With respect to the commenters opposing an internal grievance procedure, section 1932(b)(4) actually requires that such a procedure be available, and that enrollees be permitted to “challenge” a “denial of coverage of, or payment for” services under such procedures. Thus, using exclusively a State administered fair hearing mechanism was not even an option under the law. Furthermore, providing for an MCO/PIHP level of review is consistent with the appeals rules under the Medicare+Choice program, and most versions of Patients Bill of Rights legislation. We believe that as long as the timeframes and notice requirements conform with what is allowed under direct access, an internal system is a proper and efficient way to adjudicate appeals. However, we also believe that the State should have full discretion when it comes to whether to require the utilization of the required internal appeals process, or permit direct access to State fair hearing. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters found that the word “grievance,” referring to the overall system as well as a particular avenue of adjudication, is inherently confusing. They recommended changing “grievance system” to something such as the “dispute resolution process” or “complaint process.” Others felt that the definition was too broad, triggering rights where a different avenue for resolution would make more sense. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we refer to the overall process as the “grievance system,” States are free to call it by any name they prefer. We chose “grievance system” over terms such as “dispute resolution process” or “complaint process” because this is the term used in section 1932(b)(4), and the other terms suggested by the commenters were too informal. To some people, “complaint” conjures up ideas of more trivial matters, while “dispute resolution” is sometimes associated with arbitration, which connotes a less strict standard than we wanted to convey. While we based our reference to the overall system on the reference to “an internal grievance procedure” in section 1932(b)(4), our use of the term “grievance” to refer to disputes not resulting from an “action” tracks the approach in the Medicare+Choice regulations, and is based on the broad connotations of the word grievance to capture a variety of types of complaints. We believe that the timeframes and other administrative requirements in this final rule provide sufficient State flexibility to not be a burden on the grievance system. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters recommended additional general requirements for the grievance system. These recommendations included specific terms in the regulations requiring: (1) That all processes, policies, and procedures meet the conditions set forth in this subpart; (2) a State's written approval of an MCO's or PHP's policies and procedures before implementation; (3) a governing body responsible for effective operation of the system including disposing of grievances and resolving appeals; (4) assurance that punitive action is neither threatened nor taken against a provider who requests or supports a grievance or appeal; (5) acceptance of grievances and appeals from the enrollee or his or her representative; (6) the provision of information required under this subpart, (7) the referral to the State of quality of care grievances in which the enrollee is dissatisfied; and (8) that providers be required to give notice in accordance with § 438.404(d). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that many of the above suggested requirements are already addressed in this final rule, either directly or implicitly. For example, we believe that while it would be clear without any explicit statement that grievance processes, policies and 
                        <PRTPAGE P="41057"/>
                        procedures must be consistent with the regulatory requirements in part F, § 438.228 already expressly requires States to ensure, through its contracts, that MCOs and PIHPs have grievance systems that satisfy the requirements of this subpart. This includes the requirement on States to conduct random reviews of MCOs and PIHPs to ensure that they are notifying enrollees in a timely manner. The acceptance of appeals and grievances from the enrollee or a representative is similarly already provided for, as is the requirement, in § 438.10, for provision of information on appeals. We have addressed in section A of this preamble the commenters' suggestion for an assurance of no punitive action for requesting an appeal. Most of the other suggestions above would in our view most appropriately be addressed by the States without further Federal regulation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters believed that a State should not be permitted to establish a deadline for appealing an adverse action that is less than 30 days, even though shorter periods are now permissible in the fee-for-service Medicaid program. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in the introduction, our intent was to mirror the filing timeframes for the State fair hearing; that is, a reasonable amount of time up to 90 days. In addition, we incorporated the longstanding policy at § 2901.3 of the State Medicaid Manual that beneficiaries be given a minimum of 20 days to file an appeal. We believe that this policy gives beneficiaries a reasonable amount of time to file an appeal, while providing States with the flexibility to tailor those timeframes to their particular internal and State procedures. Therefore, we will retain the requirement that the State specify a timeframe for filing an appeal that is no less than 20 days and does not exceed 90 days from the date of the MCO's or PIHP's notice of action. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter objected to the fact that the proposed rule would allow providers, with written consent, to file an appeal on behalf of the enrollee, but prohibit providers from acting as an authorized representative for grievances or State fair hearings. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As noted in section E. 1. above, we have limited the right to request a fair hearing, and the right to appeal a denial of coverage, to enrollees, and to providers on behalf of enrollees, in deference to our interpretation of congressional intent. In the case of grievances, since these are likely to involve a provider, we have limited the right to file a grievance to an enrollee. The commenter, however, correctly notes that we have not just denied a provider the 
                        <E T="03">right</E>
                         to file a grievance or fair hearing request on behalf of an enrollee, but have affirmatively 
                        <E T="03">prohibited</E>
                         providers from doing so, through the second sentence in proposed § 438.402(b)(1)(ii). In considering this comment, we have determined that we do not wish to prohibit providers from acting as authorized representatives for grievances, appeals and state fair hearings, if the State wishes to provide them with this right. Since the current prohibition would pre-empt a State law to the contrary, we are, in response to this comment, changing the second sentence in proposed § 438.402(b)(1)(ii) to read, “A provider may file a grievance or fair hearing request on behalf of an enrollee if the State permits the provider to act as the enrollee's authorized representative in doing so.” 
                    </P>
                    <HD SOURCE="HD3">3. Notice of Action (Proposed § 438.404) </HD>
                    <P>Under the proposed rule, the notice MCOs and PIHPs are required to provide to enrollees under proposed § 438.404 would be the first step in the grievance system. It would serve as the enrollee's first formal indication that the MCO or PIHP will or has taken action, such as denying payment or denying, limiting, reducing, suspending or terminating a service through a service authorization decision. We proposed in § 438.404(a) that the notice meet the language and format requirements of proposed § 438.10(c) and (d) of this chapter to ensure ease of understanding. The notice must include the elements that are listed in proposed § 438.404(b), as follows: </P>
                    <P>• The action the MCO or PIHP or its contractor has taken or intends to take. </P>
                    <P>• The reasons for the action. </P>
                    <P>• The enrollee's or the provider's right to file an MCO or PIHP appeal. </P>
                    <P>• If the State does not require the enrollee to exhaust the MCO or PIHP level appeal procedures, the enrollee's right to request a State fair hearing. </P>
                    <P>• The procedures for exercising the rights specified in this section. </P>
                    <P>• The circumstances under which expedited resolution of an appeal is available, and how to request it. </P>
                    <P>• The enrollee's right to have benefits continue pending resolution of the appeal, how to request that benefits be continued, and the circumstances under which the enrollee may be required to pay the costs of these services. </P>
                    <P>In proposed § 438.404(c), we specified the timeframes in which the MCO and PIHP must mail the notices. Under proposed § 438.404(c)(1), timeframes for notices for the reduction, suspension, or termination of previously authorized services are governed by the State fair hearing regulations found in 42 CFR part 431, subpart E. While some MCOs and PIHPs may find the advance notice requirement inappropriate, there are exceptions to advance notice that allow notice to be given on the date of the action (see § 431.213). These exceptions would cover the situation in which a provider believes an immediate change in care is appropriate for the health condition of the enrollee. For denial of payment, we required in proposed § 438.404(c)(2) that notice be given at the time of any action affecting the claim. Proposed § 438.404(c)(3) and (c)(4) required that for standard service authorization decisions that deny or limit services, notice must be given within the timeframes specified in § 438.210(d). Further, if the MCO or PIHP were to extend the timeframe in accordance with proposed § 438.210(d), it would have to give the enrollee written notice of the reason for the decision to extend the timeframe, inform the enrollee of the right to file a grievance if he or she disagrees with that decision, and issue and carry out its determination as expeditiously as the enrollee's health conditions requires and no later than the date the extension expires. In situations in which the service authorization decision is not reached within specified timeframes, and the failure to authorize a decision constitutes an adverse decision, we proposed at § 438.404(c)(5) that notice be mailed on the date that the timeframe for authorizing services expires without an authorization decision being made. Finally, for expedited service authorization decisions, under the proposed rule notice had to be given within the timeframes specified in proposed § 438.210(e) (recodified in this final rule at § 438.210(d)). </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believed that a strict application of the proposed notice requirement would be burdensome, especially if applied to decisions of primary care physicians (PCPs) made without involvement of the MCO or PHP. Commenters also asked that CMS distinguish between claims that involve liability where the enrollee is actually billed, versus where there is no actual payment liability. Some commenters contended that MCOs and PIHPs do not always know when their providers deny services, making it difficult for them to comply with the notice requirements. Another commenter was concerned with § 438.404(b)(1) requiring a notice to explain the action the MCO or PIHP or its contractor has taken or intends to take. They felt that “contractor” could 
                        <PRTPAGE P="41058"/>
                        be read as being a provider. They requested clarification. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters that a provider, using his or her professional judgement in making a determination of medical necessity, should not trigger a notice by reason of recommending against or preferring an alternative to a particular treatment. As discussed above, in response to comments received (including this comment), we have removed the word “provider” from the definition of “action” triggering notice obligations and appeal rights. As used in § 438.404(b)(1), a “contractor” would not include a provider, but rather any entity in which an MCO or PIHP delegated this particular authority/responsibility. However, an enrollee retains the right to request that the MCO or PIHP provide a particular service against the advice of a provider, triggering the requirement of a notice from that MCO or PIHP if the request results in a denial, reduction, or suspension. We disagree that notice rights are triggered only when a beneficiary is actually held liable for a particular claim. An action that may include a claim arising from a third party (such as, a hospital) because an MCO or PIHP refused to pay the claim. Even though the hospital may choose not to bill the beneficiary, a denial for payment of a service has occurred, triggering a notice to the beneficiary that the claim was denied. This ensures that a beneficiary is made aware of his or her appeal rights in case they are billed by a third party. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters noted that they do not believe that the expiration of an approved number of visits should be considered a termination. They noted that the enrollee is free to request that the service be continued, but that this request should be treated as a new request for a service. Other commenters expressed the opposite view; they believe that re-authorization of a service at a lower level than previously received, or a denial of re-authorization, is a termination or reduction of the service and should require notice and the continuation of benefits pending appeal.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the first set of commenters that the expiration of an approved number of visits does not constitute a termination for purposes of notice and continuation of benefits. Likewise, when a prescription (including refills) runs out and the enrollee requests another prescription, this is a new request not a termination of benefits. In these circumstances, the MCO or PIHP would not need to send a notice or continue benefits pending the outcome of an appeal or State fair hearing. If the enrollee requests a re-authorization that the MCO or PIHP denies, the MCO or PIHP must treat this request as a new request for service authorization and provide notice of the denial or limitation. We disagree with the second commenters that a denial of authorization for additional days is a “termination,” since the enrollee had no expectation of coverage on those days, and this was thus simply a denial of a new request, not a termination of services the enrollee had a right to expect to continue. 
                    </P>
                    <P>
                        We believe that the proposed rule already clearly reflected the above interpretation. In the definition of “Action,” the reference to a “reduction, suspension, or termination” in the proposed rule was qualified by the phrase, “of a previously authorized service.” Thus, the cessation of services because the authorization expired would not be an “action,” because services after the date when the authorization expired would not be “previously authorized.” In proposed § 438.404(c)(1), the reference to timeframes for a notice of a “termination, suspension, or reduction” was similarly qualified by “of previously authorized Medicaid-covered services.” In proposed § 438.420(b), specifically governing the continuation of services, the right to continued benefits is expressly conditioned on the “[t]he appeal involv[ing] the termination, suspension, or reduction of a previously authorized course of treatment.” Again, we believe it is clear that if additional days were not authorized, ending treatment as provided in the original authorization would not constitute a termination triggering the right to continued benefits. We have made one change in this rule in response to this comment, however. In a case in which services which 
                        <E T="03">were</E>
                         “previously authorized” are continued or reinstated at the request of the enrollee pending appeal, and during this continuation period, the period of authorization expires, services may be terminated as provided in the original authorization. We have added a new § 438.420(c)(4) to make this clear. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter believed that CMS underestimated the true burden associated with MCO and PIHP notices, suggesting that it is closer to 20 minutes than 30 seconds per notice. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We address this issue under the Collection of Information Requirements section of this preamble. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received many comments regarding the elements of a notice. Several commenters suggested that the written notice requirements of proposed § 434.404 be modified to mirror the existing State fair hearing regulations. Other commenters did not believe that there were sufficient protections in place to ensure that enrollees not only have rights, but have effective notice of those rights. These other commenters recommended additional requirements addressing the right to request a State fair hearing, the right to present evidence, how to contact the MCO or PHP for assistance, how to obtain copies of enrollee records, the right of an enrollee to represent himself or herself or use counsel, and the right to be free from any negative impact from having filed an appeal. Several commenters were concerned that while oral requests for standard appeals must be followed up in writing, there was no requirement that enrollees be told this in the notice. They wanted to see this added. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that information given by MCOs and PIHPs should generally contain the information required by the State fair hearing notices. However, the provision of most of this information is required under the information requirements in § 438.10(g)(1) and the content requirements for a notice in § 438.404. These requirements will ensure that enrollees are informed, for example, that an oral request for a standard appeal will not be pursued unless it is followed up in writing, of the enrollee's right to a hearing, the method for having a hearing, and circumstances surrounding continuation of benefits, if applicable. We have previously addressed the comment on language concerning negative actions by an MCO or PIHP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that § 438.404(c)(6) included an incorrect reference. The reference to § 438.210(e) should read “§ 438.210(d).” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter. We have made the appropriate change in § 438.404(c)(6) by correcting the cross reference to read § 438.210(d). 
                    </P>
                    <HD SOURCE="HD3">4. Handling of Grievances and Appeals (Proposed § 438.406) </HD>
                    <P>Section 438.406 proposed to set forth how grievances and appeals must be handled. The general requirement for handling grievances and appeals would require MCOs and PIHPs to do the following: </P>
                    <P>• Give enrollees any reasonable assistance in completing forms and taking other procedural steps. </P>
                    <P>• Acknowledge receipt of each grievance and appeal. </P>
                    <P>
                        • Ensure that individuals who make decisions on grievances and appeals are 
                        <PRTPAGE P="41059"/>
                        individuals who were not involved in any previous level of review or decision making and who, if deciding an appeal of a denial that is based on lack of medical necessity, a grievance regarding denial of expedited resolution of an appeal, or a grievance or appeal that involves clinical issues, are health care professionals who have the appropriate clinical expertise in treating the enrollee's condition or disease. 
                    </P>
                    <P>We would require the MCO and PIHP, at proposed § 438.406(a)(1), that the “reasonable assistance” provided to enrollees include interpreter services and toll free numbers that have adequate TTY/TTD and interpreter capability. By including these as examples of types of assistance required to meet certain needs, we did not intend that other reasonable assistance need not be given. We believe, for example, that MCOs and PIHPs are required by this provision to provide reasonable assistance to meet other needs of enrollees, and assisting enrollees who have low-literacy abilities. </P>
                    <P>Proposed § 438.406(b) specified the following requirements that the appeals process would have to meet: </P>
                    <P>• Provide that oral inquiries seeking to appeal an action are treated as appeals and must be confirmed in writing, unless the enrollee or the provider requests expedited resolution. This is required in order to establish the earliest possible filing date for the appeal. </P>
                    <P>• Provide the enrollee a reasonable opportunity to present evidence, and allegations of fact or law, in person as well as in writing. </P>
                    <P>• Provide the enroll and his or her representative the opportunity, before and during the appeals process, to examine the enrollee's case file, including medical records, and any other documents and records considered during the appeals process. </P>
                    <P>• Include, as parties to the appeal, the enrollee and his or her representative or the legal representative of a deceased enrollee's estate. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was unclear whether the proposed rule permitted conducting State fair hearings using a video-conferencing system. The commenter noted that many states now use this technology, with videoconference facilities in numerous locations. Multiple sites can be linked to make it more convenient for all parties to participate in the hearing, reducing travel costs, and conserving time. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Nothing in the statute or regulation prevents MCOs, PIHPs, or States from using videoconferencing equipment as long as they adhere to the evidentiary rules described in parts 431 and 438. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended that CMS establish more general standards regarding the qualifications of hearings officers. Commenters were concerned with the burden of finding providers with clinical expertise for a voluminous number of cases. They requested that it be permissible to either use physicians or other types of providers with appropriate clinical expertise. Other commenters recommended being more specific in linking certain cases to a particular area of expertise. For example, one commenter wanted language ensuring that all grievances and appeals involving care to a child be reviewed by pediatricians and pediatric specialists. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that it is important for adjudicators to have clinical training appropriate for the case in which they are presiding. However, we are leaving the definition of “appropriate clinical expertise” to be defined by the States. This allows States to decide what clinical expertise level is necessary to fit its particular appeals process and volume of cases. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters suggested adding “but not limited to” to § 438.406(a)(1) where it includes examples of enrollee assistance with grievance and appeals procedures. They believed that this addition would make the language of the regulation comport with the expressed intent of CMS. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters, and in response to this comment, we have added “but is not limited to” in § 438.406(a)(1). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters urged CMS to require MCOs and PHPs to have an adequately staffed office designated as the central point for enrollee issues, including grievances and appeals. This would ensure that the processing is someone's job, and not viewed as a chore that is handled on an ad hoc basis. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenters. As long as States can ensure that those requirements in § 438.406 are met, we believe that it should be their decision as to how best an MCO or PIHP can fulfill those requirements. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters questioned the impartiality of an internal appeals system, and felt that CMS should add language to the regulation preventing any employees of the MCO or PHP from being final decision makers on coverage decisions. ]
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In both the Medicare and Medicaid programs, the Congress has provided for an initial level of review of enrollee appeals at the managed care organization level. We believe that the use of the words “internal grievance procedure” in section 1932(b)(4) indicates that the Congress contemplated that review be performed by MCO employees. Within this context, this final rule requires that the decision-makers not be individuals involved in any previous level of review, and either be physicians or have the clinical expertise needed to make a decision involving the enrollee's particular condition or disease. We believe that these requirements help insure that internal decisions will be as objective as possible. With respect to the “final decision” on a coverage question, all MCO or PIHP coverage decisions are subject to review by non-MCO employees at the State fair hearing level. We believe that those safeguards are reasonable and necessary at the internal appeals level. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believed that we should require MCOs and PHPs to explicitly state that enrollees may obtain copies of their records. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.406(b)(3) requires that MCOs and PIHPs provide the enrollee and his or her representative with the opportunity to examine the enrollee's case file, including medical records, and any other documents and records considered during the appeals process. However, we believe that the State is in the best position to decide in what way enrollees must be notified about this right. 
                    </P>
                    <HD SOURCE="HD3">5. Resolution and Notification: Grievances and Appeals (Proposed § 438.408) </HD>
                    <P>In proposed § 438.408(a), we required that the MCO or PIHP dispose of each grievance and resolve each appeal, and provide notice, as expeditiously as the enrollee's health condition requires. In addition, this section required that the State establish timeframes for disposition of grievances and resolution of appeals, not to exceed the specific timeframes proposed in this section. </P>
                    <P>While we proposed timeframes to resolve appeals, we realize that the Congress, as part of proposals for a patient's bill of rights, is considering several other timeframes for internal MCO appeals. Some of these proposals would apply the timeframes to the Medicaid program. If these proposals were enacted, such statutory timeframes would supersede those set forth in this final rule. </P>
                    <P>
                        Under proposed § 438.408(b), we established the specific maximum timeframes for disposition of grievances 
                        <PRTPAGE P="41060"/>
                        and resolution of appeals. For the standard disposition of a grievance and notice to affected parties, the State may establish a timeframe for disposition that may not exceed 90 days from the day the MCO or PIHP receives the grievance. For standard resolution of an appeal and notice to affected parties, proposed § 438.408(b)(2) required that the State establish a timeframe no longer than 45 days from the day the MCO or PIHP receives the appeal. However, this proposed timeframe could be extended under proposed § 438.408(c), which specified that the MCO or PIHP may extend the timeframe by up to 14 calendar days if the enrollee requests the extension, or the MCO or PIHP shows (to the satisfaction of the State agency, upon its request) that there is need for additional information and how the delay is in the enrollee's interest. 
                    </P>
                    <P>Proposed § 438.408(b)(3) provided a maximum timeframe for expedited resolution of appeals and notice to affected parties. We required that the State establish a timeframe no longer than 3 working days after the MCO or PIHP receives the appeal. We believe that expedited resolution is necessary to ensure that appeals of situations that potentially place an enrollee's heath in jeopardy are not delayed. Although States have historically instituted different processes to protect beneficiaries, we believe that a standardized expedited appeal process is needed to protect beneficiaries in a capitated health care delivery system. Further, this is an important beneficiary protection and is necessary to ensure that the overall timeframe of 90 days for a decision at the State fair hearing (excluding the time the beneficiary takes to file for a State fair hearing) can be met in all cases. However, similar to standard resolution of appeals, we proposed that this expedited timeframe can also be extended by 14 calendar days if the enrollee requests extension or the MCO or PIHP shows (to the satisfaction of the State agency, upon its request) that there is need for additional information and how the delay is in the enrollee's interest. </P>
                    <P>We proposed certain parameters for the extension process. Under proposed § 438.408(c)(2), if the MCO or PIHP grants itself an extension, it is required to notify the enrollee in writing of the reason for the delay. In § 438.408(d), we required the State to establish the method MCOs and PIHPs will use to notify an enrollee of the disposition of a grievance. Under proposed § 438.408(e), we specified that written notice of the appeal resolution must include the following:</P>
                    <P>• The results of the resolution process and the date it was completed. </P>
                    <P>• For appeals not resolved in favor of the enrollee, the enrollee's right to request a State fair hearing and how to do so, the right to request to receive continuation of benefits, and that the enrollee may be held liable for the cost of those continued benefits if the State fair hearing decision upholds the MCO's or PIHP's action. </P>
                    <P>Finally, at proposed § 438.408(f) (this paragraph was erroneously codified as a second paragraph (c), an error that has been corrected in this final rule), we outlined the requirements for State fair hearings. We required the State to permit the enrollee to request a State fair hearing within a reasonable time period specified by the State, but not less than 20 days or in excess of 90 days from the date of the MCO's or PIHP's notice of resolution (if the State requires exhaustion of the MCO or PIHP level appeal procedures) or from the date on the MCO's or PIHP's notice of action (if the State does not require exhaustion and the enrollee appeals directly to the State for a fair hearing). We also felt it was important to outline at proposed § 438.408(f)(2) that the parties to the State fair hearing include the MCO or PIHP as well as the enrollee and his or her representative, or the representative of a deceased enrollee's estate. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters felt that proposed § 438.408(a) should be revised to require that all notices of dispositions of grievances be provided in writing. These commenters argued that MCOs and PIHPs often confuse cases which should be treated as a grievance with those that should be handled as an appeal. Written dispositions of grievances would in the views of these commenters provide a mechanism for addressing this issue by revealing whether or not an MCO or PIHP is resolving a dispute pursuant to the appropriate mechanism. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that § 438.408 makes the difference between a grievance and an appeal very clear. An appeal is triggered through an action, while a grievance involves any dissatisfaction other than an action. If a State chooses to monitor its MCOs and PIHPs by requiring written notices, it may do so. However, we see no reason to require a written notice at the Federal level for all grievances, when many may not be of a nature for which such a notice is appropriate, and there is no Federal right to review by the State of such matters. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Comments on timeframes widely differed. Many commenters questioned the fact that the timeframes for appeals in the proposed rule were longer than those in place under Medicaid fee-for-service, Medicare+Choice, and versions of Patients Bill of Rights legislation. The commenters apparently believed that departing from these standards failed to adequately protect beneficiaries, and raised constitutional due process questions. These commenters wanted standard internal appeals to be resolved within 30 days. However, several other commenters found the 45-day timeframe more reasonable. Still other commenters were confused about the timeframes in general, and wanted an explanation of how they worked. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We realize that the proposed timeframes were confusing as proposed, and potentially would not give the State a reasonable amount of time—or under some scenarios, any time, to conduct a fair hearing. We believe that after an MCO or PIHP takes up to 45 days, plus a possible 14-day extension, to make a decision, the 90-day clock for a fair hearing decision should stop during the time the enrollee takes to file for a State fair hearing (which could be as long as 90 days itself). Therefore, in response to the above comments, we have clarified in § 431.244(f) that the State is required to resolve the State fair hearing within 90 days of the day the MCO or PIHP received the appeal, not including the number of days the enrollee took to subsequently file for a State fair hearing. We believe that this is a reasonable timeframe because it holds the State accountable within a 90-day timeframe as long as the enrollee takes prompt action to follow up any denial at the internal appeal level. This will guarantee a high level of commitment on both sides. We also believe that 45 days is a reasonable standard timeframe for an MCO or PIHPs, because an enrollee may request an expedited appeal if he or she feels that a standard timeframe could jeopardize his or her health. With respect to the comments raising constitutional due process issues, we believe that applying this timeframe in this situation is fully consistent with due process requirements. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters noted that most States already have a complex grievance system in place, with specified timeframes and other rules, and changing these requirements may be confusing for beneficiaries and may not provide any additional protections to enrollees. These commenters asked us to permit “deeming” of compliance with Medicaid rules when the State's system met certain standards. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The grievance and appeals requirements in § 438.408 set forth 
                        <PRTPAGE P="41061"/>
                        minimum standards that MCOs, PIHPs, and States must follow. As long as those standards are met, a State is free to tailor those to the system it operates. We believe that these timeframes, notice requirements, and other standards grant States flexibility (
                        <E T="03">e.g.,</E>
                         the State is granted the discretion to establish timeframes, within ranges), and constitute the minimum necessary to ensure reasonable beneficiary protections. We strongly believe that the established timeframes give States, MCOs and PIHPs adequate time to make an informed decision for enrollees at both the internal and State fair hearing levels. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believed that the mandatory timeframes for the grievance and appeals process in § 438.408 might be difficult to meet if enrollees fail to submit timely information, or are not available for an in-person presentation to the MCO or PIHP. These commenters asked that a limit be placed on the number of days MCOs and PIHPs are responsible for providing continued services pending a final determination in the case of an appeal from a termination of benefits. Some commenters wanted the timeframes to begin when all documentation is received from providers, rather than the date of notice of the action being appealed, for fear that the timeframes would be impossible to meet in certain cases. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the timeframes in § 438.408 will result in timely decisions based on all necessary evidence in the vast majority of cases. Enrollees have a strong incentive to cooperate fully with officials in an internal appeals process to facilitate timely coverage decisions. However, if some enrollees do not provide enough information to support their appeal, the MCO or PIHP is responsible for deciding the appeal on the basis of available information within the timeframes set out. Since continuation of benefits for authorized services being terminated may, at the beneficiary's request, continue throughout the appeals process until the final decision is made at the MCO, PIHP, or State level, we believe that it is reasonable to require MCOs and PIHPs to make decisions within the specified timeframes so they are not responsible for covering benefits due to another party's delay. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter felt that the timeliness for grievance and fair hearing completions may be difficult to meet in the case of mental health enrollees. The commenter inquired as to whether decisions on an action could be made retroactively, still comply with the requirements. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The timeframe for filing an appeal in a State will be between 20 and 90 days, as determined by that State. We believe that this should be sufficient time for all enrollees to request a hearing. MCO, PIHPs, and States are then responsible for assisting enrollees with any procedural barriers they may encounter. Once the appeal is filed, the MCO, PIHP, or State is responsible for ensuring that a fair decision is made within the mandated timeframes. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters noted that in proposed § 438.408, the paragraph titled “Requirements for a State fair hearing,” which was identified in the preamble as paragraph (f), was inadvertently labeled paragraph (c) in the regulations text. The commenter assumed this was a typographical error. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter, and as noted above, we have made the appropriate change in § 438.408. 
                    </P>
                    <HD SOURCE="HD3">6. Expedited Resolution of Appeals (Proposed § 438.410) </HD>
                    <P>In proposed § 438.410 we required each MCO and PIHP to establish and maintain an expedited review process for appeals when the MCO or PIHP determines or the provider indicates that taking the time for a standard resolution could seriously jeopardize the enrollee's life or health or ability to attain, maintain, or regain maximum function. Further, the MCO or PIHP was required under proposed § 438.410(b) to ensure that no punitive action is threatened or taken against a provider who requests an expedited resolution, or supports an enrollee's request for an expedited appeal. </P>
                    <P>If the MCO or PIHP denies a request for expedited resolution of an appeal, it would be required under proposed § 438.410(c) to transfer the appeal to the standard resolution timeframe in accordance with proposed § 438.408(b)(2), and give the enrollee prompt oral notice of the denial following within two calendar days with a written notice. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter contended that the definition of “expedited authorization decisions” can be applied to nearly any medical necessity determination. This commenter recommend removing language related to the “enrollee's ability to attain, maintain, or regain maximum function * * * could be jeopardized.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter. If a standard appeals process is long enough to place an enrollee's health in jeopardy based on the definition above, we believe that an expedited appeal is warranted. Furthermore, the provider, MCO, PIHP, or State has the final decision on whether or not that threshold has been met. Therefore, we believe that it does not add any unwarranted administrative burden to MCOs, PIHPs, or States during the process. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Comments on the timeframes in proposed § 438.410 again differed widely. Many commenters (again citing due process concerns and comparing the timeframes to other situations) wanted expedited internal appeals to be resolved within 72 hours, mirroring Medicare+Choice and State fair hearing timeframes.
                    </P>
                    <P>However, several commenters found the timeframes unreasonable, unrealistic, subjective, and too prescriptive, and asked for more State flexibility to set timeframes. Some wanted the expedited process to be longer, such as a minimum of five working days, arguing that the present timeframe was unworkable. One commenter noted that most States already have timeframes, and suggested that changing these requirements may be confusing for beneficiaries while not providing any additional meaningful protections to enrollees. </P>
                    <P>
                        <E T="03">Response:</E>
                         We continue to believe that the regulation should establish timeframes for steps in the internal appeal process, and that an expedited timeframe is necessary when the use of standard timeframes may  jeopardize the enrollee's health. An expedited timeframe is an important beneficiary protection and ensures that those enrollees who need a quick decision will receive one. However, we believe that three working days for an expedited internal appeal makes the most sense. It provides for a very timely decision for those enrollees whose health may be in jeopardy, yet facilitates MCOs and PIHPs with the difficulty of operating during weekends and holidays. If an enrollee's health is jeopardized by an emergency medical condition, as defined in § 438.114(a), then he or she would go to the nearest emergency room. In § 438.408(a) we provide for States to establish timeframes that may not exceed the timeframes specified in this final rule. Thus, States may establish shorter timeframes. Again, with respect to the commenter's due process concerns, we are unaware of any legal basis for the suggestion that these regulations would violate due process. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters suggested that the regulations expressly allow the beneficiary to obtain an expedited review based on their primary care provider's opinion that the standard for expedited review has been met. They believed that MCOs and 
                        <PRTPAGE P="41062"/>
                        PIHPs should not be given complete control over the situation, because their financial arrangements may provide an incentive to deny services. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Under § 438.410(a), an MCO or PIHP must provide expedited review if it determines the standard for such review has been met, in the case of a request by an enrollee or if “the provider” makes such a determination. The preamble to the proposed rule did not specify whether “the provider” included the enrollee's primary care provider, or only the provider who would be furnishing the service requested in connection with the appeal. In response to this comment, we are clarifying that “the provider,” as used in § 438.410(a), refers to the provider of the services requested, since this provider is in the best position to evaluate the enrollee's need for those services. In some cases, this may be the primary care provider, in which case the current regulations would provide for the result the commenter seeks. In other cases, however, the primary care provider's opinion would not be dispositive of whether expedited review would be granted. We assume that the primary care provider's views would be taken into account by the MCO or PIHP in making their determination, or by “the provider” of the services sought, in deciding whether to request review or support the enrollee's request as provided in § 438.410(a). If an enrollee disagrees with the MCO's or PIHP's decision, and the provider who would be furnishing the services does not support the enrollee's request, nothing prevents him or her from contacting the State and asking for its involvement or assistance. Furthermore, States have the option to make a primary care provider's decision binding in all cases as part of their contract requirements, or State law, if they choose. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters were concerned about the MCO's and PIHP's ability to extend the 3-day expedited timeframe for 14 more days in cases in which this extension was not requested by the enrollee, and with the fact that the enrollee does not have the right to appeal such an extension. These commenters argued that the State has no mechanism for knowing that an MCO or PIHP has given itself such an extension, making the expedited provision arguably an empty mechanism. Furthermore, it appears to these commenters that the MCO or PIHP could give itself extensions indefinitely because there is no requirement to resolve the appeal after the first extension. They recommended only allowing an extension in these cases if the enrollee requests it. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We partially disagree with the commenters' interpretation of the regulation. We state in § 438.408(b)(3) that an MCO or PIHP may extend the timeframe of 3 working days up to an additional 14 calendar days. This is intended to be the outer time limit before a decision is made or the enrollee is eligible to file for a State fair hearing. Thus, an MCO or PIHP could not continue “indefinitely” to grant additional 14 day extensions. With respect to cases in which an enrollee does not request the extension, the extension still must be in the enrollee's interests, and an enrollee is free to argue to the State that this standard has not been met. The State then may decide if it should intervene. Moreover, we note that States have the option in contracts or in State law of permitting extensions only when requested by the enrollee. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern regarding the logistics of requiring MCOs and PHPs to give prompt oral notice to an enrollee of any denial of an expedited request. They noted that some Medicaid enrollees may not be accessible by telephone. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We are aware that some Medicaid enrollees may not have telephones, and that it therefore may be difficult in some cases to provide oral notice. Therefore, in response to this comment, we have revised § 438.410(c)(2) by requiring MCOs and PIHPs to make reasonable efforts to notify enrollees orally of decisions not to expedite an appeal, and to follow up with a written notice within two calendar days. MCOs and PIHPs should request information from enrollees about how and where they can be contacted. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters recommended that the State Medicaid agency be permitted 3 working days to hear expedited appeals that they receive, rather than 72 hours. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters. In response to this comment, the final rule, at § 431.244(f)(2) and (3), now requires the State to conduct a fair hearing and make its decision within 3 working days for service authorization denials that meet the criteria for expeditious handling. We have chosen to use the same 3-working-days standard that applies to MCO or PIHP review in expedited cases so that the State would not be required to complete review of all expedited cases during weekends or holidays. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters advocated a requirement that expedited internal appeals not decided wholly in the enrollee's favor be automatically forwarded to the State fair hearing process. These commenters felt that timing during an expedited process was essential, and that automatic forwarding would provide necessary speed to the process. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenters. We believe that the burden on MCOs, PIHPs and States, of automatic forwarding of appeal materials even in cases in which the enrollee may not wish to pursue a further appeal outweighs any benefits that might be achieved by such a policy. As in the case of when a beneficiary files an appeal during the 90 standard timeframe, it is reasonable to expect any enrollee who is seeking a particular service or benefit to promptly file for a State fair hearing if he or she is not wholly successful at the internal appeals level. We do not believe this would significantly add to the time it takes to handle the appeal. We note that the MCO or PIHP must give enrollees reasonable assistance in completing forms and taking other procedural steps. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that the proposed rule did not grant enrollees a right to a State fair hearing for an enrollee whose request for an expedited resolution is denied. Specifically, the commenter noted that this was not listed among the bases for a State fair hearing. The commenter wanted clarification on this point. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The omission of a denial of a request for an expedited hearing from the ground for a fair hearing was intentional. As noted above, if a request for an expedited resolution is denied, the case is automatically treated as a standard appeal. However, if that internal appeal is not resolved wholly in favor of the enrollee, then the enrollee has a right to a State fair hearing. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter objected to the fact that the proposed rule did not include a requirement for an expedited review process for grievances. They argued that this would be dangerous for enrollees with severe health problems who could not wait for the time frame of the standard review process. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A grievance involves any dispute other than an “action.” Only an action should involve the possibility of a delay putting an enrollee with severe health problems at risk. We have an expedited provision for those type of disputes. Therefore, we do not believe that an expedited grievance process is a necessary mandate at the Federal level. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that proposed § 438.410(a) should have a period at the end rather than a semi-colon. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter, and we made the appropriate change in § 438.410(a) the final regulation. 
                        <PRTPAGE P="41063"/>
                    </P>
                    <HD SOURCE="HD3">7. Information About the Grievance System to Providers and Subcontractors (Proposed § 438.414) </HD>
                    <P>Proposed § 438.414 required that the MCO or PIHP must provide the information specified at § 438.10(g)(1) about the grievance system to all providers and subcontractors at the time they enter into a contract. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that CMS require that information about the grievance system be provided to subcontractors as well as to contracting providers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Proposed § 438.414, which is unchanged in this final rule, already provided that this information must be provided to providers “and subcontractors.”
                    </P>
                    <HD SOURCE="HD3">8. Recordkeeping and Reporting Requirements (Proposed § 438.416) </HD>
                    <P>Proposed § 438.416 required the State to require MCOs and PIHPs to maintain records of grievances and appeals and review the information as part of the State quality strategy. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Commenters urged that the regulation require States to provide members of the public, upon request, with MCO and PHP summaries of grievance and appeal logs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         States have the authority to require that MCOs and PIHPs make available to the State, or at the State's option, to members of the public, grievance and appeal logs or other MCO and PIHP grievance system documents. We do not agree that we should mandate this, however. In some cases, raw appeals data may be confusing to the public, or potentially misleading. We believe States are in the best position to decide how such information should be presented to the public. In designing their quality strategies, States should consider what information they and the public will need to support those strategies. 
                    </P>
                    <HD SOURCE="HD3">9. Continuation of Benefits When an MCO or PIHP Appeal of a Termination, Suspension, or Reduction, and State Fair Hearing on Such an Action, are Pending (Proposed § 438.420) </HD>
                    <P>Proposed § 438.420 required that when the dispute involves the termination, suspension, or reduction of a previously authorized course of treatment, the MCO or PIHP must continue the enrollee's benefits until issuance of the final appeal decision or State fair hearing decision, if all of the following occur: </P>
                    <P>•  The enrollee or the provider files the appeal timely. </P>
                    <P>•  The services were ordered by an authorized provider. </P>
                    <P>•  The period covered by the authorization has not expired. </P>
                    <P>•  The enrollee requests such an extension of benefits. </P>
                    <P>We specified that timely filing means filing on or before the later of either the expiration of the timeframe specified by the State (in accordance with § 438.404(c)(2)) and communicated in the notice of action or the intended effective date of the MCO's or PIHP's proposed action. </P>
                    <P>This provision would apply only when the MCO or PIHP physician initially authorized the services (that is, it would not apply to pre-service authorization requests that were denied) and when the beneficiary requests the services be continued (that is, the mere action of filing for an appeal or State fair hearing in a timely manner is not sufficient for benefits to be continued). The continuation of benefits provision would not require a further statement of authorization from the MCO or PIHP physician or affect benefits not originally authorized. </P>
                    <P>If the MCO or PIHP continues or reinstates the enrollee's benefits while the appeal is pending, under proposed § 438.420(c), the benefits must be continued until one of the following occurs: </P>
                    <P>•  The enrollee withdraws the appeal. </P>
                    <P>•  The MCO or PIHP resolves the appeal against the enrollee, unless the enrollee has requested a State fair hearing with continuation of benefits until a State fair hearing decision is reached. </P>
                    <P>•  A State fair hearing officer issues a hearing decision adverse to the enrollee. </P>
                    <P>Beneficiaries who have received continuation of benefits while they appeal to the MCO or PIHP are not obligated to pursue their appeal further, through the State fair hearing process, if the MCO or PIHP denies their appeal. It remains the beneficiaries' choice. It is important to note, however, that enrollees who lose their appeal at either the MCO, PIHP or State fair hearing levels will be liable for the costs of all appealed services from the later of the effective date of the notice of intended action or the date of the timely-filed appeal, through the date of the denial of the appeal. As a result, in § 438.420(d), we proposed that if the final resolution of the appeal is adverse to the enrollee (that is, it upholds the MCO's or PIHP's action) the MCO or PIHP may recover the cost of the services furnished to the enrollee while the appeal was pending, to the extent that they were furnished solely because of the requirements of this section, and in accordance with § 431.230(b). </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters pointed out that the proposed rule does not specify all the same circumstances set forth in §§ 431.230 and 430.231 as situations in which benefits must be continued or reinstated. These commenters specifically cited advanced notice requirements, and argued that this rewards MCOs and PIHPs that do not provide advanced notice. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenters. MCOs, PIHPs, and States have a strong incentive to notify enrollees timely of any reduction, limitation, or suspension of existing services. While enrollees have to actively request continuation of benefits while filing an appeal, they must be given the opportunity to do so before the benefits are reduced, limited, or suspended. And since enrollees have this right until an adverse State fair hearing decision (assuming of course that he or she follows the applicable rules), a delay in notice only gives enrollees benefits for a longer period of time. However, in response to this comment, we now state in the regulation text that the enrollee has 10 days after the MCO or PIHP mails the notice of action to request continuation of benefits. Therefore, even if the effective date of action has passed, an MCO or PIHP may not discontinue those benefits until 10 days after the notice is mailed. We believe that this sufficiently addresses the commenters' concern. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received many comments regarding enrollees' rights to continuation of benefits during the MCO and PIHP appeal process. Several commenters thought that the regulations mandate that MCOs and PIHPs continue benefits in all cases in which the appeal involves services that are being terminated or reduced. Several commenters felt that continuation of benefits pending resolution of an appeal or State fair hearing, without financial risk, is one of the most important protections needed for managed care enrollees. 
                    </P>
                    <P>In contrast, several other commenters were opposed to extending continuation of benefits requirements to the MCO and PIHP appeal process. One commenter contended that this requirement would have significant cost implications for MCOs and PIHPs. Another commenter felt that benefits should be continued only at the point when an enrollee requests a State fair hearing. </P>
                    <P>
                        One commenter thought that requiring MCOs and PHPs to continue benefits would place them in an untenable position with their providers, compromising their ability to manage care and cost. This commenter expressed concern that this provision 
                        <PRTPAGE P="41064"/>
                        may damage managed care programs, and believed it was unnecessary, given the requirement of expedited review of appeals in cases in which a delay could jeopardize health. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Because we allow States to require exhaustion of the MCO and PIHP appeal before receiving a State fair hearing, we believe that, in order for the right to continued benefits during a State fair hearing to be meaningful, continuation of benefits must begin with the filing of an MCO or PIHP appeal, and continue until the State fair hearing decision. Given that, with few exceptions, the overall 90-day timeframe for a final fair hearing decision applies even when exhaustion is required, the amount of time benefits must be continued is the same under this final rule as under the longstanding fair hearing system. Continuation of benefits at the MCO and PIHP level thus is part of the same longstanding right to continuation of benefits that has existed for Medicaid beneficiaries when services are reduced or terminated. 
                    </P>
                    <P>As in fee-for-service, under managed care, the right to continuation of benefits is not exercised without financial risk to the beneficiary of payment for services provided should he or she lose the appeal. Otherwise, MCOs, PIHPs, or States would be unfairly liable for treatment in which they were correct in limiting, reducing, or suspending. It is because of this potential risk for enrollees that we require that the enrollee specifically request continuation of benefits. Under § 438.404(b)(7), the notice of adverse action must include an explanation of this choice.</P>
                    <P>While expedited appeals will decrease the amount of time MCOs and PIHPs are liable to continue benefits for enrollees with pending appeals, the expedited appeal process does not substitute for the protection provided to Medicaid beneficiaries of the right to continuation of previously authorized benefits pending the outcome of a State fair hearing decision. </P>
                    <P>If the benefit is a Medicaid covered service, but not an MCO or PIHP covered service, the State, not the MCO or PIHP is responsible for providing those services pending the outcome of the State fair hearing. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters requested that § 438.420 should clearly state that re-authorization of a service at a lower level than previously received, or a denial of re-authorization, is a termination or reduction of the service requiring the continuation of benefits pending appeal. Other commenters requested that we make clear in the regulation text that continuation of benefits does not include the expiration of an approved number of visits through an authorized course of treatment. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As noted above, we agree that the expiration of an approved number of visits does not constitute a termination for purposes of notice and continuation of benefits. If an enrollee requests re-authorization for services and the MCO or PIHP denies the request or re-authorizes the services at a lower level than requested, the MCO or PIHP must treat this request as a new service authorization request and provide notice of the denial. We have explained above that the language in the proposed rule already limited the right to continued benefits to services that were authorized. In response to this comment, in order to make clear that the continuation of benefits itself is not what we mean by “authorized,” we have revised § 438.420(b)(4) by adding the word “original” to make clear that benefits are only continued to the extent they were originally authorized. As noted above, we also have added a new § 438.420(c)(4) in this final rule to make clear that when benefits are continued under § 438.420(b), they may be discontinued when the original authorization expires. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned about the status of enrollees who received authorization for a course of treatment from a non-network physician but then had those benefits limited by a new MCO once the course of treatment had begun. They believe that these enrollees need protection for their benefits. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         An enrollee who has his or her existing benefits reduced, limited, or suspended by an MCO, PIHP, or State has the right to request a continuation of benefits regardless of the source as long as it originated from a Medicaid participating provider. It is the State's decision as to what entity is liable for those benefits during the appeals process. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter argued that discontinuing services being provided by an MCO without a State fair hearing was unconstitutional. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not believe that we need reach constitutional issues (such as, regarding whether a property interest or State action exist) because Medicaid beneficiary rights are directly addressed in section 1902(a)(3) and 1932(b)(4), and it is these statutory rights that are implemented in this final rule. As noted above, we believe that if services are discontinued on the date the authorization expires, this is not a “termination” of services that the enrollee had any right to expect to receive, and thus is not a termination within the meaning of section 1902(a)(3) and the implementing regulations. In the case of a termination of authorized services prior to the expiration date of the authorization, we agree with the commenter that a beneficiary should have the right to have these benefits continue pending a hearing on the termination. We provide the enrollee with 10 days to request to have benefits continue under these circumstances, pending an appeal and State fair hearing. We believe that this process is fully consistent with the Medicaid statute and constitutional requirements, to the extent applicable. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters requested that we delete the requirement that the beneficiary must request continued benefits. They contended that this requirement was constitutionally defective in that they believed continued benefits, without pre-requisites to obtaining them, to be required under due process. 
                    </P>
                    <P>The commenters noted that while the existing regulation at § 431.230(b) provides for the possibility of recoupment, benefits are continued when an appeal is filed timely. The commenters found no reason to change this long-standing rule for beneficiaries who are receiving services through an MCO or PIHP. Also, several commenters believed that proposed § 438.420(c)(2) made it impossible for benefits to continue through a State fair hearing, because a beneficiary would have had to file for a State fair hearing before the MCO or PIHP had even made its internal appeal decision in order for benefits to continue. </P>
                    <P>
                        <E T="03">Response:</E>
                         Again, we do not believe we need reach constitutional issues here, but that the final rule as proposed is fully consistent with any applicable constitutional requirements. It is not true that benefits continue under fee-for-service Medicaid “without pre-requisites to obtaining them.” Benefits only continue under fee-for-service if the beneficiary timely files an appeal. We do not see the difference between requiring the filing of an appeal for benefits to continue and requiring that as part of such an appeal, the beneficiary request that benefits continue. Indeed, given the possibility of beneficiary liability in both cases, we believe that the approach in this final rule is more protective of beneficiary rights. Under this rule, after an action, the beneficiary will be notified both of this right to continuation of benefits and the possible liability for services if the final decision is not in his or her favor. Thus, we believe the general concern about continued benefits not being automatic with an appeal is unfounded. 
                        <PRTPAGE P="41065"/>
                    </P>
                    <P>However, we agree with the concerns expressed by several commenters' that proposed § 438.420(c)(2) could make it impossible for benefits to continue through a State fair hearing as proposed. Therefore, in response to these comments, we have revised § 438.420(c)(2) by requiring beneficiaries to re-request continuation of benefits within 10 days after the mailing of the internal appeal decision against the enrollee, in order to preserve continuation of benefits during a State fair hearing. </P>
                    <HD SOURCE="HD3">10. Effectuation of Reversed Appeal Resolutions (Proposed § 438.424) </HD>
                    <P>Proposed § 438.424 required that if the MCO, PIHP, or the State fair hearing officer reverses a decision to deny, limit, or delay services that were not furnished while the appeal was pending, the MCO or PIHP must authorize or provide the disputed services promptly, and as expeditiously as the enrollee's health condition requires. Furthermore, if the MCO, PIHP, or the State fair hearing officer reverses a decision to deny authorization of services, and the enrollee received the disputed services while the appeal was pending, the MCO, PIHP, or the State would be required to pay for those services, in accordance with State policy and regulations. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters supported a time frame of no more than 10 days for an MCO or PIHP to provide or pay for services subsequent to a State fair hearing because enrollees with successful appeals should not have to adjudicate over the word “promptly.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree that MCOs and PIHPs should be held to a Federal timeframe to provide or pay for services, because such a timeframe may not be reasonable in the case of the circumstances of all States. Consistent with the State fair hearing policy in § 431.246, we are requiring that the services are provided promptly, or as expeditiously as the enrollee's health condition requires. We believe that the States are in the best position to decide whether to require specific time limits if they choose. 
                    </P>
                    <HD SOURCE="HD2">F. Certifications and Program Integrity (Subpart H) </HD>
                    <P>Fraud and abuse can negatively affect both the quality of health care services rendered to Medicaid beneficiaries, and an MCO's, PIHP's, PAHP's, or PCCM's financial viability. Promoting program integrity within Medicaid managed care programs can protect against misspent Medicaid program funds, and promote quality health care services. Proposed subpart H of part 438 contains safeguards against fraud and abuse and requires that organizations with Medicaid contracts make a commitment to a formal and effective fraud and abuse program. </P>
                    <P>In proposed § 438.600 we stated that the statutory basis for this subpart is under sections 1902(a)(4) and 1902(a)(19) of the Act. These sections require that methods be provided in the State plan for the proper and efficient operation of the plan and that safeguards are provided consistent with the best interests of the recipients. </P>
                    <P>In proposed § 438.602 we provided that the certification and program integrity requirements contained in subpart H apply to MCOs and PIHPs as a condition for contracting and for receiving payment under the Medicaid managed care program. </P>
                    <P>In proposed § 438.604 we provided that data, including enrollment and encounter data, must be certified and submitted to the State, if State payments are based on the data. We also specified that other information required by the State and information included in contracts, proposals, and other related documents must be certified. We also required in § 438.604(b) that the MCO or PIHP certify that they are in substantial compliance with the terms of the contract. </P>
                    <P>In proposed § 438.606 we required that certifications be provided concurrently with the data they relate to, and required that certifications be signed by the MCO's or PIHP's Chief Executive Officer, Chief Financial Officer, or an individual delegated authority to sign for one of these individuals. We proposed that the certifications must include attestations to the truthfulness, accuracy, and completeness of the data based on best knowledge, information, and belief. </P>
                    <P>In proposed § 438.608 we required that each MCO or PIHP have administrative and management arrangements or procedures, including a mandatory compliance plan, designed to guard against fraud and abuse. This section also outlined the required elements to be included in the arrangements and procedures. </P>
                    <P>In this final rule we are making a technical correction to add two additional sources of authority. First, we are adding a citation to section 1903(m), which establishes conditions for payments to the State with respect to contracts with MCOs. Second, we are adding a new § 438.610 to incorporate the requirements of section 1932(d)(1) of the Act. That provision of the statute is self-implementing, and therefore we did not include it in the proposed regulation. However, we are including the substance of the requirement in this final regulation to make it easier for the public to find all the relevant provisions in one place. Under the authority of section 1902(a)(4) of the Act, we are also applying these provisions to PIHPs and PAHPs. </P>
                    <P>We believe it is in the best interests of State Agencies, MCOs, PCCMs, PIHPs, PAHPs, and CMS to significantly aid in the fight against fraud and abuse and the requirements of this subpart work to achieve that goal.</P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter proposed that we develop a standard form for certifications since we are requiring certifications by the Chief Executive Officer or the Chief Financial Officer or other person who is delegated the authority of the MCO or PIHP to certify data submitted. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter as we wish to maintain State flexibility in this area. In §§ 438.604 and 438.606 respectively, we provide that data certifications are required if data are being used to set payments. We have described the source, content, and timing required for certifications. We do not, however, wish to be overly prescriptive and therefore, we are not prescribing the format of the certifications. If the commenter is requesting a sample format that could be used as a model certification form, one can be found on the CMS website at 
                        <E T="03">http://www.hcfa.gov/medicaid/letters/smd80700.htm</E>
                         in the document entitled, “Guidelines for Addressing Fraud and Abuse in Medicaid Managed Care” at appendix 2. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that it is unclear as to when certifications are required and if the certifications of data to set payments is meant to reference payments under the current contract year or for proposed contract years. The commenter also believes that the requirements for certifications for substantial compliance with the terms of the contract are unclear. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         In § 438.604(a) we require that MCOs and PIHPs provide certification of data requested by the State if payments to the MCOs and PIHPs are based on the data submitted, and in § 438.606(c) we require that MCOs and PIHPs submit the certification concurrently with the data. This applies regardless of whether the data are used for setting payments for current contract years, or for other contract years. If data are not being used to set payments, then certifications would not be required. 
                    </P>
                    <P>
                        We agree with the commenter that clarification is necessary regarding 
                        <PRTPAGE P="41066"/>
                        certification for substantial compliance with the terms of the contract. We previously proposed, in §§ 438.604(b), that an MCO or PIHP must certify that it is in substantial compliance with the terms of its contract. 
                    </P>
                    <P>We understand the commenter's confusion regarding this requirement since the statute and regulations already require States to monitor compliance with contracts executed under this rule and provides sanctions to be used where certain requirements are not met. Further we would expect to require corrective action plans in situations in which a State is found to be out of compliance with these rules. Consequently, we believe that the requirements on States, MCOs, PIHPs, PAHPs, and PCCMs contained in § 438.6 and elsewhere in this rule and the mechanisms for monitoring and enforcement are sufficiently clear that the requirements for “substantial compliance” in §§ 438.604 and 438.606 are unnecessary and we have deleted them from this subpart. Hence renumbering has taken place in these sections. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters believe that subcontractor certifications are necessary since MCOs could delegate functions to subcontractors including physicians, hospitals, and clinics as well as to administrative service organizations that collect data from network providers and report the data to the MCO and the State. The commenters argued that without accurate and complete data, States may not have the information necessary to set actuarially sound capitation rates. Commenters expressed opposing views on this issue with one commenter believing that this requirement would be burdensome to plans and providers because of the complexities involved in obtaining provider certifications. Other commenters stated that subcontractor certifications are necessary to protect CMS and others against being defrauded or paying an MCO more than the amount to which it should be entitled. We received further suggestions that not having subcontractor requirements could undermine federal enforcement of the False Claims Act. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We have considered the commenters' suggestions and we agree that subcontractors play an important role in an MCO's network. We require MCOs and PIHPs to certify 
                        <E T="03">all</E>
                         data they submit, which would include any data produced by subcontractors. We believe that MCOs and PIHPs should be held accountable for their subcontractors and their subcontractors' data. We believe that States must be able to rely on the MCOs' and PIHPs' certifications if they are to combat potential fraud and abuse, and continue to set capitation payments to MCOs and PIHPs appropriately. Therefore, we are only requiring in this subpart that data certifications be required of MCOs and PIHPs and not of their subcontractors. It is up to the State or the MCO or PIHP to determine whether subcontractor data is accurate. If data is not used to set payments, certifications by MCOs and PIHPs are not necessary. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         We received opposing views about whether PAHPs should be exempt from the program integrity protections outlined in this subpart. One commenter suggested that PAHPs should be required to have fraud and abuse plans and data certifications to justify State payments, since fraud can be significant in ambulatory plans also. In contrast, another commenter believes we should require that fraud and abuse plans be implemented only by entities with 10,000 enrollees or more. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We clearly intend that PAHPs should work to combat against fraud and abuse. However, we are recognizing that it may not be appropriate to require those organizations to implement formal fraud and abuse plans, given that they generally have relatively few enrollees and provide a relatively narrow range of services. We believe that the benefits of requiring PAHPs to comply with the formal measures of subpart H in order to protect against fraud and abuse is outweighed by the level of burden placed on these organizations, which could place some plans at financial risk. 
                    </P>
                    <P>Consequently, we are only requiring that §§ 438.600 through 438.610 apply to MCOs, to PIHPs, and only to PAHPs and PCCMs where specifically noted. Typically, MCOs and PIHPs, which include at least some inpatient hospital or institutional care services, are larger, more complex organizations, and will in most cases, have higher enrollment levels. </P>
                    <P>We believe the more comprehensive plans (such as, MCOs and PIHPs) are likely to need to provide for more sophisticated methods for combating fraud and abuse and may also need to provide for compliance officers as part of their staff. This is because they are more complex organizations, and need to contract with a large number, and greater variety of providers. These plans typically serve more enrollees and provide more services. Furthermore, more complex organizations are likelier to include administrative staff that collect and report data, and that need more in-depth monitoring. We disagree with the commenter that the applicability of these requirements should depend on the PAHP's enrollment level, because enrollment can fluctuate, and we believe that approach would lead to arbitrary results. </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter suggested that we should not mandate the use of a compliance plan developed by a federal enforcement agency, that is, the OIG, that was intended for M+C plans. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenter that to require the use of guidelines developed for a national program (such as, M+C) by a Federal enforcement agency would be overly prescriptive and could impede State flexibility in combating fraud and abuse. In § 438.608 we require MCOs and PIHPs to have administrative and management procedures, including a mandatory compliance plan, designed to guard against fraud and abuse; however, we have not mandated the use of the compliance plan developed by the OIG. The commenter is correct that the compliance plan developed by the OIG is intended for M+C plans and not for Medicaid managed care plans. Further, we agree that it is important for States to have flexibility in combating fraud and abuse in the Medicaid program and we believe States can maintain that flexibility by developing their own compliance plans. 
                    </P>
                    <HD SOURCE="HD2">G. Sanctions (Subpart I) </HD>
                    <P>Section 1932(e)(1) of the Act requires, as a condition for entering into or renewing contracts under section 1903(m) of the Act, that State agencies establish intermediate sanctions that the State agency may impose on an MCO that commits one of six specified offenses: (1) Failing substantially to provide medically necessary items and services that are required by law, or are required under the MCO's contract with the State; (2) imposing premiums or charges in excess of those permitted under title XIX; (3) discriminating among enrollees based on health status or requirements for health care services; (4) misrepresenting or falsifying information; and (5) failing to comply with statutory requirements that apply to physician incentive plans. Under section 1932(e)(1)(A) a State may also impose sanctions against MCOs and PCCMs for distributing, directly or through an agent or contractor, marketing materials that contain false or materially misleading information. Proposed § 438.700 contained the above provisions from section 1932(e)(1) of the Act. </P>
                    <P>
                        In section 1932(e)(2) of the Act, Congress described the types of sanction authority that would satisfy the State's obligation to have intermediate 
                        <PRTPAGE P="41067"/>
                        sanctions. For the most part, the State has discretion to choose which of these sanctions to use. However, the State is required to have authority to appoint temporary management under section 1932(e)(2)(B), and to permit individuals to terminate without cause under section 1932(e)(2)(C). This is because section 1932(e)(3) requires the State to impose at least those two sanctions if an MCO repeatedly fails to meet the requirements of sections 1903(m) or 1932. The other provisions that would clearly satisfy the State's obligation to have intermediate sanction authority include authority to impose civil money penalties for specified violations, up to specified maximum amounts, and to suspend enrollment or payment for new enrollees. These provisions were reflected in proposed § 438.702(a). 
                    </P>
                    <P>Under section 1932(e)(2)(B), one of the sanctions that would satisfy section 1932(e)(1) is for the State to oversee the operation of the MCO “upon a finding by the State that there is continued egregious behavior by the organization or there is a substantial risk to the health of enrollees * * * or to assure the health of the organization's enrollees.” Given the extraordinary nature of the sanction of taking over management of an MCO, we proposed in § 438.706 that this sanction be imposed only when those egregious circumstances exist. </P>
                    <P>The requirement in section 1932(e)(1), that the State have intermediate sanction authority as a condition of contracting, only applies to contracts with MCOs. It does not place a similar requirement on States with respect to PCCMs. However, subsections (e)(1)(A) and (e)(2)(D) and (E) refer to “managed care entities,” and thus envision that the State would choose to apply those sanctions to PCCMs as well. </P>
                    <P>Section 1932(e)(4) of the Act authorizes State agencies to terminate the contract of any MCO or PCCM that fails to meet the requirements in sections 1932, 1903(m), or 1905(t) of the Act. This provision was included in proposed § 438.708. However, if the State chooses that remedy, under section 1932(e)(4)(B) the State is required to provide a hearing before terminating a contract. Proposed § 438.710 set forth requirements that apply to the notice to the MCO or PCCM, and to the pre-termination hearing. Under section 1932(e)(4)(C), enrollees may be notified of their right to disenroll immediately without cause in the case of any entity subject to a termination hearing. Proposed § 438.722 described the provisions for disenrollment during the termination hearing process. Finally, in § 438.724, we proposed that States be required to notify CMS whenever it imposes or lifts a sanction. </P>
                    <P>Under section 1903(m)(5) of the Act, CMS has its own direct authority to impose sanctions when Medicaid-contracting MCOs commit offenses that are essentially the same as those identified in section 1932(e)(1) of the Act. Section 1903(m)(5) is currently implemented by regulations codified at 42 CFR § 434.67. We proposed to move those regulations to proposed § 438.730. However, we inadvertently made substantive changes, including omission of parts of the original regulation text dealing with denial of payment, and expanding the State plan requirement previously found in § 434.67(i). The final rule conforms the text of §§ 438.726 and 438.730 to the text of § 434.67. We proposed in § 438.726 to broaden the State plan requirements to include a plan to monitor for violations that involve the actions and failures to act that are specified in part 438 and to implement the provisions of part 438. We received no comments on this change and will maintain as it was proposed in this final rule. It also incorporates into § 438.726 the text of the existing § 434.22, which was cross-referenced by § 434.67(e), and which was inadvertently eliminated in the proposed changes to the regulation. Finally, there were certain ambiguities in the original regulation text which we are clarifying. In particular, § 434.67(c) was not clear with respect to who would forward the notice of sanction to the OIG at the same time it was sent to the MCO. We have clarified that it is sent by CMS. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested clarification as to which sanctions were mandatory and which were discretionary.
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(e)(1) of the Act requires, as a condition for entering into or renewing contracts under section 1903(m) of the Act, that State agencies must establish intermediate sanctions that the agency may impose on an MCO that commits one of the specified offenses in § 438.700(b). The type of sanction and the discretion to apply sanctions is generally up to the State agency. However, if it finds that an MCO has repeatedly failed to meet substantive requirements in section 1903(m) or section 1932 of the Act, or this Part, then the State must impose temporary management, must permit beneficiaries to disenroll without cause, and must notify them of the right to disenroll. See section 1932(e)(3) of the Act, and proposed §§ 438.706(b) and 438.702(a)(3). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters suggested that PIHPs and PAHPs be subject to the same sanctioning as MCOs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the suggestion. The PIHP and PAHP regulations are based on the authority under section 1902(a)(4) of the Act to provide for methods of administration that are “found by the Secretary to be necessary for * * * proper and efficient administration.” While we believe this provides the authority to establish requirements that apply to PIHPs and PAHPs, we do not believe it provides the authority to promulgate regulations that would authorize a State to impose civil money penalties, or other sanctions that are provided for by the Congress only in the case of MCOs. However, States may cover PIHPs and PAHPs under their own State sanction laws, and we encourage States to do so whenever they believe it necessary. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter requested clarification of whether the requirement for a pre-termination hearing in proposed § 438.710(b) applies if the State is terminating an MCO or PCCM contract under State authority and not the authority in § 438.708. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A State that is not relying on the authority in § 438.708 to terminate an MCO or PCCM contract should follow only the State procedures related to the authority they are exercising to terminate the MCO or PCCM contract. To the extent the State is relying on the authority under § 438.708, the State must meet the requirements for a pre-termination hearing. The State may exercise the disenrollment options provided in § 438.722 regardless of the underlying authority on which they are basing termination. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was unclear about whether the notice to CMS under proposed § 438.724(a) was required only for sanctions specified in § 438.702(a) or if it also applied to State operated penalty systems such as a progressive penalty point accumulation system. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Under § 438.724, notice to CMS is only required when a State imposes an intermediate sanction for one of the violations in § 438.700(b). To the extent the State has sanctions that it imposes for additional violations, notice to CMS is not required, but encouraged. We have added clarifying language to the regulation text. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters suggested notification to CMS was appropriate but that beneficiaries have the right to know when a plan has been sanctioned and that publication of the notice should be required in the 
                        <PRTPAGE P="41068"/>
                        regulations. These commenters recommended that the State publish a notice describing the intermediate sanction imposed, explaining the reasons for the sanction and specifying the amount of any civil money penalty. Further, this notice should be published no later than 30 days after the State imposes the sanction, and the notice should be published in the newspaper of widest circulation in each city within the MCO's service area that has a population of 50,000 or more or in the newspaper of widest circulation in the MCO's service area, if there is no city with a population of 50,000 or more in that area. Several other commenters supported limiting the notification requirements to notifying CMS noting that publication is an unnecessary expense and inconsistent with current insurance practices. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree that widespread publication would be an unnecessary expense. We also believe requiring public publication could discourage a State from imposing sanctions and could unnecessarily alarm enrollees. In addition, a State is not prohibited from publishing sanction information. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that we clarify in proposed § 438.726 that States can delegate certain functions to other entities as an acceptable way of accomplishing the goal of enrollee protection. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The State agency is ultimately responsible for implementation of the provisions of this subpart but may delegate appropriate functions to other entities as part of their process. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter indicated that it is crucial that the State's ability to delegate certain functions to other entities be explicitly recognized as an acceptable method for accomplishing the goal of enrollee protection through the use of sanctions and temporary management. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe that the regulation, as written, maintains the State's ability to delegate functions. We recognize that with the imposition of temporary management, the State may need to delegate activities to another department within the State. We have maintained flexibility for States to determine what best fits their needs. 
                    </P>
                    <HD SOURCE="HD2">H. Conditions for Federal Financial Participation (Subpart J) </HD>
                    <P>Subpart J of the proposed rule contains rules regarding the availability of Federal financial participation (FFP) in MCO contracts. In addition to setting forth recodified versions of existing regulations governing eligibility for FFP currently set forth in part 434, subpart F, the regulations in proposed subpart J reflected new provisions in the BBA affecting FFP (such as., the new restrictions on FFP in enrollment broker contracts), and set forth a proposed new limitation on FFP related to the actuarial soundness requirements in proposed § 438.6(c). </P>
                    <HD SOURCE="HD3">1. Basic Requirements (Proposed § 438.802) </HD>
                    <P>Proposed § 438.802 was based largely on the existing § 434.70, and provided that FFP is only available in expenditures under MCO contracts for periods for which (1) the contract is in effect and meets specified requirements, and (2) the MCO, its subcontractors, and the State, are in substantial compliance with specified contract requirements and the requirements in part 438. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested that we clarify what we meant by the requirement in § 438.802 that the MCO and its subcontractors be in “substantial compliance” with physician incentive plan requirements and that the MCO and the State be in “substantial compliance” with the contract and these regulations, in order to qualify for FFP. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Proposed § 438.802 was based on the existing § 434.70, which, in paragraph (b), specifically provided that FFP may be withheld for any period the MCO fails to comply with the physician incentive requirements, or the MCO or the State fail to comply with the terms of the contract between them or the provisions of this regulation. We understand the commenter's confusion regarding this requirement since this rule already requires states to monitor compliance with this rule and contracts executed under this rule and provides sanctions to be used where certain requirements are not met. Further we would expect to initiate penalties such as corrective action plans in these situations where a state is found to be out of compliance with these rules. Finally, in considering the commenter's question, we realize the difficulty in issuing useful guidance as to what constitutes “substantial compliance” for purposes of putting FFP at risk. Because we believe that the requirements on States and MCOs contained in § 438.6 and elsewhere in this rule, and the mechanisms for monitoring and enforcement are sufficiently clear, the requirement for “substantial compliance” in § 438.802 is potentially confusing and unnecessary, we have deleted it from this section. 
                    </P>
                    <HD SOURCE="HD3">2. Prior Approval (Proposed § 438.806) </HD>
                    <P>Proposed § 438.806 was based on § 434.71 (as affected by new threshold amounts for prior approval enacted in section 4708(a) of the BBA), and provided that FFP was not available in expenditures under contracts involving over a specified financial amount ($1,000,000 for 1998, adjusted by the consumer price index for future years) unless the contracts were “prior approved” by CMS. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter inquired whether § 438.806 precludes the availability of FFP for a period that a risk contract was under review by CMS, and whether the prior approval requirement applied to all MCOs or just new MCOs. If applicable to all MCOs, the commenter asked whether the FFP limitation applied to the entire amount paid or just the marginal difference from the previously approved contract amount? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The requirement for prior approval of a new contract or new contract amendment applies to all comprehensive risk contracts, whether with a new or currently contracting MCO. FFP is not available for contracts that CMS has not approved. However, once we approve a contract, FFP is available for any period during which an approvable contract was under review. The limitation on FFP in this provision must be applied to the entire contract. FFP is not available for any portions of the contract unless it is approved. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter questioned whether the requirement in § 438.806(a)(2) meant that a State would lose FFP should it not reach its quality strategy goals. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.806(a)(2) requires that the written contract with the MCO meets the requirements specified as a condition for FFP. The contract would not be approved if it did not meet all the requirements of the law and regulations, including establishing the quality assessment and performance improvement program required by § 438.240. However, this is different from the issue of the MCO's or State's performance in implementing this contractually required program. A failure on the part of an MCO or State to meet a particular quality goal would not apply to the conditions in § 438.806(a)(2). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters pointed out that the reference in § 438.806(a)(1) to entities described in § 438.6 (a)(2) through (a)(5) should instead refer to § 438.6(b)(2) through (b)(5). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We appreciate the commenters' assistance and have made the appropriate changes. 
                        <PRTPAGE P="41069"/>
                    </P>
                    <HD SOURCE="HD3">3. Exclusion of Entities (Proposed § 438.808) </HD>
                    <P>Proposed § 438.808 reflects the limitation on FFP in section 1902(p)(2) of the Act, under which FFP in payments to an MCO is conditioned on the State excluding from participation as an MCO any entity that could be excluded from Medicare and Medicaid under section 1128(b)(8) of the Act, that— </P>
                    <P>• Has substantial contractual relationship with an entity described in section 1128(b)(8)(B) of the Act. </P>
                    <P>• Employs or contracts with individuals excluded from Medicaid. We received no comments on this section. </P>
                    <HD SOURCE="HD3">4. Expenditures for Enrollment Broker Services (Proposed § 438.810) </HD>
                    <P>Proposed § 438.810 reflects the conditions on FFP for enrollment broker services set forth in section 1903(b)(4) of the Act, which was added by section 4707(b) of the BBA. This section permits FFP in State expenditures for the use of enrollment brokers only if the following conditions are met: </P>
                    <P>• The broker is independent of any managed care entity or health care provider that furnishes services in the State in which the broker provides enrollment services (regardless of whether the entity or provider participates in Medicaid). </P>
                    <P>• No person who is the owner, employee, or consultant of the broker or has any contract with the broker: </P>
                    <P>• Has any direct or indirect financial interest in any managed care entity or health care provider that furnishes services in the State in which the broker provides enrollment services. </P>
                    <P>• Has been excluded from participation under title XVIII or XIX of the Act. </P>
                    <P>• Has been debarred by any Federal agency. </P>
                    <P>• Has been, or is now, subject to civil monetary penalties under the Act. </P>
                    <P>In addition to reflecting the above statutory requirements from section 1903(b)(4), proposed § 438.812 included the following proposed requirement: </P>
                    <P>• The initial contract or memorandum of agreement (MOA) or memorandum of understanding (MOU) for services performed by the broker must be reviewed and approved by CMS before the effective date of the contract or MOA. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter felt that the proposed regulations were too broad for application in many States, and that States thus were required to create standards to ensure protective measures to support independent operations of enrollment brokers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We disagree with the commenter that the regulations are too broad. We believe that the language in section 1903(b)(4) of the Act, reflected in § 438.810, is very specific about limitations as to who can serve as an enrollment broker. A broker either is independent of “any” MCO, PIHP, or PCCM and of “any health care providers” that provide services in the State, or it is not. Similarly, a broker either does or does not have an owner, employee, consultant or contract with a person who (1) has a direct or indirect interest in an MCO, PIHP, PCCM or provider, or (2) has been excluded, debarred or subject to civil money penalties. While these standards are “broad” in their reach, this was a decision made by Congress. We do not believe that significant additional clarification is required. Moreover, § 438.810 does contain some additional clarification, in that paragraph (a) contains definitions of “choice counseling,” “enrollment activities,” “enrollment broker,” and “enrollment services.” It is not clear what additional clarification the commenter thinks would be needed. We also note that States may set rules more stringent than the Federal rules if they wish. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter questioned whether there was a conflict between § 438.208(c), which provides for health screening assessments by an enrollment broker, and § 438.810(b)(1), which requires that enrollment brokers be independent. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         There is no conflict between these two sections. The independence of enrollment brokers from MCOs, PIHPs, PCCMs and providers of services is a separate issue from the activities of the enrollment broker in assessing and screening special needs individuals. The latter activities are performed by the broker for the State, as part of its activities as an enrollment broker, and not as the agents of an MCO, PIHP, PCCM or provider. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A commenter asked whether it was CMS' intent to exclude all potential enrollment brokers who have any relationship with a health care provider, whether or not that health care provider serves the Medicaid population. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         CMS is bound by the statutory provision on enrollment brokers, and section 1903(b)(4)(A) of the Act specifically prohibits the availability of FFP for enrollment brokers who are not independent of any health care providers, “whether or not any such provider participates in the State plan under this title.” Congress presumably believed that such independence was necessary to ensure that the Medicaid enrollment process was free from even potential bias. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters noted that the independence requirement could prevent employees of a county from serving as enrollment brokers that operates an MCO, PIHP, or PCCM, or provides services or is affiliated with providers, from serving as enrollment brokers, and contended that this result would be detrimental to the enrollment process. Commenters also felt that MCOs should be able to assist in enrollments. One commenter believed that it was not feasible for States to rely only upon community-based or non-profit organizations to process enrollments. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         First, with respect to the comments on MCO involvement in enrollment, States may permit MCOs to process enrollments in their own plans. This provision only involves a State contract with an enrollment “broker” which processes enrollments in multiple plans. With respect to the issue of employees of counties that operate managed care entities or provide health care services, we believe that such an employee would not meet the statutory standard of being “independent” of such providers, and that Congress has prohibited them from serving as enrollment brokers. An enrollment broker might be a public or quasi-public entity with a contract or MOA/MOU with the State or county, as long as the entity does not furnish health care services in the State. For example, a State may not claim FFP for a contract with, or have an MOU with, a county health department to do managed care enrollment or choice counseling because the health department provides health services. A community organization that provides health services in the State, for example, an organization providing health care to homeless individuals, may contract or subcontract to perform outreach and education, but not enrollment and choice counseling functions covered by the enrollment broker provisions in section 1903(b)(4). 
                    </P>
                    <P>
                        Neither the statute nor these rules specifically address the use of non-profit or community-based organizations to fulfill the enrollment broker function, but these entities would be subject to the same requirements for independence and prohibitions on conflict of interest as any other prospective brokers. We note that the regulations also would permit for-profit enrollment brokers if they met the conditions in § 438.810. 
                        <PRTPAGE P="41070"/>
                    </P>
                    <HD SOURCE="HD3">5. Costs Under Risk and Nonrisk Contracts (Proposed § 438.812) </HD>
                    <P>Proposed § 438.812 was transferred in its entirety from previous §§ 434.74 and 434.75. It provides that States receive Federal matching for all costs covered under a risk contract at the medical assistance rate, while under a non-risk contract, only the costs of medical services are matched as medical assistance, while all other costs are matched at the administrative rate. We received no comments on this provision. </P>
                    <HD SOURCE="HD3">6. Limit on Payments in Excess of Capitation Rates (Proposed § 438.814) </HD>
                    <P>Section 438.814 proposed limitations on the availability of FFP in contracts, which contain incentive arrangement or “risk corridors.” As described in proposed § 438.6(c)(5) on rate setting for risk contracts, under this proposal, FFP was only available in contract payments to the extent they did not exceed 105 percent of the payment rate determined to be “actuarially sound.” The theory for this limitation was that rates too far in excess of those established to be actuarially sound were not actuarially sound, and therefore did not meet the condition for FFP in section 1903(m)(2)(A)(iii). </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters disagreed with the proposal to limit Federal matching at 105 percent of approved capitation rates in contracts with risk corridors. Some commenters questioned the rationale for setting the limit at 105 percent, while others questioned how it was determined that this limit would be appropriate for every contracting situation, State and contractor. Most commenters felt that the limit on risk corridors was inappropriate and arbitrary; would discourage States from using this mechanism, which the commenters felt could be an effective tool in setting rates for populations with little or no managed care experience, including the chronically ill and disabled; would prevent the State and Federal governments from sharing in profits and being protected from overpayments; and would discourage MCOs from taking the risk to cover these populations. 
                    </P>
                    <P>Other commenters pointed out that risk corridors are an important mechanism to address unforeseen costs to MCOs during contract periods from these factors as changes in case mix, enrollment patterns, utilization patterns, or provider networks, or coverage of populations with little or no managed care history. A 105 percent cap on these arrangements constrains States' flexibility to effectively address these issues without administratively cumbersome mid-year rate adjustments and could, in the commenters' view, result in over-projection of capitation rates in order to remain under the ceiling. Commenters suggested CMS either: (1) Accept an actuarial certification that the amount paid to an MCO after settlement is actuarially sound, and permit FFP for that entire amount; (2) permit a “good cause” exception to the 105 percent limit; or (3) or raise the limit to 110 percent. One commenter supported CMS' acknowledgment of risk sharing and risk corridors as acceptable payment mechanisms up to 105 percent of capitation rates. </P>
                    <P>
                        <E T="03">Response:</E>
                         We understand the commenters concerns and upon consideration of these comments, agree that the 105 percent limit on FFP on contracts, or portions of contracts with risk corridors, is too restrictive to permit the continued use of this important risk sharing mechanism. We agree that is inappropriate to place a specific percentage limitation on FFP where risk corridors are used in a contract. The purpose of this mechanism is to share both the risk and the profits between the contractor and the State (and the Federal government by virtue of its matching of State expenditures.) One potential risk that can be addressed in risk corridors is the risk of fluctuations in utilization based on the changing demographics of a population (such as, the high costs of an increased percentage of disabled enrollees.) A fixed percentage limit does not take such risks into account. In considering the commenters' concerns, we have determined that a more appropriate outer limit on the actuarial soundness of payments under a risk corridor methodology would be a limitation based on what Medicaid would spend for the specific services utilized, plus an amount to cover the managed care plan's reasonable administrative costs. Such a limit would be similar to the “non-risk upper payment limit” in § 447.362, except for the recognition of administrative costs. The reason we did not simply adopt the rule in § 447.362 is because the amount allocable to administrative costs under that section of the regulations is not based on a managed care entity's reasonable administrative costs, but rather on the amount the Medicaid agency “saves” in its administrative costs by not having to pay fee-for-service claims for the beneficiaries enrolled in the managed care plan. We believe this amount is likely to be much lower than even the administrative costs of a well run managed care organization. 
                    </P>
                    <P>Thus, we are revising the requirement in proposed § 438.814 to impose an upper limit on payments under risk corridors that is based on “what Medicaid would have paid on a fee for service basis for the services actually furnished to recipients” plus an allowance for the managed care plan's reasonable actual administrative costs. This limit reflects the fact that a risk corridor extended to its ultimate extreme would become a nonrisk contract, and that the rule governing FFP in nonrisk contracts (with the modification noted) is the most logical limit to apply. We are also moving this requirement to § 438.6(c)(5) in order to have all of the payment provisions in one subpart of this rule. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters also believe the 105 percent limit was arbitrary and inappropriate for incentive arrangements, and could discourage programs intended to achieve quality-related goals (such as increases in EPSDT services and meeting quality improvement targets). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We do not agree with commenters that the 105 percent limit is inappropriate and arbitrary for, and would discourage the use of, incentive arrangements. Under the new payment rules in § 438.6(c), capitation rates are to be established to reflect the level of State plan services to be delivered under the contract. Further, States are free to combine financial withholds and incentives for such things as quality improvement targets. Thus, we do not believe it is necessary to establish financial incentives above a level at which FFP would be available under this provision. As with the provision on risk corridors, we are moving this provision to § 438.6(c)(5). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that CMS define the term “risk corridors” as used in this section and in § 438.6(c). 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         A risk corridor is a risk sharing mechanism in which States and MCOs share in both profits and losses under the contract outside of predetermined threshold amount. The amount of risk shared under this arrangement is usually graduated so that after an initial corridor in which the MCO is responsible for all losses or retains all profits, the State contributes a portion toward any additional losses, and receives a portion of any additional profits. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked whether this provision places a limit on any and all payments and payment mechanisms that are in excess of the capitation rate, or whether there are any 
                        <PRTPAGE P="41071"/>
                        payment mechanisms which would be excepted from the cap? 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 438.6(c) sets forth the requirements for payments under all risk contracts, and requires that these payments be identified and computed on an actuarially sound basis. This requirement applies to reinsurance, stop-loss limits, or other risk sharing mechanisms. We believe that amounts payable under these other arrangements (except for incentives and risk corridors) will be offset by actuarially determined amounts in determining the capitation rate to be paid. Thus, the limit in any of these arrangements will be predetermined based on the amount of the offset or deduction from the capitation rate. Since the potential payments under these risk-sharing mechanisms are determined in this manner, the limits in this provision do not apply. Section 438.6(c) does not authorize any other payment in excess of the capitation rates. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters asked that CMS define what is included in the term “aggregate amount of approved capitation payments” as used in this section. Specifically, the commenters wanted to know whether this includes administration, profit and other expenditures. One commenter asked whether this provision applies when a State withholds a percentage of approved capitation rates and later distributes the pool of withheld funds based on some type of risk arrangement, and whether the amount of funds withheld would be considered part of the approved capitation amount, or would be capped under this provision. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The term “aggregate amount of approved capitation payments” as used in this section refers to the total amount of the capitation rates approved under the contract that are attributable to the individuals and services covered by the incentive arrangement. This would include portions of the rate intended for administration, profit or any other purposes and would be determined prior to any withhold amount being deducted. Further, the 105 percent limit applies only to those portions of a contract, which apply to the individuals or services, governed by the incentive arrangement. For example, if the contract includes provisions to withhold a portion of the capitation payments for not meeting targets for initial screenings for enrollees, neither the payments nor any withheld amounts for these services would be part of the calculation for determining any incentive payments due the plan under a separate contract provision for meeting targets for childhood immunizations. To further clarify this distinction, we have eliminated the provision in § 438.6(c)(5)(iii)(C) that required contracts with incentive arrangements to have withhold penalties for targets not met (proposed paragraphs (D), (E) and (F) have been redesignated as paragraphs (C)). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter questioned whether the 105 percent limit is to be applied in the aggregate, or is it applicable to each individual rating cell. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This would be determined by the specific arrangement under the contract. In most contracts, we would expect a target established for specific populations who may comprise their own rate cells under the contract. In this case, the limit would have to be applied to each individual or groups of cells covered by the arrangement. If the incentive applies to the entire population covered under the contract, the limit would be applied in the aggregate. 
                    </P>
                    <HD SOURCE="HD2">I. Revisions to Parts 435, 440, and 447; Miscellaneous Comments </HD>
                    <P>In addition to the provisions set forth in the new part 438 and the fair hearing provisions in part 431 discussed in section II. E. of this preamble, the proposed rule contained amendments to parts 435, 440, and 447 that we discuss below. These provisions included amendments to §§ 435.212 and 435.326 to reflect the new terminology adopted by the BBA. We also proposed a new § 440.168 in part 440 to include a description of primary care case management services. Amendments to part 447 not already addressed above include a new § 447.46(f) implementing the timely claims payment requirements in section 1932(f), and a new § 447.60 regulating MCO cost-sharing, which was made permissible under BBA amendments to section 1916 of the Act. In this section, we discuss the comments we received on the above regulations. We received no comments on the revisions to § 447.60. In this section, we also address miscellaneous comments that did not relate to a specific section of the proposed regulations. </P>
                    <HD SOURCE="HD3">1. Guaranteed Eligibility (Proposed § 435.212) </HD>
                    <P>Section 435.212 was revised in the proposed rule to implement section 1902(e)(2) of the Social Security Act. This change will permit State agencies, at their option, to provide for a minimum enrollment period of up to 6 months for individuals enrolled in a PCCM or any MCO. Previously, this option was only available to enrollees of Federally qualified HMOs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed support for this provision. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenter for the support. 
                    </P>
                    <HD SOURCE="HD3">2. Definition of PCCM Services (Proposed § 440.168) </HD>
                    <P>Section 4702 of the BBA added PCCM services to the list of optional Medicaid services in section 1905(a) of the Act. The BBA also added section 1905(t) to the Act. This subsection defines PCCM services, identifies who may provide them, and sets forth requirements for contracts between PCCMs and the State agency. This means that in addition to contracting with PCCMs under a section 1915(b) waiver program or section 1115 demonstration project, or under the new authority in section 1932(a)(1) to mandate managed care enrollment, States may add PCCMs as an optional State plan service. Regardless of the vehicle used, proposed § 438.6(k) set forth the minimum contract requirements States must have with their primary care case managers. </P>
                    <P>Proposed § 440.168(a), implementing section 1905(t)(1) of the Act, defined “primary care case management services” as case management related services that include locating, coordinating and monitoring health care services, and that are provided under a contract between the State and a primary care case manager. A PCCM was defined as including either (1) an individual physician (or, at State option, a physician assistant, nurse practitioner, or certified nurse-midwife), or (2) a group practice or entity that employs or arranges with physicians to furnish services. Proposed § 440.168(b) provided that PCCM services may be offered as a voluntary option under the State plan, or on a mandatory basis under section 1932(a)(1) or under a section 1115 or section 1915(b) waiver. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter disagreed with the language designating it a “State's Option” to qualify nurse practitioners as PCCM providers. The commenter believes nurse practitioners should be recognized as PCCM providers by the Medicaid program. It is critical that CMS ensure that Medicaid beneficiaries have the option to choose a nurse practitioner as their PCCM provider. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The definition of a primary care case manager in § 438.2 of this part mirrors the statutory language in section 1905(t)(2) of the Act. The statute is clear that there are two categories of PCCMs. The first category is PCCMs that are physicians or physician groups, or that employ or arrange for the provision of physician services. The definition of a physician does not include a nurse 
                        <PRTPAGE P="41072"/>
                        practitioner. (See sections 1905(a)(5)(A) and 1861(r)(1) of the Act.) The second category is non-physicians who are included as PCCMs “at State option.” The statute expressly provides for nurse practitioners to be PCCMs “at State option.” 
                    </P>
                    <HD SOURCE="HD3">3. Timely Claims Payment by MCOs (Proposed § 447.46) </HD>
                    <P>Section 1932(f) of the Act specifies that contracts with MCOs under section 1903(m) must provide that, unless an alternative arrangement is agreed to, payment to health care providers for items and services covered under the contract must be made on a timely basis, consistent with the claims payment procedures described under section 1902(a)(37)(A) of the Act. Section 1902(a)(37)(A) of the Act requires that 90 percent of claims for payment (for which no further written information or substantiation is required in order to make payment) made for covered services provided by health care providers are paid within 30 days of receipt, and that 99 percent of the claims are paid within 90 days of receipt. These requirements were included in proposed § 447.46. We received no comments on this section. </P>
                    <HD SOURCE="HD3">4. Miscellaneous Preamble Comments </HD>
                    <HD SOURCE="HD3">a. Effective Date of the Final Rule </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters offered suggestions for the effective date and timeframe for implementation of the final rule. The commenters urged CMS to provide an adequate opportunity for MCOs and States to come into compliance with the regulation following its effective date as implementation will require both States and MCOs to make substantial changes to contracts, waivers, and other State procedures. One commenter recommended that the effective date be 180 days after the State's MCO contract renewal date following publication of the final rule. A few commenters recommended that States be given 2 years to come into compliance with the final rule. Several other commenters recommended that a full year be given for all contracts, regardless of their renewal date, to come into compliance with the final rule. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We agree with the commenters that adequate time needs to be given for implementation of this final rule. Therefore, we have established that the final regulation will become effective 60 days post publication, and must be fully implemented by 1 year from the effective date of the regulation. This would allow new provisions to be implemented without forcing States to amend contracts in mid-term, although States would have the option to implement portions of the regulation in the interim period. 
                    </P>
                    <HD SOURCE="HD3">b. Violation of APA </HD>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters contended that the August 20, 2001 proposed rule did not comply with the Administrative Procedure Act (APA) as interpreted by the Supreme Court in 
                        <E T="03">Motor Vehicle Manufacturers Assoc.</E>
                         v. 
                        <E T="03">State Farm Mutual Automobile Ins. Co.</E>
                        , 463 U.S. 29 (1983). Specifically, the commenters suggested that we did not comply with the requirement in that case that agencies supply reasoned analysis in support of a change in policy. The commenters also quoted the U.S. Court of Appeals for the District of Columbia's decision in 
                        <E T="03">National Black Media Coalition</E>
                         v. 
                        <E T="03">FCC</E>
                        , 775 F.2d 342, 356 n. 17 (D.C. Cir. 1985) for the proposition that “an agency may not repudiate precedent simply to conform with shifting political mood,” and that “the agency must demonstrate that its new policy is consistent with the mandate with which the Congress has charged it.” In citing these cases, these commenters were comparing the regulations in the August 20, 2001 proposed rule, to those in the January 19, 2001 final rule that never took effect. The commenters believe that we were required in the proposed rule to explain any differences between the rules proposed in the August 2001 proposed rule and those published on January 19, 2001 and find support in “the rulemaking record” for any such differences. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The cases cited by the commenters concern changes made to existing regulations. In those cases, regulations had been published and taken effect, and the agencies were making changes to existing regulations. In this case, as noted in the previous comment, the effective date of the January 19, 2001 final rule was delayed, and those regulations had never taken effect. Thus, there are no “existing regulations” in part 438 that this proposed rule would “change.” Rather, the existing regulations governing Medicaid managed care are the regulations in part 434 which predate the earlier rulemaking that led to the January 19, 2001 final rule. We believe that the preamble to the proposed rule clearly articulates our reasons for proposing changes to these existing part 434 regulations. Most of the major changes in the proposed rule implement, or are based on, Medicaid managed care provisions in the Balanced Budget Act of 1997 (BBA), which was enacted after the existing part 434 regulations were promulgated. When we proposed changes in policy not directly based on BBA provisions, the preamble explains the basis for the policy choice made, including discussion of inadequacies in the part 434 regulations, when appropriate.
                    </P>
                    <P>We note that, while not required to do so by the cases cited by the commenters, we did explain in the preamble our rationale for the departures in this proposed rule from the approach taken in the January 19, 2001 regulations. We indicated that in developing this proposed rule, we were “guided by several considerations” set forth in detail in the preamble. (See 66 FR 43616.) For example, we indicated that the proposed rule was designed to recognize that Medicaid is a “Federal-State partnership” under which “States are assigned the responsibility of designing their State programs” and need the flexibility to “employ different approaches to achieving the same goal within their varying State marketplaces and health care delivery systems.” We also noted “new advances and findings in health care, health quality assessment and improvement” that “unfold on an almost daily basis,” and noted that regulations containing too rigid a structure are not able to adapt to these changes. The extent to which some aspects of the proposed rule differed from those in the January 19, 2001 rule is attributable to our reassessment, described above.</P>
                    <HD SOURCE="HD3">c. Applicability of BBA Provisions and Other Parts of This Final Rule To Waiver Programs </HD>
                    <P>Section 4710(c) of the BBA specifies that the requirements in sections 4701 through 4710 do not affect the terms and conditions of any demonstration projects or waiver programs approved by the Secretary under the authority of sections 1115 or 1915(b) of the Act. We have consistently interpreted this to be a “grandfather” provision that applies only to waivers or demonstration projects that were in effect, or already approved, as of August 5, 1997, the date of enactment of the BBA. Thus, when the waiver or demonstration project expires, the grandfather provision in section 4710(c) no longer applies. </P>
                    <P>
                        Under section 4710(c), the grandfather provision applies to the “terms and conditions” of a waiver. Any provisions of a State's section 1115 demonstration project or section 1915(b) waiver program that were specifically addressed in the State's waiver proposal, statutory waivers, special terms and conditions, operational protocol, or other official State policy or procedures approved by us, are 
                        <PRTPAGE P="41073"/>
                        considered to be the “terms and conditions” of the waiver. To the extent the terms and conditions of the State's approved waiver program covered the same subject matter as any of the BBA requirements, that portion of the State's program would not have to comply with the BBA until the waiver expired. For example, if the State's waiver program included enrollment and disenrollment rules, the enrollment and disenrollment rules in section 1932 of the Act would not apply while the waiver was still in effect. For any part of the State's Medicaid managed care program that was not within the scope of the waiver, the BBA provisions applied immediately, with certain exceptions specified below, dealing with newly submitted or amended waivers. 
                    </P>
                    <P>As noted above, under our interpretation, the exemption from the BBA requirements applied to section 1915(b) waiver programs only until the date that the waiver authority that was approved or in effect as of August 5, 1997 expired. Because none of those waivers exceeded two years, all of them expired no later than 1999. After the waiver expired, the State was required to comply with all BBA requirements. Similarly, in the case of section 1115 demonstration projects, the “grandfather” provision in 4710(c) only applies until the demonstration expires, as established by the expiration date that appears in the waiver documents that were approved or in effect on August 5, 1997. However, section 1115(e) of the Act provides a State with a statutory right to extend any waiver previously approved under 1115(a), on the same “terms and conditions,” unless the Secretary specifically disapproves the extension. This extension can be for up to three years. As long as the State applies for an extension under section 1115(e) while its demonstration project is still subject to the “grandfather” provision described above, the statutory requirement that the waiver continue under the “same terms and conditions” means that those waiver provisions cannot be subject to the BBA requirements until the extension expires. The Medicare, Medicaid, and State Child Health Insurance Program Benefits Improvement and Protection Act of 2000 (BIPA), enacted on December 21, 2000 (Pub. L. 106-554) added section 1115(f) of the Act, to provide for additional extensions of section 1115 health care reform demonstrations. Unlike section 1115(e), section 1115(f) does not require that the demonstration project be extended under the same terms and conditions, providing, instead, for the negotiation of new terms and conditions. Therefore, unless the Secretary uses his discretionary authority to waive the requirements, as explained below, the BBA requirements apply to all demonstration projects approved under section 1115 except during the “grandfather” period and any subsequent extension under section 1115(e)(2). </P>
                    <P>For newly submitted or amended section 1115 waivers, the Secretary of DHHS retains the discretionary authority to exempt the State from specific BBA managed care provisions. Generally, exemptions are granted to allow States some flexibility in operating their Medicaid programs, while promoting the proper and efficient administration of a State's plan. However, particularly for those BBA provisions related to increased beneficiary protections and quality assurance standards, we anticipate that we would not approve an exemption unless a State can demonstrate that the waiver program has beneficiary protections or quality standards that would equal or exceed the BBA requirements. </P>
                    <P>In addition, the Secretary may use his discretionary authority (to the extent permitted by the specific waiver provision) to waive other requirements in this rule which do not implement provisions of the BBA, such as the new rate setting requirements, requirements that apply to PIHPs and PAHPs, and requirements that were redesignated from part 434 or other parts of 42 CFR. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters questioned the applicability of these rules to waiver programs. One commenter wanted CMS to confirm the belief that the proposed rule does not apply to States with current section 1115 demonstrations, while another wanted CMS to specify in the text of final rule that these regulations do not apply to waiver programs under section 1115 or 1915(b), to be consistent with section 4710(c) of the BBA. Another commenter supported CMS' decision to apply the final rule to both new and renewed section 1115 and 1915(b) waivers. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As stated in the proposed rule and reiterated above, section 4710(c) of the BBA is time-limited, has expired for all section 1915(b) waiver programs, and only applies to section 1115 health care reform demonstrations during the period of approval that was in effect as of August 5, 1997 and any 3-year extension periods granted under the authority in section 1115(e)(2) of the Act. We disagree with the suggestion that the provisions of this part should never apply to programs conducted under these waivers. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked that CMS grant States flexibility in applying these rules through 1915(b) waivers, but another commenter opposed the decision to consider granting any new waivers of these requirements. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         As indicated above, waiver authorities in section 1915(b) and 1115 remain in effect. If a State requests a waiver in order to implement an alternative approach for its Medicaid program that requires a waiver of provisions contained in this rule, while maintaining necessary beneficiary protections and meeting the specific requirements of the waiver authority requested, we may grant the waiver. We believe granting these waivers reflects the intent of the Congress which did not modify or limit the authority in either of these waiver provisions. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked to what extent the provisions in this rule apply to section 1915(c) waiver programs. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         To the extent any provisions of these rules are relevant to the contract requirement, payment mechanisms, enrollment, or any other aspect of a program operating under a section 1915(c) waiver authority, the requirements apply. While we do not believe that most current 1915(c) programs would be subject to any of these requirements, any program operating under a combined 1915(b) and (c) authority which includes such things as an enrollment lock-in period, a capitated reimbursement methodology, or a provider that qualifies as a PAHP, would have to comply with the provision of this final rule as applicable. 
                    </P>
                    <P>See section II.E. of this preamble for further discussion regarding the applicability of the BBA requirements to States with waivers.</P>
                    <HD SOURCE="HD3">d. Education of MCOs, PIHPs, PAHPs, and PCCMs About Special Health Care Needs</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Many commenters believe that there should be language stating that the “State agency must have in effect procedures for educating MCOs, PIHPs, PAHPs, PCCMs, and any subcontracting providers about the clinical and other needs of enrollees with special health care needs.” The commenters stated that this is an essential way for the State to ensure that health plans, that have not traditionally served Medicaid enrollees or enrollees with special health care needs, understand those needs. Another commenter stated that managed care must be sensitized to the needs of special needs beneficiaries, for whom 
                        <PRTPAGE P="41074"/>
                        disruptions in service and impediments to access can be serious. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While we understand the need for awareness of special health care needs, we want to give States the flexibility to decide at what level this should happen. Many States may not have the capability or feel that it is appropriate for the State to provide education to MCOs, PIHPs, PAHPs, PCCMs, and providers on what is often a clinical issue. Public health departments and local medical societies are often doing this type of work in the State.
                    </P>
                    <HD SOURCE="HD3">e. Miscellaneous Comments </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters applauded CMS for amending the Medicaid managed care regulations with the proposed rule published on August 20, 2001. Commenters appreciated that the proposed regulation removed much of the prescriptiveness of the requirements and acknowledged the expertise and work that continues at the State level. Most commenters were pleased to see a renewed emphasis on State flexibility. The proposed rule changed the focus from detailing how States and MCOs should operate to laying out the basic requirements for Medicaid managed care and allowing States the authority to implement them in a manner appropriate for each State. Further, commenters stated that the new rule simplified many of the provisions and eliminated redundancy so that requirements are stated only once. Commenters believe that the simplification of the regulation and removal of duplicative and redundant provisions will help States to accurately interpret, follow, and enforce this regulation. 
                    </P>
                    <P>Other commenters stated that the proposed rule will permit innovation and support program growth under standards that respond to the needs of the full spectrum of enrollees and implementation of the January 2001 rule would have seriously undermined the availability of the benefits of MCOs to Medicaid beneficiaries. Another commenter believes that removal of much of the highly detailed language contained in the January 2001 rule will enhance the ability of both the Federal and State governments to exercise responsibilities as purchasers and regulators effectively. Further, States have proven their ability to innovate in the quality arena and will continue to strive towards providing the highest quality care to Medicaid beneficiaries. Several other commenters noted that the proposed rule is a significant improvement over the rules published in January 2001, many provisions of which would have significantly raised health plan compliance costs without meaningfully improving patient care. One commenter urged immediate implementation of the proposed rule. </P>
                    <P>
                        <E T="03">Response:</E>
                         We thank the commenters for their support. We will continue to work with States during the implementation period of the final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous commenters expressed their dissatisfaction with the proposed rule published on August 20, 2001. These commenters strongly support the immediate implementation of the January 19, 2001 final rule. Most of these commenters stated that the January rule reflected a true balance between providing States additional flexibility and providing Medicaid beneficiaries, including those with disabilities, the protections they need to ensure that Medicaid managed care meets their needs; that the revised proposed rule and the accompanying delays in implementation demonstrate that the Administration is more attuned to the desires of the States and managed care industry than to the needs of the people who are supposed to benefit from the Medicaid program; that the proposed rule pays too little attention to the special needs of children and adults with mental retardation and other disabilities. These commenters believe that the January rules establish important new protections for beneficiaries with respect to access to care, grievance and appeal procedures, and mandatory enrollment requirements. 
                    </P>
                    <P>
                        Other commenters stated that more specific requirements are warranted related to transitioning children into and out of managed care, and the identification, screening and assessment of children with special health care needs. Some commenters urged CMS to strengthen the proposed rule to ensure safeguards for children with special health care needs, consistent with the waiver criteria for children with special health care needs. These commenters also called upon CMS to incorporate the recommendations of the Department's November 2000 Report to the Congress entitled 
                        <E T="03">“Safeguards for Individuals with Special Health Care Needs Enrolled in Medicaid Managed Care”</E>
                         into the regulation. 
                    </P>
                    <P>Another commenter expressed concern that many provisions of the proposed rule do not provide adequate protections for consumers of mental health and substance abuse services enrolled in managed care plans through the Medicaid program. The commenter further suggested that the proposed rule unjustifiably undermines the consumer safeguards established in the January 2001 final rule. Another commenter specified that the proposed rule represents a profound failure to implement the statutory provisions of the BBA and does not provide even basic patient protections. These commenters urged CMS to reinstate many aspects of the January rule, which they believe better effectuate the BBA. Many other commenters believe that if the proposed rule is implemented it will be extremely harmful to Medicaid beneficiaries with special health care needs, including people living with HIV/AIDS. </P>
                    <P>
                        <E T="03">Response:</E>
                         In development of the proposed and final rules we gave serious attention to all of the concerns raised to us. We believe the final rule reflects the path chosen by the Congress to strike an appropriate balance between State flexibility and beneficiary protections. We believe that this final rule reflects that balance and appropriately implements the beneficiary protections established by the BBA. We believe all commenters have expressed the same goal, namely: strong, viable, State Medicaid managed care programs that deliver high quality health care to Medicaid beneficiaries. We believe that the final rule will help States achieve this goal. The Congress drafted the statute in full recognition of the Medicaid program as a Federal-State partnership and we share that recognition. States are assigned the responsibility of designing their State programs. We drafted this regulation to recognize the responsibilities of the States and the need to employ different approaches to achieving the same goal within their State marketplaces and health care delivery systems. We heard from some key stakeholders in Medicaid managed care, including States, provider organizations, and advocates for beneficiaries. Some of these stakeholders expressed serious concerns about the regulation, including changes made to the January 2001 final rule that had not been included in the September 1998 proposed rule. Other stakeholders strongly supported the January 2001 final rule and urged us to continue with implementation. We decided that the best approach was to make some modifications to the January 19, 2001 final rule and republish it as a proposed rule in order to give everyone the opportunity to comment on all of the provisions. 
                    </P>
                    <P>
                        We believe we have created a set of requirements that appropriately balances the necessary protections for all beneficiaries enrolled in Medicaid managed care plans, including individuals with special health care needs, and States' flexibility to manage 
                        <PRTPAGE P="41075"/>
                        their managed care programs. We have not reduced the emphasis on requiring States to provide high quality care to beneficiaries, especially those with special needs. The rule requires States to identify managed care enrollees with special needs to make sure that they will receive appropriate access to quality care. States retain the flexibility to develop these mechanisms and define the special needs populations. This approach enables States to better target their Medicaid resources to those most in need. We believe this is a far more efficient approach than imposing regulatory burdens that may not have their intended effects. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern that the August 20, 2001 proposed rule did not contain important regulatory language that was included in the 1998 proposed rule supportive of protections for the mentally ill in Medicaid managed care. The commenter pointed out that a number of its recommendations were not included and the commenter requests an explanation for these negative decisions. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation, as now written, is intended to address the needs of, and protections for, all Medicaid beneficiaries in managed care, including persons with disabilities and those who suffer from mental illness. The regulation is written in a manner to establish a general framework for States to use when developing managed care programs to serve all of its enrolled populations. Therefore, we do not believe it is necessary to list specific medical conditions within the regulation text. As far as comments received on the September 28, 1998 proposed rule, responses to all of the comments and rationale for changes can be found in the January 19, 2001 final rule preamble. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A few commenters, while supportive of the fact that CMS delayed implementation of the January 2001 final rule and then made substantial revisions in the August proposed rule, were still concerned that the proposed rule will increase the cost and administrative burden associated with Medicaid managed care. The commenters believe that health plans serving members other than Medicaid beneficiaries will be placed at a disadvantage. The commenters also urged CMS to take steps to encourage commercial plans and providers to participate in Medicaid managed care programs and to regulate the program in a manner that allows States to continue moving forward with managed care. Another commenter expressed concern regarding the overall impact on access, quality of care and cost effectiveness of applying the regulations to specialty mental health programs. And to the extent CMS does not provide more flexibility to States in these regulations, it should seriously consider providing reasonable flexibility to States in the section 1915(b) waiver process. Another commenter stated that the speed with which these rules have been rewritten has lead to a proposed rule that shows a lack of clarity and careful consideration. The regulatory process did not provide for adequate participation by the States with the knowledge and experience to help draft effective and efficient rules for managed care. The commenter urged CMS to involve State representatives in a final rewrite of the rule. In addition, when considering the imposition of every new administrative requirement, CMS needs to be cognizant that each of those requirements costs the States' increasingly limited resources that could better be focused on provision of care. Further, every new requirement on MCOs and providers can affect their continued participation in managed care. Another commenter advised CMS to keep in mind that as regulations are designed with particular focus on enrollee protections, it is critical to keep in mind that overly prescriptive requirements that shift potentially unnecessary administrative costs and burdens to plans and providers may result in the unintended consequence of provider and/or plan withdrawal from the Medicaid program. This could then lead to impeded access to quality care for vulnerable populations. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         The regulation was developed to provide States with an appropriate level of flexibility that we believe to be consistent with necessary beneficiary protections. 
                    </P>
                    <P>State flexibility had to be balanced against the statutory requirements of the BBA. Further, the regulation has been designed to provide a framework that allows CMS and States to continue to incorporate further advances for oversight of managed care, particularly as they pertain to beneficiary protection and quality of care. We recognize that States are unique and have different needs for their enrolled populations. This final rule was designed to promote State flexibility as much as possible so that States can implement managed care programs that meet the needs of their beneficiaries. With respect to MCO and provider participation, we further believe that the new rate-setting provisions will allow States to set rates that more appropriately reflect the costs of health services for the variety of Medicaid populations served, especially those with special health care needs. </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that changes should be made to the proposed rule to ensure that providers are compensated in a timely manner, so they can continue to provide needed services to low-income patients. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         Section 1932(f) of the Act specifies that contracts under 1903(m) must provide that, unless an alternative arrangement is agreed to, payment to health care providers for services covered under the contract be made on a timely basis, consistent with the claims payment procedures described under section 1902(a)(37)(A) of the Act. These procedures require that 90 percent of claims for payment (for which no further written information or substantiation is required in order to make payment) made for services covered under the contract and provided by health care providers are paid within 30 days of receipt, and that 99 percent of the claims are paid within 90 days of receipt. These requirements are included in § 447.46. We do not believe that additional changes need to be made. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that the proposed rule does not take into consideration the frontier nature of some States. Many of the provisions would be difficult to meet even for the non-Medicaid population. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We believe this final rule affords States the flexibility to implement these requirements for Medicaid managed care in all areas of their State. Further, the final rule provides for an exception to the choice requirements (§ 438.52) for residents in rural areas. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that these rules continue to require monitoring and oversight on issues that would result in higher requirements for Medicaid enrollees than for fee-for-service Medicaid or the general population. The commenter noted that it remains a distressing tendency to enforce things for managed care that are not enforced for the fee-for-service population. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         While CMS agrees that beneficiary protections are also important for beneficiaries receiving care under fee-for-service arrangements, this rulemaking implements Chapter 1 of Subtitle H of the BBA, titled “Managed Care.” These statutory provisions do not apply to fee-for-service Medicaid, and cannot be extended to fee-for-service arrangements in this final rule. However, States do have the flexibility to develop beneficiary protections similar to those presented in this regulation for those still receiving care through fee-for-service. States may establish similar 
                        <PRTPAGE P="41076"/>
                        standards that can be monitored on the same scale as those standards established for Medicaid managed care. We agree that it is important to recognize that beneficiaries are afforded additional assistance in managed care than may be afforded in fee-for-service. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that when establishing protections for Medicaid managed care beneficiaries, CMS should recognize that oral health is an inseparable part of an individual's overall health and the formation of an effective Medicaid dental delivery system is just as important as the creation of an adequate Medicaid medical delivery system. The commenter stated that all dental patients, whether they are in private plans, Medicaid fee-for-service or any Medicaid managed care arrangement, deserve equal access to health services and equal protections under the law. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the importance of oral health and the importance of serving the dental needs of the Medicaid population. The final rule is designed to address access issues related to all Medicaid managed care services. For example, an MCO or PAHP that delivers dental services to Medicaid beneficiaries must comply with the access requirements in this regulation. The MCO or PAHP must ensure that it offers an appropriate range of services and that it maintains a network of providers that is sufficient to meet the needs of enrollees. Further, each State must ensure that all of the covered services are accessible for all beneficiaries enrolled. We are also optimistic that managed care will facilitate increased utilization in the area of dental services. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter expressed concern regarding some of the regulatory provisions, as they may pose or have a different effect in the territories, particularly since Medicaid funds are capped. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We recognize the commenter's concern, however territories are required to meet all Medicaid requirements except for provisions specified in Federal law and regulation. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that none of the Medicaid managed care rules has included any discussion of the need for State Medicaid programs to develop incentives for physicians to participate in Medicaid managed care plans. The commenters specified that lack of sufficient physician participation may pose a significant barrier to high quality care for Medicaid beneficiaries. Development of incentives for physician participation should be a central issue for Federal and State governments as they design, implement and evaluate managed care programs. One commenter recommended that State agencies be required to consult with State medical societies early on in the process of designing Medicaid managed care programs and continue to seek input from the physician community throughout implementation. The commenter cited a recent report from the American Academy of Pediatrics that concluded “in order to ensure that expanding insurance coverage for children translates into viable access to care, States must provide incentives for pediatricians to extend their resources to serve new Medicaid and SCHIP enrollees.” 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         We realize that physician consultation is an important factor in the development of Medicaid managed care initiatives and encourage stakeholder input at all stages of managed care development. However, we are not specifically requiring stakeholder involvement since States, based on the uniqueness of their Medicaid managed care programs, are in the best position to determine how this involvement should be structured. Each State is required to have a Medical Care Advisory Committee (MCAC) established for the purpose of advising the Medicaid agency about health and medical services. This committee, by regulatory definition, is required to include physicians. We encourage States to continue to use the MCAC as a mechanism for obtaining input on managed care issues. Likewise, under § 438.202, we require public consultation in development of the State's quality strategy. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter disagreed with the deletion of the requirement that no more than 75 percent of enrollees in risk contracts be eligible for Medicare or Medicaid. 
                    </P>
                    <P>
                        <E T="03">Response:</E>
                         This change was made by the Congress in the BBA, and we thus had no discretion in this rulemaking to retain it. We note that this requirement was previously used as a rough “proxy” to ensure quality services by requiring that an MCO attract commercial consumers. This “proxy” has been replaced in the BBA with more direct quality requirements implemented in this final rule. 
                    </P>
                    <HD SOURCE="HD1">III. Summary of Changes to the Proposed Rule </HD>
                    <P>For reasons discussed above in the preamble, we have made the following changes to the proposed rule: </P>
                    <PART>
                        <HD SOURCE="HED">PART 431—STATE ORGANIZATION AND GENERAL ADMINISTRATION </HD>
                        <HD SOURCE="HD2">Section 431.200 </HD>
                        <P>We have added language to include PAHP actions to suspend, terminate, or reduce services such as those that would result in access to the State fair hearing. </P>
                        <HD SOURCE="HD2">Section 431.220 </HD>
                        <P>We have included a new paragraph (a)(6) requiring that any PAHP enrollee who has an action must be granted the opportunity for a State fair hearing. </P>
                        <HD SOURCE="HD2">Section 431.244 </HD>
                        <P>We have added language in paragraph (f)(1)(i) to specify that the 90-day timeframe for resolution of the State fair hearing begins the date the enrollee filed an MCO or PIHP appeal, not including the number of days the enrollee took to subsequently file for a State fair hearing. In paragraph (f)(1)(ii) we clarify the regulation text to State that if permitted by the State, the date the enrollee filed for direct access to a State fair hearing. </P>
                        <P>In paragraphs (f)(2) and (f)(3) we have changed the limit for appeals of a denial of service by an MCO or PIHP 72 hours to three working days. </P>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 438—MANAGED CARE PROVISIONS </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—General Provisions </HD>
                            <HD SOURCE="HD2">Section 438.1 </HD>
                        </SUBPART>
                        <P>In paragraph (b), we have included PIHPs in the scope of contracted entities provided in part 438. </P>
                        <HD SOURCE="HD2">Section 438.2 </HD>
                        <P>We moved the definition of “health care professional” from § 438.102 to § 438.2, as it applies to all of part 438. </P>
                        <P>We have clarified the definition of “health insuring organization” to reflect language in section 1932(a)(3) of the act. </P>
                        <HD SOURCE="HD2">Section 438.6 </HD>
                        <P>In paragraph (c)(3)(ii), we have added language to clarify that we are referring to data factors such as medical trend inflation, incomplete data, and MCO, PIHP, or PAHP administration. </P>
                        <P>In paragraph (c)(4)(ii), we have added language to clarify that payment rates are based only upon services covered under the State plan, or costs directly related to providing these services (such as, MCO, PIHP, or PAHP administration.) </P>
                        <P>
                            We removed proposed § 438.6(c)(5)(ii) that referred to limitations on payment for risk corridors and incentive arrangements in proposed § 438.814. We 
                            <PRTPAGE P="41077"/>
                            added new paragraph c)(5)(ii), which contains revised limitations on payment for risk corridors. 
                        </P>
                        <P>We added a new paragraph c)(5)(iii) that contains the payment limitations for incentive arrangements that were originally in proposed § 438.814. </P>
                        <P>We have redesignated proposed paragraph (c)(5)(iii) as (c)(5)(iv). </P>
                        <P>We have removed proposed paragraph (c)(5)(iii)(C), which required that for all incentive arrangements, the contract must provide that the arrangement is designed to include withholds or other payment penalties if the contractor does not perform the specified activities or does not meet the specified targets. </P>
                        <P>We have included a new paragraph (c)(5)(v) to require that if a State makes payments to providers for graduate medical education costs under an approved State plan, the State must adjust the capitation rates to account for the aggregate amount of the graduate medical education payments to be made on behalf of enrollees covered under the contract. </P>
                        <P>We have included a new paragraph (i)(2) specifying that all PAHP contracts must also provide compliance with the advance directive requirements if the PAHP includes, in its network, any of those providers listed under requirements on advance directives in § 489.102(a). </P>
                        <HD SOURCE="HD2">Section 438.8 </HD>
                        <P>We have made revisions in paragraph (b)(1) to specify that PAHPs must meet the contract requirements of § 438.6, except for those that pertain to HIOs and the requirements for advance directives unless the PAHP includes any of the providers listed in § 489.102. </P>
                        <P>We have revised paragraph (b)(6) to require PAHPs to meet all designated portions of subpart D (Quality Assessment and Performance Improvement). </P>
                        <P>We have added a new paragraph (b)(7) to specify that PAHP enrollees have the right to a State fair hearing under subpart E of part 431 (State Organization and General Administration). </P>
                        <HD SOURCE="HD2">Section 438.10 </HD>
                        <P>We have added paragraph (b)(2) requiring that the State must have in place a mechanism to help enrollees and potential enrollees understand the State's managed care plan. We also added paragraph (b)(3) requiring each MCO and PIHP to have in place a mechanism to help enrollees and potential enrollees understand the requirements and benefits of the plan. </P>
                        <P>We have revised paragraph (c)(2) to require that the State must make available written information in each prevalent non-English language. </P>
                        <P>In paragraph (f) we rephrased the introductory language to require that information be furnished to MCO, PIHP, PAHP, and PCCM enrollees. In paragraph (f)(1) we have added language to clarify that for those States that choose to restrict disenrollment for periods of 90 days or more, notice of the enrollees disenrollment rights must be sent no less than 60 days before the start of each enrollment period. In paragraphs (f)(2) and (3) we now include references to paragraphs (g) and (h) of this section to specify the information certain enrollees have a right to request and obtain at least once a year. </P>
                        <P>We have included, in paragraph (f)(4) that the State, its contracted representative, or the MCO, PIHP, PAHP, or PCCM must give each enrollee written notice of any change that is deemed significant in the specified information in paragraphs (f)(6) of this section and paragraphs (g) and (h) of this section, if applicable. </P>
                        <P>In paragraph (f)(6) we have clarified that the information in this section must be provided by the State, its contracted representative, or the MCO, PIHP, PAHP, or PCCM. We have revised paragraph (f)(6)(i) to clarify that information on the names, locations, telephone numbers of, and non-English languages spoken by current contracting providers in the enrollees service area, including identification of providers that are not accepting new patients be provided to all enrollees. For MCOs, PIHPs, and PAHPs this includes, at a minimum, information on primary care physicians, specialists and hospitals. Further, in paragraph (f)(6)(iv) we add that for PAHP enrollees, the information specified in § 438.10(h) must be provided. </P>
                        <P>We have revised paragraph (g)(3) to provide that detailed information of physician incentive plans is available upon request. </P>
                        <P>We have added a new paragraph (h) that requires specific information that must be provided for PAHP enrollees. The State, its contracted representative, or the PAHP must provide information to their enrollees on the right to a State fair hearing, including the right to a hearing, the method for obtaining a hearing, and the rules that govern representation. In paragraph (h)(2), we have specified that information must be provided on advance directives, as set forth in § 438.6(i)(2) and in paragraph (h)(3) that, upon request, information must be provided on physician incentive plans as set forth in § 438.6(h). We have redesignated the previous paragraph (h) as paragraph (i) in the final rule. </P>
                        <P>We have clarified in paragraph (i)(2)(i) the timeframes for when information must be furnished to all enrollees of a State plan program under § 438.50. For these enrollees, the timeframe is annually and upon request and for potential enrollees within the timeframe specified in § 438.10(e)(1). In paragraph (i)(3), we have clarified that the information provided is only for each contracting MCO or PCCM in the potential enrollee and enrollee's service area. Finally, in paragraph (i)(3)(v), we have removed reference to disenrollment rates as defined by the States as information that must be included. </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart B—State Responsibilities </HD>
                            <HD SOURCE="HD2">Section 438.60 </HD>
                        </SUBPART>
                        <P>We have included language allowing for payment exceptions when the State has adjusted the capitation rates paid under the contract, in accordance with § 438.6(c)(5)(v), to make payments for graduate medical education. </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart C—Enrollee Rights and Protections </HD>
                            <HD SOURCE="HD2">Section 438.100 </HD>
                        </SUBPART>
                        <P>We have moved paragraph (b)(3)(iii) regarding requests for medical records to new paragraph (b)(2)(vi). We have revised paragraph (b)(3) to specify that an enrollee of an MCO, PIHP, or PAHP (consistent with the scope of the PAHP's contracted services) has the right to be furnished health care services in accordance with §§ 438.206 through 438.210. We have removed paragraph (b)(3)(ii), regarding the right to obtain a second opinion. </P>
                        <HD SOURCE="HD2">Section 438.102 </HD>
                        <P>We have moved the definition of health care professional to § 438.2. </P>
                        <HD SOURCE="HD2">Section 438.104 </HD>
                        <P>We have revised paragraph (b)(1)(iv) to clarify that the requirement regarding the sale of other insurance applies to “private” insurance. </P>
                        <P>In paragraphs (b)(2) and (c) we have corrected cross-references to paragraphs (e) and (f) of § 438.10. </P>
                        <HD SOURCE="HD2">Section 438.114 </HD>
                        <P>
                            In paragraph (a) we have removed references to § 422.113(b) and (c) and included the full text of definitions of emergency medical condition, emergency services and post-stabilization care services. In paragraph (d)(1)(ii) we have revised language to specify that entities may not refuse to 
                            <PRTPAGE P="41078"/>
                            cover emergency services based on the emergency room provider, hospital, or fiscal agent not notifying the enrollee's primary care provider, MCO, or applicable State entity of the enrollee's screening and treatment within 10 days of presentation for emergency services. 
                        </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart D—Quality Assessment and Performance Improvement </HD>
                        </SUBPART>
                        <P>In subpart D, §§ 438.200, 438.206, 438.207, 438.208, 438.210, 438.214, 438.224, 438.230, and 438.236 have been amended by adding PAHPs to allow this network to have the same services. </P>
                        <HD SOURCE="HD2">Section 438.202 </HD>
                        <P>In paragraph (b) we replaced the words “provide for” with “obtain” and the words “including making” to “and make.” In paragraph (c) we replaced the word “compliance” with the words “The MCOs, PIHPs, and PAHPs comply.” </P>
                        <HD SOURCE="HD2">Section 438.204 </HD>
                        <P>In paragraph (b)(1) we have removed the word “including” and clarified that procedures must assess the quality and appropriateness of care and services furnished to Medicaid enrollees under the MCO and PIHP contracts, and to all individuals with special health care needs. In paragraph (b)(3), we have clarified that the procedures must regularly monitor and evaluate the MCO and PIHP compliance with the standards. In paragraph (c) we have added, “For MCOs and PIHPs, any national” before “performance” and “that may be” before “identified.” In paragraph (e) we have added the phrase “For MCOs,” before “appropriate.” </P>
                        <HD SOURCE="HD2">Section 438.206 </HD>
                        <P>In paragraph (a) we reversed the words “services” and “covered,” and added the words “under the State plan” after “covered.” </P>
                        <P>In paragraph (b)(1)(ii) we revised the second clause to read “taking into consideration the characteristics and health care needs of specific Medicaid populations represented in the particular MCO, PIHP, and PAHP.” </P>
                        <P>In paragraph (c)(1)(i) we added the word “the” between the words “of” and “need.” </P>
                        <P>In paragraph (c)(1)(iv) we added at the end, the words “by providers.” </P>
                        <P>In paragraph (c)(1)(v), we added the word “providers” after the word “Monitor” and replaced “continuously” with “regularly” to clarify that each MCO, PIHP, and PAHP must monitor regularly to determine compliance. </P>
                        <HD SOURCE="HD2">Section 438.207 </HD>
                        <P>In paragraph (a), we added the words “and providers supporting documentation that demonstrates” after the word “State.” </P>
                        <P>In paragraph (b), we changed the title from “Nature of assurances” to “Nature of supporting documentation” and removed the words “acceptable to CMS.” </P>
                        <P>In paragraph (c), we removed the words “and specifically” and replaced them with “but no less frequently than.” </P>
                        <P>In paragraph (d) we replaced the word “submission” to “certification” in the title. </P>
                        <HD SOURCE="HD2">Section 438.208 </HD>
                        <P>Section 438.208 is revised. We have made significant changes to the organization of this section. </P>
                        <HD SOURCE="HD2">Section 438.210 </HD>
                        <P>In paragraph (a), we have reorganized and revised language for clarity. </P>
                        <HD SOURCE="HD2">Section 438.214 </HD>
                        <P>In paragraph (b) we have added a requirement that each State must establish a uniform credentialing and recredentialing policy that each MCO, PIHP, and PAHP must follow. </P>
                        <HD SOURCE="HD2">Section 438.240 </HD>
                        <P>In paragraph (a)(2) we have removed “standardized quality measures” and replaced it with “performance measures.” We have revised paragraph (b)(1) to require that performance improvement projects must be designed to achieve, through ongoing measurements and intervention, significant improvement, sustained over time, in clinical care and non-clinical care areas that are expected to have a favorable effect on health outcomes and enrollee satisfaction. We redesignated paragraph (b)(2) as (b)(3) and we redesignated paragraph (b)(3) as (b)(4). We added a new paragraph (b)(2) to specify that each MCO and PIHP must submit performance measurement data, as described in paragraph (c) of this section. </P>
                        <P>In paragraphs (c) and (d)(2) we have clarified that each MCO and PIHP must annually measure and report to the State its performance (including requirements under § 438.204(c) and § 438.240(a)(2)), submit to the State data to enable the State to calculate measures, or perform a combination of the above activities. </P>
                        <HD SOURCE="HD2">Section 438.242 </HD>
                        <P>In paragraph (a) we have added “and appeals” after “grievances” to clarify that a health information system must provide information on appeals. </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart E—[Reserved] </HD>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart F—Grievance System </HD>
                            <HD SOURCE="HD2">Section 438.400 </HD>
                        </SUBPART>
                        <P>We have removed “or any of its providers” from the definition of “action.” We have clarified the definition of “action,” to include unreasonable delays in services or appeals not acted upon within the necessary timeframes provided in § 438.408(b). </P>
                        <HD SOURCE="HD2">Section 438.402 </HD>
                        <P>In paragraph (b)(1)(ii) we clarified that a provider may file a grievance or request a State fair hearing on behalf of an enrollee, if the State permits the provider to act as the enrollee's authorized representative in doing so. </P>
                        <HD SOURCE="HD2">Section 438.404 </HD>
                        <P>In paragraph (c)(6) we have corrected the cross-reference to § 438.210(d)—timeframes for expedited service authorizations. </P>
                        <HD SOURCE="HD2">Section 438.406 </HD>
                        <P>We have revised paragraph (a)(1) to clarify that giving enrollees any reasonable assistance in completing forms and taking other procedural steps is not limited to providing interpreter services and toll-free numbers that have adequate TTY/TTD and interpreter capability. </P>
                        <P>In paragraph (a)(3)(ii) we have clarified that the individuals who make decisions on grievances and appeals are individuals who are health care professionals who have the appropriate clinical expertise, as determined by the State, in treating the enrollee's condition or disease. </P>
                        <HD SOURCE="HD2">Section 438.408 </HD>
                        <P>In paragraph (d)(2)(ii) we have added language clarifying that the MCO or PIHP must also make reasonable efforts to provide oral notice. </P>
                        <HD SOURCE="HD2">Section 438.410 </HD>
                        <P>In paragraph (c)(2) we have added language clarifying the MCO or PIHP must make reasonable efforts to give the enrollee prompt oral notice of the denial. </P>
                        <HD SOURCE="HD2">Section 438.420 </HD>
                        <P>In paragraph (b)(4) we have included the word, “original” to describe the type of authorization. </P>
                        <P>
                            In paragraph (c), we have added language to clarify the duration of continued or reinstated benefits. If, at the enrollee's request, the MCO or PIHP continues or reinstates the enrollee's benefits while the appeal is pending, the 
                            <PRTPAGE P="41079"/>
                            benefits must be continued until one of the following occurs: 
                        </P>
                        <P>• The enrollee withdraws the appeal. </P>
                        <P>• Ten days have passed after the MCO or PIHP resolves the appeal against the enrollee, unless the enrollee, within the 10-day timeframe, has requested a State fair hearing with continuation of benefits until a State fair hearing decision is reached. </P>
                        <P>We have added a new paragraph (c)(4) to specify that benefits must be continued until the time period or service limits of a previously authorized service has been met. </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart G—[Reserved] </HD>
                        </SUBPART>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart H—Certifications and Program Integrity </HD>
                            <HD SOURCE="HD2">Section 438.600 </HD>
                        </SUBPART>
                        <P>We have added sections “1903(m)” and “1932(d)(1)” to the statutory basis to establish conditions for payments to the State with respect to contracts with MCOs and to incorporate the BBA provisions prohibiting affiliations with individuals debarred by Federal agencies. </P>
                        <HD SOURCE="HD2">Sections 438.604 and 438.606 </HD>
                        <P>We deleted the requirement for “substantial compliance” with the terms of the contract and for submitting certifications for “substantial compliance” respectively in order to prevent unnecessary lawsuits against MCOs and States. In addition, the statute and regulations already require States to monitor compliance with contracts executed under this rule. </P>
                        <HD SOURCE="HD2">Section 438.610 </HD>
                        <P>We added a new section to incorporate language from section 1932(d)(1) of the Act to the regulation to implement the BBA provisions prohibiting affiliations with individuals debarred by Federal agencies. This self-implementing provision has not been published previously, but was added in the final rule to include all of the relevant protections against fraud and abuse in one section. </P>
                        <P>We added application to PCCMs and to PAHPs to this section. (The BBA provided that section 1932(d)(1) of the Act be applied to MCEs; therefore we included application to PCCMs. We applied this section to PAHPs under the authority of section 1902(a)(4) of the Act. </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart I—Sanctions </HD>
                            <HD SOURCE="HD2">Section 438.724 </HD>
                        </SUBPART>
                        <P>We have clarified that the notice that must be given to the CMS Regional Office whenever a State imposes or lifts a sanction is only applicable to those sanctions under § 438.700. </P>
                        <HD SOURCE="HD2">Section 438.726 </HD>
                        <P>We have added a new paragraph (b) which states that a contract with an MCO must provide that payments provided for under the contract will be denied for new enrollees when, and for so long as payment for those enrollees is denied by CMS. </P>
                        <HD SOURCE="HD2">Section 438.730 </HD>
                        <P>We have reorganized this section so that it conforms to removed § 434.67.</P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart J—Conditions for Federal Financial Participation </HD>
                            <HD SOURCE="HD2">Section 438.802 </HD>
                        </SUBPART>
                        <P>We have removed the requirement for substantial compliance with physician incentive plans, the MCO's contract, and the provisions of part 438 as a condition for FFP. </P>
                        <HD SOURCE="HD2">Section 438.806 </HD>
                        <P>We have made technical revisions to correct erroneous cross-references in paragraph (a)(1). We now correctly refer back to paragraphs (b)(2) through (b)(5) of § 438.6. </P>
                        <HD SOURCE="HD2">Section 438.814 </HD>
                        <P>We have revised and moved the provisions of this section to paragraphs (c)(5)(ii) and (c)(5)(iii) of § 438.6. </P>
                        <HD SOURCE="HD1">IV. Collection of Information Requirements </HD>
                        <P>
                            Under the Paperwork Reduction Act (PRA) of 1995, we are required to provide 30-day notice in the 
                            <E T="04">Federal Register</E>
                             and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget (OMB) for review and approval. 
                        </P>
                        <P>In order to fairly evaluate whether OMB should approve an information collection, section 3506(c)(2)(A) of the PRA of 1995 requires that we solicit comment on the following issues: </P>
                        <P>• The need for the information collection and its usefulness in carrying out the proper functions of our agency. </P>
                        <P>• The accuracy of our estimate of the information collection burden. </P>
                        <P>• The quality, utility, and clarity of the information to be collected. </P>
                        <P>• Recommendations to minimize the information collection burden on the affected public, including automated collection techniques. </P>
                        <P>Therefore, we are soliciting public comments on each of these issues for the information collection requirements discussed below. </P>
                        <P>The following information collection requirements and associated burdens are subject to the PRA. For purposes of this requirement, we incorporated pertinent managed care data from the 2000 Medicaid enrollment report. As of June, 2000, there were 339 managed care organizations (MCOs) (this includes three HIOs that must adhere to the MCO requirements of this regulation), 37 primary care case management (PCCM) systems, 376 managed care entities (MCOs and PCCMs combined), 123 mental health and substance abuse prepaid health plans (PIHPs) and 34 dental, primary care and transportation prepaid health plans (PAHP), all of which have previously been regulated as PHPs. There were a total of 25,821,196 beneficiaries enrolled in these plans (some beneficiaries are enrolled in more than one plan) in forty-eight States and the District of Columbia (Wyoming and Alaska do not currently enroll beneficiaries in any type of managed care). </P>
                        <HD SOURCE="HD2">A. Section 438.6 Contract Requirements </HD>
                        <HD SOURCE="HD3">Section 438.6(c) Payments Under Risk Contracts </HD>
                        <P>1. Requirement. Section 438.6(c) modifies the rules governing payments to MCOs, PIHPs, and PAHPs by doing the following: (1) Eliminating the upper payment limit (UPL) requirement; (2) requiring actuarial certification of capitation rates; (3) specifying data elements that must be included in the methodology used to set capitation rates; (4) requiring States to consider the costs for individuals with chronic illness, disability, ongoing health care needs, or catastrophic claims in developing rates; (5) requiring States to provide explanations of risk sharing or incentive methodologies; and (6) imposing special rules, including a limitation on the amount that can be paid under FFP in some of these arrangements. </P>
                        <P>
                            2. Burden. It is difficult to quantify the burden on States of providing information to support the actuarial soundness of the capitation rates for their risk-based, managed care contracts, because the rate setting methodologies and data sources vary widely from State to State. Under the UPL requirements, States were required to provide the capitation rates and any requested supporting documentation for all rate cells used which may vary from 5 to 10 cells on one end to 60 or more on another. In addition, States needed to generate data to meet the UPL requirement using historical fee-for-service (FFS) data trended forward to 
                            <PRTPAGE P="41080"/>
                            the contract year. This would be a relatively simple process for a State initiating its managed care program, where it can rely on a very recent full year of FFS data for this purpose. However, almost all States have been operating risk-based managed care programs for at least 5 to 10 years and must make numerous adjustments to that data so that it can be used for this purpose. We estimate the average burden on States to comply with the current rate setting and UPL rules to be 16 hours per contract for documenting the capitation rates (setting out and explaining rate cells, risk sharing mechanisms, etc) and 40 hours per contract for generating a UPL for comparison purposes. This results in a total burden of 56 hours per contract for 496 risk contracts, resulting in a total burden of 27,776 hours.
                        </P>
                        <P>Under the new requirements for actuarial soundness, States will need to provide an actuarial certification and additional documentation not previously required, including: specific data elements used to set capitation rates; methodologies to consider the costs for individuals with chronic illness, disability, ongoing health care needs, or catastrophic claims; explanations of risk sharing or incentive methodologies; and documentation supporting special contract provisions. We estimate the burden to comply with these requirements to average approximately 32 hours per contract for the 496 risk contracts, resulting in a total burden of 15,872 hours. This amount is limited to the time required for the State to compile documentation the State and its actuaries would already have developed in determining the capitation rates and submitting this documentation, as required, to CMS. Since, under this new rule, States will no longer need to generate a UPL in addition to the rate setting burden, this change results in a net reduction in burden of 11,904 hours. </P>
                        <HD SOURCE="HD3">Section 438.6(i)(3) Advance directives </HD>
                        <P>1. Requirement. This paragraph requires that MCOs, PIHPs, and certain PAHPs provide adult enrollees with written information on advance directives policies and include a description of applicable State law. </P>
                        <P>2. Burden. The burden associated with this requirement is the time it takes to furnish the information to enrollees. We assume that this information would be furnished with the rest of the information required by § 438.10 and is therefore subsumed under those requirements. </P>
                        <P>There is also an implied recordkeeping requirement associated with contracts; i.e., that would be documented. Maintaining documentation is a usual and customary business practice and does not add to the burden. </P>
                        <HD SOURCE="HD2">B. Section 438.8  Provisions That Apply to PIHPs and PAHPs </HD>
                        <P>1. Requirement. This section specifies which of the contract requirements contained in § 438.6 apply to PIHPs and which apply to PAHPs. Requirements for advance directives apply only to PIHPs and certain limited numbers of PAHPs. </P>
                        <P>2. Burden. PHPs (now designated as PIHPs and PAHPs) have not previously been required to maintain written policies and procedures with respect to advance directives. This rule requires the PIHP and some PAHPs to provide written information to enrollees of their rights under this provision and the PIHPs policies with respect to the implementation of those rights. We project 8 hours of time for each of 123 PIHPs and 2 PAHPs to establish this policy and 2 minutes per enrollee for provision of this information, and acceptance of this right to each of approximately 6.3 million individuals enrolled in PIHPs and the specified PAHPs. The total time for this is approximately 212,000 hours. </P>
                        <P>1. Requirement. Under the physician incentive plan provision, PIHPs and PAHPs, like MCOs, will be required to provide descriptive information to States and CMS to determine whether or not there is substantial financial risk in their subcontracts. In addition, enrollees must be surveyed and provided information on the risk arrangements when substantial risk exists. </P>
                        <P>
                            2. Burden. We are basing our projections of burden upon information published in the 
                            <E T="04">Federal Register</E>
                             on March 27, 1996 and December 31, 1996 (61 FR 13445 and 61 FR 69049) which contained the original regulatory provisions on physician incentive plans for Medicare and Medicaid HMOs. Based on those assumptions, we believe no more than 
                            <FR>1/3</FR>
                             of the approximately 157 PIHPs and PAHPs use incentive or risk payment arrangements with their subcontracting providers. Affected PIHPs and PAHPs would be required to provide detailed responses to State surveys regarding their payment mechanisms and amounts. At the projected 100 hours per response for approximately 53 PIHPs and PAHPs the total burden would be 5,300 hours. For those PIHPs and PAHPs with substantial financial risk, there are other requirements such as stop/loss insurance and beneficiary surveys. We believe there would be minimal additional burden as a result of these requirements (because many already comply with these requirements) and that this would apply to no more than 
                            <FR>1/4</FR>
                             of those PIHPs and PAHPs with risk or incentive payments, or a total of 13. We estimate an additional 10 hours per plan for a total of 130 hours. Altogether, we estimate 5,430 hours of burden through imposition of this requirement on PIHPs and PAHPs. 
                        </P>
                        <HD SOURCE="HD2">C. Section 438.10 Information Requirements </HD>
                        <HD SOURCE="HD3">Section 438.10(c), (d), (e), (f), (g), and (h) </HD>
                        <P>1. Requirement. In summary, § 438.10 requires that each State, its contracted representative, or at the option of the State, each MCO, PIHP, PAHP, and PCCM furnish information to enrollees and potential enrollees to meet the requirements of this section. Paragraph (c)(4) requires that the State and each MCO, PIHP, PAHP, and PCCM, make oral interpretation available in languages other than English. Paragraph (c)(5) requires that beneficiaries be informed how to access those services. Paragraph (d)(2) requires that all enrollees and potential enrollees must be informed that information is available in alternative formats and how to access those formats. The basic information listed in paragraph (e)(2) must be provided to each potential enrollee by the State or its contracted representative. </P>
                        <P>The State, its contracted representative or the MCO, PIHP, PAHP, or PCCM must provide the information in paragraph (f)(6), and for MCOs and PIHPs, in paragraph (g) at least once a year. The information that must be provided includes the following: </P>
                        <P>(a) Information for potential enrollees: </P>
                        <P>(1) General information must be provided about the basic features of managed care, which populations are excluded from enrollment, subject to mandatory enrollment, or free to enroll voluntarily in an MCO or PIHP, and MCO and PIHP responsibilities for coordination of enrollee care. </P>
                        <P>
                            (2) Information specific to each MCO, PIHP, PAHP, and PCCM serving an area that encompasses the potential enrollee's service area must be provided in summary form, or in more detail, upon request of the enrollee. This includes information on benefits covered; cost sharing if any; service area; names, locations, and telephone numbers of current network providers, including at a minimum, information on primary care physicians, specialists, and hospitals, and identification of providers that are not accepting new 
                            <PRTPAGE P="41081"/>
                            patients; and benefits that are available under the State plan but are not covered under the contract, including how and where the enrollee may obtain those benefits, any cost sharing, and how transportation is provided. 
                        </P>
                        <P>(b) Information for enrollees: </P>
                        <P>(1) The State must notify enrollees of their disenrollment rights annually. The State, or the MCO, PIHP, PAHP, and PCCM, if delegated this responsibility by the State, must provide certain information to new enrollees and notify enrollees annually of their right to request additional information. The State must give each enrollee written notice of any change (that the State defines as “significant”) in the information specified at least 30 days before the intended effective date of the change and make a good faith effort to give written notice of termination of a contracted provider, within 15 days after receipt or issuance of the termination notice, to each enrollee who received his or her primary care from, or was seen on a regular basis by, the terminated provider. </P>
                        <P>(c) General information for all enrollees of MCOs, PIHPs, PAHPs, and PCCMs: </P>
                        <P>(1) Names, locations, and telephone numbers of, and non-English languages spoken by, current network providers, including information at least on primary care physicians, specialists, and hospitals, and identification of providers that are not accepting new patients. </P>
                        <P>(2) Any restrictions on the enrollee's freedom of choice among network providers. </P>
                        <P>(3) Enrollee rights and responsibilities as specified in § 438.100. </P>
                        <P>(4) Information on grievance and fair hearing procedures, and for MCO and PIHP enrollees, the information specified in § 438.10(g)(i). </P>
                        <P>(5) The amount, duration, and scope of benefits available under the contract in sufficient detail to ensure that enrollees understand the benefits to which they are entitled. </P>
                        <P>(6) Procedures for obtaining benefits, including authorization requirements. </P>
                        <P>(7) The extent to which, and how, enrollees may obtain benefits, including family planning services from out-of-town network providers. </P>
                        <P>(8) The extent to which, and how, after-hours and emergency coverage are provided. </P>
                        <P>(9) What constitutes emergency medical condition, emergency services, and post-stabilization services, with reference to the definitions in § 438.114, and the fact that prior authorization is not required for emergency services. </P>
                        <P>(10) The post-stabilization care services rules set forth at § 438.113(c) of this chapter. </P>
                        <P>(11) Policy on referrals for specialty care and for other benefits not furnished by the enrollee's primary care provider. </P>
                        <P>(12) Cost sharing, if any. </P>
                        <P>(13) How and where to access any benefits that are available under the State plan but are not covered under the contract, including how and where the enrollee may obtain those benefits, any cost sharing, and how transportation is provided. </P>
                        <P>(14) For a counseling or referral service the MCO, PIHP, PAHP, or PCCM does not cover because of moral or religious objections, the MCO, PIHP, or PCCM need not furnish information on how and where to obtain the service. The State must furnish information about how and where to obtain the service. </P>
                        <FP>(d) Specific information requirements for enrollees of MCOs and PIHPs: </FP>
                        <P>(1) In addition to the requirements in § 438.10(e), MCOs and PIHPs must provide to their enrollees the following information specified in § 438.10(g): </P>
                        <P>(i) Grievance, appeal, and fair hearing procedures and timeframes, as provided in § 438.400 through 438.424, in a State-developed or State-approved description, which includes: </P>
                        <P>(ii) The right to a State fair hearing and the method for obtaining a hearing, </P>
                        <P>(iii) The rules governing representation at the hearing, </P>
                        <P>(iv) The right to file grievances and appeals </P>
                        <P>(v) The filing requirements, timeframes, and availability of assistance with the filing process, </P>
                        <P>(vi) The toll-free numbers enrollees can use to file a grievance or appeal by phone, </P>
                        <P>(vii) The fact that when requested by the enrollee, benefits will continue if the enrollee files an appeal or a request for a State fair hearing within the specified timeframes, </P>
                        <P>(viii) The possibility that the enrollee may be required to pay the cost of services furnished during the appeal process, if the final decision is adverse, </P>
                        <P>(ix) Any appeal rights that the State chooses to make available to providers to challenge the failure of the organization to cover a service, </P>
                        <P>(x) Information on advance directives, as set forth in § 438.6(i)(2) and physician incentive plans, as set forth in § 438.6(h) and </P>
                        <P>(xi) Additional information that is available upon request, including structure and operation of the MCO or PIHP </P>
                        <P>2. Burden. We believe the burden placed on States, MCOs, PIHPs, PAHPs, and PCCMs, and enrollment brokers as a result of these requirements is the time associated with modifying the content of existing information materials, as well as the time associated with distributing the materials to enrollees as specified by the regulation. We estimate that it will initially take 12 hours for each MCO, PIHP, PAHP, or PCCM system to modify existing information materials to conform to the requirements above. We further estimate that there are approximately 533 MCOs, PIHPs, PAHPs, and PCCM systems equating to an initial modification burden of approximately 6,396 hours. After the initial modification, we estimate that it will take MCOs, PIHPs, and PAHPs approximately 4 hours each to annually update the information materials, equating to an annual total burden of approximately 2,132 hours. </P>
                        <P>We estimate that that it will take MCOs, PIHPs, PAHPs, and PCCM systems approximately 5 minutes per enrollee to mail a packet of materials to potential enrollees and enrollees. We estimate that each year approximately 15 percent of the Medicaid managed care enrollee population are new enrollees. This equates to approximately 3.9 million potential enrollees a year for a total burden on the States of 65,000 hours. Mailing the annual packet of information to the 25,731,040 enrollees, at 5 minutes a packet, will result in a burden to the State, or the MCOs, PIHPs, PAHPs, and PCCMs, if delegated this responsibility by the State, of 2,144,253 hours. </P>
                        <P>We similarly estimate that it annually will take MCOs, PIHPs, PAHPs, and PCCMs 5 minutes per enrollee to supply information requested by potential enrollees and enrollees. We estimate that 10 percent of potential enrollees and enrollees will request information each year. For the 390,000 potential enrollees requesting information, this results in a burden on States of 6,500 hours. For the 2,573,104 enrollees requesting information, this results in a burden on States, or MCOs, PIHPs, PAHPs, and PCCMs if delegated this responsibility by the State, of 214,425 hours. </P>
                        <P>Section 438.10(i) Special Rules: States With Mandatory Enrollment Under State Plan Authority </P>
                        <P>
                            1. Requirement. Under (h), if the State plan provides for mandatory MCO or PCCM enrollment under section 1932(a)(1)(A) of the Act, the State or its contracted representative must provide information in a comparative, chart-like format, to potential enrollees. The information must include the MCO's or PCCM's service area, the benefits covered under the contract, any cost 
                            <PRTPAGE P="41082"/>
                            sharing imposed by the MCOs or PCCMs and, to the extent available, quality and performance indicators, including but not limited to disenrollment rates and enrollee satisfaction. 
                        </P>
                        <P>2. Burden. For the requirement to provide information in a chart-like format, we believe that the additional burden on States (i.e., not yet captured in the above provisions) is the length of time associated with creating the comparative chart. We estimate that it will take States approximately 8 hours each to create the comparative chart. Currently, 10 States per year have approved managed care under the State Plan Option, for a total annual burden of approximately 80 hours. </P>
                        <HD SOURCE="HD2">D. Section 438.12 Provider Discrimination Prohibited </HD>
                        <P>1. Requirement. This section requires that if an MCO, PIHP, or PAHP declines to include individual or groups of providers in its network, it must give the affected providers written notice of the reason for its decision. </P>
                        <P>2. Burden. The burden associated with this requirement is the time it takes the MCO, PIHP, or PAHP to draft and furnish the providers with the requisite notice. We estimate that it will take 1 hour to draft and furnish any given notice. We estimate that on average each MCO, PIHP, and PAHP will need to produce 10 notices per year for a total of 4,960 hours. </P>
                        <HD SOURCE="HD2">E. Section 438.50(b) State Plan Information </HD>
                        <P>1. Requirements. Each State must have a process for the design and initial implementation of the State plan that involves the public and must have methods in place to ensure ongoing public involvement once the State plan has been implemented. </P>
                        <P>2. Burden. The burden associated with this section includes the time associated with developing the process for public involvement, including annual updates. We estimate that it will take 10 current States 40 hours per State to develop the process for involving the public for a total burden of 400 hours. We estimate that ensuring ongoing public involvement will take another 20 hours per State annually for a total annual burden of 200 hours. </P>
                        <P>The recordkeeping burden involved in maintaining documentation that the requirements are met is a usual and customary business practice and imposes no additional burden. </P>
                        <HD SOURCE="HD2">F. Section 438.56 Disenrollment: Requirements and Limitations </HD>
                        <HD SOURCE="HD3">Section 438.56(d)(1) </HD>
                        <P>1. Requirement. In order to disenroll, the beneficiary (or his or her representative) must submit an oral or written request to the State agency (or its agent) or to the MCO, PIHP, PAHP, or PCCM where permitted. </P>
                        <P>2. Burden. We believe that the burden associated with this requirement is the length of time it would take enrollees to submit in writing a disenrollment request, if they choose to use the written format. We estimate that it will take approximately 10 minutes per enrollee to generate a written disenrollment request. We estimate that approximately 5 percent of MCO, PIHP, PAHP, and PCCM enrollees will request that they be disenrolled from an MCO, PIHP, PAHP, or PCCM. Approximately one-fourth of the enrollees will choose a written rather than an oral request. This equates to an annual burden of approximately 10 minutes multiplied by 321,638 affected enrollees (one-fourth of the 1,286,552 enrollees requesting disenrollment), or approximately 53,606 hours. We estimate a burden of 3 minutes per oral request for disenrollment (for 3/4ths of the 1,286,552 enrollees, or 964,914 enrollees) for a total burden of 48,246 hours. </P>
                        <HD SOURCE="HD3">Section 438.56(f) </HD>
                        <P>1. Requirement. Under paragraph (f), a State that restricts disenrollment under this section must provide that enrollees and their representatives are given written notice of disenrollment rights at least 60 days before the start of each enrollment period. </P>
                        <P>2. Burden. The burden for this section is addressed in § 438.10(f). </P>
                        <HD SOURCE="HD2">G. Section 438.102 Enrollee-Provider Communications </HD>
                        <P>1. Requirement. Section 438.102(a)(2) states that the general rule in paragraph (a)(1) of this section does not require the MCOs, PIHPs, and PAHPs to cover, furnish, or pay for a particular counseling or referral service if the MCO, PIHP, or PAHP objects to the provision of that service on moral or religious grounds; and makes written information on these policies available to (1) prospective enrollees, before and during enrollment and, (2) current enrollees, within 90 days after adopting the policy with respect to an any particular service. </P>
                        <P>
                            2. Burden. We believe the burden associated with this requirement will affect no more than 3 MCOs or PIHPs annually since it applies only to the services they discontinue providing on moral or religious grounds during the contract period. We estimate that it takes 4 hours to devise a notice and 5 minutes to mail, affecting 52,000 enrollees, for a total burden of 4,345 hours. [12 hours + (52,000 × 
                            <FR>1/2</FR>
                            )] The burden for notification of prospective enrollees of the services not covered by the MCO, PIHP, or PAHP on these grounds is included in the overall burden arising from the Information Requirements in § 438.10. 
                        </P>
                        <HD SOURCE="HD2">H. Section 438.202 State Responsibilities </HD>
                        <P>1. Requirement. Each State contracting with an MCO or PIHP must have a written strategy for assessing and improving the quality of managed care services offered by the MCO or PIHP, make it available for public comment before adopting it in final, and conduct periodic reviews to evaluate the effectiveness of the strategy. We expect States will conduct these periodic reviews every 3 years. Each State must also submit to CMS a copy of the initial strategy and a copy of the revised strategy whenever significant changes are made. In addition, States are required to submit to CMS regular reports on the implementation and effectiveness of the strategy, consistent with the State's own periodic review of its strategy's effectiveness. </P>
                        <P>
                            2. Burden. The burden associated with this section is limited to those States offering managed care through MCOs or PIHPs (41) and includes the time associated with developing the proposed strategy, publicizing the proposed strategy, incorporating public comments, submitting an initial copy of the strategy to CMS prior to its implementation and whenever significant changes are made, and submitting regular reports on the implementation and effectiveness of the strategy. We estimate that it will take 40 hours per State to develop the proposed strategy for a total burden of 1,640 hours. We estimate that publicizing the proposed strategy will take 2 hours per State for a total burden of 82 hours. We estimate that incorporating public comments for the final strategy will take another 40 hours per State for a total burden of 1640 hours. We estimate it will take 1 hour per State to submit an initial copy of the strategy to CMS prior to implementation and whenever significant changes are made for a total of 41 hours. We estimate it will take 40 hours per State to create and submit a report on the implementation and effectiveness of the strategy and that these reports will be submitted at 
                            <PRTPAGE P="41083"/>
                            approximately every 3 years for a total annual burden of 546 hours. 
                        </P>
                        <HD SOURCE="HD2">I. Section 438.204 Elements of State Quality Strategies: </HD>
                        <P>1. Requirement. In the final rule we require at § 438.204(b)(2) that a State identify the race, ethnicity, and primary language spoken by each MCO and PIHP enrollee and report this information to each MCO and PIHP in which each beneficiary enrolls at the time of their enrollment. </P>
                        <P>2. Burden. We believe that most States currently track race and ethnicity data in their eligibility systems. If States do not, minor changes in their software will be needed. With respect to primary language of enrollees, there will likely be additional programming needed for all States. We estimate that this would require 4 hours of programming for each of the 41 jurisdictions for a total of 164 hours. </P>
                        <HD SOURCE="HD2">J. Section 438.207 Assurances of Adequate Capacity and Services </HD>
                        <P>1. Requirement. Section 438.207(b) requires that each MCO, PIHP, and PAHP (where applicable) submit documentation to the State, in a format specified by the State, to demonstrate that it has the capacity to demonstrate that it complies with specified requirements and that it has the capacity to serve the expected enrollment in its service area in accordance with the State's standards for access to care and meets specified requirements. </P>
                        <P>Section 438.207(c) requires that this documentation be submitted to the State at the time the MCO, PIHP, or PAHP enters into a contract with the State and at any time there has been a significant change (as defined both by the State and this regulation) in the MCO's, PIHP's, or PAHPs operations that would affect adequate capacity and services. </P>
                        <P>Section 438.207(d) requires the State, after reviewing the MCO's, PIHP's, or PAHP's documentation, to certify to CMS that the MCO, PIHP, or PAHP has complied with the State's requirements for availability of services, as set forth at § 438.206. </P>
                        <P>2. Burden. We believe that MCOs, PIHPs, and PAHPs already collect and provide this information to State agencies as part of their customary and usual business practices and that the only additional burden on MCOs, PIHPs, and PAHPs is the length of time required for these entities to compile this information in the format specified by the State agency, and the length of time to mail the information to the State and to CMS. We estimate that it will take each MCO, PIHP, and PAHP approximately 20 hours to compile the information necessary to meet this requirement, for a total of 20 hours multiplied by 486 MCOs, PIHPs, and PAHPs with networks, or approximately 9,720 hours. In addition, we estimate that it will take MCOs, PIHPs, and PAHPs approximately 5 minutes each to mail the materials associated with this burden to the State for an annual burden of approximately 5 minutes multiplied by 486 of these entities, or approximately 4 hours. </P>
                        <P>We estimate that obtaining information on: (1) The numbers and types of persons with special health care needs that could be anticipated to enroll in the MCO or PIHP; (2) the types of experienced providers they would require; (3) the experience of the existing providers in the MCO's or PIHPs network; and (4) the numbers and types of additional experienced providers needed, would require an estimated 40 hours of work for each of the 462 MCOs, PIHP, and PAHP for a total estimated burden of 18,480 hours. </P>
                        <HD SOURCE="HD2">K. Section 438.208 Coordination and Continuity of Care </HD>
                        <P>1. Requirement. Under paragraph (b)(3) of this section requires MCOs, PIHPs, and PAHPs to share with other MCOs, PIHPs, and PAHPs serving the enrollee the results of its identification and assessment of any enrollee with special health care needs so that those activities need not be duplicated. </P>
                        <P>2. Burden. The burden associated with this information collection requirement is the time it will take to disclose information on enrollees. We estimated that it will be necessary to disclose information on 619,709 enrollees and take it will take 45 minutes for each one, for an annual total of 464,782 hours. </P>
                        <HD SOURCE="HD2">L. Section 438.210 Coverage and Authorization of Services </HD>
                        <P>1. Requirement. Under paragraph (b) of this section, for the processing of requests for initial and continuing authorizations of services, each contract must require that the MCO, PIHP, or PAHP and its subcontractors have in place written policies and procedures. </P>
                        <P>2. Burden. The burden associated with this requirement is the time required to develop the policies and procedures. We do not believe that this requirement will increase an entity's burden as it part of usual and customary business practices. </P>
                        <P>1. Requirement. Under paragraph (c) of this section, each contract must provide for the MCO, PIHP, or PAHP to notify the requesting provider, and give the enrollee written notice of any decision by the MCO, PIHP, or PAHP to deny a service authorization request, or to authorize a service in an amount, duration, or scope that is less than requested. </P>
                        <P>2. Burden. The burden associated with this requirement will be the time required to notify the requesting provider and the enrollee. We believe that there will be approximately 100 notifications under this provision and that it will take 60 minutes to complete the notification (including writing it) per MCO or PIHP. There are approximately 339 MCOs and 123 PIHPs for a total of 462 for a total of 46,200. </P>
                        <HD SOURCE="HD2">M. Section 438.214 Provider Selection </HD>
                        <P>1. Requirement. Under this section, each State must ensure, through its contracts, that each MCO, PIHP, or PAHP implements written policies and procedures for selection and retention of providers. </P>
                        <P>2. Burden. The burden associated with this requirement is the usual and customary recordkeeping collection associated with maintaining documentation. </P>
                        <HD SOURCE="HD2">N. Section 438.230 Subcontractual Relationships and Delegation </HD>
                        <P>1. Requirement. Under paragraph (b), there must be a written agreement that specifies the activities and report responsibilities delegated to the subcontractor and provides for revoking delegation or imposing other sanctions if the subcontractor's performance is inadequate. </P>
                        <P>2. Burden. The burden associated with this requirement is the time required to write the agreement and the time required to maintain documentation of the agreement. We believe that these activities and usual and customary business practices and do not affect the entities' burden. </P>
                        <HD SOURCE="HD2">O. Section 438.236 Practice Guidelines </HD>
                        <P>1. Requirement. Under paragraph (c) of this section, each MCO, PIHP, and PHAP must disseminate guidelines to its affected providers and, upon request, to enrollees and potential enrollees. </P>
                        <P>2. Burden. The burden associated with this requirement is the time required to disseminate the guidelines. We believe that these will be rare requests and will occur infrequently. </P>
                        <HD SOURCE="HD2">P. Section 438.240 Quality Assessment and Performance Improvement Program; Performance Improvement Projects </HD>
                        <P>
                            1. Requirement. Section 438.240(c) states that each MCO and PIHP must annually measure its performance using 
                            <PRTPAGE P="41084"/>
                            standard measures required by the State and report its performance to the State. In addition to using and reporting on measures of its performance, § 438.240(d)(1) requires States to ensure that each MCO and PIHP have an ongoing program of performance improvement projects. In § 438.240(d)(2) each MCO and PIHP is required to report the status and results of each such project to the State as requested. 
                        </P>
                        <P>2. Burden. This regulation requires States to require each MCO and PIHP to have an ongoing program of performance improvement. Based on discussions with the 17 States with the largest Medicaid managed care enrollments, all 17 States are already doing so. Because the use of performance measures in managed care has become commonplace in commercial, Medicare, and Medicaid managed care, we do not believe that this regulatory provision imposes any new burden on MCOs, PIHPs, or States. </P>
                        <P>With respect to the requirements for ongoing performance improvement projects in § 438.240(d), we expect that, in any given year, each MCO and PIHP will complete two projects, and will have four others underway. We further expect that States will request the status and results of each MCO's and PIHP's projects annually. Accordingly, we estimate that it will take each MCO and PIHP 5 hours to prepare its report for each project, for an annual total burden of 30 hours per MCO and PIHP. In aggregate, this burden equates to 30 hours multiplied by an estimated 462 MCOs and PIHPs, or approximately 13,860 hours. </P>
                        <HD SOURCE="HD2">Q. Section 438.242 Health Information Systems </HD>
                        <P>1. Requirement. Section 438.242(b)(1) requires the State to require each MCO and PIHP to collect data on enrollee and provider characteristics as specified by the State, and on services furnished to enrollees, through an encounter data system or other such methods as may be specified by the State. Paragraph (3) requires that the data be made available to the State and, upon request, to CMS. </P>
                        <P>2. Burden. The above information collection requirement is subject to the PRA. However, we believe that the burden associated with these information collection requirements is exempt from the Act in accordance with 5 CFR 1320.3(b)(2) because the time, effort, and financial resources necessary to comply with these requirements would be incurred by persons in the normal course of their activities. </P>
                        <HD SOURCE="HD2">R. Section 438.402 General Requirements </HD>
                        <P>1. Requirement. In summary, § 438.402 requires each MCO and PIHP to have a grievance system, sets out general requirements for the system, and establishes filing requirements. It provides that grievances and appeals may be filed either orally or in writing, but that oral appeals (except those with respect to expedited service authorization decisions) must be followed by a written request. </P>
                        <P>2. Burden. We estimate that it will take approximately 5.5 hours for each MCO and PIHP to conform their existing general grievance system requirements to those in the regulation. It will take approximately 2.5 hours to create or change the filing requirements, including developing or revising templates for a notice of action and a notice of disposition or resolution. The total burden for 462 MCOs and PIHPs is 3,696 hours. </P>
                        <P>We estimate that approximately 1 percent of 23.7 million MCO and PIHP enrollees (237,000) annually will file a grievance with their MCO or PIHP and that approximately .5 percent (118,000) annually will file an appeal. For these cases, we estimate that the burden on the enrollee filing a grievance or appeal is approximately 20 minutes per case. The total annual burden on enrollees is 118,500 hours. </P>
                        <HD SOURCE="HD2">S. Section 438.404 Notice of Action </HD>
                        <P>1. Requirement. In summary, § 438.404 states that if an MCO or PIHP intends to deny, limit, reduce, or terminate a service; deny payment; deny the request of an enrollee in a rural area with one MCO or PIHP to go out of network to obtain a service; or fails to furnish, arrange, provide, or pay for a service in a timely manner, the MCO or PIHP must give the enrollee timely written notice and sets forth the requirements of that notice. </P>
                        <P>2. Burden. We estimate that the burden associated with this requirement is the length of time it would take an MCO or PIHP to provide written notice of an intended action. We estimate that it will take MCOs and PIHP 30 seconds per action to make this notification. We estimate that approximately 5 percent (1,185,000) of the approximately 23.7 million MCO and PIHP enrollees will receive one notice of intended action per year from their MCO or PIHP for a total burden of approximately 9,875 hours. </P>
                        <HD SOURCE="HD2">T. Section 438.406 Handling of Grievances and Appeals </HD>
                        <P>1. Requirement. In summary, § 438.406 states that each MCO and PIHP must acknowledge receipt of each grievance and appeal. </P>
                        <P>2. Burden. The above information collection requirement is not subject to the PRA. It is exempt under 5 CFR 1320.4(a) because it occurs as part of an administrative action. </P>
                        <HD SOURCE="HD2">U. Section 438.408 Resolution and Notification: Grievances and Appeals </HD>
                        <P>1. Requirement. In summary, § 438.408 states that for grievances filed in writing or related to quality of care, the MCO or PIHP must notify the enrollee in writing of its decision within specified timeframes. The notice must also specify that the enrollee has the right to seek further review by the State and how to seek it. All decisions on appeals must be sent to the enrollee in writing within specified timeframes and for notice of expedited resolution, the MCO or PIHP must also provide oral notice. The decision notice must include the MCO or PIHP contact for the appeal and the results of the process and the date it was completed. For an oral grievance that does not relate to quality of care, the MCO or PIHP may provide oral notice unless the enrollee request that it be written. </P>
                        <P>2. Burden. The above information collection requirements are not subject to the PRA. They are exempt under 5 CFR 1320.4(a) because they occur as part of an administrative action. </P>
                        <HD SOURCE="HD2">V. Section 438.410 Expedited Resolution of Appeals </HD>
                        <P>1. Requirement. Paragraph (c), Action following denial of a request for expedited resolution, requires each MCO and PIHP to provide written notice to an enrollee whose request for expedited resolution is denied. </P>
                        <P>2. Burden. The above information collection requirement is not subject to the PRA. It is exempt under 5 CFR 1320.4(a) because it occurs as part of an administrative action. </P>
                        <HD SOURCE="HD2">W. Section 438.414 Information About the Grievance System to Providers and Subcontractors</HD>
                        <P>1. Requirement. Under this section, the MCO or PIHP must provide the information specified at § 438.10(g)(i) about the grievance system to all providers and subcontractors at the time they enter into a contract. </P>
                        <P>
                            2. Burden. The burden associated with this requirement is the time required to include the necessary language in the contract. We believe that this is usual and customary business practice and does not add any burden. 
                            <PRTPAGE P="41085"/>
                        </P>
                        <HD SOURCE="HD2">X. Section 438.416 Record Keeping and Reporting Requirements </HD>
                        <P>1. Requirement. This section requires the State to require MCOs and PIHPs to maintain records of grievances and appeals. </P>
                        <P>2. Burden. We estimate that approximately 95,000 (.5 percent) of the approximately 19 million MCO and PIHP enrollees will file a grievance or appeal with their MCO or PIHP (205 per MCO or PIHP). The recording and tracking burden associated with each grievance is estimated to be 1 minute per request (3.4 hours per MCO or PIHP), for a total burden of 1,583 hours (1 minute multiplied by an estimated 95,000 enrollees who would file a grievance or appeal). </P>
                        <HD SOURCE="HD2">Y. Section 438.604 Data That Must Be Certified </HD>
                        <P>1. Requirement. The data that must be certified include, but are not limited to, enrollment information, encounter data, and other information required by the State and contained in contracts, proposals, and related documents. </P>
                        <P>2. Burden. While the requirement for MCOs and PIHPs is to certify all documents required by the State, the burden associated with these requirements is captured during the submission of such information. Therefore, we are assigning 1 token hour of burden for this requirement </P>
                        <HD SOURCE="HD2">Z. Section 438.608 Program Integrity Requirements. </HD>
                        <P>1. Requirement. Under this section, the MCO or PIHP must have administrative and management arrangements or procedures that are designed to guard against fraud and abuse. The arrangements or procedures must include written policies, procedures, and standards of conduct that articulate the organization's commitment to comply with all applicable Federal and State standards and the designation of a compliance officer and a compliance committee that are accountable to senior management. </P>
                        <P>2. Burden. The burden associated with this requirement is the time required to file a copy of the written procedures. We believe that this is a normal business practice and does not add any burden. </P>
                        <HD SOURCE="HD2">AA. Section 438.710 Due Process: Notice of Sanction and Pre-Termination Hearing </HD>
                        <HD SOURCE="HD3">Section 438.710(a) Due Process: Notice of Sanction and Pre-Termination Hearing </HD>
                        <P>1. Requirement. Section 438.710(a) states that before imposing any of the sanctions specified in this subpart, the State must give the affected MCO or PCCM written notice that explains the basis and nature of the sanction. </P>
                        <P>2. Burden. The above information collection requirement is not subject to the PRA. It is exempt under 5 CFR 1320.4(a) because it occurs as part of an administrative action. </P>
                        <HD SOURCE="HD3">Section 438.710(b)(2) Due Process: Notice of Sanction and Pre-Termination Hearing </HD>
                        <P>1. Requirement. Section 438.710(b)(2) states that before terminating an MCO's or PCCM's contract, the State must:</P>
                        <P>(i) Give the MCO or PCCM written notice of its intent to terminate, the reason for termination, the time and place of the hearing; </P>
                        <P>(ii) After the hearing, give the entity written notice of the decision affirming or reversing the proposed termination of the contract and, for an affirming decision, the effective date of termination; and </P>
                        <P>(iii) For an affirming decision, give enrollees of the MCO or PCCM notice of the termination and information, consistent with § 438.10, on their options for receiving Medicaid services following the effective date of termination. </P>
                        <P>2. Burden. The above information collection requirement is not subject to the PRA. It is exempt under 5 CFR 1320.4(a) because it occurs as part of an administrative action. </P>
                        <HD SOURCE="HD2">BB. Section 438.722 Disenrollment During Termination Hearing Process </HD>
                        <P>1. Requirement. Section 438.722(a) states that after a State has notified an MCO or PCCM of its intention to terminate the MCO's or PCCM's contract, the State may give the MCO's or PCCM's enrollees written notice of the State's intent to terminate the MCO's or PCCM's contract. </P>
                        <P>2. Burden. States already have the authority to terminate MCO or PCCM contracts according to State law and have been providing written notice to the MCOs or PCCMs. States are now given, at their discretion, the option of notifying the MCO's or PCCM's enrollees of the State's intent to terminate the MCO's or PCCM's contract. While it is not possible to gather an exact figure, we estimate that 12 States may terminate 1 contract per year. We estimate that it will take States 1 hour to prepare the notice to enrollees, for a total burden of 12 hours. In addition, we estimate that it will take States approximately 5 minutes per beneficiary to notify them of the termination, equating to a burden of 5 minutes multiplied by 12 States multiplied by 46,194 beneficiaries per MCO or PCCM, for a burden of approximately 46,194 hours. The total burden of preparing the notice and notifying enrollees is 46,206. </P>
                        <HD SOURCE="HD2">CC. Section 438.724 Notice to CMS </HD>
                        <P>1. Requirement. Section 438.724 requires that the State give the CMS Regional Office written notice whenever it imposes or lifts a sanction. The notice must specify the affected MCO, the kind of sanction, and the reason for the State's decision to impose or lift a sanction. </P>
                        <P>2. Burden. We anticipate that no more than 36 States would impose or lift a sanction each year and that it would take each one 30 minutes to give the regional office notice. Thus the annual burden would be 18 hours. </P>
                        <HD SOURCE="HD2">DD. Section 438.730 Sanction by CMS: Special Rules for MCOs With Risk Contracts </HD>
                        <P>1. Requirement. Section 438.730(b), Notice of Sanction, requires that if CMS accepts a State agency's recommendation for a sanction, the State agency gives the MCO written notice of the proposed sanction. </P>
                        <P>Paragraph (c) of this section, Informal reconsideration, requires that if the MCO submits a timely response to the notice of sanction, the State agency gives the MCO a concise written decision setting forth the factual and legal basis for the decision. In addition, if CMS reverses the State's decision, the State sends a copy to the MCO. </P>
                        <P>2. Burden. These requirements are exempt under 5 CFR 1320.4(a) because they occur as part of administrative actions. </P>
                        <HD SOURCE="HD2">EE. Section 438.810 Expenditures for Enrollment Broker Services</HD>
                        <P>1. Requirement. Section 438.810(c) requires that a State contracting with an enrollment broker must submit the contract or memorandum of agreement (MOA) for services performed by the broker to CMS for review and approval. </P>
                        <P>2. Burden. The burden associated with this requirement is the length of time for a State to mail each contract to CMS for review. We estimated that the burden associated with this requirement is 5 minutes per enrollment broker contract, for a total annual burden of approximately 3 hours per year (5 minutes multiplied by an estimated 35 enrollment broker contracts in the States using brokers). </P>
                        <P>
                            We have submitted a copy of this final rule to OMB for its review of the information collection requirements described above in §§ 438.6, 438.8, 438.10, 438.12, 438.50, 438.56, 438.102, 
                            <PRTPAGE P="41086"/>
                            438.202, 438.204, 438.207, 438.208, 438.210, 438.214, 438.230, 438.236, 438.240, 438.242, 438.402, 438.404, 438.406, 438.408, 438.410, 438.414, 438.416, 438.608, 438.710, 438.722, 438.724, 438.730, and 438.804. These requirements are not effective until they have been approved by OMB. 
                        </P>
                        <P>If you comment on these information collection requirements, please mail copies directly to the following: </P>
                    </PART>
                    <FP SOURCE="FP-1">Centers for Medicare &amp; Medicaid Services, Office of Information Services, DCES, SSG, Attn: Julie Brown, CMS-2104-F, Room N2-14-26, 7500 Security Boulevard, Baltimore, MD 21244-1850; </FP>
                    <FP>   and </FP>
                    <FP SOURCE="FP-1">Office of Information and Regulatory Affairs, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503, Attn: Brenda Aguilar, Desk Officer.</FP>
                    <HD SOURCE="HD1">V. Regulatory Impact Analysis </HD>
                    <HD SOURCE="HD2">A. Overall Impact </HD>
                    <P>We have examined the impacts of this rule as required by Executive Order 12866 (September 1993, Regulatory Planning and Review) and the Regulatory Flexibility Act (RFA) (September 19, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act, the Unfunded Mandates Reform Act of 1995 (Pub.L. 104-4), and Executive Order 13132. Executive Order 12866 directs agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). A regulatory impact analysis (RIA) must be prepared for major rules with economically significant effects ($100 million or more in any 1 year.) We project the cost of this rule to be between $221 and $295 million annually. The burden of these costs will be shared between States, MCOs, PIHPs, PAHPs, PCCMs, and the Federal government. It should be noted that a large portion of these costs will be born by the Federal government through its matching payments to States for Medicaid expenditures. </P>
                    <P>This rule will implement new requirements for Medicaid managed care programs which have not been previously implemented through either the previous Part 434 of the CFR or the State Medicaid Director Letters listed in section I.A. of the Preamble, or self-implemented through the BBA. The new provisions implemented under this rule are requirements governing : (1) Payments under risk contracts; (2) PIHPs and PAHPs; (3) information that must be provided to beneficiaries; quality assessment and performance improvement for managed care programs; and (4) grievances and appeals. </P>
                    <P>The RFA requires agencies to analyze options for regulatory relief of small entities. We have provided an analysis of alternatives to these rules in section V.C. of the Preamble. </P>
                    <P>This final rule primarily impacts beneficiaries, State agencies, enrollment brokers, MCOs, PIHPs, PAHPs, and PCCMs. Small entities include small businesses in the health care sector that are HMO medical centers or health practitioners as prepaid health plans with receipts of less than $8.5 million, nonprofit organizations, and other entities. (See 65 FR 69432). For purposes of the RFA, individuals and State governments are not included in this definition. In the proposed rule we invited comments on alternatives to provisions of the proposed rule that would reduce burden on small entities. We did not receive any comments in response to this invitation. </P>
                    <P>As of June 2000, there were 339 MCOs, 123 PIHPs, 34 PAHPs, and 37 PCCM systems. We believe that only a few of these entities qualify as small entities. Specifically, we believe that 16 MCOs, 14 PIHPs, 11 PAHPs, and most managed care entities in the 37 PCCM systems are likely to be small entities. We estimate that there are 4.8 million beneficiaries enrolled in these small entities. We believe that the remaining MCOs, PIHPs, and PAHPs have annual receipts from Medicaid contracts and other business interests in excess of $8.5 million. </P>
                    <P>The primary impact on small entities will be through the requirements placed on PIHPs and PAHPs by § 438.8. Under this rule, PIHPs will be subject to nearly all of the requirements for MCOs, including the requirements for quality assessment and improvement and grievances and appeals. PAHPs are not subject to the grievance and appeals requirements, but will be subject to quality requirements like network adequacy and coverage and authorization of services where it is determined to be applicable. The impact on these entities from these provisions is discussed later in this section. However, we are identifying additional burden on the 14 PIHPs and 11 PAHPs, which we project to be small entities of 2,000 hours from the requirement for advance directives and 900 hours on information on solvency requirements, for a total burden of 2,900 hours. Using the mean hourly wage the average wage for the health care service sector of $16.34 (Bureau of Labor Statistics, March 2001), this will result in a total cost to these small entities of $47,386. </P>
                    <P>The most significant burden relates to providing information to enrollees. Specifically, MCOs, PIHPs, PAHPs, and PCCMs are required to make written materials available in languages that are prevalent in its service area (as determined by the State) and provide oral interpretation services when needed. The final rule requires MCOs, PIHPs, PAHPs, and PCCMs to make oral interpretation services available to each potential enrollee or enrollee requesting them. This requirement is actually derived from the provisions of Title VI of the Civil Rights Act of 1964 and Executive Order 13166, and not created by this rule. We estimate that less than 1% of the enrollees of these entities (or 48,000 individuals) will require this service an average of 2 times per year. Using the baseline commercial language line charges of $2.20 per minute with a one hour minimum, we estimate the cost of providing oral interpretation services to be $12.7 million annually. We believe that this estimate may overstate the impact of this requirement, because: (1) Many providers are bilingual or have staff that are bilingual (particularly in areas with relatively a large percentage of non-English speaking individuals); (2) there are less costly alternatives than the example we have used to provide oral interpretation; (3) many enrollees in need of oral interpretation will prefer to use a friend or relative; and (4) these specific costs should be mitigated by the costs of complying with current civil rights requirements to provide translation services. </P>
                    <P>We do not believe that there is significant burden as a result of the remainder of this section. PCCMs or PAHPs do not normally provide much written material directly to enrollees since, in the final rule, we place the responsibility on States, rather than PCCMs and PAHPs. We believe that States will usually prepare this information so that the only burden on PCCMs and PAHPs will be to distribute the information when it is requested by an enrollee. For the small entities who must perform this function themselves, including those MCOs and PIHPs identified as such we have projected a burden of 36,000 hours for compliance with the requirements in the information section. This results in an additional burden of $588,240. </P>
                    <P>
                        The final rule also imposes requirements for quality assessment and improvement in subpart D on all MCOs 
                        <PRTPAGE P="41087"/>
                        and PIHPs and those PAHPs designated by the State. Based on the estimates in the Collection of Information section of this preamble, we project a burden of 3,800 hours or $62,092. 
                    </P>
                    <P>In addition, Subpart F of this rule requires the 16 MCOs and 14 PIHPs that are small entities to develop and implement a grievance system as described in that section. While most of these entities would have had a system in place already, they will, at a minimum, need to modify the current system to comply with the requirements of this section. We project the burden for these modifications and operation of the grievance systems by these entities to be a total of 8 hours per entity for the development and modification of the current system and an average of 4 hours each for the resolution of the expected 1440 grievances and appeals filed by the enrollees of these entities (based on the estimates contained in section IV of this preamble on Information Collection Requirements). This results in a total burden of 6,000 hours at the mean hourly wage of $16.34, for a total cost of $98,040. </P>
                    <P>We do not believe that the remaining impact of the provisions of this final rule are great on the small entities that we have identified. These small entities must meet certain contract requirements, however, these are consistent with the nature of their business in contracting with the State for the provision of services to Medicaid enrollees. They, likewise, must meet requirements related to disenrollment of enrollees for cause, including receipt and initial processing of disenrollment requests if the State delegates this function to the entity. However, all enrollees have an annual opportunity to disenroll, and historically the number of disenrollment requests for cause are small. In addition, these entities must submit marketing material to the State for review and approval, and those MCOs, PIHPs, and PAHPs which are at risk for emergency services must cover and pay for emergency services based on the prudent layperson standard. However, the provisions governing marketing materials and emergency services have already been implemented through State Medicaid Director Letters. </P>
                    <P>We have clarified that PAHP enrollees have the right to a State fair hearing under subpart E of part 431, although this is not a new requirement. Additionally, PAHPs may not discriminate against providers seeking to participate in the plan. This requirement imposes no burden as it would reflect their usual and customary business operations. </P>
                    <P>In addition, section 1102(b) of the Act requires us to prepare a regulatory impact analysis for any rule that may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 604 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside a Metropolitan Statistical Area and has fewer than 100 beds. </P>
                    <P>We do not anticipate that the provisions in this final rule will have a substantial economic impact on most hospitals, including small rural hospitals. The BBA provisions include some new requirements on States, MCOs, and PIHPs, but no new direct requirements on individual hospitals. However, the prudent layperson standard for emergency services should benefit these hospitals by providing a uniform standard on which to determine the potential for coverage of these services across all MCOs. The impact on individual hospitals will vary according to each hospital's current and future contractual relationships with MCOs and PIHPs, but any additional burden on small rural hospitals should be negligible. </P>
                    <P>We have determined that we are not preparing analysis for either the RFA or section 1102(b) of the Act because we have determined, and we certify that this rule will not have a significant economic impact on a substantial number of small entities or a significant impact on the operations of a substantial number of small rural hospitals in comparison to total revenues of these entities. </P>
                    <HD SOURCE="HD2">B. Anticipated Effects </HD>
                    <P>This final rule implements the Medicaid provisions as directed by the BBA. The primary objectives of these provisions are to provide greater beneficiary protections and quality assurance standards and to allow for greater flexibility for State agencies to participate in Medicaid managed care programs. The final rule addresses pertinent areas of concern between States and MCOs, PIHPs, PAHPs and PCCMs. </P>
                    <P>Specific provisions of the regulation include the following: </P>
                    <P>• Permitting States to require in their State plan that Medicaid beneficiaries be enrolled in managed care. (This provision was implemented through a State Medicaid Director (SMD) Letter dated December 17, 1997, but this rule adds requirements for public involvement in the process.) </P>
                    <P>• Eliminating the requirement that no more than 75 percent of enrollees in an MCO or PHP be Medicaid or Medicare enrollees. (This provision was implemented through an SMD Letter dated January 14, 1998.) </P>
                    <P>• Specifying a grievance and appeal procedure for MCO and PIHP enrollees. </P>
                    <P>• Providing for the types of information that must be given to enrollees and potential enrollees, including requirements related to language and format. </P>
                    <P>• Requiring that MCOs, PIHPs and PAHPs document for the States that they have adequate capacity to serve their enrollees and that States certify this to us. </P>
                    <P>• Specifying quality standards for States, MCOs, and PIHPs. </P>
                    <P>• Increasing program integrity protections and requiring certification of data by MCOs and PIHPs. </P>
                    <P>• Increasing the threshold for prior approval of MCO contracts. (This provision was implemented through an SMD Letter dated January 14, 1998.) </P>
                    <P>• Permitting cost sharing for managed care enrollees under the same circumstances as permitted in fee-for-service. (This provision was implemented through an SMD Letter dated December 30, 1997.) </P>
                    <P>• Expanding the managed care population for which States can provide 6 months of guaranteed eligibility. (This provision was implemented through an SMD Letter dated March 23, 1998.) </P>
                    <P>• Revising the rules for setting capitation rates. </P>
                    <P>
                        It is extremely difficult to accurately quantify the overall impact of this regulation on States, MCOs, PIHPs, PAHPs, and PCCMs because there is enormous variation among States and these entities regarding their current regulatory and contract requirements, as well as organizational structure and capacity. Any generalization would mask important variations in the impact by State or managed care program type. The Lewin Group, under a contract with the Center for Health Care Strategies, released a study of the cost impact of the earlier proposed regulation published on September 29, 1998 the 
                        <E T="04">Federal Register</E>
                         (63 FR 52022). Because this new final rule addresses the same areas as the September 29, 1998 proposed rule and includes many similar provisions, the Lewin study remains the best information we have available on the potential incremental impact of this final rule. However, the provisions discussed in the study were more prescriptive, and thus more costly to implement, than the provisions contained in this final rule. Consequently, we believe that these 
                        <PRTPAGE P="41088"/>
                        estimates are higher than the actual costs will be to implement these requirements. 
                    </P>
                    <P>The Lewin study did not analyze the original proposed regulation in total, but focused on four areas within the original proposed regulation: individual treatment plans, initial health assessments, quality improvement programs, and grievance systems/State fair hearings. These areas are discussed in more detail in the specific section of the Impact Analysis addressing that provision. While the study's focus is limited to selected provisions of the previous regulation, and some of the details of the provisions in this final rule differ from the earlier proposed rule, nevertheless, we believe that the overall cost conclusions are relevant to this final rule. In addition to examining the four regulatory requirements, the Lewin study cited the need to evaluate both the incremental and aggregate effects of the rule; the affect on different managed care environments (for example, overall enrollment; the Medicare, commercial, and Medicaid mix; geographic location); and differing regulatory requirements of the State (for example, State patient rights laws, regulation of noninsurance entities). The Lewin report also points out that many of the BBA provisions were implemented through previous guidance to the States, so the regulatory impact only captures a subset of the actual impact of the totality of BBA requirements. </P>
                    <P>In summary, according to the Lewin Study, States and their contracting managed care plans have already implemented many provisions of the BBA. While there are incremental costs associated with these regulatory requirements, they will vary widely based on characteristics of individual managed care plans and States. Finally, the BBA requirements are being implemented in an increasingly regulatory environment at the State level. Therefore, States, MCOs, and PIHPs will likely face additional costs not related to these regulatory requirements absent these new regulations. Thus, the incremental impact of these requirements on costs to be incurred would be difficult if not impossible to project. </P>
                    <P>We believe that the overall impact of this final rule will be beneficial to Medicaid beneficiaries, MCOs, PIHPs, PAHPs, PCCMs, States, and CMS. Many of the BBA Medicaid managed care requirements merely codify the Federal statute standards widely in place in State law or in the managed care industry. Some of the BBA provisions represent new requirements for States, MCOs, PIHPs, PAHPs, and PCCMs, but also provide expanded opportunities for participation in Medicaid managed care. </P>
                    <P>It is clear that all State agencies will be affected by this final Medicaid rule but in varying degrees. Much of the burden will be on MCOs, PIHPs, PAHPs, and PCCMs contracting with States, but this will also vary by existing and continuing relationships between State agencies and MCOs, PIHPs, PAHPs, and PCCMs. This regulation is intended to provide important beneficiary protections while giving States flexibility and minimizing the compliance cost to States, MCOs, PIHPs, PAHPs, and PCCMs to the extent possible consistent with the detailed BBA requirements. We believe the final rule provisions will result in improved patient care outcomes and satisfaction over the long term. </P>
                    <P>Recognizing that a large number of entities, such as hospitals, State agencies, MCOs, PIHPs, PAHPs, and PCCMs will be affected by the implementation of these statutory provisions, and a substantial number of these entities may be required to make changes in their operations, we have prepared the following analysis. This analysis, in combination with the rest of the preamble, is consistent with the standards for analysis set forth by both the RFA and RIA. </P>
                    <HD SOURCE="HD3">1. State Options To Use Managed Care </HD>
                    <P>Under this provision, a State agency may amend its State plan to require all Medicaid beneficiaries in the State to enroll in either an MCO or PCCM without the need to apply for a waiver of “freedom of choice” requirements under either section 1915(b) or 1115 of the Act. However, waivers will still be required to include certain exempted populations in mandatory managed care programs, notably dual Medicare-Medicaid eligibles, Indians, and groups of children with special needs. Federal review will be limited to a one-time State plan amendment approval, while States will no longer need to request waiver renewals every 2 years for section 1915(b) of the Act and 3-5 years for section 1115 of the Act waivers. State agencies may include “exempted” populations as voluntary enrollees in the State plan managed care programs or as mandatory enrollees in State waiver programs. Currently, ten States use State plan amendments to require beneficiary enrollment in MCOs and PCCMs. In short, the new State plan option provides State agencies with a new choice of method to require participation in managed care. The ability of States to require enrollment in managed care through their State plans rather than through a waiver will not alter the standards of care practiced by MCOs and health care providers and, therefore, will not change the cost of providing care to managed care enrollees. </P>
                    <P>Pursuing the State plan amendment option rather than a waiver under section 1915(b) or 1115 of the Act waiver may reduce State administrative costs because it will eliminate the need for States to go through the waiver renewal process. Likewise, we will benefit from a reduced administrative burden if fewer waiver applications and renewals are requested. However, we believe the overall reduction in administrative burden to both the States and Federal government of approximately 40 hours annually per State will be offset by an additional burden of approximately 40 hours annually to develop and maintain the public process required by this rule. </P>
                    <HD SOURCE="HD3">2. Elimination of 75/25 Rule </HD>
                    <P>Before the passage of the BBA, nearly all MCOs, and PHPs contracting with Medicaid were required to limit combined Medicare and Medicaid participation to 75 percent of their enrollment, and State agencies had to verify enrollment composition as a contract requirement. Elimination of this rule allows MCOs, PIHPs, and PAHPs to participate without meeting this requirement and eliminates the need for States to monitor enrollment composition in contracting MCOs, PIHPs, and PAHPs. This will broaden the number of MCOs, PIHPs, and PAHPs available to States for contracting, leading to more choice for beneficiaries. This provision results in no additional burden on States since it merely eliminates a previous statutory requirement and has already been implemented through the BBA amendment and the State Medicaid Director Letter in 1998. </P>
                    <HD SOURCE="HD3">3. Increased Beneficiary Protection—Grievance Procedures </HD>
                    <P>
                        The BBA requires MCOs to establish internal grievance procedures that permit an eligible enrollee, or a provider on behalf of an enrollee, to challenge the denials of medical assistance or denials of payment. Prior to the enactment of the BBA, the regulations at 42 CFR 434.59, required MCOs and PHPs to have an internal grievance procedure. While the regulations do not specify a procedure for MCOs or PIHPs to follow for their grievance process, we believe that these entities have grievance systems that are similar in their processes to the requirements of this final regulation. This belief is supported 
                        <PRTPAGE P="41089"/>
                        by surveys of State Medicaid agencies, such as the survey of 10 States conducted by the National Academy for State Health Policy in 1999, and the survey of 13 States conducted by the American Public Human Services Association in 1997. Therefore, while this regulation will require uniform procedures across MCOs and PIHPs, and will require MCOs and PIHPs to change their procedures to conform to the regulation, the requirements of the final rule will not impose significant additional requirements on MCOs and PIHPs, beyond the 8 hours per entity we estimated in the Collection of Information section of this preamble (and included in the totals below) to make current systems conform with the provisions of this rule. For States, we estimate an additional burden for the development of an expedited process for State fair hearings of 20 hours per State for the 40 States that contract with MCOs and/or PIHPs for a total burden of 800 hours and a cost of $13,640. 
                    </P>
                    <P>In the Collection of Information section of this preamble, we assigned 9,875 burden hours to MCOs and PIHPs for the notice requirements of the grievance system, and 1,583 hours for the record keeping requirements and summary reports to be prepared by MCOs and PIHPs and submitted to the States. This results in 11,458 total burden hours. Using the mean hourly wage for the health care service sector (the Bureau of Labor Statistics, March 2001) of $16.34, this would result in a total cost to MCOs and PIHPs of $187,224. </P>
                    <HD SOURCE="HD3">4. Provision of Information </HD>
                    <P>In mandatory managed care programs, we require that beneficiaries be informed of the choices available to them when enrolling with MCOs, PIHPs, PAHPs, and PCCMs. Section 1932(a)(5) of the Act, enacted in section 4701(a)(5) of the BBA, describes the kind of information that must be made available to Medicaid enrollees and potential enrollees. It also requires that this information, and all enrollment notices and instructional materials related to enrollment in MCOs, PIHPs, PAHPs, and PCCMs be in a format that can be easily understood by the individuals to whom it is directed. We do not believe that these requirements deviate substantially from current practice, including the new mechanism requirement. Programs operated under section 1915(b) and 1115 authority have always had more stringent beneficiary protections. Furthermore, there is no way to quantify the degree of burden on State agencies, MCOs, PIHPs, PAHPs, and PCCMs for several reasons. We do not have State-specific data on what information States currently provide, or the manner in which they provide it. Variability among States indicates that implementing or continuing enrollee information requirements will represent different degrees of difficulty and expense. </P>
                    <P>The information requirements for MCOs and PCCMs in the final rule are required under the BBA. In this final rule, however, we extend requirements to PIHPs and PAHPs. In the Collection of Information section of this Preamble, we have estimated the total burden on States, MCOs, PIHPs, PAHPs, and PCCMs of 2,358,678 hours to comply with these requirements. Using a weighted average between the mean hourly wages for State employees and the health care service sector of $16.70, this results in a total cost of $39,389,923. </P>
                    <P>As a requirement under the provision of information section, State agencies opting to implement mandatory managed care programs under the State plan amendment option are required to provide comparative information on MCOs and PCCMs to potential enrollees. Currently only ten States have exercised the option to use a State plan amendment to require beneficiary enrollment in managed care. However, for States that do select this option, we do not believe that providing the comparative data in itself represents an additional burden, as these are elements of information that most States currently provide. The regulation specifies that the information must be presented in a comparative or chart-like form that facilitates comparison among MCOs, and PCCMs. This may be perceived as a burden to States that have previously provided this information in some other manner; however, it is our belief that even in the absence of the regulation, the trend is for States, and many accreditation bodies such as the National Committee for Quality Assurance (NCQA), to use chart-like formats. Consequently, enrollees will benefit from having better information for selecting MCOs, and PCCMs. Only a few States have opted for State plan amendments so far, but it is anticipated that more States will participate over the long term. States that participate in the future will benefit from any comparative tools developed by other States. We state in the Collection of Information section of this preamble that ten States availed themselves of the State Plan option, and thereby will be required to display information on a comparative chart. We are assuming it will take 8 hours each to create the comparative chart, or 80 hours for 10 States. Using the mean hourly wage for State employees (the Bureau of Labor Statistics, March 2001) of $17.05, this would result in total costs to States of $1364. We estimate that there may be additional costs associated with the production of these charts of $2,000—$5,000 per state that are not reflected in the Collection of Information requirements. This results in a total estimated cost from $21,364 to $51,364 to comply with this requirement </P>
                    <HD SOURCE="HD3">5. Demonstration of Adequate Capacity and Services </HD>
                    <P>The BBA requires Medicaid MCOs to provide the State and the Secretary of HHS with assurances of adequate capacity and services, including service coverage, within reasonable timeframes. States currently require assurances of adequate capacity and services as part of their existing contractual arrangements with MCOs, PIHPs and PAHPs. However, certification of adequacy has not been routinely provided to us in the past. Under this rule, each State retains its authority to establish standards for adequate capacity and services within MCO, PIHP and PAHP contracts. This may be perceived as a burden to MCOs, PIHPs and PAHPs, and for States that have not been required to formally certify that an MCO, PIHP or PAHP meets the States' capacity and service requirements. However, certification to us will ensure an important beneficiary protection while imposing only a minor burden on States to issue a certification to us of the information that should already be in their possession. </P>
                    <P>Each State agency has its own documentation requirements and its own procedures to assure adequate capacity and services. This regulation contemplates that States continue to have that flexibility. </P>
                    <P>
                        Under this regulation, State agencies must determine and specify both the detail and type of documentation to be submitted by the MCO, PIHP or PAHP as applicable, to assure adequate capacity and services and the type of certification to be submitted to us. We believe the 24 PAHPs contracting as dental plans or transportation providers will need to meet this requirement. Accordingly, variability among State agencies implementing this regulation represents different degrees of detail and expense. Regardless of the level of additional burden on MCOs, PIHPs, PAHPs, State agencies, and us, Medicaid beneficiaries will receive continued protections in access to health care under both State and Federal statute. For purposes of the Collection of Information section of this preamble, we assume that it would take 20 hours per 
                        <PRTPAGE P="41090"/>
                        MCO, PIHP, or PAHP to complete this requirement. For the 486 MCOs, PIHPs, and PAHPs, this requirement would take 9,720 hours to complete annually. Based on a mix of clerical and administrative salaries to produce, verify, and submit this information, we project a total cost of $174,960 (9720 hours at $18 per hour) to MCOs, PIHPs, and PAHPs to comply with this requirement. 
                    </P>
                    <HD SOURCE="HD3">6. New Quality Standards </HD>
                    <P>The BBA requires that each State agency have an ongoing quality assessment and improvement strategy for its Medicaid managed care contracting program. The strategy, among other things, must include: (1) Standards for access to care so that covered services are available within reasonable timeframes and in a manner that ensures continuity of care and adequate capacity of primary care and specialized services providers; (2) examination of other aspects of care and service directly related to quality of care, including grievance procedures and information standards; (3) procedures for monitoring and evaluating the quality and appropriateness of care and service to enrollees; and (4) periodic reviews to evaluate the effectiveness of the State's quality strategy.</P>
                    <P>The provisions of this final rule impose requirements for State quality strategies and requirements for MCOs and PIHPs that States are to incorporate as part of their quality strategy. These MCO and PIHP requirements address: (1) MCO and PIHP structure and operations; (2) Medicaid enrollees' access to care; and (3) MCO and PIHP responsibilities for measuring and improving quality. While these new Medicaid requirements are a significant increase in Medicaid regulatory requirements in comparison to the regulatory requirements that existed before the BBA, we believe the increases are appropriate because many of the requirements are either identical to or consistent with quality requirements placed on MCOs by private sector purchasers, the Medicare program, State licensing agencies, and private sector accreditation organizations. While these new requirements also will have implications for State Medicaid agencies that are responsible for monitoring for compliance with the new requirements, we believe that a number of recent statutory, regulatory, and private sector developments will enable State Medicaid agencies to more easily monitor for compliance than in the past at potentially less cost to the State. </P>
                    <P>Prior to issuance of that proposed rule, we worked closely with State Technical Advisory Groups (TAGs) in developing the managed care quality regulations and standards. Requirements under this final regulation build on a variety of initiatives of State Medicaid agencies and us to promote the assessment and improvement of quality in plans contracting with Medicaid, including: </P>
                    <P>The Quality Improvement System for Managed Care (QISMC), an initiative with State and Federal officials, beneficiary advocates, and the managed care industry to develop a coordinated quality oversight system for Medicare and Medicaid that reduces duplicate or conflicting efforts and emphasizes demonstrable and measurable improvement. </P>
                    <P>QARI, serving as a foundation to the development of QISMC, highlights the key elements in the Health Care Quality Improvement System (HCQIS), including internal quality assurance programs, State agency monitoring, and Federal oversight. This guidance emphasizes quality standards developed in conjunction with all system participants, such as managed care contractors, State regulators, Medicaid beneficiaries or their representatives, and external review organizations. </P>
                    <P>Further, we have built on efforts in other sectors in developing these quality requirements in order to capitalize on current activities and trends in the health care industry. For example, many employers and cooperative purchasing groups and some State agencies already require that organizations be accredited by the National Committee on Quality Assurance (NCQA), the Joint Commission on Accreditation of Healthcare Organizations (JCAHO), the American Accreditation Healthcare Commission (AAHC), or other independent bodies. Many also require that organizations report their performance using Health Plan Employer Data &amp; Information Set (HEDIS), Foundation for Accountability (FACCT), or other measures and conduct enrollee surveys using the Consumer Assessment of Health Plans Study (CAHPS) or other instruments. NCQA estimates that more than 90 percent of plans are collecting some or all of HEDIS data for their commercial population. Also, States have heightened their regulatory efforts through insurance or licensing requirements, and the National Association of Insurance Commissioners (NAIC) has developed model acts on network adequacy, quality assessment and improvement, and utilization review. </P>
                    <P>While we anticipate that many organizations will need to invest in new staff and information systems in order to perform these new quality improvement activities, it is difficult to quantify these financial and operational “investments,” as State agencies, MCOs, and PIHPs across the country exhibit varying capabilities in meeting these standards. These new quality requirements may present administrative challenges for some State agencies, MCOs, and PIHPs. However, States have significant latitude in how these requirements are implemented. Acknowledging that there likely will be some degree of burden on States, MCOs, and PIHPs, we also believe that the long-term benefits of greater accountability and improved quality in care delivery outweigh the costs of implementing and maintaining these processes over time. </P>
                    <P>According to the MCOs included in the Lewin study, many of the quality provisions in the September 1998 proposed rule (as well as those in this final rule) are not expected to have large incremental costs. The study mainly focused on the assessment and treatment management components of the regulation, as well as the quality improvement projects. For example, they estimate the cost of an initial assessment (called “screening” in this final regulation) as ranging from $0.17 to $0.26 per member per month (PMPM), but for an MCO that currently performs an initial assessment, the incremental cost is estimated as $0.03 to $0.06 PMPM. Extrapolating these estimates to the population of Medicaid managed care enrollees, if all enrollees were enrolled in plans doing initial assessments, the total cost would range from $6.8 million to $13.5 million. If all enrollees were enrolled in plans that did not perform initial assessments, the total cost would be $38 million to $58 million. </P>
                    <P>
                        Similarly, the costs of quality improvement projects can vary from $60,000 to $100,000 per project in the first year (start-up), $80,000 to $100,000 in the second and third years (the intervention and improvement measurement cycle), and $40,000 to $50,000 for the forth and subsequent years (ongoing performance measurement). If we assume that each of the approximately 339 MCOs and 123 PIHPs were to have one quality improvement project in each year, these costs will range from $180,000 to $230,000 per MCO or PIHP for a total cost of between $83 and $106 million. 
                        <PRTPAGE P="41091"/>
                    </P>
                    <HD SOURCE="HD3">7. Administration </HD>
                    <P>a. Certifications and Program Integrity Protections. Sections 1902(a)(4) and (19) of BBA require that States conduct appropriate processes and methods to ensure the efficient operation of the health plans. This includes mechanisms to not only safeguard against fraud and abuse but also to ensure accurate reporting of data among health plans, States, and us. </P>
                    <P>Section 438.602 of the final rule addresses the importance of reliable data that are submitted to States and requires MCOs and PIHPs to certify the accuracy of these data to the State. These data include enrollment information, encounter data, or other information that is used for payment determination. Even if States do not use encounter data to set capitation rates for MCOs and PIHPs, these data, along with provider and enrollment data, are useful for States in measuring quality performance and other monitoring of health plans. The provision of the final rule that requires plans to attest to the validity of data presents an additional step in the process of data submission. MCOs and PHPs have historically worked closely with States when reporting Medicaid data in order to affirm that the data are accurate and complete. Submitting a certification of validity of data submitted does not represent a significant burden to health plans. </P>
                    <P>Section 438.606 requires MCOs and PIHPs to have effective operational capabilities to guard against fraud and abuse. As a result, MCOs and PIHPs will uncover information about possible violations of law that they would be required to report to the State. We do not believe that these will be frequent or large in number and, therefore, will not result in burdens to the MCOs and PIHPs beyond what is usual in the course of business. </P>
                    <P>b. Change in Threshold from $100,000 to $1 Million. Before the passage of the BBA, the Secretary's prior approval was required for all HMO contracts involving expenditures of $100,000 or more. Under the BBA, the threshold amount is increased to $1 million. This change in threshold will have minimal impact on plans currently contracting with State agencies for Medicaid managed care. Currently, only one or two plans in the country have annual Medicaid expenditures of under $1 million. Therefore, this final rule provision will not affect a significant number of plans or States. </P>
                    <HD SOURCE="HD3">8. Permitting Same Copayments in Managed Care as in FFP </HD>
                    <P>Under section 4708(c) of the BBA, States may now allow copayments for services provided by MCOs to the same extent that they allow copayments under fee-for-service. Imposition of copayments in commercial markets typically results in lower utilization of medical services, depending on the magnitude of payments required of the enrollee. Thus, we normally expect State agencies that implement copayments for MCO enrollees to achieve some savings. However, applying copayments to Medicaid enrollees may cause States and MCOs to incur administrative costs that more than offset these savings. This is due to several factors. First, the amount of copayments allowed by statute are significantly lower than typical commercial copayments. Second, it is difficult to ensure compliance with these payments, especially given that the enrollees have limited income. Third, to achieve maximum compliance, collection efforts will be necessary on the part of MCOs or PHPs. It is also possible that, if State agencies take advantage of this option, Medicaid managed care enrollees may defer receipt of health care services, their health conditions may deteriorate, and the costs of medical treatment may be greater over the long term. For these reasons, it is difficult to predict how many States will take advantage of this option or of the net costs or savings that would result. </P>
                    <HD SOURCE="HD3">9. Six-Month Guaranteed Eligibility </HD>
                    <P>The legislation expanded the States' option to guarantee up to 6 months eligibility in two ways. First, it expands the types of MCOs whose members may have guaranteed eligibility, in that it now includes anyone who is enrolled with a Medicaid managed care organization as defined in section 1903(m)(1)(A) of the Act. Second, it expands the option to include those enrolled with a PCCM as defined in section 1905(t) of the Act. These changes were effective October 1, 1997. To the extent that State agencies choose this option, we expect MCOs, PIHPs, PAHPs, and PCCMs in those States to support the use of this provision since it affords health plans with assurance of membership for a specified period of time. Likewise, beneficiaries will gain from this coverage expansion, and continuity of care would be enhanced. The table below displays our estimates of the impact of the expanded option for 6 months of guaranteed eligibility under section 4709 of the BBA. </P>
                    <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s25,5,5,5,5">
                        <TTITLE>Cost of 6-Month Guaranteed Eligibility Option </TTITLE>
                        <TDESC>[Dollars in millions rounded to the nearest $5 million] </TDESC>
                        <BOXHD>
                            <CHED H="1">  </CHED>
                            <CHED H="1">
                                FY 
                                <LI>2002 </LI>
                            </CHED>
                            <CHED H="1">
                                FY 
                                <LI>2003 </LI>
                            </CHED>
                            <CHED H="1">
                                FY 
                                <LI>2004 </LI>
                            </CHED>
                            <CHED H="1">
                                FY 
                                <LI>2005 </LI>
                            </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Federal </ENT>
                            <ENT>80 </ENT>
                            <ENT>115 </ENT>
                            <ENT>165 </ENT>
                            <ENT>230 </ENT>
                        </ROW>
                        <ROW RUL="n,s">
                            <ENT I="01">State </ENT>
                            <ENT>60 </ENT>
                            <ENT>90 </ENT>
                            <ENT>125 </ENT>
                            <ENT>175 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="03">Total </ENT>
                            <ENT>140 </ENT>
                            <ENT>205 </ENT>
                            <ENT>290 </ENT>
                            <ENT>405 </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>Because this provision was effective shortly after enactment of the BBA, the estimates of Federal costs have been reflected in our Medicaid budget since FY 1998. The estimates assume that half of the current Medicaid population is enrolled in managed care and that this proportion would increase to about two-thirds by 2003. We also assume that 15 percent of managed care enrollees were covered by guaranteed eligibility under rules in effect prior to enactment of the BBA and that the effect of the expanded option under section 4709 of the BBA would be to increase this rate to 20 percent initially and to 30 percent by 2003. The guaranteed eligibility provision is assumed to increase average enrollment by 3 percent in populations covered by the option. This assumption is based on computer simulations of enrollment and turnover in the Medicaid program. Per capita costs used for the estimate were taken from the President's FY 1999 budget projections and the costs for children take into account the interaction of this provision with the State option for 12 months of continuous eligibility under section 4731 of the BBA. The distribution between Federal and State costs is based on the average Federal share representing 57 percent of the total costs. </P>
                    <P>In States electing the 6-month guaranteed eligibility option, Medicaid beneficiaries will have access to increased continuity of care, which should result in better health care management and improved clinical outcomes. </P>
                    <HD SOURCE="HD3">10. Financial Impact of Revised Rules for Setting Capitation Payments </HD>
                    <P>
                        This final rule replaces the current UPL requirement at § 447.361 with new rate-setting rules incorporating an expanded requirement for actuarial soundness of capitation rates as described in detail in § 438.6(c). In general, we do not expect a major budget impact from the use of these new rate setting rules. While the rate setting rules may provide some States additional flexibility in setting higher capitation rates than what would have 
                        <PRTPAGE P="41092"/>
                        been allowed under current rules, we believe that the requirements for actuarial certification of rates, along with budgetary considerations by State policy makers, would serve to limit increases to within reasonable amounts. Moreover, the Secretary retains the authority to look behind rates that appear questionable and disapprove any that do not comply with the rate setting requirements. 
                    </P>
                    <P>Because we cannot predict State behavior in these areas, we are unable to quantify the impact of potential rate increases that may be triggered by these new rules. However, as an illustration of the potential impact, we can compare states such as Oregon and Tennessee, which have had the upper payment limit requirement waived under their health care reform demonstrations to the other states providing managed care through contracts with MCOs. The capitation rates paid by these states do no vary significantly from most states operating under the UPL requirement. </P>
                    <P>Another example to consider is pediatric dental care, where low payment rates have frequently been cited as a barrier to access. Using Medicaid statistical and financial data, we estimate that the average Medicaid payment for dental services to children, on a per member per month (PMPM) basis, is about $10. A recent study by the Milbank Memorial Fund recommended a model pediatric dental program that is estimated to cost $14.50 PMPM, or 45 percent higher than the current average.</P>
                    <P>If these new rules induced 10 percent of States (on a dollar volume basis) to adopt the Millbank program or its monetary equivalent, annual Federal and State premium costs for children would rise by about 0.3 percent, or approximately $50 million. As indicated above, such increases in spending could be achieved under current rules, so it is difficult to predict the extent to which the proposed changes to rate setting requirements would precipitate these or any other additional costs to the Medicaid program. </P>
                    <P>As discussed in the Collection of Information section of this Preamble, we expect a net reduction in administrative burden on states of 11,904 hours through this change, resulting in a projected savings of $202,963. </P>
                    <HD SOURCE="HD3">11. Costs to States and Providers of Provisions Assigned Burden Hours </HD>
                    <P>The Collection of Information Requirements section of this preamble includes estimates of the number of hours it will take States, providers, and enrollees to provide information required under this regulation. For States, the total hours are estimated to be 2,481,076. To estimate the cost impact of these requirements on States, we assume the total cost of these requirements to be the sum of the estimated hours times the mean hourly wage for State employees of $17.05 (the Bureau of Labor Statistics, March, 2001), or $42,302,346. Because the Federal government shares the general administrative costs of the Medicaid program with the States, we estimate the total cost of these requirements to States to be approximately $21 million dollars annually. </P>
                    <P>For MCOs, PIHPs, PAHPs, and PCCMs, we estimate that the Collection and Information Requirements will take 1,264,461.5 hours annually to complete. To estimate the cost impact of these requirements on providers, we multiplied these hours by the mean hourly wage for health care service workers of $16.34 (the Bureau of Labor Statistics, March, 2001) to estimate the cost of these requirements to be approximately $20.7 million. </P>
                    <HD SOURCE="HD3">12. Contract Monitoring </HD>
                    <P>This final rule requires States to include certain specifications in their contracts with MCOs, PIHPs, PAHPs, and PCCMs and to monitor compliance with those contract provisions. It also requires States to take a proactive role in monitoring the quality of their managed care program. These requirements add some administrative burden and costs to States. The amount of additional administrative cost will vary by State depending on how inclusive current practice is of the new requirements. In addition, for those States not using like requirements at present, we believe that most will be adopting similar requirements on their own in the future absent this final rule. </P>
                    <P>The final rule also increases Federal responsibilities for monitoring State performance in managing their managed care programs. However, no new Federal costs are expected as we plan to use existing staff to monitor these new requirements. </P>
                    <HD SOURCE="HD2">C. Alternatives Considered </HD>
                    <P>In publishing this final rule implementing the BBA Medicaid managed care provisions, we considered two main alternatives. The first alternative was to allow the January 19, 2001 final rule with comment to become effective as published. The second alternative was to implement the BBA statute as written and not regulate beyond the statutory language. We believe that this final rule as now written maintains an appropriate balance between these two alternatives. </P>
                    <P>We realized that allowing the more prescriptive January 2001 rule to become effective would cost states and health plans more to implement and could potentially restrict access if states and health plans became unwilling to participate in Medicaid managed care. We heard from several key stakeholders that the January 2001 final rule with comment was overly burdensome and did not allow sufficient State flexibility. In addition, others stated that the January 2001 final rule was a micro-managing approach to Medicaid managed care and would make it increasingly difficult for State Medicaid agencies to provide access to quality health care through managed care, since MCOs and other providers would not be willing to participate. Many felt that the requirements would be administratively burdensome to implement, particularly for small entities, and created significant business risks for MCOs. The rules would have resulted in an increase in health plan compliance costs and a significant additional burden on small entities without meaningfully improving patient care. Particular examples of provisions, which would increase costs significantly, were the requirements for specific timeframes for conducting initial health screenings, performing comprehensive health assessments and the detailed requirements under the notice of action provisions. Based on these concerns we decided that we needed more time to understand the impact of the January 2001 final rule. In the interim we believed the best approach was to streamline the January 2001 provisions and republish as a proposed rule. The removal of the highly prescriptive requirements will enhance States' abilities to continue innovations with their managed care programs leading to improved efficiencies and reduced costs. Further the new rate setting provisions will result in rates that more appropriately reflect the cost of health services. </P>
                    <P>
                        On the other hand, implementing the BBA statutory language as written would not have provided adequate patient protections and may have resulted in lower overall quality of care. In addition to the broad patient protection and quality provisions in the BBA statute, this final rule provides consumers with comprehensive, easy-to-understand information about their health plan, establishes timeframes for review of grievance and appeals, requires adequate provider networks sufficient to meet the needs of enrolled individuals, requires identification of individuals with special health care 
                        <PRTPAGE P="41093"/>
                        needs, specifies timeframes for service authorization decisions and requires continuity and coordination of care. In addition, States must have an overall strategy to ensure the delivery of quality health care by its MCOs, PIHPs and PAHPs. Further, MCOs and PIHPs are required to conduct performance improvement projects that must be designed to achieve significant improvement in clinical care and nonclinical care areas that are expected to have a favorable effect on health outcomes and enrollee satisfaction. We believe that all of these provisions, while consistent with the BBA's intent will work to improve overall quality of care for Medicaid beneficiaries enrolled in Medicaid managed care. Through enhanced care coordination and quality monitoring, the final rule's provisions will enable the earlier identification of serious medical conditions and the effective management of individuals with special health care needs. States will be able to highlight quality of care, which will result in decreased costs for health plans and States. All of these requirements will work together to improve patient outcomes and possibly reduce health complications and costly procedures. 
                    </P>
                    <P>These new rules appropriately balance the necessary protections for all beneficiaries enrolled in MMC and state flexibility to manage their programs. They create a framework for States to design managed care programs that will permit innovation and support program growth. This final rule is written to recognize the responsibilities of States and the need to employ different approaches to achieving the same goal of strong, viable Medicaid managed care programs that deliver high quality health care within State marketplaces and health care delivery systems. </P>
                    <HD SOURCE="HD2">D. Conclusion </HD>
                    <P>This BBA managed care final rule will affect States, MCOs, PIHPs, PAHPs, PCCMs, providers, and beneficiaries and us in different ways. The initial investments that are needed by State agencies and MCOs, PIHPs, PAHPs, and PCCMs will result in improved and more consistent standards for the delivery of health care to Medicaid beneficiaries. Greater consumer safeguards will result from new quality improvement and protection provisions, which meet or exceed those in other public or private health care plans. In addition, this rule provides a degree of flexibility in how these new requirements are met, so that necessary changes can be phased in by states and health plans in ways that work best in a particular state's Medicaid program. Further, the new rules on payments under risk contracts remove the limitation on payment rates at historical fee-for-service costs, giving states some added flexibility in establishing payment systems that maintain or expand their current managed care programs, thus enhancing choice for Medicaid consumers and their ability to find a medical home. Consequently, long term savings will be derived from more consistent standards across States, MCOs, PIHPs, PAHPs, and PCCMs and increased opportunities for provider and beneficiary involvement in improved access, outcomes, and satisfaction. </P>
                    <P>In accordance with the provisions of Executive Order 12866, this regulation was reviewed by the Office of Management and Budget. </P>
                    <HD SOURCE="HD2">E. Unfunded Mandates Reform Act of 1995 </HD>
                    <P>Section 202 of the Unfunded Mandates Reform Act of 1995 also requires that agencies assess anticipated costs and benefits before issuing any rule that may result in an expenditure in any 1 year by State, local, and tribal governments, in the aggregate, or by the private sector, of $110 million or more (adjusted annually for inflation). We have determined that this final rule does not impose any mandates on State, local, or tribal governments, or the private sector that will result in an annual expenditure of $110 million or more. </P>
                    <HD SOURCE="HD2">F. Federalism </HD>
                    <P>Under Executive Order 13132, we are required to adhere to certain criteria regarding Federalism in developing regulations. We have determined that this final rule would not significantly affect States rights, roles, and responsibilities. This regulation supersedes existing State laws regulating managed care, unless State laws are more restrictive. </P>
                    <P>The BBA requires States that contract with organizations under section 1903(m) of the Act to have certain beneficiary protections in place when mandating managed care enrollment. This rule implements those BBA provisions in accordance with the Administrative Procedure Act. This rule also eliminates certain requirements viewed by States as impediments to the growth of managed care programs, such as disenrollment without cause at any time and the inability to require enrollment in managed care without a waiver. We also apply many of these requirements to prepaid health plans that provide for inpatient hospital and institutional services. We believe this is consistent with the intent of the Congress in enacting the quality and beneficiary protection provisions of the BBA. We worked with States in developing this final regulation. In 1997-1998, when we were developing the original proposed rule, published in September 1998, we consulted with State Medicaid agency representatives in order to understand the potential impacts of the provisions of the regulations then being considered. In November 1997 we met with the Executive Board of the National Association of State Medicaid Directors (NASMD) and discussed the process for providing initial guidance to States about the Medicaid provisions of the BBA. We provided this guidance in a series of over 50 letters to State Medicaid Directors. Much of the policy included in this final regulation relating to the State plan option provision was included in these letters. In May 1998, we briefed the Executive Committee of NASMD on the general content of the proposed regulation. More specific State input was obtained through discussions throughout the spring of 1998 with the Medicaid Technical Advisory Groups (TAGs) on Managed Care and Quality. These groups are comprised of Medicaid agency staff with notable expertise in the subject area and our regional office staff and are staffed by the American Public Human Services Association. The Managed Care TAG devoted much of its agenda for several monthly meetings to BBA issues. The Quality TAG participated in two conference calls exclusively devoted to discussion of BBA quality issues. Through these contacts, we explored with State agencies their preferences regarding policy issues and the feasibility and practicality of implementing policy under consideration. We also invited public comments as part of the rulemaking process and received comments from over 380 individuals and organizations. Most of the commenters had substantial comments that addressed many provisions of the regulation. </P>
                    <P>
                        Following publication of the final rule with comment on January 19, 2001, the new Administration delayed the effective date of the January 2001 rule three times to provide it an opportunity to conduct its own review of the regulation. During this additional review period, we heard from key stakeholders in the Medicaid managed care program, including States, provider organizations, and advocates for beneficiaries. Some of these parties expressed serious concerns about the regulation. After further consideration of the regulations and the issues raised, 
                        <PRTPAGE P="41094"/>
                        in August 2001 we published an interim final rule with comment period to further delay the effective date of the January 2001 final rule with comment. Immediately following the further delay, on August 20, 2001 we published a new Medicaid managed care proposed rule to implement the Medicaid managed care provisions of the BBA and to give consideration to all the concerns that were communicated to us. 
                    </P>
                    <P>We received comments from over 300 parties (States, managed care organizations, providers, provider organizations and advocates for beneficiaries) on the August 2001 proposed rule. Many of the recommendations made by commenters have been incorporated into this final rule. For recommendations not accepted, a response has been included in this preamble. Moreover, we discussed technical issues with State experts through the TAGS to make certain that the final rule could be practically applied.</P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects </HD>
                        <CFR>42 CFR Part 400 </CFR>
                        <P>Grant programs-health, Health facilities, Health maintenance organizations (HMO), Medicaid, Medicare, Reporting and recordkeeping requirements.</P>
                        <CFR>42 CFR Part 430 </CFR>
                        <P>Administrative practice and procedure, Grant programs-health, Medicaid, Reporting and recordkeeping requirements. </P>
                        <CFR>42 CFR Part 431 </CFR>
                        <P>Grant programs-health, Health facilities, Medicaid, Privacy, Reporting and recordkeeping requirements. </P>
                        <CFR>42 CFR Part 434 </CFR>
                        <P>Grant programs-health, Health maintenance organizations (HMO), Medicaid, Reporting and recordkeeping requirements. </P>
                        <CFR>42 CFR Part 435 </CFR>
                        <P>Aid to Families with Dependent Children, Grant programs-health, Medicaid, Reporting and recordkeeping requirements, Supplemental Security Income (SSI), Wages. </P>
                        <CFR>42 CFR Part 438 </CFR>
                        <P>Grant programs-health, Managed care entities, Medicaid, Quality assurance, Reporting and recordkeeping requirements. </P>
                        <CFR>42 CFR Part 440 </CFR>
                        <P>Grant programs-health, Medicaid.</P>
                    </LSTSUB>
                    <REGTEXT TITLE="42" PART="400">
                        <AMDPAR>For the reasons set forth in the preamble, 42 CFR chapter IV is amended as set forth below: </AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 400—INTRODUCTION; DEFINITIONS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 400 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Secs. 1102 and 1871 of the Social Security Act (42 U.S.C. 1302 and 1395hh). </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="400">
                        <AMDPAR>2. In § 400.203, the following definitions for “PCCM” and “PCP” are added, in alphabetical order, and the definition of “provider” is revised to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 400.203</SECTNO>
                            <SUBJECT>Definitions specific to Medicaid. </SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">PCCM</E>
                                 stands for primary care case manager. 
                            </P>
                            <P>
                                <E T="03">PCP</E>
                                 stands for primary care physician. 
                            </P>
                            <P>
                                <E T="03">Provider</E>
                                 means either of the following: 
                            </P>
                            <P>(1) For the fee-for-service program, any individual or entity furnishing Medicaid services under an agreement with the Medicaid agency. </P>
                            <P>(2) For the managed care program, any individual or entity that is engaged in the delivery of health care services and is legally authorized to do so by the State in which it delivers the services. </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="430">
                        <PART>
                            <HD SOURCE="HED">PART 430—GRANTS TO STATES FOR MEDICAL ASSISTANCE PROGRAMS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 430 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Sec. 1102 of the Social Security Act (42 U.S.C. 1302). </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="430">
                        <AMDPAR>2. New § 430.5 is added to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 430.5</SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <P>As used in this subchapter, unless the context indicates otherwise— </P>
                            <P>
                                <E T="03">Contractor</E>
                                 means any entity that contracts with the State agency, under the State plan, in return for a payment, to process claims, to provide or pay for medical services, or to enhance the State agency's capability for effective administration of the program. 
                            </P>
                            <P>
                                <E T="03">Representative</E>
                                 has the meaning given the term by each State consistent with its laws, regulations, and policies.
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="431">
                        <PART>
                            <HD SOURCE="HED">PART 431—STATE ORGANIZATION AND GENERAL ADMINISTRATION </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 431 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Sec. 1102 of the Social Security Act (42 U.S.C. 1302). </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="431">
                        <AMDPAR>2. Section 431.51 is amended as follows: </AMDPAR>
                        <P>a. In paragraph (a) introductory text, the phrase “and 1915(a) and </P>
                        <P>(b) of the Act” is revised to read “1915(a) and (b) and 1932(a)(3) of the Act.” b. Paragraphs (a)(4) and (a)(5) are revised and a new paragraph (a)(6) is added, to read as set forth below. </P>
                        <P>c. In paragraph (b)(1) introductory text, “and part 438 of this chapter” is added immediately before the comma that follows “this section”. </P>
                        <P>d. In paragraph (b)(2), “an HMO” is revised to read “a Medicaid MCO”. </P>
                        <SECTION>
                            <SECTNO>§ 431.51</SECTNO>
                            <SUBJECT>Free choice of providers. </SUBJECT>
                            <P>(a) * * * </P>
                            <P>(4) Section 1902(a)(23) of the Act provides that a recipient enrolled in a primary care case management system or Medicaid managed care organization (MCO) may not be denied freedom of choice of qualified providers of family planning services. </P>
                            <P>(5) Section 1902(e)(2) of the Act provides that an enrollee who, while completing a minimum enrollment period, is deemed eligible only for services furnished by or through the MCO or PCCM, may, as an exception to the deemed limitation, seek family planning services from any qualified provider. </P>
                            <P>(6) Section 1932(a) of the Act permits a State to restrict the freedom of choice required by section 1902(a)(23), under specified circumstances, for all services except family planning services. </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="431">
                        <AMDPAR>3. In § 431.55, a sentence is added at the end of paragraph (c)(1)(i), to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 431.55</SECTNO>
                            <SUBJECT>Waiver of other Medicaid requirements. </SUBJECT>
                            <STARS/>
                            <P>(c) * * * </P>
                            <P>(1) * * * </P>
                            <P>(i) * * * The person or agency must comply with the requirements set forth in part 438 of this chapter for primary care case management contracts and systems. </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="431">
                        <P>4. Section 431.200 is revised to read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 431.200</SECTNO>
                            <SUBJECT>Basis and scope. </SUBJECT>
                            <P>This subpart— </P>
                            <P>(a) Implements section 1902(a)(3) of the Act, which requires that a State plan provide an opportunity for a fair hearing to any person whose claim for assistance is denied or not acted upon promptly; </P>
                            <P>
                                (b) Prescribes procedures for an opportunity for a hearing if the State agency or PAHP takes action, as stated in this subpart, to suspend, terminate, or reduce services, or an MCO or PIHP 
                                <PRTPAGE P="41095"/>
                                takes action under subpart F of part 438 of this chapter; and 
                            </P>
                            <P>(c) Implements sections 1919(f)(3) and 1919(e)(7)(F) of the Act by providing an appeals process for any person who— </P>
                            <P>(1) Is subject to a proposed transfer or discharge from a nursing facility; or </P>
                            <P>(2) Is adversely affected by the pre-admission screening or the annual resident review that are required by section 1919(e)(7) of the Act. </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="431">
                        <AMDPAR>5. In § 431.201, the following definition is added in alphabetical order: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 431.201</SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Service authorization request</E>
                                 means a managed care enrollee's request for the provision of a service. 
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="431">
                        <AMDPAR>6. In § 431.220, the introductory text of paragraph (a) is revised, the semicolons after paragraphs (a)(1), (a)(2), and (a)(3) and the “and” at the end of paragraph (a)(3) are removed and periods are added in their place, and new paragraphs (a)(5) and (a)(6) are added, to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 431.220</SECTNO>
                            <SUBJECT>When a hearing is required. </SUBJECT>
                            <P>(a) The State agency must grant an opportunity for a hearing to the following: </P>
                            <P>* * *</P>
                            <P>(5) Any MCO or PIHP enrollee who is entitled to a hearing under subpart F of part 438 of this chapter. </P>
                            <P>(6) Any PAHP enrollee who has an action as stated in this subpart. </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="431">
                        <AMDPAR>7. In § 431.244, paragraph (f) is revised to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 431.244</SECTNO>
                            <SUBJECT>Hearing decisions. </SUBJECT>
                            <STARS/>
                            <P>(f) The agency must take final administrative action as follows: </P>
                            <P>(1) Ordinarily, within 90 days from the earlier of the following: </P>
                            <P>(i) The date the enrollee filed an MCO or PIHP appeal, not including the number of days the enrollee took to subsequently file for a State fair hearing; or </P>
                            <P>(ii) If permitted by the State, the date the enrollee filed for direct access to a State fair hearing. </P>
                            <P>(2) As expeditiously as the enrollee's health condition requires, but no later than 3 working days after the agency receives, from the MCO or PIHP, the case file and information for any appeal of a denial of a service that, as indicated by the MCO or PIHP— </P>
                            <P>(i) Meets the criteria for expedited resolution as set forth in § 438.410(a) of this chapter, but was not resolved within the timeframe for expedited resolution; or </P>
                            <P>(ii) Was resolved within the timeframe for expedited resolution, but reached a decision wholly or partially adverse to the enrollee. </P>
                            <P>(3) If the State agency permits direct access to a State fair hearing, as expeditiously as the enrollee's health condition requires, but no later than 3 working days after the agency receives, directly from an MCO or PIHP enrollee, a fair hearing request on a decision to deny a service that it determines meets the criteria for expedited resolution, as set forth in § 438.410(a) of this chapter. </P>
                            <STARS/>
                              
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <PART>
                            <HD SOURCE="HED">PART 434—CONTRACTS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 434 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Sec 1102 of the Social Security Act (42 U.S.C. 1302). </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <AMDPAR>2. In § 434.1, paragraph (a) is revised to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 434.1</SECTNO>
                            <SUBJECT>Basis and scope. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Statutory basis.</E>
                                 This part is based on section 1902(a)(4) of the Act, which requires that the State plan provide for methods of administration that the Secretary finds necessary for the proper and efficient operation of the plan. 
                            </P>
                            <STARS/>
                              
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <SECTION>
                            <SECTNO>§ 434.2</SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                        </SECTION>
                        <AMDPAR>3. In § 434.2, the definitions of “capitation fee”, “clinical laboratory”, “contractor”, “enrolled recipient”, “Federally qualified HMO”, “health insuring organization”, “Health maintenance organization (HMO)”, “nonrisk”, “Prepaid health plan (PHP) “provisional status HMO”, and “risk or underwriting risk” are removed. </AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <SECTION>
                            <SECTNO>§ 434.6</SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                        </SECTION>
                        <AMDPAR>4. In paragraph (a)(1), the term “appendix G” is removed.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <SECTION>
                            <SECTNO>§§ 434.20 through 434.38 (Subpart C)</SECTNO>
                            <SUBJECT>[Removed] </SUBJECT>
                        </SECTION>
                        <AMDPAR>5. Subpart C, consisting of §§ 434.20 through 434.38, is removed and reserved. </AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <SECTION>
                            <SECTNO>§§ 434.42 through 434.44</SECTNO>
                            <SUBJECT>[Removed] </SUBJECT>
                        </SECTION>
                        <AMDPAR>6. In subpart D, §§ 434.42 and 434.44 are removed.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <SECTION>
                            <SECTNO>§§ 434.50 through 434.67 (Subpart E)</SECTNO>
                            <SUBJECT>[Removed] </SUBJECT>
                        </SECTION>
                        <AMDPAR>7. Subpart E, consisting of §§ 434.50 through 434.67, is removed and reserved.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <AMDPAR>8. Section 434.70 is revised to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 434.70</SECTNO>
                            <SUBJECT>Conditions for Federal financial participation (FFP). </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Basic requirements.</E>
                                 FFP is available only for periods during which the contract— 
                            </P>
                            <P>(1) Meets the requirements of this part; </P>
                            <P>(2) Meets the applicable requirements of 45 CFR part 74; and </P>
                            <P>(3) Is in effect. </P>
                            <P>
                                (b) 
                                <E T="03">Basis for withholding.</E>
                                 CMS may withhold FFP for any period during which the State fails to meet the State plan requirements of this part.
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="434">
                        <SECTION>
                            <SECTNO>§§ 434.71 through 434.75 and 434.80</SECTNO>
                            <SUBJECT>[Removed] </SUBJECT>
                        </SECTION>
                        <AMDPAR>9. Sections 434.71 through 434.75, and 434.80 are removed.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="435">
                        <PART>
                            <HD SOURCE="HED">PART 435—ELIGIBILITY IN THE STATES, THE DISTRICT OF COLUMBIA, THE NORTHERN MARIANA ISLANDS, AND AMERICAN SAMOA </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 435 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Sec. 1102 of the Social Security Act (42 U.S.C. 1302).</P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="435">
                        <SECTION>
                            <SECTNO>§ 435.212</SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                        </SECTION>
                        <AMDPAR>2. Amend § 435.212 as follows: </AMDPAR>
                        <AMDPAR>a. Throughout the section, “HMO”, wherever it appears, is revised to read “MCO”. </AMDPAR>
                        <AMDPAR>b. The section heading and the introductory text is revised to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 435.212</SECTNO>
                            <SUBJECT>Individuals who would be ineligible if they were not enrolled in an MCO or PCCM. </SUBJECT>
                            <P>The State agency may provide that a recipient who is enrolled in an MCO or PCCM and who becomes ineligible for Medicaid is considered to continue to be eligible— </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="435">
                        <AMDPAR>3. Section 435.326 is revised to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 435.326</SECTNO>
                            <SUBJECT>Individuals who would be ineligible if they were not enrolled in an MCO or PCCM. </SUBJECT>
                            <P>If the agency provides Medicaid to the categorically needy under § 435.212, it may provide it under the same rules to medically needy recipients who are enrolled in MCOs or PCCMs. </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="435">
                        <SECTION>
                            <SECTNO>§ 435.1002</SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                        </SECTION>
                        <AMDPAR>4. In §§ 435.1002, in paragraph (a), “§§ 435.1007 and 435.1008” is revised to read “§§ 435.1007, 435.1008, and 438.814 of this chapter”. </AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="438">
                        <AMDPAR>5. A new part 438 is added to chapter IV to read as follows: </AMDPAR>
                        <PART>
                            <PRTPAGE P="41096"/>
                            <HD SOURCE="HED">PART 438—MANAGED CARE </HD>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart A—General Provisions </HD>
                                <SECHD>Sec. </SECHD>
                                <SECTNO>438.1</SECTNO>
                                <SUBJECT>Basis and scope. </SUBJECT>
                                <SECTNO>438.2</SECTNO>
                                <SUBJECT>Definitions. </SUBJECT>
                                <SECTNO>438.6</SECTNO>
                                <SUBJECT>Contract requirements. </SUBJECT>
                                <SECTNO>438.8</SECTNO>
                                <SUBJECT>Provisions that apply to PIHPs and PAHPs. </SUBJECT>
                                <SECTNO>438.10</SECTNO>
                                <SUBJECT>Information requirements. </SUBJECT>
                                <SECTNO>438.12</SECTNO>
                                <SUBJECT>Provider discrimination prohibited. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—State Responsibilities </HD>
                                <SECTNO>438.50</SECTNO>
                                <SUBJECT>State Plan requirements. </SUBJECT>
                                <SECTNO>438.52</SECTNO>
                                <SUBJECT>Choice of MCOs, PIHPs, PAHPs, and PCCMs. </SUBJECT>
                                <SECTNO>438.56</SECTNO>
                                <SUBJECT>Disenrollment: Requirements and limitations. </SUBJECT>
                                <SECTNO>438.58</SECTNO>
                                <SUBJECT>Conflict of interest safeguards. </SUBJECT>
                                <SECTNO>438.60</SECTNO>
                                <SUBJECT>Limit on payment to other providers. </SUBJECT>
                                <SECTNO>438.62</SECTNO>
                                <SUBJECT>Continued services to recipients. </SUBJECT>
                                <SECTNO>438.66</SECTNO>
                                <SUBJECT>Monitoring procedures. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Enrollee Rights and Protections </HD>
                                <SECTNO>438.100</SECTNO>
                                <SUBJECT> Enrollee rights. </SUBJECT>
                                <SECTNO>438.102</SECTNO>
                                <SUBJECT>Provider-enrollee communications. </SUBJECT>
                                <SECTNO>438.104</SECTNO>
                                <SUBJECT>Marketing activities. </SUBJECT>
                                <SECTNO>438.106</SECTNO>
                                <SUBJECT>Liability for payment. </SUBJECT>
                                <SECTNO>438.108</SECTNO>
                                <SUBJECT>Cost sharing. </SUBJECT>
                                <SECTNO>438.114</SECTNO>
                                <SUBJECT>Emergency and poststabilization services. </SUBJECT>
                                <SECTNO>438.116</SECTNO>
                                <SUBJECT>Solvency standards. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart D—Quality Assessment and Performance Improvement </HD>
                                <SECTNO>438.200</SECTNO>
                                <SUBJECT>Scope. </SUBJECT>
                                <SECTNO>438.202</SECTNO>
                                <SUBJECT>State responsibilities. </SUBJECT>
                                <SECTNO>438.204</SECTNO>
                                <SUBJECT>Elements of State quality strategies. </SUBJECT>
                                <HD SOURCE="HD1">Access Standards </HD>
                                <SECTNO>438.206</SECTNO>
                                <SUBJECT>Availability of services. </SUBJECT>
                                <SECTNO>438.207</SECTNO>
                                <SUBJECT>Assurances of adequate capacity and services. </SUBJECT>
                                <SECTNO>438.208</SECTNO>
                                <SUBJECT>Coordination and continuity of care. </SUBJECT>
                                <SECTNO>438.210</SECTNO>
                                <SUBJECT>Coverage and authorization of services. </SUBJECT>
                                <HD SOURCE="HD1">Structure and Operation Standards </HD>
                                <SECTNO>438.214</SECTNO>
                                <SUBJECT>Provider selection. </SUBJECT>
                                <SECTNO>438.218</SECTNO>
                                <SUBJECT>Enrollee information. </SUBJECT>
                                <SECTNO>438.224</SECTNO>
                                <SUBJECT>Confidentiality. </SUBJECT>
                                <SECTNO>438.226</SECTNO>
                                <SUBJECT>Enrollment and disenrollment. </SUBJECT>
                                <SECTNO>438.228</SECTNO>
                                <SUBJECT>Grievance systems. </SUBJECT>
                                <SECTNO>438.230</SECTNO>
                                <SUBJECT>Subcontractual relationships and delegation. </SUBJECT>
                                <HD SOURCE="HD1">Measurement and Improvement Standards </HD>
                                <SECTNO>438.236</SECTNO>
                                <SUBJECT>Practice guidelines. </SUBJECT>
                                <SECTNO>438.240</SECTNO>
                                <SUBJECT>Quality assessment and performance improvement program. </SUBJECT>
                                <SECTNO>438.242</SECTNO>
                                <SUBJECT>Health information systems. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart E—[Reserved] </HD>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart F—Grievance System </HD>
                                <SECTNO>438.400</SECTNO>
                                <SUBJECT> Statutory basis and definitions. </SUBJECT>
                                <SECTNO>438.402</SECTNO>
                                <SUBJECT>General requirements. </SUBJECT>
                                <SECTNO>438.404</SECTNO>
                                <SUBJECT>Notice of action. </SUBJECT>
                                <SECTNO>438.406</SECTNO>
                                <SUBJECT>Handling of grievances and appeals. </SUBJECT>
                                <SECTNO>438.408</SECTNO>
                                <SUBJECT>Resolution and notification: Grievances and appeals. </SUBJECT>
                                <SECTNO>438.410</SECTNO>
                                <SUBJECT>Expedited resolution of appeals. </SUBJECT>
                                <SECTNO>438.414</SECTNO>
                                <SUBJECT>Information about the grievance system to providers and subcontractors. </SUBJECT>
                                <SECTNO>438.416</SECTNO>
                                <SUBJECT>Recordkeeping and reporting requirements. </SUBJECT>
                                <SECTNO>438.420</SECTNO>
                                <SUBJECT>Continuation of benefits while the MCO or PIHP appeal and the State fair hearing are pending. </SUBJECT>
                                <SECTNO>438.424</SECTNO>
                                <SUBJECT>Effectuation of reversed appeal resolutions. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart G—[Reserved] </HD>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart H—Certifications and Program Integrity </HD>
                                <SECTNO>438.600</SECTNO>
                                <SUBJECT>Statutory basis. </SUBJECT>
                                <SECTNO>438.602</SECTNO>
                                <SUBJECT>Basic rule. </SUBJECT>
                                <SECTNO>438.604</SECTNO>
                                <SUBJECT>Data that must be certified. </SUBJECT>
                                <SECTNO>438.606</SECTNO>
                                <SUBJECT>Source, content, and timing of certification. </SUBJECT>
                                <SECTNO>438.608</SECTNO>
                                <SUBJECT>Program integrity requirements. </SUBJECT>
                                <SECTNO>438.610</SECTNO>
                                <SUBJECT>Prohibited affiliations with individuals debarred by Federal agencies. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart I—Sanctions </HD>
                                <SECTNO>438.700</SECTNO>
                                <SUBJECT>Basis for imposition of sanctions. </SUBJECT>
                                <SECTNO>438.702</SECTNO>
                                <SUBJECT>Types of intermediate sanctions. </SUBJECT>
                                <SECTNO>438.704</SECTNO>
                                <SUBJECT>Amounts of civil money penalties. </SUBJECT>
                                <SECTNO>438.706</SECTNO>
                                <SUBJECT>Special rules for temporary management. </SUBJECT>
                                <SECTNO>438.708</SECTNO>
                                <SUBJECT>Termination of an MCO or PCCM contract. </SUBJECT>
                                <SECTNO>438.710</SECTNO>
                                <SUBJECT>Due process: Notice of sanction and pre-termination hearing. </SUBJECT>
                                <SECTNO>438.722</SECTNO>
                                <SUBJECT>Disenrollment during termination hearing process. </SUBJECT>
                                <SECTNO>438.724</SECTNO>
                                <SUBJECT>Notice to CMS. </SUBJECT>
                                <SECTNO>438.726</SECTNO>
                                <SUBJECT>State plan requirement.</SUBJECT>
                                <SECTNO>438.730</SECTNO>
                                <SUBJECT>Sanction by CMS: Special rules for MCOs. </SUBJECT>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart J—Conditions for Federal Financial Participation </HD>
                                <SECTNO>438.802</SECTNO>
                                <SUBJECT>Basic requirements. </SUBJECT>
                                <SECTNO>438.806</SECTNO>
                                <SUBJECT>Prior approval. </SUBJECT>
                                <SECTNO>438.808</SECTNO>
                                <SUBJECT>Exclusion of entities. </SUBJECT>
                                <SECTNO>438.810</SECTNO>
                                <SUBJECT>Expenditures for enrollment broker services. </SUBJECT>
                                <SECTNO>438.812</SECTNO>
                                <SUBJECT>Costs under risk and nonrisk contracts. </SUBJECT>
                                <AUTH>
                                    <HD SOURCE="HED">Authority:</HD>
                                    <P>Sec. 1102 of the Social Security Act (42 U.S.C. 1302). </P>
                                </AUTH>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart A—General Provisions </HD>
                                <SECTION>
                                    <SECTNO>§ 438.1</SECTNO>
                                    <SUBJECT>Basis and scope. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Statutory basis.</E>
                                         This part is based on sections 1902(a)(4), 1903(m), 1905(t), and 1932 of the Act. 
                                    </P>
                                    <P>(1) Section 1902(a)(4) requires that States provide for methods of administration that the Secretary finds necessary for proper and efficient operation of the State plan. The application of the requirements of this part to PIHPs and PAHPs that do not meet the statutory definition of an MCO or a PCCM is under the authority in section 1902(a)(4). </P>
                                    <P>(2) Section 1903(m) contains requirements that apply to comprehensive risk contracts. </P>
                                    <P>(3) Section 1903(m)(2)(H) provides that an enrollee who loses Medicaid eligibility for not more than 2 months may be enrolled in the succeeding month in the same MCO or PCCM if that MCO or PCCM still has a contract with the State. </P>
                                    <P>(4) Section 1905(t) contains requirements that apply to PCCMs. </P>
                                    <P>(5) Section 1932— </P>
                                    <P>(i) Provides that, with specified exceptions, a State may require Medicaid recipients to enroll in MCOs or PCCMs; </P>
                                    <P>(ii) Establishes the rules that MCOs, PCCMs, the State, and the contracts between the State and those entities must meet, including compliance with requirements in sections 1903(m) and 1905(t) of the Act that are implemented in this part; </P>
                                    <P>(iii) Establishes protections for enrollees of MCOs and PCCMs; </P>
                                    <P>(iv) Requires States to develop a quality assessment and performance improvement strategy; </P>
                                    <P>(v) Specifies certain prohibitions aimed at the prevention of fraud and abuse; </P>
                                    <P>(vi) Provides that a State may not enter into contracts with MCOs unless it has established intermediate sanctions that it may impose on an MCO that fails to comply with specified requirements; and </P>
                                    <P>(vii) Makes other minor changes in the Medicaid program. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Scope.</E>
                                         This part sets forth requirements, prohibitions, and procedures for the provision of Medicaid services through MCOs, PIHPs, PAHPs, and PCCMs. Requirements vary depending on the type of entity and on the authority under which the State contracts with the entity. Provisions that apply only when the contract is under a mandatory managed care program authorized by section 1932(a)(1)(A) of the Act are identified as such. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.2</SECTNO>
                                    <SUBJECT>Definitions. </SUBJECT>
                                    <P>As used in this part— </P>
                                    <P>
                                        <E T="03">Capitation payment</E>
                                         means a payment the State agency makes periodically to a contractor on behalf of each recipient enrolled under a contract for the provision of medical services under the State plan. The State agency makes the payment regardless of whether the particular recipient receives services during the period covered by the payment. 
                                        <PRTPAGE P="41097"/>
                                    </P>
                                    <P>
                                        <E T="03">Comprehensive risk contract</E>
                                         means a risk contract that covers comprehensive services, that is, inpatient hospital services and any of the following services, or any three or more of the following services: 
                                    </P>
                                    <P>(1) Outpatient hospital services. </P>
                                    <P>(2) Rural health clinic services. </P>
                                    <P>(3) FQHC services. </P>
                                    <P>(4) Other laboratory and X-ray services. </P>
                                    <P>(5) Nursing facility (NF) services. </P>
                                    <P>(6) Early and periodic screening, diagnostic, and treatment (EPSDT) services. </P>
                                    <P>(7) Family planning services. </P>
                                    <P>(8) Physician services. </P>
                                    <P>(9) Home health services. </P>
                                    <P>
                                        <E T="03">Federally qualified HMO</E>
                                         means an HMO that CMS has determined is a qualified HMO under section 1310(d) of the PHS Act. 
                                    </P>
                                    <P>
                                        <E T="03">Health care professional</E>
                                         means a physician or any of the following: a podiatrist, optometrist, chiropractor, psychologist, dentist, physician assistant, physical or occupational therapist, therapist assistant, speech-language pathologist, audiologist, registered or practical nurse (including nurse practitioner, clinical nurse specialist, certified registered nurse anesthetist, and certified nurse midwife), licensed certified social worker, registered respiratory therapist, and certified respiratory therapy technician. 
                                    </P>
                                    <P>
                                        <E T="03">Health insuring organization</E>
                                         (
                                        <E T="03">HIO</E>
                                        ) means a county operated entity, that in exchange for capitation payments, covers services for recipients— 
                                    </P>
                                    <P>(1) Through payments to, or arrangements with, providers; </P>
                                    <P>(2) Under a comprehensive risk contract with the State; and </P>
                                    <P>(3) Meets the following criteria— </P>
                                    <P>(i) First became operational prior to January 1, 1986; or </P>
                                    <P>(ii) Is described in section 9517(e)(3) of the Omnibus Budget Reconciliation Act of 1985 (as amended by section 4734 of the Omnibus Budget Reconciliation Act of 1990). </P>
                                    <P>
                                        <E T="03">Managed care organization</E>
                                         (
                                        <E T="03">MCO</E>
                                        ) means an entity that has, or is seeking to qualify for, a comprehensive risk contract under this part, and that is— 
                                    </P>
                                    <P>(1) A Federally qualified HMO that meets the advance directives requirements of subpart I of part 489 of this chapter; or </P>
                                    <P>(2) Any public or private entity that meets the advance directives requirements and is determined to also meet the following conditions: </P>
                                    <P>(i) Makes the services it provides to its Medicaid enrollees as accessible (in terms of timeliness, amount, duration, and scope) as those services are to other Medicaid recipients within the area served by the entity. </P>
                                    <P>(ii) Meets the solvency standards of § 438.116. </P>
                                    <P>
                                        <E T="03">Nonrisk contract</E>
                                         means a contract under which the contractor— 
                                    </P>
                                    <P>(1) Is not at financial risk for changes in utilization or for costs incurred under the contract that do not exceed the upper payment limits specified in § 447.362 of this chapter; and </P>
                                    <P>(2) May be reimbursed by the State at the end of the contract period on the basis of the incurred costs, subject to the specified limits. </P>
                                    <P>
                                        <E T="03">Prepaid ambulatory health plan</E>
                                         (PAHP) means an entity that— 
                                    </P>
                                    <P>(1) Provides medical services to enrollees under contract with the State agency, and on the basis of prepaid capitation payments, or other payment arrangements that do not use State plan payment rates; </P>
                                    <P>(2) Does not provide or arrange for, and is not otherwise responsible for the provision of any inpatient hospital or institutional services for its enrollees; and </P>
                                    <P>(3) Does not have a comprehensive risk contract. </P>
                                    <P>
                                        <E T="03">Prepaid inpatient health plan</E>
                                         (PIHP) means an entity that— 
                                    </P>
                                    <P>(1) Provides medical services to enrollees under contract with the State agency, and on the basis of prepaid capitation payments, or other payment arrangements that do not use State plan payment rates; </P>
                                    <P>(2) Provides, arranges for, or otherwise has responsibility for the provision of any inpatient hospital or institutional services for its enrollees; and </P>
                                    <P>(3) Does not have a comprehensive risk contract. </P>
                                    <P>
                                        <E T="03">Primary care</E>
                                         means all health care services and laboratory services customarily furnished by or through a general practitioner, family physician, internal medicine physician, obstetrician/gynecologist, or pediatrician, to the extent the furnishing of those services is legally authorized in the State in which the practitioner furnishes them. 
                                    </P>
                                    <P>
                                        <E T="03">Primary care case management</E>
                                         means a system under which a PCCM contracts with the State to furnish case management services (which include the location, coordination and monitoring of primary health care services) to Medicaid recipients. 
                                    </P>
                                    <P>
                                        <E T="03">Primary care case manager (PCCM)</E>
                                         means a physician, a physician group practice, an entity that employs or arranges with physicians to furnish primary care case management services or, at State option, any of the following: 
                                    </P>
                                    <P>(1) A physician assistant. </P>
                                    <P>(2) A nurse practitioner. </P>
                                    <P>(3) A certified nurse-midwife. </P>
                                    <P>
                                        <E T="03">Risk contract</E>
                                         means a contract under which the contractor— 
                                    </P>
                                    <P>(1) Assumes risk for the cost of the services covered under the contract; and </P>
                                    <P>(2) Incurs loss if the cost of furnishing the services exceeds the payments under the contract. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.6 </SECTNO>
                                    <SUBJECT>Contract requirements. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Regional office review.</E>
                                         The CMS Regional Office must review and approve all MCO, PIHP, and PAHP contracts, including those risk and nonrisk contracts that, on the basis of their value, are not subject to the prior approval requirement in § 438.806. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Entities eligible for comprehensive risk contracts.</E>
                                         A State agency may enter into a comprehensive risk contract only with the following: 
                                    </P>
                                    <P>(1) An MCO. </P>
                                    <P>(2) The entities identified in section 1903(m)(2)(B)(i), (ii), and (iii) of the Act. </P>
                                    <P>(3) Community, Migrant, and Appalachian Health Centers identified in section 1903(m)(2)(G) of the Act. Unless they qualify for a total exemption under section 1903(m)(2)(B) of the Act, these entities are subject to the regulations governing MCOs under this part. </P>
                                    <P>(4) An HIO that arranges for services and became operational before January 1986. </P>
                                    <P>(5) An HIO described in section 9517(c)(3) of the Omnibus Budget Reconciliation Act of 1985 (as added by section 4734(2) of the Omnibus Budget Reconciliation Act of 1990). </P>
                                    <P>
                                        (c) 
                                        <E T="03">Payments under risk contracts.</E>
                                    </P>
                                    <P>
                                        (1) 
                                        <E T="03">Terminology.</E>
                                         As used in this paragraph, the following terms have the indicated meanings: 
                                    </P>
                                    <P>
                                        (i) 
                                        <E T="03">Actuarially sound capitation rates</E>
                                         means capitation rates that— 
                                    </P>
                                    <P>(A) Have been developed in accordance with generally accepted actuarial principles and practices; </P>
                                    <P>(B) Are appropriate for the populations to be covered, and the services to be furnished under the contract; and </P>
                                    <P>(C) Have been certified, as meeting the requirements of this paragraph (c), by actuaries who meet the qualification standards established by the American Academy of Actuaries and follow the practice standards established by the Actuarial Standards Board. </P>
                                    <P>
                                        (ii) 
                                        <E T="03">Adjustments to smooth data</E>
                                         means adjustments made, by cost-neutral methods, across rate cells, to compensate for distortions in costs, utilization, or the number of eligibles. 
                                    </P>
                                    <P>
                                        (iii) 
                                        <E T="03">Cost neutral</E>
                                         means that the mechanism used to smooth data, share risk, or adjust for risk will recognize 
                                        <PRTPAGE P="41098"/>
                                        both higher and lower expected costs and is not intended to create a net aggregate gain or loss across all payments. 
                                    </P>
                                    <P>
                                        (iv) 
                                        <E T="03">Incentive arrangement</E>
                                         means any payment mechanism under which a contractor may receive additional funds over and above the capitation rates it was paid for meeting targets specified in the contract. 
                                    </P>
                                    <P>
                                        (v) 
                                        <E T="03">Risk corridor</E>
                                         means a risk sharing mechanism in which States and contractors share in both profits and losses under the contract outside of predetermined threshold amount, so that after an initial corridor in which the contractor is responsible for all losses or retains all profits, the State contributes a portion toward any additional losses, and receives a portion of any additional profits. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Basic requirements.</E>
                                         (i) All payments under risk contracts and all risk-sharing mechanisms in contracts must be actuarially sound. 
                                    </P>
                                    <P>(ii) The contract must specify the payment rates and any risk-sharing mechanisms, and the actuarial basis for computation of those rates and mechanisms. </P>
                                    <P>
                                        (3) 
                                        <E T="03">Requirements for actuarially sound rates.</E>
                                         In setting actuarially sound capitation rates, the State must apply the following elements, or explain why they are not applicable: 
                                    </P>
                                    <P>(i) Base utilization and cost data that are derived from the Medicaid population, or if not, are adjusted to make them comparable to the Medicaid population. </P>
                                    <P>(ii) Adjustments made to smooth data and adjustments to account for factors such as medical trend inflation, incomplete data, MCO, PIHP, or PAHP administration (subject to the limits in paragraph (c)(4)(ii) of this section), and utilization; </P>
                                    <P>(iii) Rate cells specific to the enrolled population, by— </P>
                                    <P>(A) Eligibility category; </P>
                                    <P>(B) Age; </P>
                                    <P>(C) Gender; </P>
                                    <P>(D) Locality/region; and </P>
                                    <P>(E) Risk adjustments based on diagnosis or health status (if used). </P>
                                    <P>(iv) Other payment mechanisms and utilization and cost assumptions that are appropriate for individuals with chronic illness, disability, ongoing health care needs, or catastrophic claims, using risk adjustment, risk sharing, or other appropriate cost-neutral methods. </P>
                                    <P>
                                        (4) 
                                        <E T="03">Documentation.</E>
                                         The State must provide the following documentation: 
                                    </P>
                                    <P>(i) The actuarial certification of the capitation rates. </P>
                                    <P>(ii) An assurance (in accordance with paragraph (c)(3) of this section) that all payment rates are—</P>
                                    <P>(A) Based only upon services covered under the State plan (or costs directly related to providing these services, for example, MCO, PIHP, or PAHP administration). </P>
                                    <P>(B) Provided under the contract to Medicaid-eligible individuals. </P>
                                    <P>(iii) The State's projection of expenditures under its previous year's contract (or under its FFS program if it did not have a contract in the previous year) compared to those projected under the proposed contract. </P>
                                    <P>(iv) An explanation of any incentive arrangements, or stop-loss, reinsurance, or any other risk-sharing methodologies under the contract. </P>
                                    <P>
                                        (5) 
                                        <E T="03">Special contract provisions.</E>
                                    </P>
                                    <P>(i) Contract provisions for reinsurance, stop-loss limits or other risk-sharing methodologies must be computed on an actuarially sound basis. </P>
                                    <P>(ii) If risk corridor arrangements result in payments that exceed the approved capitation rates, these excess payments will not be considered actuarially sound to the extent that they result in total payments that exceed the amount Medicaid would have paid, on a fee-for-service basis, for the State plan services actually furnished to enrolled individuals, plus an amount for MCO, PIHP, or PAHP administrative costs directly related to the provision of these services. </P>
                                    <P>(iii) Contracts with incentive arrangements may not provide for payment in excess of 105 percent of the approved capitation payments attributable to the enrollees or services covered by the incentive arrangement, since such total payments will not be considered to be actuarially sound. </P>
                                    <P>(iv) For all incentive arrangements, the contract must provide that the arrangement is— </P>
                                    <P>(A) For a fixed period of time; </P>
                                    <P>(B) Not to be renewed automatically; </P>
                                    <P>(C) Made available to both public and private contractors; </P>
                                    <P>(D) Not conditioned on intergovernmental transfer agreements; and </P>
                                    <P>(E) Necessary for the specified activities and targets. </P>
                                    <P>(v) If a State makes payments to providers for graduate medical education (GME) costs under an approved State plan, the State must adjust the actuarially sound capitation rates to account for the GME payments to be made on behalf of enrollees covered under the contract, not to exceed the aggregate amount that would have been paid under the approved State plan for FFS. States must first establish actuarially sound capitation rates prior to making adjustments for GME. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Enrollment discrimination prohibited.</E>
                                         Contracts with MCOs, PIHPs, PAHPs, and PCCMs must provide as follows: 
                                    </P>
                                    <P>(1) The MCO, PIHP, PAHP, or PCCM accepts individuals eligible for enrollment in the order in which they apply without restriction (unless authorized by the Regional Administrator), up to the limits set under the contract. </P>
                                    <P>(2) Enrollment is voluntary, except in the case of mandatory enrollment programs that meet the conditions set forth in § 438.50(a). </P>
                                    <P>(3) The MCO, PIHP, PAHP, or PCCM will not, on the basis of health status or need for health care services, discriminate against individuals eligible to enroll. </P>
                                    <P>(4) The MCO, PIHP, PAHP, or PCCM will not discriminate against individuals eligible to enroll on the basis of race, color, or national origin, and will not use any policy or practice that has the effect of discriminating on the basis of race, color, or national origin. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Services that may be covered.</E>
                                         An MCO, PIHP, or PAHP contract may cover, for enrollees, services that are in addition to those covered under the State plan, although the cost of these services cannot be included when determining the payment rates under § 438.6(c). 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Compliance with contracting rules.</E>
                                         All contracts under this subpart must: 
                                    </P>
                                    <P>(1) Comply with all applicable Federal and State laws and regulations including title VI of the Civil Rights Act of 1964; title IX of the Education Amendments of 1972 (regarding education programs and activities); the Age Discrimination Act of 1975; the Rehabilitation Act of 1973; and the Americans with Disabilities Act; and </P>
                                    <P>(2) Meet all the requirements of this section. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Inspection and audit of financial records.</E>
                                         Risk contracts must provide that the State agency and the Department may inspect and audit any financial records of the entity or its subcontractors. 
                                    </P>
                                    <P>
                                        (h) 
                                        <E T="03">Physician incentive plans.</E>
                                         (1) MCO, PIHP, and PAHP contracts must provide for compliance with the requirements set forth in §§ 422.208 and 422.210 of this chapter. 
                                    </P>
                                    <P>(2) In applying the provisions of §§ 422.208 and 422.210 of this chapter, references to “M+C organization”, “CMS”, and “Medicare beneficiaries” must be read as references to “MCO, PIHP, or PAHP”, “State agency” and “Medicaid recipients”, respectively. </P>
                                    <P>
                                        (i) 
                                        <E T="03">Advance directives.</E>
                                         (1) All MCO and PIHP contracts must provide for 
                                        <PRTPAGE P="41099"/>
                                        compliance with the requirements of § 422.128 of this chapter for maintaining written policies and procedures for advance directives. 
                                    </P>
                                    <P>(2) All PAHP contracts must provide for compliance with the requirements of § 422.128 of this chapter for maintaining written policies and procedures for advance directives if the PAHP includes, in its network, any of those providers listed in § 489.102(a) of this chapter. </P>
                                    <P>(3) The MCO, PIHP, or PAHP subject to this requirement must provide adult enrollees with written information on advance directives policies, and include a description of applicable State law. </P>
                                    <P>(4) The information must reflect changes in State law as soon as possible, but no later than 90 days after the effective date of the change. </P>
                                    <P>
                                        (j) 
                                        <E T="03">Special rules for certain HIOs.</E>
                                         Contracts with HIOs that began operating on or after January 1, 1986, and that the statute does not explicitly exempt from requirements in section 1903(m) of the Act, are subject to all the requirements of this part that apply to MCOs and contracts with MCOs. These HIOs may enter into comprehensive risk contracts only if they meet the criteria of paragraph (a) of this section. 
                                    </P>
                                    <P>
                                        (k) 
                                        <E T="03">Additional rules for contracts with PCCMs.</E>
                                         A PCCM contract must meet the following requirements: 
                                    </P>
                                    <P>(1) Provide for reasonable and adequate hours of operation, including 24-hour availability of information, referral, and treatment for emergency medical conditions. </P>
                                    <P>(2) Restrict enrollment to recipients who reside sufficiently near one of the manager's delivery sites to reach that site within a reasonable time using available and affordable modes of transportation. </P>
                                    <P>(3) Provide for arrangements with, or referrals to, sufficient numbers of physicians and other practitioners to ensure that services under the contract can be furnished to enrollees promptly and without compromise to quality of care. </P>
                                    <P>(4) Prohibit discrimination in enrollment, disenrollment, and re-enrollment, based on the recipient's health status or need for health care services. </P>
                                    <P>(5) Provide that enrollees have the right to disenroll from their PCCM in accordance with § 438.56(c). </P>
                                    <P>
                                        (l) 
                                        <E T="03">Subcontracts.</E>
                                         All subcontracts must fulfill the requirements of this part that are appropriate to the service or activity delegated under the subcontract. 
                                    </P>
                                    <P>
                                        (m) 
                                        <E T="03">Choice of health professional.</E>
                                         The contract must allow each enrollee to choose his or her health professional to the extent possible and appropriate. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.8 </SECTNO>
                                    <SUBJECT>Provisions that apply to PIHPs and PAHPs. </SUBJECT>
                                    <P>(a) The following requirements and options apply to PIHPs, PIHP contracts, and States with respect to PIHPs, to the same extent that they apply to MCOs, MCO contracts, and States for MCOs. </P>
                                    <P>(1) The contract requirements of § 438.6, except for requirements that pertain to HIOs. </P>
                                    <P>(2) The information requirements in § 438.10. </P>
                                    <P>(3) The provision against provider discrimination in § 438.12. </P>
                                    <P>(4) The State responsibility provisions of subpart B of this part except § 438.50. </P>
                                    <P>(5) The enrollee rights and protection provisions in subpart C of this part. </P>
                                    <P>(6) The quality assessment and performance improvement provisions in subpart D of this part to the extent that they are applicable to services furnished by the PIHP. </P>
                                    <P>(7) The grievance system provisions in subpart F of this part. </P>
                                    <P>(8) The certification and program integrity protection provisions set forth in subpart H of this part. </P>
                                    <P>(b) The following requirements and options for PAHPs apply to PAHPs, PAHP contracts, and States. </P>
                                    <P>(1) The contract requirements of § 438.6, except requirements for— </P>
                                    <P>(i) HIOs. </P>
                                    <P>(ii) Advance directives (unless the PAHP includes any of the providers listed in § 489.102) of this chapter. </P>
                                    <P>(2) All applicable portions of the information requirements in § 438.10. </P>
                                    <P>(3) The provision against provider discrimination in § 438.12. </P>
                                    <P>(4) The State responsibility provisions of subpart B of this part except § 438.50. </P>
                                    <P>(5) The provisions on enrollee rights and protections in subpart C of this part. </P>
                                    <P>(6) Designated portions of subpart D of this part. </P>
                                    <P>(7) An enrollee's right to a State fair hearing under subpart E of part 431 of this chapter. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.10 </SECTNO>
                                    <SUBJECT>Information requirements. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Terminology.</E>
                                         As used in this section, the following terms have the indicated meanings: 
                                    </P>
                                    <P>
                                        <E T="03">Enrollee</E>
                                         means a Medicaid recipient who is currently enrolled in an MCO, PIHP, PAHP, or PCCM in a given managed care program. 
                                    </P>
                                    <P>
                                        <E T="03">Potential enrollee</E>
                                         means a Medicaid recipient who is subject to mandatory enrollment or may voluntarily elect to enroll in a given managed care program, but is not yet an enrollee of a specific MCO, PIHP, PAHP, or PCCM. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Basic rules.</E>
                                         (1) Each State, enrollment broker, MCO, PIHP, PAHP, and PCCM must provide all enrollment notices, informational materials, and instructional materials relating to enrollees and potential enrollees in a manner and format that may be easily understood.
                                    </P>
                                    <P>(2) The State must have in place a mechanism to help enrollees and potential enrollees understand the State's managed care program. </P>
                                    <P>(3) Each MCO and PIHP must have in place a mechanism to help enrollees and potential enrollees understand the requirements and benefits of the plan. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Language.</E>
                                         The State must do the following: 
                                    </P>
                                    <P>(1) Establish a methodology for identifying the prevalent non-English languages spoken by enrollees and potential enrollees throughout the State. “Prevalent” means a non-English language spoken by a significant number or percentage of potential enrollees and enrollees in the State. </P>
                                    <P>(2) Make available written information in each prevalent non-English language. </P>
                                    <P>(3) Require each MCO, PIHP, PAHP, and PCCM to make its written information available in the prevalent non-English languages in its particular service area. </P>
                                    <P>(4) Make oral interpretation services available and require each MCO, PIHP, PAHP, and PCCM to make those services available free of charge to each potential enrollee and enrollee. This applies to all non-English languages, not just those that the State identifies as prevalent. </P>
                                    <P>(5) Notify enrollees and potential enrollees, and require each MCO, PIHP, PAHP, and PCCM to notify its enrollees— </P>
                                    <P>(i) That oral interpretation is available for any language and written information is available in prevalent languages; and </P>
                                    <P>(ii) How to access those services. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Format.</E>
                                         (1) Written material must— 
                                    </P>
                                    <P>(i) Use easily understood language and format; and </P>
                                    <P>(ii) Be available in alternative formats and in an appropriate manner that takes into consideration the special needs of those who, for example, are visually limited or have limited reading proficiency. </P>
                                    <P>(2) All enrollees and potential enrollees must be informed that information is available in alternative formats and how to access those formats. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Information for potential enrollees.</E>
                                    </P>
                                    <P>
                                        (1) The State or its contracted representative must provide the information specified in paragraph (e)(2) of this section to each potential enrollee as follows: 
                                        <PRTPAGE P="41100"/>
                                    </P>
                                    <P>(i) At the time the potential enrollee first becomes eligible to enroll in a voluntary program, or is first required to enroll in a mandatory enrollment program. </P>
                                    <P>(ii) Within a timeframe that enables the potential enrollee to use the information in choosing among available MCOs, PIHP, PAHPs, or PCCMs. </P>
                                    <P>(2) The information for potential enrollees must include the following: </P>
                                    <P>(i) General information about— </P>
                                    <P>(A) The basic features of managed care; </P>
                                    <P>(B) Which populations are excluded from enrollment, subject to mandatory enrollment, or free to enroll voluntarily in the program; and </P>
                                    <P>(C) MCO, PIHP, PAHP, and PCCM responsibilities for coordination of enrollee care; </P>
                                    <P>(ii) Information specific to each MCO, PIHP, PAHP, or PCCM program operating in potential enrollee's service area. A summary of the following information is sufficient, but the State must provide more detailed information upon request: </P>
                                    <P>(A) Benefits covered. </P>
                                    <P>(B) Cost sharing, if any. </P>
                                    <P>(C) Service area. </P>
                                    <P>(D) Names, locations, telephone numbers of, and non-English language spoken by current contracted providers, and including identification of providers that are not accepting new patients. For MCOs, PIHPs, and PAHPs, this includes at a minimum information on primary care physicians, specialists, and hospitals. </P>
                                    <P>(E) Benefits that are available under the State plan but are not covered under the contract, including how and where the enrollee may obtain those benefits, any cost sharing, and how transportation is provided. For a counseling or referral service that the MCO, PIHP, PAHP, or PCCM does not cover because of moral or religious objections, the State must provide information about where and how to obtain the service. </P>
                                    <P>
                                        (f) 
                                        <E T="03">General information for all enrollees of MCOs, PIHPs, PAHPs, and PCCMs.</E>
                                         Information must be furnished to MCO, PIHP, PAHP, and PCCM enrollees as follows: 
                                    </P>
                                    <P>(1) The State must notify all enrollees of their disenrollment rights, at a minimum, annually. For States that choose to restrict disenrollment for periods of 90 days or more, States must send the notice no less than 60 days before the start of each enrollment period. </P>
                                    <P>(2) The State, its contracted representative, or the MCO, PIHP, PAHP, or PCCM must notify all enrollees of their right to request and obtain the information listed in paragraph (f)(6) of this section and, if applicable, paragraphs (g) and (h) of this section, at least once a year. </P>
                                    <P>(3) The State, its contracted representative, or the MCO, PIHP, PAHP, or PCCM must furnish to each of its enrollees the information specified in paragraph (f)(6) of this section and, if applicable, paragraphs (g) and (h) of this section, within a reasonable time after the MCO, PIHP, PAHP, or PCCM receives, from the State or its contracted representative, notice of the recipient's enrollment. </P>
                                    <P>(4) The State, its contracted representative, or the MCO, PIHP, PAHP, or PCCM must give each enrollee written notice of any change (that the State defines as “significant”) in the information specified in paragraphs (f)(6) of this section and, if applicable, paragraphs (g) and (h) of this section, at least 30 days before the intended effective date of the change. </P>
                                    <P>(5) The MCO, PIHP, and, when appropriate, the PAHP or PCCM, must make a good faith effort to give written notice of termination of a contracted provider, within 15 days after receipt or issuance of the termination notice, to each enrollee who received his or her primary care from, or was seen on a regular basis by, the terminated provider. </P>
                                    <P>(6) The State, its contracted representative, or the MCO, PIHP, PAHP, or PCCM must provide the following information to all enrollees: </P>
                                    <P>(i) Names, locations, telephone numbers of, and non-English languages spoken by current contracted providers in the enrollee's service area, including identification of providers that are not accepting new patients. For MCOs, PIHPs, and PAHPs this includes, at a minimum, information on primary care physicians, specialists, and hospitals. </P>
                                    <P>(ii) Any restrictions on the enrollee's freedom of choice among network providers. </P>
                                    <P>(iii) Enrollee rights and protections, as specified in § 438.100. </P>
                                    <P>(iv) Information on grievance and fair hearing procedures, and for MCO and PIHP enrollees, the information specified in § 438.10(g)(1), and for PAHP enrollees, the information specified in § 438.10(h). </P>
                                    <P>(v) The amount, duration, and scope of benefits available under the contract in sufficient detail to ensure that enrollees understand the benefits to which they are entitled. </P>
                                    <P>(vi) Procedures for obtaining benefits, including authorization requirements. </P>
                                    <P>(vii) The extent to which, and how, enrollees may obtain benefits, including family planning services, from out-of-network providers. </P>
                                    <P>(viii) The extent to which, and how, after-hours and emergency coverage are provided, including: </P>
                                    <P>(A) What constitutes emergency medical condition, emergency services, and poststabilization services, with reference to the definitions in § 438.114(a). </P>
                                    <P>(B) The fact that prior authorization is not required for emergency services. </P>
                                    <P>(C) The process and procedures for obtaining emergency services, including use of the 911-telephone system or its local equivalent. </P>
                                    <P>(D) The locations of any emergency settings and other locations at which providers and hospitals furnish emergency services and poststabilization services covered under the contract. </P>
                                    <P>(E) The fact that, subject to the provisions of this section, the enrollee has a right to use any hospital or other setting for emergency care. </P>
                                    <P>(ix) The poststabilization care services rules set forth at § 422.113(c) of this chapter. </P>
                                    <P>(x) Policy on referrals for specialty care and for other benefits not furnished by the enrollee's primary care provider. </P>
                                    <P>(xi) Cost sharing, if any. </P>
                                    <P>(xii) How and where to access any benefits that are available under the State plan but are not covered under the contract, including any cost sharing, and how transportation is provided. For a counseling or referral service that the MCO, PIHP, PAHP, or PCCM does not cover because of moral or religious objections, the MCO, PIHP, PAHP, or PCCM need not furnish information on how and where to obtain the service. The State must provide information on how and where to obtain the service. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Specific information requirements for enrollees of MCOs and PIHPs.</E>
                                         In addition to the requirements in § 438.10(f), the State, its contracted representative, or the MCO and PIHP must provide the following information to their enrollees: 
                                    </P>
                                    <P>(1) Grievance, appeal, and fair hearing procedures and timeframes, as provided in §§ 438.400 through 438.424, in a State-developed or State-approved description, that must include the following: </P>
                                    <P>(i) For State fair hearing— </P>
                                    <P>(A) The right to hearing; </P>
                                    <P>(B) The method for obtaining a hearing; and </P>
                                    <P>(C) The rules that govern representation at the hearing. </P>
                                    <P>(ii) The right to file grievances and appeals. </P>
                                    <P>
                                        (iii) The requirements and timeframes for filing a grievance or appeal. 
                                        <PRTPAGE P="41101"/>
                                    </P>
                                    <P>(iv) The availability of assistance in the filing process. </P>
                                    <P>(v) The toll-free numbers that the enrollee can use to file a grievance or an appeal by phone. </P>
                                    <P>(vi) The fact that, when requested by the enrollee— </P>
                                    <P>(A) Benefits will continue if the enrollee files an appeal or a request for State fair hearing within the timeframes specified for filing; and </P>
                                    <P>(B) The enrollee may be required to pay the cost of services furnished while the appeal is pending, if the final decision is adverse to the enrollee. </P>
                                    <P>(vii) Any appeal rights that the State chooses to make available to providers to challenge the failure of the organization to cover a service. </P>
                                    <P>(2) Advance directives, as set forth in § 438.6(i)(2). </P>
                                    <P>(3) Additional information that is available upon request, including the following: </P>
                                    <P>(i) Information on the structure and operation of the MCO or PIHP. </P>
                                    <P>(ii) Physician incentive plans as set forth in § 438.6(h) of this chapter. </P>
                                    <P>
                                        (h) 
                                        <E T="03">Specific information for PAHPs.</E>
                                         The State, its contracted representative, or the PAHP must provide the following information to their enrollees: 
                                    </P>
                                    <P>(1) The right to a State fair hearing, including the following: </P>
                                    <P>(i) The right to a hearing. </P>
                                    <P>(ii) The method for obtaining a hearing. </P>
                                    <P>(iii) The rules that govern representation. </P>
                                    <P>(2) Advance directives, as set forth in § 438.6(i)(2), to the extent that the PAHP includes any of the providers listed in § 489.102(a) of this chapter. </P>
                                    <P>(3) Upon request, physician incentive plans as set forth in § 438.6(h). </P>
                                    <P>
                                        (i) 
                                        <E T="03">Special rules: States with mandatory enrollment under State plan authority</E>
                                        —(1) 
                                        <E T="03">Basic rule.</E>
                                         If the State plan provides for mandatory enrollment under § 438.50, the State or its contracted representative must provide information on MCOs and PCCMs (as specified in paragraph (i)(3) of this section), either directly or through the MCO or PCCM. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">When and how the information must be furnished.</E>
                                         The information must be furnished as follows: 
                                    </P>
                                    <P>(i) For potential enrollees, within the timeframe specified in § 438.10(e)(1). </P>
                                    <P>(ii) For enrollees, annually and upon request. </P>
                                    <P>(iii) In a comparative, chart-like format. </P>
                                    <P>
                                        (3) 
                                        <E T="03">Required information.</E>
                                         Some of the information is the same as the information required for potential enrollees under paragraph (e) of this section and for enrollees under paragraph (f) of this section. However, all of the information in this paragraph is subject to the timeframe and format requirements of paragraph (i)(2) of this section, and includes the following for each contracting MCO or PCCM in the potential enrollee and enrollee's service area: 
                                    </P>
                                    <P>(i) The MCO's or PCCM's service area. </P>
                                    <P>(ii) The benefits covered under the contract. </P>
                                    <P>(iii) Any cost sharing imposed by the MCO or PCCM. </P>
                                    <P>(iv) To the extent available, quality and performance indicators, including enrollee satisfaction. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.12 </SECTNO>
                                    <SUBJECT>Provider discrimination prohibited. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rules.</E>
                                         (1) An MCO, PIHP, or PAHP may not discriminate for the participation, reimbursement, or indemnification of any provider who is acting within the scope of his or her license or certification under applicable State law, solely on the basis of that license or certification. If an MCO, PIHP, or PAHP declines to include individual or groups of providers in its network, it must give the affected providers written notice of the reason for its decision. 
                                    </P>
                                    <P>(2) In all contracts with health care professionals, an MCO, PIHP, or PAHP must comply with the requirements specified in § 438.214. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Construction.</E>
                                         Paragraph (a) of this section may not be construed to— 
                                    </P>
                                    <P>(1) Require the MCO, PIHP, or PAHP to contract with providers beyond the number necessary to meet the needs of its enrollees; </P>
                                    <P>(2) Preclude the MCO, PIHP, or PAHP from using different reimbursement amounts for different specialties or for different practitioners in the same specialty; or </P>
                                    <P>(3) Preclude the MCO, PIHP, or PAHP from establishing measures that are designed to maintain quality of services and control costs and are consistent with its responsibilities to enrollees. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—State Responsibilities </HD>
                                <SECTION>
                                    <SECTNO>§ 438.50 </SECTNO>
                                    <SUBJECT>State Plan requirements. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rule.</E>
                                         A State plan that requires Medicaid recipients to enroll in managed care entities must comply with the provisions of this section, except when the State imposes the requirement— 
                                    </P>
                                    <P>(1) As part of a demonstration project under section 1115 of the Act; or </P>
                                    <P>(2) Under a waiver granted under section 1915(b) of the Act. </P>
                                    <P>
                                        (b) 
                                        <E T="03">State plan information.</E>
                                         The plan must specify— 
                                    </P>
                                    <P>(1) The types of entities with which the State contracts; </P>
                                    <P>(2) The payment method it uses (for example, whether fee-for-service or capitation); </P>
                                    <P>(3) Whether it contracts on a comprehensive risk basis; and </P>
                                    <P>(4) The process the State uses to involve the public in both design and initial implementation of the program and the methods it uses to ensure ongoing public involvement once the State plan has been implemented. </P>
                                    <P>
                                        (c) 
                                        <E T="03">State plan assurances.</E>
                                         The plan must provide assurances that the State meets applicable requirements of the following statute and regulations: 
                                    </P>
                                    <P>(1) Section 1903(m) of the Act, for MCOs and MCO contracts. </P>
                                    <P>(2) Section 1905(t) of the Act, for PCCMs and PCCM contracts. </P>
                                    <P>(3) Section 1932(a)(1)(A) of the Act, for the State's option to limit freedom of choice by requiring recipients to receive their benefits through managed care entities. </P>
                                    <P>(4) This part, for MCOs and PCCMs. </P>
                                    <P>(5) Part 434 of this chapter, for all contracts. </P>
                                    <P>(6) Section 438.6(c), for payments under any risk contracts, and § 447.362 of this chapter for payments under any nonrisk contracts. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Limitations on enrollment.</E>
                                         The State must provide assurances that, in implementing the State plan managed care option, it will not require the following groups to enroll in an MCO or PCCM: 
                                    </P>
                                    <P>(1) Recipients who are also eligible for Medicare. </P>
                                    <P>(2) Indians who are members of Federally recognized tribes, except when the MCO or PCCM is— </P>
                                    <P>(i) The Indian Health Service; or </P>
                                    <P>(ii) An Indian health program or Urban Indian program operated by a tribe or tribal organization under a contract, grant, cooperative agreement or compact with the Indian Health Service. </P>
                                    <P>(3) Children under 19 years of age who are— </P>
                                    <P>(i) Eligible for SSI under title XVI; </P>
                                    <P>(ii) Eligible under section 1902(e)(3) of the Act; </P>
                                    <P>(iii) In foster care or other out-of-home placement; </P>
                                    <P>(iv) Receiving foster care or adoption assistance; or </P>
                                    <P>(v) Receiving services through a family-centered, community-based, coordinated care system that receives grant funds under section 501(a)(1)(D) of title V, and is defined by the State in terms of either program participation or special health care needs. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Priority for enrollment.</E>
                                         The State must have an enrollment system under which recipients already enrolled in an MCO or PCCM are given priority to 
                                        <PRTPAGE P="41102"/>
                                        continue that enrollment if the MCO or PCCM does not have the capacity to accept all those seeking enrollment under the program. 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Enrollment by default.</E>
                                         (1) For recipients who do not choose an MCO or PCCM during their enrollment period, the State must have a default enrollment process for assigning those recipients to contracting MCOs and PCCMs. 
                                    </P>
                                    <P>(2) The process must seek to preserve existing provider-recipient relationships and relationships with providers that have traditionally served Medicaid recipients. If that is not possible, the State must distribute the recipients equitably among qualified MCOs and PCCMs available to enroll them, excluding those that are subject to the intermediate sanction described in § 438.702(a)(4). </P>
                                    <P>(3) An “existing provider-recipient relationship” is one in which the provider was the main source of Medicaid services for the recipient during the previous year. This may be established through State records of previous managed care enrollment or fee-for-service experience, or through contact with the recipient. </P>
                                    <P>(4) A provider is considered to have “traditionally served” Medicaid recipients if it has experience in serving the Medicaid population. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.52 </SECTNO>
                                    <SUBJECT>Choice of MCOs, PIHPs, PAHPs, and PCCMs. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rule.</E>
                                         Except as specified in paragraphs (b) and (c) of this section, a State that requires Medicaid recipients to enroll in an MCO, PIHP, PAHP, or PCCM must give those recipients a choice of at least two entities. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Exception for rural area residents.</E>
                                         (1) Under any of the following programs, and subject to the requirements of paragraph (b)(2) of this section, a State may limit a rural area resident to a single MCO, PIHP, PAHP, or PCCM system: 
                                    </P>
                                    <P>(i) A program authorized by a plan amendment under section 1932(a) of the Act. </P>
                                    <P>(ii) A waiver under section 1115 of the Act. </P>
                                    <P>(iii) A waiver under section 1915(b) of the Act. </P>
                                    <P>(2) A State that elects the option provided under paragraph (b)(1) of this section, must permit the recipient— </P>
                                    <P>(i) To choose from at least two physicians or case managers; and </P>
                                    <P>(ii) To obtain services from any other provider under any of the following circumstances: </P>
                                    <P>(A) The service or type of provider (in terms of training, experience, and specialization) is not available within the MCO, PIHP, PAHP, or PCCM network. </P>
                                    <P>(B) The provider is not part of the network, but is the main source of a service to the recipient, provided that— </P>
                                    <P>
                                        (
                                        <E T="03">1</E>
                                        ) The provider is given the opportunity to become a participating provider under the same requirements for participation in the MCO, PIHP, PAHP, or PCCM network as other network providers of that type. 
                                    </P>
                                    <P>
                                        (
                                        <E T="03">2</E>
                                        ) If the provider chooses not to join the network, or does not meet the necessary qualification requirements to join, the enrollee will be transitioned to a participating provider within 60 days (after being given an opportunity to select a provider who participates). 
                                    </P>
                                    <P>(C) The only plan or provider available to the recipient does not, because of moral or religious objections, provide the service the enrollee seeks. </P>
                                    <P>(D) The recipient's primary care provider or other provider determines that the recipient needs related services that would subject the recipient to unnecessary risk if received separately (for example, a cesarean section and a tubal ligation) and not all of the related services are available within the network. </P>
                                    <P>(E) The State determines that other circumstances warrant out-of-network treatment. </P>
                                    <P>(3) As used in this paragraph, “rural area” is any area other than an “urban area” as defined in § 412.62(f)(1)(ii) of this chapter. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Exception for certain health insuring organizations (HIOs).</E>
                                         The State may limit recipients to a single HIO if— 
                                    </P>
                                    <P>(1) The HIO is one of those described in section 1932(a)(3)(C) of the Act; and </P>
                                    <P>(2) The recipient who enrolls in the HIO has a choice of at least two primary care providers within the entity. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Limitations on changes between primary care providers.</E>
                                         For an enrollee of a single MCO, PIHP, PAHP, or HIO under paragraph (b)(2) or (b)(3) of this section, any limitation the State imposes on his or her freedom to change between primary care providers may be no more restrictive than the limitations on disenrollment under § 438.56(c). 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.56</SECTNO>
                                    <SUBJECT>Disenrollment: Requirements and limitations. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Applicability.</E>
                                         The provisions of this section apply to all managed care arrangements whether enrollment is mandatory or voluntary and whether the contract is with an MCO, a PIHP, a PAHP, or a PCCM. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Disenrollment requested by the MCO, PIHP, PAHP, or PCCM.</E>
                                         All MCO, PIHP, PAHP, and PCCM contracts must—(1) Specify the reasons for which the MCO, PIHP, PAHP, or PCCM may request disenrollment of an enrollee; 
                                    </P>
                                    <P>(2) Provide that the MCO, PIHP, PAHP, or PCCM may not request disenrollment because of an adverse change in the enrollee's health status, or because of the enrollee's utilization of medical services, diminished mental capacity, or uncooperative or disruptive behavior resulting from his or her special needs (except when his or her continued enrollment in the MCO, PIHP, PAHP, or PCCM seriously impairs the entity's ability to furnish services to either this particular enrollee or other enrollees); and </P>
                                    <P>(3) Specify the methods by which the MCO, PIHP, PAHP, or PCCM assures the agency that it does not request disenrollment for reasons other than those permitted under the contract. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Disenrollment requested by the enrollee.</E>
                                         If the State chooses to limit disenrollment, its MCO, PIHP, PAHP, and PCCM contracts must provide that a recipient may request disenrollment as follows: 
                                    </P>
                                    <P>(1) For cause, at any time. </P>
                                    <P>(2) Without cause, at the following times: </P>
                                    <P>(i) During the 90 days following the date of the recipient's initial enrollment with the MCO, PIHP, PAHP, or PCCM, or the date the State sends the recipient notice of the enrollment, whichever is later. </P>
                                    <P>(ii) At least once every 12 months thereafter. </P>
                                    <P>(iii) Upon automatic reenrollment under paragraph (g) of this section, if the temporary loss of Medicaid eligibility has caused the recipient to miss the annual disenrollment opportunity. </P>
                                    <P>(iv) When the State imposes the intermediate sanction specified in § 438.702(a)(3). </P>
                                    <P>
                                        (d) 
                                        <E T="03">Procedures for disenrollment—</E>
                                         (1) 
                                        <E T="03">Request for disenrollment.</E>
                                         The recipient (or his or her representative) must submit an oral or written request— 
                                    </P>
                                    <P>(i) To the State agency (or its agent); or </P>
                                    <P>(ii) To the MCO, PIHP, PAHP, or PCCM, if the State permits MCOs, PIHP, PAHPs, and PCCMs to process disenrollment requests. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Cause for disenrollment.</E>
                                         The following are cause for disenrollment: 
                                    </P>
                                    <P>(i) The enrollee moves out of the MCO's, PIHP's, PAHP's, or PCCM's service area. </P>
                                    <P>(ii) The plan does not, because of moral or religious objections, cover the service the enrollee seeks. </P>
                                    <P>
                                        (iii) The enrollee needs related services (for example a cesarean section and a tubal ligation) to be performed at the same time; not all related services are available within the network; and the enrollee's primary care provider or 
                                        <PRTPAGE P="41103"/>
                                        another provider determines that receiving the services separately would subject the enrollee to unnecessary risk. 
                                    </P>
                                    <P>(iv) Other reasons, including but not limited to, poor quality of care, lack of access to services covered under the contract, or lack of access to providers experienced in dealing with the enrollee's health care needs. </P>
                                    <P>
                                        (3) 
                                        <E T="03">MCO, PIHP, PAHP, or PCCM action on request.</E>
                                         (i) An MCO, PIHP, PAHP, or PCCM may either approve a request for disenrollment or refer the request to the State. 
                                    </P>
                                    <P>(ii) If the MCO, PIHP, PAHP, PCCM, or State agency (whichever is responsible) fails to make a disenrollment determination so that the recipient can be disenrolled within the timeframes specified in paragraph (e)(1) of this section, the disenrollment is considered approved. </P>
                                    <P>
                                        (4) 
                                        <E T="03">State agency action on request.</E>
                                         For a request received directly from the recipient, or one referred by the MCO, PIHP, PAHP, or PCCM, the State agency must take action to approve or disapprove the request based on the following: 
                                    </P>
                                    <P>(i) Reasons cited in the request. </P>
                                    <P>(ii) Information provided by the MCO, PIHP, PAHP, or PCCM at the agency's request. </P>
                                    <P>(iii) Any of the reasons specified in paragraph (d)(2) of this section. </P>
                                    <P>
                                        (5) 
                                        <E T="03">Use of the MCO, PIHP, PAHP, or PCCM grievance procedures.</E>
                                         (i) The State agency may require that the enrollee seek redress through the MCO, PIHP, PAHP, or PCCM's grievance system before making a determination on the enrollee's request. 
                                    </P>
                                    <P>(ii) The grievance process, if used, must be completed in time to permit the disenrollment (if approved) to be effective in accordance with the timeframe specified in § 438.56(e)(1). </P>
                                    <P>(iii) If, as a result of the grievance process, the MCO, PIHP, PAHP, or PCCM approves the disenrollment, the State agency is not required to make a determination. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Timeframe for disenrollment determinations.</E>
                                         (1) Regardless of the procedures followed, the effective date of an approved disenrollment must be no later than the first day of the second month following the month in which the enrollee or the MCO, PIHP, PAHP, or PCCM files the request. 
                                    </P>
                                    <P>(2) If the MCO, PIHP, PAHP, or PCCM or the State agency (whichever is responsible) fails to make the determination within the timeframes specified in paragraph (e)(1) of this section, the disenrollment is considered approved. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Notice and appeals.</E>
                                         A State that restricts disenrollment under this section must take the following actions: 
                                    </P>
                                    <P>(1) Provide that enrollees and their representatives are given written notice of disenrollment rights at least 60 days before the start of each enrollment period. </P>
                                    <P>(2) Ensure access to State fair hearing for any enrollee dissatisfied with a State agency determination that there is not good cause for disenrollment. </P>
                                    <P>
                                        (g) 
                                        <E T="03">Automatic reenrollment: Contract requirement.</E>
                                         If the State plan so specifies, the contract must provide for automatic reenrollment of a recipient who is disenrolled solely because he or she loses Medicaid eligibility for a period of 2 months or less. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.58</SECTNO>
                                    <SUBJECT>Conflict of interest safeguards. </SUBJECT>
                                    <P>(a) As a condition for contracting with MCOs, PIHPs, or PAHPs, a State must have in effect safeguards against conflict of interest on the part of State and local officers and employees and agents of the State who have responsibilities relating to the MCO, PIHP, or PAHP contracts or the default enrollment process specified in § 438.50(f). </P>
                                    <P>(b) These safeguards must be at least as effective as the safeguards specified in section 27 of the Office of Federal Procurement Policy Act (41 U.S.C. 423). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.60</SECTNO>
                                    <SUBJECT>Limit on payment to other providers. </SUBJECT>
                                    <P>The State agency must ensure that no payment is made to a provider other than the MCO, PIHP, or PAHP for services available under the contract between the State and the MCO, PIHP, or PAHP, except when these payments are provided for in title XIX of the Act, in 42 CFR, or when the State agency has adjusted the capitation rates paid under the contract, in accordance with § 438.6(c)(5)(v), to make payments for graduate medical education. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.62</SECTNO>
                                    <SUBJECT>Continued services to recipients. </SUBJECT>
                                    <P>The State agency must arrange for Medicaid services to be provided without delay to any Medicaid enrollee of an MCO, PIHP, PAHP, or PCCM whose contract is terminated and for any Medicaid enrollee who is disenrolled from an MCO, PIHP, PAHP, or PCCM for any reason other than ineligibility for Medicaid. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.66</SECTNO>
                                    <SUBJECT>Monitoring procedures. </SUBJECT>
                                    <P>The State agency must have in effect procedures for monitoring the MCO's, PIHP's, or PAHP's operations, including, at a minimum, operations related to the following: </P>
                                    <P>(a) Recipient enrollment and disenrollment. </P>
                                    <P>(b) Processing of grievances and appeals. </P>
                                    <P>(c) Violations subject to intermediate sanctions, as set forth in subpart I of this part. </P>
                                    <P>(d) Violations of the conditions for FFP, as set forth in subpart J of this part. </P>
                                    <P>(e) All other provisions of the contract, as appropriate. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart C—Enrollee Rights and Protections </HD>
                                <SECTION>
                                    <SECTNO>§ 438.100</SECTNO>
                                    <SUBJECT>Enrollee rights. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rule.</E>
                                         The State must ensure that— 
                                    </P>
                                    <P>(1) Each MCO and PIHP has written policies regarding the enrollee rights specified in this section; and </P>
                                    <P>(2) Each MCO, PIHP, PAHP, and PCCM complies with any applicable Federal and State laws that pertain to enrollee rights, and ensures that its staff and affiliated providers take those rights into account when furnishing services to enrollees. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Specific rights—</E>
                                         (1) 
                                        <E T="03">Basic requirement.</E>
                                         The State must ensure that each managed care enrollee is guaranteed the rights as specified in paragraphs (b)(2) and (b)(3) of this section. 
                                    </P>
                                    <P>(2) An enrollee of an MCO, PIHP, PAHP, or PCCM has the following rights: The right to — </P>
                                    <P>(i) Receive information in accordance with § 438.10. </P>
                                    <P>(ii) Be treated with respect and with due consideration for his or her dignity and privacy. </P>
                                    <P>(iii) Receive information on available treatment options and alternatives, presented in a manner appropriate to the enrollee's condition and ability to understand. (The information requirements for services that are not covered under the contract because of moral or religious objections are set forth in § 438.10(f)(6)(xiii).) </P>
                                    <P>(iv) Participate in decisions regarding his or her health care, including the right to refuse treatment. </P>
                                    <P>(v) Be free from any form of restraint or seclusion used as a means of coercion, discipline, convenience or retaliation, as specified in other Federal regulations on the use of restraints and seclusion. </P>
                                    <P>(vi) If the privacy rule, as set forth in 45 CFR parts 160 and 164 subparts A and E, applies, request and receive a copy of his or her medical records, and request that they be amended or corrected, as specified in 45 CFR § 164.524 and 164.526. </P>
                                    <P>
                                        (3) An enrollee of an MCO, PIHP, or PAHP (consistent with the scope of the PAHP's contracted services) has the right to be furnished health care services 
                                        <PRTPAGE P="41104"/>
                                        in accordance with §§ 438.206 through 438.210. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Free exercise of rights.</E>
                                         The State must ensure that each enrollee is free to exercise his or her rights, and that the exercise of those rights does not adversely affect the way the MCO, PIHP, PAHP, or PCCM and its providers or the State agency treat the enrollee. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Compliance with other Federal and State laws.</E>
                                         The State must ensure that each MCO, PIHP, PAHP, and PCCM complies with any other applicable Federal and State laws (such as: title VI of the Civil Rights Act of 1964 as implemented by regulations at 45 CFR part 80; the Age Discrimination Act of 1975 as implemented by regulations at 45 CFR part 91; the Rehabilitation Act of 1973; and titles II and III of the Americans with Disabilities Act; and other laws regarding privacy and confidentiality). 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.102</SECTNO>
                                    <SUBJECT>Provider-enrollee communications. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rules.</E>
                                         (1) An MCO, PIHP, or PAHP may not prohibit, or otherwise restrict, a health care professional acting within the lawful scope of practice, from advising or advocating on behalf of an enrollee who is his or her patient, for the following: 
                                    </P>
                                    <P>(i) The enrollee's health status, medical care, or treatment options, including any alternative treatment that may be self-administered. </P>
                                    <P>(ii) Any information the enrollee needs in order to decide among all relevant treatment options. </P>
                                    <P>(iii) The risks, benefits, and consequences of treatment or nontreatment. </P>
                                    <P>(iv) The enrollee's right to participate in decisions regarding his or her health care, including the right to refuse treatment, and to express preferences about future treatment decisions. </P>
                                    <P>(2) Subject to the information requirements of paragraph (b) of this section, an MCO, PIHP, or PAHP that would otherwise be required to provide, reimburse for, or provide coverage of, a counseling or referral service because of the requirement in paragraph (a)(1) of this section is not required to do so if the MCO, PIHP, or PAHP objects to the service on moral or religious grounds. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Information requirements: MCO, PIHP, and PAHP responsibility.</E>
                                         (1) An MCO, PIHP, or PAHP that elects the option provided in paragraph (a)(2) of this section must furnish information about the services it does not cover as follows: 
                                    </P>
                                    <P>(i) To the State— </P>
                                    <P>(A) With its application for a Medicaid contract; and </P>
                                    <P>(B) Whenever it adopts the policy during the term of the contract. </P>
                                    <P>(ii) Consistent with the provisions of § 438.10— </P>
                                    <P>(A) To potential enrollees, before and during enrollment; and </P>
                                    <P>(B) To enrollees, within 90 days after adopting the policy with respect to any particular service. (Although this timeframe would be sufficient to entitle the MCO, PIHP, or PAHP to the option provided in paragraph (a)(2) of this section, the overriding rule in § 438.10(f)(4) requires the State, its contracted representative, or MCO, PIHP, or PAHP to furnish the information at least 30 days before the effective date of the policy.) </P>
                                    <P>(2) As specified in § 438.10(e) and (f), the information that MCOs, PIHPs, and PAHPs must furnish to enrollees and potential enrollees does not include how and where to obtain the service excluded under paragraph (a)(2) of this section. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Information requirements: State responsibility.</E>
                                         For each service excluded by an MCO, PIHP, or PAHP under paragraph (a)(2) of this section, the State must provide information on how and where to obtain the service, as specified in § 438.10(e)(2)(ii) and (f)(6)(xii). 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Sanction.</E>
                                         An MCO that violates the prohibition of paragraph (a)(1) of this section is subject to intermediate sanctions under subpart I of this part. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.104</SECTNO>
                                    <SUBJECT>Marketing activities. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Terminology.</E>
                                         As used in this section, the following terms have the indicated meanings: 
                                    </P>
                                    <P>
                                        <E T="03">Cold-call marketing</E>
                                         means any unsolicited personal contact by the MCO, PIHP, PAHP, or PCCM with a potential enrollee for the purpose of marketing as defined in this paragraph. 
                                    </P>
                                    <P>
                                        <E T="03">Marketing</E>
                                         means any communication, from an MCO, PIHP, PAHP, or PCCM to a Medicaid recipient who is not enrolled in that entity, that can reasonably be interpreted as intended to influence the recipient to enroll in that particular MCO's, PIHP's, PAHP's, or PCCM's Medicaid product, or either to not enroll in, or to disenroll from, another MCO's, PIHP's, PAHP's, or PCCM's Medicaid product. 
                                    </P>
                                    <P>
                                        <E T="03">Marketing materials</E>
                                         means materials that— 
                                    </P>
                                    <P>(1) Are produced in any medium, by or on behalf of an MCO, PIHP, PAHP, or PCCM; and </P>
                                    <P>(2) Can reasonably be interpreted as intended to market to potential enrollees. </P>
                                    <P>
                                        <E T="03">MCO, PIHP, PAHP, or PCCM</E>
                                         include any of the entity's employees, affiliated providers, agents, or contractors. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Contract requirements.</E>
                                         Each contract with an MCO, PIHP, PAHP, or PCCM must comply with the following requirements: 
                                    </P>
                                    <P>(1) Provide that the entity— </P>
                                    <P>(i) Does not distribute any marketing materials without first obtaining State approval; </P>
                                    <P>(ii) Distributes the materials to its entire service area as indicated in the contract; </P>
                                    <P>(iii) Complies with the information requirements of § 438.10 to ensure that, before enrolling, the recipient receives, from the entity or the State, the accurate oral and written information he or she needs to make an informed decision on whether to enroll; </P>
                                    <P>(iv) Does not seek to influence enrollment in conjunction with the sale or offering of any private insurance; and </P>
                                    <P>(v) Does not, directly or indirectly, engage in door-to-door, telephone, or other cold-call marketing activities. </P>
                                    <P>(2) Specify the methods by which the entity assures the State agency that marketing, including plans and materials, is accurate and does not mislead, confuse, or defraud the recipients or the State agency. Statements that will be considered inaccurate, false, or misleading include, but are not limited to, any assertion or statement (whether written or oral) that— </P>
                                    <P>(i) The recipient must enroll in the MCO, PIHP, PAHP, or PCCM in order to obtain benefits or in order to not lose benefits; or </P>
                                    <P>(ii) The MCO, PIHP, PAHP, or PCCM is endorsed by CMS, the Federal or State government, or similar entity. </P>
                                    <P>
                                        (c) 
                                        <E T="03">State agency review.</E>
                                         In reviewing the marketing materials submitted by the entity, the State must consult with the Medical Care Advisory Committee established under § 431.12 of this chapter or an advisory committee with similar membership. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.106</SECTNO>
                                    <SUBJECT>Liability for payment. </SUBJECT>
                                    <P>Each MCO, PIHP, and PAHP must provide that its Medicaid enrollees are not held liable for any of the following: </P>
                                    <P>(a) The MCO's, PIHP's, or PAHP's debts, in the event of the entity's insolvency. </P>
                                    <P>(b) Covered services provided to the enrollee, for which— </P>
                                    <P>(1) The State does not pay the MCO, PIHP, or PAHP; or </P>
                                    <P>(2) The State, or the MCO, PIHP, or PAHP does not pay the individual or health care provider that furnishes the services under a contractual, referral, or other arrangement. </P>
                                    <P>
                                        (c) Payments for covered services furnished under a contract, referral, or other arrangement, to the extent that those payments are in excess of the amount that the enrollee would owe if 
                                        <PRTPAGE P="41105"/>
                                        the MCO, PIHP, or PAHP provided the services directly. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.108</SECTNO>
                                    <SUBJECT>Cost sharing. </SUBJECT>
                                    <P>The contract must provide that any cost sharing imposed on Medicaid enrollees is in accordance with §§ 447.50 through 447.60 of this chapter. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.114</SECTNO>
                                    <SUBJECT>Emergency and poststabilization services. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Definitions.</E>
                                         As used in this section— 
                                    </P>
                                    <P>
                                        <E T="03">Emergency medical condition</E>
                                         means a medical condition manifesting itself by acute symptoms of sufficient severity (including severe pain) that a prudent layperson, who possesses an average knowledge of health and medicine, could reasonably expect the absence of immediate medical attention to result in the following: 
                                    </P>
                                    <P>(1) Placing the health of the individual (or, with respect to a pregnant woman, the health of the woman or her unborn child) in serious jeopardy. </P>
                                    <P>(2) Serious impairment to bodily functions. </P>
                                    <P>(3) Serious dysfunction of any bodily organ or part. </P>
                                    <P>
                                        <E T="03">Emergency services</E>
                                         means covered inpatient and outpatient services that are as follows: 
                                    </P>
                                    <P>(1) Furnished by a provider that is qualified to furnish these services under this title. </P>
                                    <P>(2) Needed to evaluate or stabilize an emergency medical condition. </P>
                                    <P>
                                        <E T="03">Poststabilization care services</E>
                                         means covered services, related to an emergency medical condition that are provided after an enrollee is stabilized in order to maintain the stabilized condition, or, under the circumstances described in paragraph (e) of this section, to improve or resolve the enrollee's condition. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Coverage and payment:</E>
                                          
                                        <E T="03">General rule.</E>
                                         The following entities are responsible for coverage and payment of emergency services and poststabilization care services. 
                                    </P>
                                    <P>(1) The MCO, PIHP, or PAHP. </P>
                                    <P>(2) The PCCM that has a risk contract that covers these services. </P>
                                    <P>(3) The State, in the case of a PCCM that has a fee-for-service contract. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Coverage and payment:</E>
                                          
                                        <E T="03">Emergency services.</E>
                                         (1) The entities identified in paragraph (b) of this section— 
                                    </P>
                                    <P>(i) Must cover and pay for emergency services regardless of whether the provider that furnishes the services has a contract with the MCO, PIHP, PAHP, or PCCM; and </P>
                                    <P>(ii) May not deny payment for treatment obtained under either of the following circumstances: </P>
                                    <P>
                                        (A) An enrollee had an emergency medical condition, including cases in which the absence of immediate medical attention would not have had the outcomes specified in paragraphs (1), (2), and (3) of the definition of 
                                        <E T="03">emergency medical condition</E>
                                         in paragraph (a) of this section. 
                                    </P>
                                    <P>(B) A representative of the MCO, PIHP, PAHP, or PCCM instructs the enrollee to seek emergency services. </P>
                                    <P>(2) A PCCM must— </P>
                                    <P>(i) Allow enrollees to obtain emergency services outside the primary care case management system regardless of whether the case manager referred the enrollee to the provider that furnishes the services; and </P>
                                    <P>(ii) Pay for the services if the manager's contract is a risk contract that covers those services. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Additional rules for emergency services.</E>
                                         (1) The entities specified in paragraph (b) of this section may not— 
                                    </P>
                                    <P>(i) Limit what constitutes an emergency medical condition with reference to paragraph (a) of this section, on the basis of lists of diagnoses or symptoms; and </P>
                                    <P>(ii) Refuse to cover emergency services based on the emergency room provider, hospital, or fiscal agent not notifying the enrollee's primary care provider, MCO, or applicable State entity of the enrollee's screening and treatment within 10 calendar days of presentation for emergency services. </P>
                                    <P>(2) An enrollee who has an emergency medical condition may not be held liable for payment of subsequent screening and treatment needed to diagnose the specific condition or stabilize the patient. </P>
                                    <P>(3) The attending emergency physician, or the provider actually treating the enrollee, is responsible for determining when the enrollee is sufficiently stabilized for transfer or discharge, and that determination is binding on the entities identified in paragraph (b) of this section as responsible for coverage and payment. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Coverage and payment:</E>
                                          
                                        <E T="03">Poststabilization care services.</E>
                                         Poststabilization care services are covered and paid for in accordance with provisions set forth at § 422.113(c) of this chapter. In applying those provisions, reference to “M+C organization” must be read as reference to the entities responsible for Medicaid payment, as specified in paragraph (b) of this section. 
                                    </P>
                                    <P>
                                        (f) 
                                        <E T="03">Applicability to PIHPs and PAHPs.</E>
                                         To the extent that services required to treat an emergency medical condition fall within the scope of the services for which the PIHP or PAHP is responsible, the rules under this section apply. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.116</SECTNO>
                                    <SUBJECT>Solvency standards. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Requirement for assurances</E>
                                         (1) Each MCO, PIHP, and PAHP that is not a Federally qualified HMO (as defined in section 1310 of the Public Health Service Act) must provide assurances satisfactory to the State showing that its provision against the risk of insolvency is adequate to ensure that its Medicaid enrollees will not be liable for the MCO's, PIHP's, or PAHP's debts if the entity becomes insolvent. 
                                    </P>
                                    <P>(2) Federally qualified HMOs, as defined in section 1310 of the Public Health Service Act, are exempt from this requirement. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Other requirements</E>
                                        —(1) 
                                        <E T="03">General rule.</E>
                                         Except as provided in paragraph (b)(2) of this section, an MCO, PIHP, and PAHP must meet the solvency standards established by the State for private health maintenance organizations, or be licensed or certified by the State as a risk-bearing entity. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Exception.</E>
                                         Paragraph (b)(1) of this section does not apply to an MCO, PIHP, or PAHP that meets any of the following conditions: 
                                    </P>
                                    <P>(i) Does not provide both inpatient hospital services and physician services. </P>
                                    <P>(ii) Is a public entity. </P>
                                    <P>(iii) Is (or is controlled by) one or more Federally qualified health centers and meets the solvency standards established by the State for those centers. </P>
                                    <P>(iv) Has its solvency guaranteed by the State. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart D—Quality Assessment and Performance Improvement </HD>
                                <SECTION>
                                    <SECTNO>§ 438.200</SECTNO>
                                    <SUBJECT>Scope. </SUBJECT>
                                    <P>This subpart implements section 1932(c)(1) of the Act and sets forth specifications for quality assessment and performance improvement strategies that States must implement to ensure the delivery of quality health care by all MCOs, PIHPs, and PAHPs. It also establishes standards that States, MCOs, PIHPs, and PAHPs must meet. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.202</SECTNO>
                                    <SUBJECT>State responsibilities. </SUBJECT>
                                    <P>Each State contracting with an MCO or PIHP must do the following: </P>
                                    <P>(a) Have a written strategy for assessing and improving the quality of managed care services offered by all MCOs and PIHPs. </P>
                                    <P>(b) Obtain the input of recipients and other stakeholders in the development of the strategy and make the strategy available for public comment before adopting it in final. </P>
                                    <P>
                                        (c) Ensure that MCOs, PIHPs, and PAHPs comply with standards established by the State, consistent with this subpart. 
                                        <PRTPAGE P="41106"/>
                                    </P>
                                    <P>(d) Conduct periodic reviews to evaluate the effectiveness of the strategy, and update the strategy periodically, as needed. </P>
                                    <P>(e) Submit to CMS the following: </P>
                                    <P>(1) A copy of the initial strategy, and a copy of the revised strategy whenever significant changes are made. </P>
                                    <P>(2) Regular reports on the implementation and effectiveness of the strategy. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.204</SECTNO>
                                    <SUBJECT>Elements of State quality strategies. </SUBJECT>
                                    <P>At a minimum, State strategies must include the following: </P>
                                    <P>(a) The MCO and PIHP contract provisions that incorporate the standards specified in this subpart. </P>
                                    <P>(b) Procedures that— </P>
                                    <P>(1) Assess the quality and appropriateness of care and services furnished to all Medicaid enrollees under the MCO and PIHP contracts, and to individuals with special health care needs. </P>
                                    <P>(2) Identify the race, ethnicity, and primary language spoken of each Medicaid enrollee. States must provide this information to the MCO and PIHP for each Medicaid enrollee at the time of enrollment. </P>
                                    <P>(3) Regularly monitor and evaluate the MCO and PIHP compliance with the standards. </P>
                                    <P>(c) For MCOs and PIHPs, any national performance measures and levels that may be identified and developed by CMS in consultation with States and other relevant stakeholders. </P>
                                    <P>(d) Arrangements for annual, external independent reviews of the quality outcomes and timeliness of, and access to, the services covered under each MCO and PIHP contract. </P>
                                    <P>(e) For MCOs, appropriate use of intermediate sanctions that, at a minimum, meet the requirements of subpart I of this part. </P>
                                    <P>(f) An information system that supports initial and ongoing operation and review of the State's quality strategy. </P>
                                    <P>(g) Standards, at least as stringent as those in the following sections of this subpart, for access to care, structure and operations, and quality measurement and improvement. </P>
                                    <HD SOURCE="HD1">Access Standards </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.206</SECTNO>
                                    <SUBJECT>Availability of services. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Basic rule.</E>
                                         Each State must ensure that all services covered under the State plan are available and accessible to enrollees of MCOs, PIHPs, and PAHPs. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Delivery network.</E>
                                         The State must ensure, through its contracts, that each MCO, and each PIHP and PAHP consistent with the scope of the PIHP's or PAHP's contracted services, meets the following requirements: 
                                    </P>
                                    <P>(1) Maintains and monitors a network of appropriate providers that is supported by written agreements and is sufficient to provide adequate access to all services covered under the contract. In establishing and maintaining the network, each MCO, PIHP, and PAHP must consider the following: </P>
                                    <P>(i) The anticipated Medicaid enrollment. </P>
                                    <P>(ii) The expected utilization of services, taking into consideration the characteristics and health care needs of specific Medicaid populations represented in the particular MCO, PIHP, and PAHP. </P>
                                    <P>(iii) The numbers and types (in terms of training, experience, and specialization) of providers required to furnish the contracted Medicaid services. </P>
                                    <P>(iv) The numbers of network providers who are not accepting new Medicaid patients. </P>
                                    <P>(v) The geographic location of providers and Medicaid enrollees, considering distance, travel time, the means of transportation ordinarily used by Medicaid enrollees, and whether the location provides physical access for Medicaid enrollees with disabilities. </P>
                                    <P>(2) Provides female enrollees with direct access to a women's health specialist within the network for covered care necessary to provide women's routine and preventive health care services. This is in addition to the enrollee's designated source of primary care if that source is not a women's health specialist. </P>
                                    <P>(3) Provides for a second opinion from a qualified health care professional within the network, or arranges for the enrollee to obtain one outside the network, at no cost to the enrollee. </P>
                                    <P>(4) If the network is unable to provide necessary services, covered under the contract, to a particular enrollee, the MCO, PIHP, or PAHP must adequately and timely cover these services out of network for the enrollee, for as long as the MCO, PIHP, or PAHP is unable to provide them. </P>
                                    <P>(5) Requires out-of-network providers to coordinate with the MCO or PIHP with respect to payment and ensures that cost to the enrollee is no greater than it would be if the services were furnished within the network. </P>
                                    <P>(6) Demonstrates that its providers are credentialed as required by § 438.214. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Furnishing of services.</E>
                                         The State must ensure that each MCO, PIHP, and PAHP contract complies with the requirements of this paragraph. 
                                    </P>
                                    <P>
                                        (1) 
                                        <E T="03">Timely access.</E>
                                         Each MCO, PIHP, and PAHP must do the following: 
                                    </P>
                                    <P>(i) Meet and require its providers to meet State standards for timely access to care and services, taking into account the urgency of the need for services. </P>
                                    <P>(ii) Ensure that the network providers offer hours of operation that are no less than the hours of operation offered to commercial enrollees or comparable to Medicaid fee-for-service, if the provider serves only Medicaid enrollees. </P>
                                    <P>(iii) Make services included in the contract available 24 hours a day, 7 days a week, when medically necessary. </P>
                                    <P>(iv) Establish mechanisms to ensure compliance by providers. </P>
                                    <P>(v) Monitor providers regularly to determine compliance. </P>
                                    <P>(vi) Take corrective action if there is a failure to comply. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Cultural considerations.</E>
                                         Each MCO, PIHP, and PAHP participates in the State's efforts to promote the delivery of services in a culturally competent manner to all enrollees, including those with limited English proficiency and diverse cultural and ethnic backgrounds. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.207</SECTNO>
                                    <SUBJECT>Assurances of adequate capacity and services. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Basic rule.</E>
                                         The State must ensure, through its contracts, that each MCO, PIHP, and PAHP gives assurances to the State and provides supporting documentation that demonstrates that it has the capacity to serve the expected enrollment in its service area in accordance with the State's standards for access to care under this subpart. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Nature of supporting documentation.</E>
                                         Each MCO, PIHP, and PAHP must submit documentation to the State, in a format specified by the State to demonstrate that it complies with the following requirements: 
                                    </P>
                                    <P>(1) Offers an appropriate range of preventive, primary care, and specialty services that is adequate for the anticipated number of enrollees for the service area. </P>
                                    <P>(2) Maintains a network of providers that is sufficient in number, mix, and geographic distribution to meet the needs of the anticipated number of enrollees in the service area. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Timing of documentation.</E>
                                         Each MCO, PIHP, and PAHP must submit the documentation described in paragraph (b) of this section as specified by the State, but no less frequently than the following: 
                                    </P>
                                    <P>(1) At the time it enters into a contract with the State. </P>
                                    <P>
                                        (2) At any time there has been a significant change (as defined by the State) in the MCO's, PIHP's, or PAHP's operations that would affect adequate capacity and services, including— 
                                        <PRTPAGE P="41107"/>
                                    </P>
                                    <P>(i) Changes in MCO, PIHP, or PAHP services, benefits, geographic service area or payments; or </P>
                                    <P>(ii) Enrollment of a new population in the MCO, PIHP, or PAHP. </P>
                                    <P>
                                        (d) 
                                        <E T="03">State review and certification to CMS.</E>
                                         After the State reviews the documentation submitted by the MCO, PIHP, or PAHP, the State must certify to CMS that the MCO, PIHP, or PAHP has complied with the State's requirements for availability of services, as set forth in § 438.206. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">CMS' right to inspect documentation.</E>
                                         The State must make available to CMS, upon request, all documentation collected by the State from the MCO, PIHP, or PAHP. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.208 </SECTNO>
                                    <SUBJECT>Coordination and continuity of care. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Basic requirement</E>
                                        —(1) 
                                        <E T="03">General rule.</E>
                                         Except as specified in paragraphs (a)(2) and (a)(3) of this section, the State must ensure through its contracts, that each MCO, PIHP, and PAHP complies with the requirements of this section. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">PIHP and PAHP exception.</E>
                                         For PIHPs and PAHPs, the State determines, based on the scope of the entity's services, and on the way the State has organized the delivery of managed care services, whether a particular PIHP or PAHP is required to— 
                                    </P>
                                    <P>(i) Meet the primary care requirement of paragraph (b)(1) of this section; and </P>
                                    <P>(ii) Implement mechanisms for identifying, assessing, and producing a treatment plan for an individual with special health care needs, as specified in paragraph (c) of this section. </P>
                                    <P>
                                        (3) 
                                        <E T="03">Exception for MCOs that serve dually eligible enrollees.</E>
                                         (i) For each MCO that serves enrollees who are also enrolled in and receive Medicare benefits from a Medicare+Choice plan, the State determines to what extent the MCO must meet the primary care coordination, identification, assessment, and treatment planning provisions of paragraphs (b) and (c) of this section with respect to dually eligible individuals. 
                                    </P>
                                    <P>(ii) The State bases its determination on the services it requires the MCO to furnish to dually eligible enrollees. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Primary care and coordination of health care services for all MCO, PIHP, and PAHP enrollees.</E>
                                         Each MCO, PIHP, and PAHP must implement procedures to deliver primary care to and coordinate health care service for all MCO, PIHP, and PAHP enrollees. These procedures must meet State requirements and must do the following: 
                                    </P>
                                    <P>(1) Ensure that each enrollee has an ongoing source of primary care appropriate to his or her needs and a person or entity formally designated as primarily responsible for coordinating the health care services furnished to the enrollee. </P>
                                    <P>(2) Coordinate the services the MCO, PIHP, or PAHP furnishes to the enrollee with the services the enrollee receives from any other MCO, PIHP, or PAHP. </P>
                                    <P>(3) Share with other MCOs, PIHPs, and PAHPs serving the enrollee with special health care needs the results of its identification and assessment of that enrollee's needs to prevent duplication of those activities. </P>
                                    <P>(4) Ensure that in the process of coordinating care, each enrollee's privacy is protected in accordance with the privacy requirements in 45 CFR parts 160 and 164 subparts A and E, to the extent that they are applicable. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Additional services for enrollees with special health care needs.</E>
                                    </P>
                                    <P>
                                        (1) 
                                        <E T="03">Identification.</E>
                                         The State must implement mechanisms to identify persons with special health care needs to MCOs, PIHPs and PAHPs, as those persons are defined by the State. These identification mechanisms— 
                                    </P>
                                    <P>(i) Must be specified in the State's quality improvement strategy in § 438.202; and </P>
                                    <P>(ii) May use State staff, the State's enrollment broker, or the State's MCOs, </P>
                                    <P>PIHPs and PAHPs. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Assessment.</E>
                                         Each MCO, PIHP, and PAHP must implement mechanisms to assess each Medicaid enrollee identified by the State (through the mechanism specified in paragraph (c)(1) of this section) and identified to the MCO, PIHP, and PAHP by the State as having special health care needs in order to identify any ongoing special conditions of the enrollee that require a course of treatment or regular care monitoring. The assessment mechanisms must use appropriate health care professionals. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Treatment plans.</E>
                                         If the State requires MCOs, PIHPs, and PAHPs to produce a treatment plan for enrollees with special health care needs who are determined through assessment to need a course of treatment or regular care monitoring, the treatment plan must be— 
                                    </P>
                                    <P>(i) Developed by the enrollee's primary care provider with enrollee participation, and in consultation with any specialists caring for the enrollee; </P>
                                    <P>(ii) Approved by the MCO, PIHP, or PAHP in a timely manner, if this approval is required by the MCO, PIHP, or PAHP; and </P>
                                    <P>(iii) In accord with any applicable State quality assurance and utilization review standards. </P>
                                    <P>
                                        (4) 
                                        <E T="03">Direct access to specialists.</E>
                                         For enrollees with special health care needs determined through an assessment by appropriate health care professionals (consistent with § 438.208(c)(2)) to need a course of treatment or regular care monitoring, each MCO, PIHP, and PAHP must have a mechanism in place to allow enrollees to directly access a specialist (for example, through a standing referral or an approved number of visits) as appropriate for the enrollee's condition and identified needs. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.210 </SECTNO>
                                    <SUBJECT>Coverage and authorization of services. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Coverage.</E>
                                         Each contract with an MCO, PIHP, or PAHP must do the following: 
                                    </P>
                                    <P>(1) Identify, define, and specify the amount, duration, and scope of each service that the MCO, PIHP, or PAHP is required to offer. </P>
                                    <P>(2) Require that the services identified in paragraph (a)(1) of this section be furnished in an amount, duration, and scope that is no less than the amount, duration, and scope for the same services furnished to beneficiaries under fee-for-service Medicaid, as set forth in § 440.230. </P>
                                    <P>(3) Provide that the MCO, PIHP, or PAHP— </P>
                                    <P>(i) Must ensure that the services are sufficient in amount, duration, or scope to reasonably be expected to achieve the purpose for which the services are furnished. </P>
                                    <P>(ii) May not arbitrarily deny or reduce the amount, duration, or scope of a required service solely because of diagnosis, type of illness, or condition of the beneficiary; </P>
                                    <P>(iii) May place appropriate limits on a service— </P>
                                    <P>(A) On the basis of criteria applied under the State plan, such as medical necessity; or </P>
                                    <P>(B) For the purpose of utilization control, provided the services furnished can reasonably be expected to achieve their purpose, as required in paragraph (a)(3)(i) of this section; and </P>
                                    <P>(4) Specify what constitutes “medically necessary services” in a manner that— </P>
                                    <P>(i) Is no more restrictive than that used in the State Medicaid program as indicated in State statutes and regulations, the State Plan, and other State policy and procedures; and </P>
                                    <P>(ii) Addresses the extent to which the MCO, PIHP, or PAHP is responsible for covering services related to the following: </P>
                                    <P>(A) The prevention, diagnosis, and treatment of health impairments. </P>
                                    <P>(B) The ability to achieve age-appropriate growth and development. </P>
                                    <P>
                                        (C) The ability to attain, maintain, or regain functional capacity. 
                                        <PRTPAGE P="41108"/>
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Authorization of services.</E>
                                         For the processing of requests for initial and continuing authorizations of services, each contract must require— 
                                    </P>
                                    <P>(1) That the MCO, PIHP, or PAHP and its subcontractors have in place, and follow, written policies and procedures. </P>
                                    <P>(2) That the MCO, PIHP, or PAHP— </P>
                                    <P>(i) Have in effect mechanisms to ensure consistent application of review criteria for authorization decisions; and </P>
                                    <P>(ii) Consult with the requesting provider when appropriate. </P>
                                    <P>(3) That any decision to deny a service authorization request or to authorize a service in an amount, duration, or scope that is less than requested, be made by a health care professional who has appropriate clinical expertise in treating the enrollee's condition or disease. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Notice of adverse action.</E>
                                         Each contract must provide for the MCO, PIHP, or PAHP to notify the requesting provider, and give the enrollee written notice of any decision by the MCO, PIHP, or PAHP to deny a service authorization request, or to authorize a service in an amount, duration, or scope that is less than requested. For MCOs and PIHPs, the notice must meet the requirements of § 438.404, except that the notice to the provider need not be in writing. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Timeframe for decisions.</E>
                                         Each MCO, PIHP, or PAHP contract must provide for the following decisions and notices: 
                                    </P>
                                    <P>
                                        (1) 
                                        <E T="03">Standard authorization decisions.</E>
                                         For standard authorization decisions, provide notice as expeditiously as the enrollee's health condition requires and within State-established timeframes that may not exceed 14 calendar days following receipt of the request for service, with a possible extension of up to 14 additional calendar days, if— 
                                    </P>
                                    <P>(i) The enrollee, or the provider, requests extension; or </P>
                                    <P>(ii) The MCO, PIHP, or PAHP justifies (to the State agency upon request) a need for additional information and how the extension is in the enrollee's interest. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Expedited authorization decisions.</E>
                                         (i) For cases in which a provider indicates, or the MCO, PIHP, or PAHP determines, that following the standard timeframe could seriously jeopardize the enrollee's life or health or ability to attain, maintain, or regain maximum function, the MCO, PIHP, or PAHP must make an expedited authorization decision and provide notice as expeditiously as the enrollee's health condition requires and no later than 3 working days after receipt of the request for service. 
                                    </P>
                                    <P>(ii) The MCO, PIHP, or PAHP may extend the 3 working days time period by up to 14 calendar days if the enrollee requests an extension, or if the MCO, PIHP, or PAHP justifies (to the State agency upon request) a need for additional information and how the extension is in the enrollee's interest. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Compensation for utilization management activities.</E>
                                         Each contract must provide that, consistent with § 438.6(h), and § 422.208 of this chapter, compensation to individuals or entities that conduct utilization management activities is not structured so as to provide incentives for the individual or entity to deny, limit, or discontinue medically necessary services to any enrollee. 
                                    </P>
                                    <HD SOURCE="HD1">Structure and Operation Standards </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.214 </SECTNO>
                                    <SUBJECT>Provider selection. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rules.</E>
                                         The State must ensure, through its contracts, that each MCO, PIHP, or PAHP implements written policies and procedures for selection and retention of providers and that those policies and procedures include, at a minimum, the requirements of this section. 
                                    </P>
                                    <P>
                                        (a) 
                                        <E T="03">Credentialing and recredentialing requirements.</E>
                                         (1) Each State must establish a uniform credentialing and recredentialing policy that each MCO, PIHP, and PAHP must follow. 
                                    </P>
                                    <P>(2) Each MCO, PIHP, and PAHP must follow a documented process for credentialing and recredentialing of providers who have signed contracts or participation agreements with the MCO, PIHP, or PAHP. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Nondiscrimination.</E>
                                         MCO, PIHP, and PAHP provider selection policies and procedures, consistent with § 438.12, must not discriminate against particular providers that serve high-risk populations or specialize in conditions that require costly treatment. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Excluded providers.</E>
                                         MCOs, PIHPs, and PAHPs may not employ or contract with providers excluded from participation in Federal health care programs under either section 1128 or section 1128A of the Act. 
                                    </P>
                                    <P>
                                        (e) 
                                        <E T="03">State requirements.</E>
                                         Each MCO, PIHP, and PAHP must comply with any additional requirements established by the State. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.218 </SECTNO>
                                    <SUBJECT>Enrollee information.</SUBJECT>
                                    <P>The requirements that States must meet under § 438.10 constitute part of the State's quality strategy at § 438.204. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.224 </SECTNO>
                                    <SUBJECT>Confidentiality. </SUBJECT>
                                    <P>The State must ensure, through its contracts, that (consistent with subpart F of part 431 of this chapter), for medical records and any other health and enrollment information that identifies a particular enrollee, each MCO, PIHP, and PAHP uses and discloses such individually identifiable health information in accordance with the privacy requirements in 45 CFR parts 160 and 164, subparts A and E, to the extent that these requirements are applicable. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.226 </SECTNO>
                                    <SUBJECT>Enrollment and disenrollment. </SUBJECT>
                                    <P>The State must ensure that each MCO, PIHP, and PAHP contract complies with the enrollment and disenrollment requirements and limitations set forth in § 438.56. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.228 </SECTNO>
                                    <SUBJECT>Grievance systems. </SUBJECT>
                                    <P>(a) The State must ensure, through its contracts, that each MCO and PIHP has in effect a grievance system that meets the requirements of subpart F of this part. </P>
                                    <P>(b) If the State delegates to the MCO or PIHP responsibility for notice of action under subpart E of part 431 of this chapter, the State must conduct random reviews of each delegated MCO or PIHP and its providers and subcontractors to ensure that they are notifying enrollees in a timely manner. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.230 </SECTNO>
                                    <SUBJECT>Subcontractual relationships and delegation. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rule.</E>
                                         The State must ensure, through its contracts, that each MCO, PIHP, and PAHP—
                                    </P>
                                    <P>(1) Oversees and is accountable for any functions and responsibilities that it delegates to any subcontractor; and </P>
                                    <P>(2) Meets the conditions of paragraph (b) of this section. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Specific conditions.</E>
                                         (1) Before any delegation, each MCO, PIHP, and PAHP evaluates the prospective subcontractor's ability to perform the activities to be delegated. 
                                    </P>
                                    <P>(2) There is a written agreement that— </P>
                                    <P>(i) Specifies the activities and report responsibilities delegated to the subcontractor; and </P>
                                    <P>(ii) Provides for revoking delegation or imposing other sanctions if the subcontractor's performance is inadequate. </P>
                                    <P>(3) The MCO, PIHP, or PAHP monitors the subcontractor's performance on an ongoing basis and subjects it to formal review according to a periodic schedule established by the State, consistent with industry standards or State MCO laws and regulations. </P>
                                    <P>
                                        (4) If any MCO, PIHP, or PAHP identifies deficiencies or areas for improvement, the MCO, PIHP, or PAHP and the subcontractor take corrective action. 
                                        <PRTPAGE P="41109"/>
                                    </P>
                                    <HD SOURCE="HD1">Measurement and Improvement Standards </HD>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.236 </SECTNO>
                                    <SUBJECT>Practice guidelines. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Basic rule:</E>
                                         The State must ensure, through its contracts, that each MCO and, when applicable, each PIHP and PAHP meets the requirements of this section. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Adoption of practice guidelines.</E>
                                         Each MCO and, when applicable, each PIHP and PAHP adopts practice guidelines that meet the following requirements: 
                                    </P>
                                    <P>(1) Are based on valid and reliable clinical evidence or a consensus of health care professionals in the particular field. </P>
                                    <P>(2) Consider the needs of the MCO's, PIHP's, or PAHP's enrollees. </P>
                                    <P>(3) Are adopted in consultation with contracting health care professionals. </P>
                                    <P>(4) Are reviewed and updated periodically as appropriate. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Dissemination of guidelines.</E>
                                         Each MCO, PIHP, and PAHP disseminates the guidelines to all affected providers and, upon request, to enrollees and potential enrollees. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Application of guidelines.</E>
                                         Decisions for utilization management, enrollee education, coverage of services, and other areas to which the guidelines apply are consistent with the guidelines. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.240 </SECTNO>
                                    <SUBJECT>Quality assessment and performance improvement program. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rules.</E>
                                         (1) The State must require, through its contracts, that each MCO and PIHP have an ongoing quality assessment and performance improvement program for the services it furnishes to its enrollees. 
                                    </P>
                                    <P>(2) CMS, in consultation with States and other stakeholders, may specify performance measures and topics for performance improvement projects to be required by States in their contracts with MCOs and PIHPs. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Basic elements of MCO and PIHP quality assessment and performance improvement programs.</E>
                                         At a minimum, the State must require that each MCO and PIHP comply with the following requirements: 
                                    </P>
                                    <P>(1) Conduct performance improvement projects as described in paragraph (d) of this section. These projects must be designed to achieve, through ongoing measurements and intervention, significant improvement, sustained over time, in clinical care and nonclinical care areas that are expected to have a favorable effect on health outcomes and enrollee satisfaction. </P>
                                    <P>(2) Submit performance measurement data as described in paragraph (c) of this section. </P>
                                    <P>(3) Have in effect mechanisms to detect both underutilization and overutilization of services. </P>
                                    <P>(4) Have in effect mechanisms to assess the quality and appropriateness of care furnished to enrollees with special health care needs. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Performance measurement.</E>
                                         Annually each MCO and PIHP must— 
                                    </P>
                                    <P>(1) Measure and report to the State its performance, using standard measures required by the State including those that incorporate the requirements of § 438.204(c) and § 438.240(a)(2); </P>
                                    <P>(2) Submit to the State, data specified by the State, that enables the State to measure the MCO's or PIHP's performance; or </P>
                                    <P>(3) Perform a combination of the activities described in paragraphs (c)(1) and (c)(2) of this section. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Performance improvement projects.</E>
                                         (1) MCOs and PIHPs must have an ongoing program of performance improvement projects that focus on clinical and nonclinical areas, and that involve the following: 
                                    </P>
                                    <P>(i) Measurement of performance using objective quality indicators. </P>
                                    <P>(ii) Implementation of system interventions to achieve improvement in quality. </P>
                                    <P>(iii) Evaluation of the effectiveness of the interventions. </P>
                                    <P>(iv) Planning and initiation of activities for increasing or sustaining improvement. </P>
                                    <P>(2) Each MCO and PIHP must report the status and results of each project to the State as requested, including those that incorporate the requirements of § 438.240(a)(2). Each performance improvement project must be completed in a reasonable time period so as to generally allow information on the success of performance improvement projects in the aggregate to produce new information on quality of care every year. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Program review by the State.</E>
                                    </P>
                                    <P>(1) The State must review, at least annually, the impact and effectiveness of each MCO's and PIHP's quality assessment and performance improvement program. The review must include— </P>
                                    <P>(i) The MCO's and PIHP's performance on the standard measures on which it is required to report; and </P>
                                    <P>(ii) The results of each MCO's and PIHP's performance improvement projects. </P>
                                    <P>(2) The State may require that an MCO or PIHP have in effect a process for its own evaluation of the impact and effectiveness of its quality assessment and performance improvement program. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.242</SECTNO>
                                    <SUBJECT>Health information systems. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rule.</E>
                                         The State must ensure, through its contracts, that each MCO and PIHP maintains a health information system that collects, analyzes, integrates, and reports data and can achieve the objectives of this subpart. The system must provide information on areas including, but not limited to, utilization, grievances and appeals, and disenrollments for other than loss of Medicaid eligibility. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Basic elements of a health information system.</E>
                                         The State must require, at a minimum, that each MCO and PIHP comply with the following: 
                                    </P>
                                    <P>(1) Collect data on enrollee and provider characteristics as specified by the State, and on services furnished to enrollees through an encounter data system or other methods as may be specified by the State. </P>
                                    <P>(2) Ensure that data received from providers is accurate and complete by— </P>
                                    <P>(i) Verifying the accuracy and timeliness of reported data; </P>
                                    <P>(ii) Screening the data for completeness, logic, and consistency; and </P>
                                    <P>(iii) Collecting service information in standardized formats to the extent feasible and appropriate. </P>
                                    <P>(3) Make all collected data available to the State and upon request to CMS, as required in this subpart. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart E—[Reserved] </HD>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart F—Grievance System </HD>
                                <SECTION>
                                    <SECTNO>§ 438.400</SECTNO>
                                    <SUBJECT>Statutory basis and definitions. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Statutory basis.</E>
                                         This subpart is based on sections 1902(a)(3), 1902(a)(4), and 1932(b)(4) of the Act. 
                                    </P>
                                    <P>(1) Section 1902(a)(3) requires that a State plan provide an opportunity for a fair hearing to any person whose claim for assistance is denied or not acted upon promptly. </P>
                                    <P>(2) Section 1902(a)(4) requires that the State plan provide for methods of administration that the Secretary finds necessary for the proper and efficient operation of the plan. </P>
                                    <P>(3) Section 1932(b)(4) requires Medicaid managed care organizations to establish internal grievance procedures under which Medicaid enrollees, or providers acting on their behalf, may challenge the denial of coverage of, or payment for, medical assistance. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Definitions.</E>
                                         As used in this subpart, the following terms have the indicated meanings: 
                                    </P>
                                    <P>
                                        <E T="03">Action</E>
                                         means— 
                                    </P>
                                    <P>In the case of an MCO or PIHP— </P>
                                    <P>
                                        (1) The denial or limited authorization of a requested service, including the type or level of service; 
                                        <PRTPAGE P="41110"/>
                                    </P>
                                    <P>(2) The reduction, suspension, or termination of a previously authorized service; </P>
                                    <P>(3) The denial, in whole or in part, of payment for a service; </P>
                                    <P>(4) The failure to provide services in a timely manner, as defined by the State; </P>
                                    <P>(5) The failure of an MCO or PIHP to act within the timeframes provided in § 438.408(b); or </P>
                                    <P>(6) For a resident of a rural area with only one MCO, the denial of a Medicaid enrollee's request to exercise his or her right, under § 438.52(b)(2)(ii), to obtain services outside the network. </P>
                                    <P>
                                        <E T="03">Appeal</E>
                                         means a request for review of an action, as “action” is defined in this section. 
                                    </P>
                                    <P>
                                        <E T="03">Grievance</E>
                                         means an expression of dissatisfaction about any matter other than an action, as “action” is defined in this section. The term is also used to refer to the overall system that includes grievances and appeals handled at the MCO or PIHP level and access to the State fair hearing process. (Possible subjects for grievances include, but are not limited to, the quality of care or services provided, and aspects of interpersonal relationships such as rudeness of a provider or employee, or failure to respect the enrollee's rights.) 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.402</SECTNO>
                                    <SUBJECT>General requirements. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">The grievance system.</E>
                                         Each MCO and PIHP must have a system in place for enrollees that includes a grievance process, an appeal process, and access to the State's fair hearing system. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Filing requirements—</E>
                                        (1) 
                                        <E T="03">Authority to file.—</E>
                                        (i) An enrollee may file a grievance and an MCO or PIHP level appeal, and may request a State fair hearing. 
                                    </P>
                                    <P>(ii) A provider, acting on behalf of the enrollee and with the enrollee's written consent, may file an appeal. A provider may file a grievance or request a State fair hearing on behalf of an enrollee, if the State permits the provider to act as the enrollee's authorized representative in doing so. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Timing.</E>
                                         The State specifies a reasonable timeframe that may be no less than 20 days and not to exceed 90 days from the date on the MCO's or PIHP's notice of action. Within that timeframe— 
                                    </P>
                                    <P>(i) The enrollee or the provider may file an appeal; and </P>
                                    <P>(ii) In a State that does not require exhaustion of MCO and PIHP level appeals, the enrollee may request a State fair hearing. </P>
                                    <P>
                                        (3) 
                                        <E T="03">Procedures.</E>
                                         (i) The enrollee may file a grievance either orally or in writing and, as determined by the State, either with the State or with the MCO or the PIHP. 
                                    </P>
                                    <P>(ii) The enrollee or the provider may file an appeal either orally or in writing, and unless he or she requests expedited resolution, must follow an oral filing with a written, signed, appeal. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.404</SECTNO>
                                    <SUBJECT>Notice of action. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Language and format requirements.</E>
                                         The notice must be in writing and must meet the language and format requirements of § 438.10(c) and (d) to ensure ease of understanding. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Content of notice.</E>
                                         The notice must explain the following: 
                                    </P>
                                    <P>(1) The action the MCO or PIHP or its contractor has taken or intends to take. </P>
                                    <P>(2) The reasons for the action. </P>
                                    <P>(3) The enrollee's or the provider's right to file an MCO or PIHP appeal. </P>
                                    <P>(4) If the State does not require the enrollee to exhaust the MCO or PIHP level appeal procedures, the enrollee's right to request a State fair hearing. </P>
                                    <P>(5) The procedures for exercising the rights specified in this paragraph. </P>
                                    <P>(6) The circumstances under which expedited resolution is available and how to request it. </P>
                                    <P>(7) The enrollee's right to have benefits continue pending resolution of the appeal, how to request that benefits be continued, and the circumstances under which the enrollee may be required to pay the costs of these services. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Timing of notice.</E>
                                         The MCO or PIHP must mail the notice within the following timeframes: 
                                    </P>
                                    <P>(1) For termination, suspension, or reduction of previously authorized Medicaid-covered services, within the timeframes specified in §§ 431.211, 431.213, and 431.214 of this chapter. </P>
                                    <P>(2) For denial of payment, at the time of any action affecting the claim. </P>
                                    <P>(3) For standard service authorization decisions that deny or limit services, within the timeframe specified in § 438.210(d)(1). </P>
                                    <P>(4) If the MCO or PIHP extends the timeframe in accordance with § 438.210(d)(1), it must—</P>
                                    <P>(i) Give the enrollee written notice of the reason for the decision to extend the timeframe and inform the enrollee of the right to file a grievance if he or she disagrees with that decision; and </P>
                                    <P>(ii) Issue and carry out its determination as expeditiously as the enrollee's health condition requires and no later than the date the extension expires. </P>
                                    <P>(5) For service authorization decisions not reached within the timeframes specified in § 438.210(d) (which constitutes a denial and is thus an adverse action), on the date that the timeframes expire. </P>
                                    <P>(6) For expedited service authorization decisions, within the timeframes specified in § 438.210(d). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.406</SECTNO>
                                    <SUBJECT>Handling of grievances and appeals. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General requirements.</E>
                                         In handling grievances and appeals, each MCO and each PIHP must meet the following requirements: 
                                    </P>
                                    <P>(1) Give enrollees any reasonable assistance in completing forms and taking other procedural steps. This includes, but is not limited to, providing interpreter services and toll-free numbers that have adequate TTY/TTD and interpreter capability. </P>
                                    <P>(2) Acknowledge receipt of each grievance and appeal. </P>
                                    <P>(3) Ensure that the individuals who make decisions on grievances and appeals are individuals— </P>
                                    <P>(i) Who were not involved in any previous level of review or decision-making; and </P>
                                    <P>(ii) Who, if deciding any of the following, are health care professionals who have the appropriate clinical expertise, as determined by the State, in treating the enrollee's condition or disease. </P>
                                    <P>(A) An appeal of a denial that is based on lack of medical necessity. </P>
                                    <P>(B) A grievance regarding denial of expedited resolution of an appeal. </P>
                                    <P>(C) A grievance or appeal that involves clinical issues. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Special requirements for appeals.</E>
                                         The process for appeals must: 
                                    </P>
                                    <P>(1) Provide that oral inquiries seeking to appeal an action are treated as appeals (to establish the earliest possible filing date for the appeal) and must be confirmed in writing, unless the enrollee or the provider requests expedited resolution. </P>
                                    <P>(2) Provide the enrollee a reasonable opportunity to present evidence, and allegations of fact or law, in person as well as in writing. (The MCO or PIHP must inform the enrollee of the limited time available for this in the case of expedited resolution.) </P>
                                    <P>(3) Provide the enrollee and his or her representative opportunity, before and during the appeals process, to examine the enrollee's case file, including medical records, and any other documents and records considered during the appeals process. </P>
                                    <P>(4) Include, as parties to the appeal— </P>
                                    <P>(i) The enrollee and his or her representative; or </P>
                                    <P>(ii) The legal representative of a deceased enrollee's estate. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.408</SECTNO>
                                    <SUBJECT>Resolution and notification: Grievances and appeals. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Basic rule.</E>
                                         The MCO or PIHP must dispose of each grievance and resolve 
                                        <PRTPAGE P="41111"/>
                                        each appeal, and provide notice, as expeditiously as the enrollee's health condition requires, within State-established timeframes that may not exceed the timeframes specified in this section. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Specific timeframes.—</E>
                                         (1) 
                                        <E T="03">Standard disposition of grievances.</E>
                                         For standard disposition of a grievance and notice to the affected parties, the timeframe is established by the State but may not exceed 90 days from the day the MCO or PIHP receives the grievance. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Standard resolution of appeals.</E>
                                         For standard resolution of an appeal and notice to the affected parties, the State must establish a timeframe that is no longer than 45 days from the day the MCO or PIHP receives the appeal. This timeframe may be extended under paragraph (c) of this section. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Expedited resolution of appeals.</E>
                                         For expedited resolution of an appeal and notice to affected parties, the State must establish a timeframe that is no longer than 3 working days after the MCO or PIHP receives the appeal. This timeframe may be extended under paragraph (c) of this section. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Extension of timeframes.</E>
                                        —(1) The MCO or PIHP may extend the timeframes from paragraph (b) of this section by up to 14 calendar days if— 
                                    </P>
                                    <P>(i) The enrollee requests the extension; or </P>
                                    <P>(ii) The MCO or PIHP shows (to the satisfaction of the State agency, upon its request) that there is need for additional information and how the delay is in the enrollee's interest. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Requirements following extension.</E>
                                         If the MCO or PIHP extends the timeframes, it must—for any extension not requested by the enrollee, give the enrollee written notice of the reason for the delay. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Format of notice.—</E>
                                         (1) 
                                        <E T="03">Grievances.</E>
                                         The State must establish the method MCOs and PIHPs will use to notify an enrollee of the disposition of a grievance. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Appeals.</E>
                                         (i) For all appeals, the MCO or PIHP must provide written notice of disposition. 
                                    </P>
                                    <P>(ii) For notice of an expedited resolution, the MCO or PIHP must also make reasonable efforts to provide oral notice. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Content of notice of appeal resolution.</E>
                                         The written notice of the resolution must include the following: 
                                    </P>
                                    <P>(1) The results of the resolution process and the date it was completed. </P>
                                    <P>(2) For appeals not resolved wholly in favor of the enrollees— </P>
                                    <P>(i) The right to request a State fair hearing, and how to do so; </P>
                                    <P>(ii) The right to request to receive benefits while the hearing is pending, and how to make the request; and </P>
                                    <P>(iii) That the enrollee may be held liable for the cost of those benefits if the hearing decision upholds the MCO's or PIHP's action. </P>
                                    <P>
                                        (f) 
                                        <E T="03">Requirements for State fair hearings.—</E>
                                        (1) 
                                        <E T="03">Availability.</E>
                                         The State must permit the enrollee to request a State fair hearing within a reasonable time period specified by the State, but not less than 20 or in excess of 90 days from whichever of the following dates applies— 
                                    </P>
                                    <P>(i) If the State requires exhaustion of the MCO or PIHP level appeal procedures, from the date of the MCO's or PIHP's notice of resolution; or </P>
                                    <P>(ii) If the State does not require exhaustion of the MCO or PIHP level appeal procedures and the enrollee appeals directly to the State for a fair hearing, from the date on the MCO's or PIHP's notice of action. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Parties.</E>
                                         The parties to the State fair hearing include the MCO or PIHP as well as the enrollee and his or her representative or the representative of a deceased enrollee's estate. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.410</SECTNO>
                                    <SUBJECT>Expedited resolution of appeals. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rule.</E>
                                         Each MCO and PIHP must establish and maintain an expedited review process for appeals, when the MCO or PIHP determines (for a request from the enrollee) or the provider indicates (in making the request on the enrollee's behalf or supporting the enrollee's request) that taking the time for a standard resolution could seriously jeopardize the enrollee's life or health or ability to attain, maintain, or regain maximum function. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Punitive action.</E>
                                         The MCO or PIHP must ensure that punitive action is neither taken against a provider who requests an expedited resolution or supports an enrollee's appeal. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Action following denial of a request for expedited resolution.</E>
                                         If the MCO or PIHP denies a request for expedited resolution of an appeal, it must— 
                                    </P>
                                    <P>(1) Transfer the appeal to the timeframe for standard resolution in accordance with § 438.408(b)(2); </P>
                                    <P>(2) Make reasonable efforts to give the enrollee prompt oral notice of the denial, and follow up within two calendar days with a written notice. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.414</SECTNO>
                                    <SUBJECT>Information about the grievance system to providers and subcontractors. </SUBJECT>
                                    <P>The MCO or PIHP must provide the information specified at § 438.10(g)(1) about the grievance system to all providers and subcontractors at the time they enter into a contract. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.416 </SECTNO>
                                    <SUBJECT>Recordkeeping and reporting requirements. </SUBJECT>
                                    <P>The State must require MCOs and PIHPs to maintain records of grievances and appeals and must review the information as part of the State quality strategy. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.420 </SECTNO>
                                    <SUBJECT>Continuation of benefits while the MCO or PIHP appeal and the State fair hearing are pending. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Terminology.</E>
                                         As used in this section, “timely” filing means filing on or before the later of the following: 
                                    </P>
                                    <P>(1) Within ten days of the MCO or PIHP mailing the notice of action. </P>
                                    <P>(2) The intended effective date of the MCO's or PIHP's proposed action. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Continuation of benefits.</E>
                                         The MCO or PIHP must continue the enrollee's benefits if— 
                                    </P>
                                    <P>(1) The enrollee or the provider files the appeal timely; </P>
                                    <P>(2) The appeal involves the termination, suspension, or reduction of a previously authorized course of treatment; </P>
                                    <P>(3) The services were ordered by an authorized provider; </P>
                                    <P>(4) The original period covered by the original authorization has not expired; and </P>
                                    <P>(5) The enrollee requests extension of benefits. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Duration of continued or reinstated benefits.</E>
                                         If, at the enrollee's request, the MCO or PIHP continues or reinstates the enrollee's benefits while the appeal is pending, the benefits must be continued until one of following occurs: 
                                    </P>
                                    <P>(1) The enrollee withdraws the appeal. </P>
                                    <P>(2) Ten days pass after the MCO or PIHP mails the notice, providing the resolution of the appeal against the enrollee, unless the enrollee, within the 10-day timeframe, has requested a State fair hearing with continuation of benefits until a State fair hearing decision is reached. </P>
                                    <P>(3) A State fair hearing Office issues a hearing decision adverse to the enrollee. </P>
                                    <P>(4) The time period or service limits of a previously authorized service has been met. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Enrollee responsibility for services furnished while the appeal is pending.</E>
                                         If the final resolution of the appeal is adverse to the enrollee, that is, upholds the MCO's or PIHP's action, the MCO or PIHP may recover the cost of the services furnished to the enrollee while the appeal is pending, to the extent that they were furnished solely because of the requirements of this section, and in accordance with the policy set forth in § 431.230(b) of this chapter. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <PRTPAGE P="41112"/>
                                    <SECTNO>§ 438.424 </SECTNO>
                                    <SUBJECT>Effectuation of reversed appeal resolutions. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Services not furnished while the appeal is pending.</E>
                                         If the MCO or PIHP, or the State fair hearing officer reverses a decision to deny, limit, or delay services that were not furnished while the appeal was pending, the MCO or PIHP must authorize or provide the disputed services promptly, and as expeditiously as the enrollee's health condition requires. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Services furnished while the appeal is pending.</E>
                                         If the MCO or PIHP, or the State fair hearing officer reverses a decision to deny authorization of services, and the enrollee received the disputed services while the appeal was pending, the MCO or the PIHP or the State must pay for those services, in accordance with State policy and regulations. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart G—[Reserved] </HD>
                            </SUBPART>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart H—Certifications and Program Integrity </HD>
                                <SECTION>
                                    <SECTNO>§ 438.600 </SECTNO>
                                    <SUBJECT>Statutory basis. </SUBJECT>
                                    <P>This subpart is based on sections 1902(a)(4), 1902(a)(19), 1903(m), and 1932(d)(1) of the Act. </P>
                                    <P>(a) Section 1902(a)(4) requires that the State plan provide for methods of administration that the Secretary finds necessary for the proper and efficient operation of the plan. </P>
                                    <P>(b) Section 1902(a)(19) requires that the State plan provide the safeguards necessary to ensure that eligibility is determined and services are provided in a manner consistent with simplicity of administration and the best interests of the recipients. </P>
                                    <P>(c) Section 1903(m) establishes conditions for payments to the State with respect to contracts with MCOs. </P>
                                    <P>(d) Section 1932(d)(1) prohibits MCOs and PCCMs from knowingly having certain types of relationships with individuals excluded under Federal regulations from participating in specified activities, or with affiliates of those individuals. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.602 </SECTNO>
                                    <SUBJECT>Basic rule. </SUBJECT>
                                    <P>As a condition for receiving payment under the Medicaid managed care program, an MCO, PCCM, PIHP, or PAHP must comply with the applicable certification, program integrity and prohibited affiliation requirements of this subpart. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.604 </SECTNO>
                                    <SUBJECT>Data that must be certified. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Data certifications.</E>
                                         When State payments to an MCO or PIHP are based on data submitted by the MCO or PIHP, the State must require certification of the data as provided in § 438.606. The data that must be certified include, but are not limited to, enrollment information, encounter data, and other information required by the State and contained in contracts, proposals, and related documents. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Additional certifications.</E>
                                         Certification is required, as provided in § 438.606, for all documents specified by the State. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.606 </SECTNO>
                                    <SUBJECT>Source, content, and timing of certification. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Source of certification.</E>
                                         For the data specified in § 438.604, the data the MCO or PIHP submits to the State must be certified by one of the following: 
                                    </P>
                                    <P>(1) The MCO's or PIHP's Chief Executive Officer. </P>
                                    <P>(2) The MCO's or PIHP's Chief Financial Officer. </P>
                                    <P>(3) An individual who has delegated authority to sign for, and who reports directly to, the MCO's or PIHP's Chief Executive Officer or Chief Financial Officer. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Content of certification.</E>
                                         The certification must attest, based on best knowledge, information, and belief, as follows: 
                                    </P>
                                    <P>(1) To the accuracy, completeness and truthfulness of the data. </P>
                                    <P>(2) To the accuracy, completeness and truthfulness of the documents specified by the State. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Timing of certification.</E>
                                         The MCO or PIHP must submit the certification concurrently with the certified data. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.608 </SECTNO>
                                    <SUBJECT>Program integrity requirements. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General requirement.</E>
                                         The MCO or PIHP must have administrative and management arrangements or procedures, including a mandatory compliance plan, that are designed to guard against fraud and abuse. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Specific requirements.</E>
                                         The arrangements or procedures must include the following: 
                                    </P>
                                    <P>(1) Written policies, procedures, and standards of conduct that articulate the organization's commitment to comply with all applicable Federal and State standards. </P>
                                    <P>(2) The designation of a compliance officer and a compliance committee that are accountable to senior management. </P>
                                    <P>(3) Effective training and education for the compliance officer and the organization's employees. </P>
                                    <P>(4) Effective lines of communication between the compliance officer and the organization's employees. </P>
                                    <P>(5) Enforcement of standards through well-publicized disciplinary guidelines. </P>
                                    <P>(6) Provision for internal monitoring and auditing. </P>
                                    <P>(7) Provision for prompt response to detected offenses, and for development of corrective action initiatives relating to the MCO's or PIHP's contract. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.610 </SECTNO>
                                    <SUBJECT>Prohibited Affiliations with Individuals Debarred by Federal Agencies. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General requirement.</E>
                                         An MCO, PCCM, PIHP, or PAHP may not knowingly have a relationship of the type described in paragraph (b) of this section with the following: 
                                    </P>
                                    <P>(1) An individual who is debarred, suspended, or otherwise excluded from participating in procurement activities under the Federal Acquisition Regulation or from participating in nonprocurement activities under regulations issued under Executive Order No. 12549 or under guidelines implementing Executive Order No. 12549. </P>
                                    <P>(2) An individual who is an affiliate, as defined in the Federal Acquisition Regulation, of a person described in paragraph (a)(1) of this section. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Specific requirements.</E>
                                         The relationships described in this paragraph are as follow: 
                                    </P>
                                    <P>(1) A director, officer, or partner of the MCO, PCCM, PIHP, or PAHP. </P>
                                    <P>(2) A person with beneficial ownership of five percent or more of the MCO's, PCCM's, PIHP's, or PAHP's equity. </P>
                                    <P>(3) A person with an employment, consulting or other arrangement with the MCO, PCCM, PIHP, or PAHP for the provision of items and services that are significant and material to the MCO's, PCCM's, PIHP's, or PAHP's obligations under its contract with the State. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Effect of Noncompliance.</E>
                                         If a State finds that an MCO, PCCM, PIHP, or PAHP is not in compliance with paragraphs (a) and (b) of this section, the State: 
                                    </P>
                                    <P>(1) Must notify the Secretary of the noncompliance. </P>
                                    <P>(2) May continue an existing agreement with the MCO, PCCM, PIHP, or PAHP unless the Secretary directs otherwise. </P>
                                    <P>(3) May not renew or otherwise extend the duration of an existing agreement with the MCO, PCCM, PIHP, or PAHP unless the Secretary provides to the State and to Congress a written statement describing compelling reasons that exist for renewing or extending the agreement. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Consultation with the Inspector General.</E>
                                         Any action by the Secretary described in paragraphs (c)(2) or (c)(3) of this section is taken in consultation with the Inspector General. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <PRTPAGE P="41113"/>
                                <HD SOURCE="HED">Subpart I—Sanctions </HD>
                                <SECTION>
                                    <SECTNO>§ 438.700 </SECTNO>
                                    <SUBJECT>Basis for imposition of sanctions. </SUBJECT>
                                    <P>(a) Each State that contracts with an MCO must, and each State that contracts with a PCCM may, establish intermediate sanctions, as specified in § 438.702, that it may impose if it makes any of the determinations specified in paragraphs (b) through (d) of this section. The State may base its determinations on findings from onsite surveys, enrollee or other complaints, financial status, or any other source. </P>
                                    <P>(b) A State determines whether an MCO acts or fails to act as follows: </P>
                                    <P>(1) Fails substantially to provide medically necessary services that the MCO is required to provide, under law or under its contract with the State, to an enrollee covered under the contract. </P>
                                    <P>(2) Imposes on enrollees premiums or charges that are in excess of the premiums or charges permitted under the Medicaid program. </P>
                                    <P>(3) Acts to discriminate among enrollees on the basis of their health status or need for health care services. This includes termination of enrollment or refusal to reenroll a recipient, except as permitted under the Medicaid program, or any practice that would reasonably be expected to discourage enrollment by recipients whose medical condition or history indicates probable need for substantial future medical services. </P>
                                    <P>(4) Misrepresents or falsifies information that it furnishes to CMS or to the State. </P>
                                    <P>(5) Misrepresents or falsifies information that it furnishes to an enrollee, potential enrollee, or health care provider. </P>
                                    <P>(6) Fails to comply with the requirements for physician incentive plans, as set forth (for Medicare) in §§ 422.208 and 422.210 of this chapter. </P>
                                    <P>(c) A State determines whether an MCO, PIHP, PAHP or PCCM has distributed directly, or indirectly through any agent or independent contractor, marketing materials that have not been approved by the State or that contain false or materially misleading information. </P>
                                    <P>(d) A State determines whether— </P>
                                    <P>(1) An MCO has violated any of the other requirements of sections1903(m) or 1932 of the Act, and any implementing regulations; </P>
                                    <P>(2) A PCCM has violated any of the other applicable requirements of sections 1932 or 1905(t)(3) of the Act and any implementing regulations; </P>
                                    <P>(3) For any of the violations under paragraphs (d)(1) and (d)(2) of this section, only the sanctions specified in § 438.702, paragraphs (a)(3), (a)(4), and (a)(5) may be imposed.</P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.702 </SECTNO>
                                    <SUBJECT>Types of intermediate sanctions. </SUBJECT>
                                    <P>(a) The types of intermediate sanctions that a State may impose under this subpart include the following: </P>
                                    <P>(1) Civil money penalties in the amounts specified in § 438.704. </P>
                                    <P>(2) Appointment of temporary management for an MCO as provided in § 438.706. </P>
                                    <P>(3) Granting enrollees the right to terminate enrollment without cause and notifying the affected enrollees of their right to disenroll. </P>
                                    <P>(4) Suspension of all new enrollment, including default enrollment, after the effective date of the sanction. </P>
                                    <P>(5) Suspension of payment for recipients enrolled after the effective date of the sanction and until CMS or the State is satisfied that the reason for imposition of the sanction no longer exists and is not likely to recur. </P>
                                    <P>(b) State agencies retain authority to impose additional sanctions under State statutes or State regulations that address areas of noncompliance specified in § 438.700, as well as additional areas of noncompliance. Nothing in this subpart prevents State agencies from exercising that authority. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.704</SECTNO>
                                    <SUBJECT>Amounts of civil money penalties. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rule.</E>
                                         The limit on, or the maximum civil money penalty the State may impose varies depending on the nature of the MCO's or PCCM's action or failure to act, as provided in this section. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Specific limits.</E>
                                         (1) The limit is $25,000 for each determination under the following paragraphs of § 438.700: 
                                    </P>
                                    <P>(i) Paragraph (b)(1) (Failure to provide services). </P>
                                    <P>(ii) Paragraph (b)(5) (Misrepresentation or false statements to enrollees, potential enrollees, or health care providers). </P>
                                    <P>(iii) Paragraph (b)(6) (Failure to comply with physician incentive plan requirements). </P>
                                    <P>(iv) Paragraph (c) (Marketing violations). </P>
                                    <P>(2) The limit is $100,000 for each determination under paragraph (b)(3) (discrimination) or (b)(4) (Misrepresentation or false statements to CMS or the State) of § 438.700. </P>
                                    <P>(3) The limit is $15,000 for each recipient the State determines was not enrolled because of a discriminatory practice under paragraph (b)(3) of § 438.700. (This is subject to the overall limit of $100,000 under paragraph (b)(2) of this section). </P>
                                    <P>
                                        (c) 
                                        <E T="03">Specific amount.</E>
                                         For premiums or charges in excess of the amounts permitted under the Medicaid program, the maximum amount of the penalty is $25,000 or double the amount of the excess charges, whichever is greater. The State must deduct from the penalty the amount of overcharge and return it to the affected enrollees. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.706</SECTNO>
                                    <SUBJECT>Special rules for temporary management. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Optional imposition of sanction.</E>
                                         The State may impose temporary management only if it finds (through onsite survey, enrollee complaints, financial audits, or any other means) that— 
                                    </P>
                                    <P>(1) There is continued egregious behavior by the MCO, including but not limited to behavior that is described in § 438.700, or that is contrary to any requirements of sections 1903(m) and 1932 of the Act; or </P>
                                    <P>(2) There is substantial risk to enrollees' health; or </P>
                                    <P>(3) The sanction is necessary to ensure the health of the MCO's enrollees— </P>
                                    <P>(i) While improvements are made to remedy violations under § 438.700; or </P>
                                    <P>(ii) Until there is an orderly termination or reorganization of the MCO. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Required imposition of sanction.</E>
                                         The State must impose temporary management (regardless of any other sanction that may be imposed) if it finds that an MCO has repeatedly failed to meet substantive requirements in section 1903(m) or section 1932 of the Act, or this subpart. The State must also grant enrollees the right to terminate enrollment without cause, as described in § 438.702(a)(3), and must notify the affected enrollees of their right to terminate enrollment. 
                                    </P>
                                    <P>
                                        (c) 
                                        <E T="03">Hearing.</E>
                                         The State may not delay imposition of temporary management to provide a hearing before imposing this sanction. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Duration of sanction.</E>
                                         The State may not terminate temporary management until it determines that the MCO can ensure that the sanctioned behavior will not recur. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.708</SECTNO>
                                    <SUBJECT>Termination of an MCO or PCCM contract. </SUBJECT>
                                    <P>A State has the authority to terminate an MCO or PCCM contract and enroll that entity's enrollees in other MCOs or PCCMs, or provide their Medicaid benefits through other options included in the State plan, if the State determines that the MCO or PCCM has failed to do either of the following: </P>
                                    <P>(a) Carry out the substantive terms of its contract; or </P>
                                    <P>(b) Meet applicable requirements in sections 1932, 1903(m), and 1905(t) of the Act. </P>
                                </SECTION>
                                <SECTION>
                                    <PRTPAGE P="41114"/>
                                    <SECTNO>§ 438.710</SECTNO>
                                    <SUBJECT>Due process: Notice of sanction and pre-termination hearing. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Notice of sanction.</E>
                                         Except as provided in § 438.706(c), before imposing any of the intermediate sanctions specified in this subpart, the State must give the affected entity timely written notice that explains the following: 
                                    </P>
                                    <P>(1) The basis and nature of the sanction. </P>
                                    <P>(2) Any other due process protections that the State elects to provide. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Pre-termination hearing</E>
                                        — (1) 
                                        <E T="03">General rule.</E>
                                         Before terminating an MCO or PCCM contract under § 438.708, the State must provide the entity a pre-termination hearing. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Procedures.</E>
                                         The State must do the following: 
                                    </P>
                                    <P>(i) Give the MCO or PCCM written notice of its intent to terminate, the reason for termination, and the time and place of the hearing; </P>
                                    <P>(ii) After the hearing, give the entity written notice of the decision affirming or reversing the proposed termination of the contract and, for an affirming decision, the effective date of termination; and </P>
                                    <P>(iii) For an affirming decision, give enrollees of the MCO or PCCM notice of the termination and information, consistent with § 438.10, on their options for receiving Medicaid services following the effective date of termination. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.722</SECTNO>
                                    <SUBJECT>Disenrollment during termination hearing process. </SUBJECT>
                                    <P>After a State notifies an MCO or PCCM that it intends to terminate the contract, the State may do the following: </P>
                                    <P>(a) Give the entity's enrollees written notice of the State's intent to terminate the contract. </P>
                                    <P>(b) Allow enrollees to disenroll immediately without cause. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.724</SECTNO>
                                    <SUBJECT>Notice to CMS. </SUBJECT>
                                    <P>(a) The State must give the CMS Regional Office written notice whenever it imposes or lifts a sanction for one of the violations listed in § 438.700. </P>
                                    <P>(b) The notice must— </P>
                                    <P>(1) Be given no later than 30 days after the State imposes or lifts a sanction; and </P>
                                    <P>(2) Specify the affected MCO, the kind of sanction, and the reason for the State's decision to impose or lift a sanction. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.726</SECTNO>
                                    <SUBJECT>State plan requirement. </SUBJECT>
                                    <P>(a) The State plan must include a plan to monitor for violations that involve the actions and failures to act specified in this part and to implement the provisions of this part. </P>
                                    <P>(b) A contract with an MCO must provide that payments provided for under the contract will be denied for new enrollees when, and for so long as, payment for those enrollees is denied by CMS under section 438.730(e). </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.730</SECTNO>
                                    <SUBJECT>Sanction by CMS: Special rules for MCOs </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Basis for sanction.</E>
                                         (1) A State agency may recommend that CMS impose the denial of payment sanction specified in paragraph (e) of this section on an MCO with a contract under this part if the agency determines that the MCO acts or fails to act as specified in § 438.700(b)(1) through (b)(6). 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Effect of an Agency Determination.</E>
                                         (1) The State agency's determination becomes CMS's determination for purposes of section 1903(m)(5)(A) of the Act unless CMS reverses or modifies it within 15 days. 
                                    </P>
                                    <P>(2) When the agency decides to recommend imposing the sanction described in paragraph (e) of this section, this recommendation becomes CMS's decision, for purposes of section 1903(m)(5)(B)(ii) of the Act, unless CMS rejects this recommendation within 15 days. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Notice of sanction.</E>
                                         If the State agency's determination becomes CMS's determination under section (b)(2), the State agency takes the following actions: 
                                    </P>
                                    <P>(1) Gives the MCO written notice of the nature and basis of the proposed sanction; </P>
                                    <P>(2) Allows the MCO 15 days from the date it receives the notice to provide evidence that it has not acted or failed to act in the manner that is the basis for the recommended sanction; </P>
                                    <P>(3) May extend the initial 15-day period for an additional 15 days if— </P>
                                    <P>(i) the MCO submits a written request that includes a credible explanation of why it needs additional time; </P>
                                    <P>(ii) the request is received by CMS before the end of the initial period; and </P>
                                    <P>(iii) CMS has not determined that the MCO's conduct poses a threat to an enrollee's health or safety. </P>
                                    <P>
                                        (d) 
                                        <E T="03">Informal reconsideration.</E>
                                         (1) If the MCO submits a timely response to the notice of sanction, the State agency— 
                                    </P>
                                    <P>(i) Conducts an informal reconsideration that includes review of the evidence by a State agency official who did not participate in the original recommendation; </P>
                                    <P>(ii) Gives the MCO a concise written decision setting forth the factual and legal basis for the decision; and </P>
                                    <P>(iii) Forwards the decision to CMS. </P>
                                    <P>(2) The agency decision under paragraph (d)(1)(ii) of this section becomes CMS's decision unless CMS reverses or modifies the decision within 15 days from date of receipt by CMS. </P>
                                    <P>(3) If CMS reverses or modifies the State agency decision, the agency sends the MCO a copy of CMS's decision. </P>
                                    <P>
                                        (e) 
                                        <E T="03">Denial of payment.</E>
                                         (1) CMS, based upon the recommendation of the agency, may deny payment to the State for new enrollees of the HMO under section 1903(m)(5)(B)(ii) of the Act in the following situations: 
                                    </P>
                                    <P>(i) If a CMS determination that an MCO has acted or failed to act, as described in paragraphs (b)(1) through (b)(6) of § 438.700, is affirmed on review under paragraph (d) of this section. </P>
                                    <P>(ii) If the CMS determination is not timely contested by the MCO under paragraph (c) of this section. </P>
                                    <P>(2) Under § 438.726(b), CMS's denial of payment for new enrollees automatically results in a denial of agency payments to the HMO for the same enrollees. (A new enrollee is an enrollee that applies for enrollment after the effective date in paragraph (f)(1) of this section.) </P>
                                    <P>
                                        (f) 
                                        <E T="03">Effective date of sanction.</E>
                                         (1) If the MCO does not seek reconsideration, a sanction is effective 15 days after the date the MCO is notified under paragraph (b) of this section of the decision to impose the sanction. 
                                    </P>
                                    <P>(2) If the MCO seeks reconsideration, the following rules apply: </P>
                                    <P>(i) Except as specified in paragraph (d)(2)(ii) of this section, the sanction is effective on the date specified in CMS's reconsideration notice. </P>
                                    <P>(ii) If CMS, in consultation with the State agency, determines that the MCO's conduct poses a serious threat to an enrollee's health or safety, the sanction may be made effective earlier than the date of the agency's reconsideration decision under paragraph (c)(1)(ii) of this section. </P>
                                    <P>
                                        (g) 
                                        <E T="03">CMS's role.</E>
                                         (1) CMS retains the right to independently perform the functions assigned to the State agency under paragraphs (a) through (d) of this section. 
                                    </P>
                                    <P>(2) At the same time that the agency sends notice to the MCO under paragraph (c)(1)(i) of this section, CMS forwards a copy of the notice to the OIG. </P>
                                    <P>(3) CMS conveys the determination described in paragraph (b) of this section to the OIG for consideration of possible imposition of civil money penalties under section 1903(m)(5)(A) of the Act and part 1003 of this title. In accordance with the provisions of part 1003, the OIG may impose civil money penalties on the MCO in addition to, or in place of, the sanctions that may be imposed under this section. </P>
                                </SECTION>
                            </SUBPART>
                            <SUBPART>
                                <PRTPAGE P="41115"/>
                                <HD SOURCE="HED">Subpart J—Conditions for Federal Financial Participation </HD>
                                <SECTION>
                                    <SECTNO>§ 438.802</SECTNO>
                                    <SUBJECT>Basic requirements. </SUBJECT>
                                    <P>FFP is available in expenditures for payments under an MCO contract only for the periods during which the contract— </P>
                                    <P>(a) Meets the requirements of this part; and </P>
                                    <P>(b) Is in effect. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.806</SECTNO>
                                    <SUBJECT>Prior approval. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Comprehensive risk contracts.</E>
                                         FFP is available under a comprehensive risk contract only if— 
                                    </P>
                                    <P>(1) The Regional Office has confirmed that the contractor meets the definition of an MCO or is one of the entities described in paragraphs (b)(2) through (b)(5) of § 438.6; and </P>
                                    <P>(2) The contract meets all the requirements of section 1903(m)(2)(A) of the Act, the applicable requirements of section 1932 of the Act, and the implementing regulations in this part. </P>
                                    <P>
                                        (b) 
                                        <E T="03">MCO contracts.</E>
                                         Prior approval by CMS is a condition for FFP under any MCO contract that extends for less than one full year or that has a value equal to, or greater than, the following threshold amounts: 
                                    </P>
                                    <P>(1) For 1998, the threshold is $1,000,000. </P>
                                    <P>(2) For subsequent years, the amount is increased by the percentage increase in the consumer price index for all urban consumers. </P>
                                    <P>(c) FFP is not available in an MCO contract that does not have prior approval from CMS under paragraph (b) of this section. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.808</SECTNO>
                                    <SUBJECT>Exclusion of entities. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">General rule.</E>
                                         FFP is available in payments under MCO contracts only if the State excludes from the contracts any entities described in paragraph (b) of this section. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Entities that must be excluded.</E>
                                         (1) An entity that could be excluded under section 1128(b)(8) of the Act as being controlled by a sanctioned individual. 
                                    </P>
                                    <P>(2) An entity that has a substantial contractual relationship as defined in § 431.55(h)(3) of this chapter, either directly or indirectly, with an individual convicted of certain crimes as described in section 1128(b)(8)(B) of the Act. </P>
                                    <P>(3) An entity that employs or contracts, directly or indirectly, for the furnishing of health care, utilization review, medical social work, or administrative services, with one of the following: </P>
                                    <P>(i) Any individual or entity excluded from participation in Federal health care programs under either section 1128 or section 1128A of the Act. </P>
                                    <P>(ii) Any entity that would provide those services through an excluded individual or entity. </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.810</SECTNO>
                                    <SUBJECT>Expenditures for enrollment broker services. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Terminology.</E>
                                         As used in this section— 
                                    </P>
                                    <P>
                                        <E T="03">Choice counseling</E>
                                         means activities such as answering questions and providing information (in an unbiased manner) on available MCO, PIHP or PCCM delivery system options, and advising on what factors to consider when choosing among them and in selecting a primary care provider; 
                                    </P>
                                    <P>
                                        <E T="03">Enrollment activities</E>
                                         means activities such as distributing, collecting, and processing enrollment materials and taking enrollments by phone or in person; 
                                    </P>
                                    <P>
                                        <E T="03">Enrollment broker</E>
                                         means an individual or entity that performs choice counseling or enrollment activities, or both, and; 
                                    </P>
                                    <P>
                                        <E T="03">Enrollment services</E>
                                         means choice counseling, or enrollment activities, or both. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Conditions that enrollment brokers must meet.</E>
                                         State expenditures for the use of enrollment brokers are considered necessary for the proper and efficient operation of the State plan and thus eligible for FFP only if the broker and its subcontractors meet the following conditions: 
                                    </P>
                                    <P>
                                        (1) 
                                        <E T="03">Independence.</E>
                                         The broker and its subcontractors are independent of any MCO, PIHP, PAHP, PCCM, or other health care provider in the State in which they provide enrollment services. A broker or subcontractor is not considered “independent” if it— 
                                    </P>
                                    <P>(i) Is an MCO, PIHP, PAHP, PCCM or other health care provider in the State; </P>
                                    <P>(ii) Is owned or controlled by an MCO, PIHP, PAHP, PCCM, or other health care provider in the State; or </P>
                                    <P>(iii) Owns or controls an MCO, PIHP, PAHP, PCCM or other health care provider in the State. </P>
                                    <P>
                                        (2) 
                                        <E T="03">Freedom from conflict of interest.</E>
                                         The broker and its subcontractor are free from conflict of interest. A broker or subcontractor is not considered free from conflict of interest if any person who is the owner, employee, or consultant of the broker or subcontractor or has any contract with them— 
                                    </P>
                                    <P>(i) Has any direct or indirect financial interest in any entity or health care provider that furnishes services in the State in which the broker or subcontractor provides enrollment services; </P>
                                    <P>(ii) Has been excluded from participation under title XVIII or XIX of the Act; </P>
                                    <P>(iii) Has been debarred by any Federal agency; or </P>
                                    <P>(iv) Has been, or is now, subject to civil money penalties under the Act. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Approval.</E>
                                         The initial contract or memorandum of agreement (MOA) for services performed by the broker has been reviewed and approved by CMS. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 438.812</SECTNO>
                                    <SUBJECT>Costs under risk and nonrisk contracts. </SUBJECT>
                                    <P>(a) Under a risk contract, the total amount the State agency pays for carrying out the contract provisions is a medical assistance cost. </P>
                                    <P>(b) Under a nonrisk contract— </P>
                                    <P>(1) The amount the State agency pays for the furnishing of medical services to eligible recipients is a medical assistance cost; and </P>
                                    <P>(2) The amount the State agency pays for the contractor's performance of other functions is an administrative cost.</P>
                                </SECTION>
                            </SUBPART>
                        </PART>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="440">
                        <PART>
                            <HD SOURCE="HED">PART 440—SERVICES: GENERAL PROVISIONS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 440 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Sec. 1102 of the Social Security Act (42 U.S.C. 1302).</P>
                        </AUTH>
                        <P>2. In subpart A, a new § 440.168 is added to read as follows: </P>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="440">
                        <SECTION>
                            <SECTNO>§ 440.168</SECTNO>
                            <SUBJECT>Primary care case management services. </SUBJECT>
                            <P>(a) Primary care case management services means case management related services that— </P>
                            <P>(1) Include location, coordination, and monitoring of primary health care services; and </P>
                            <P>(2) Are provided under a contract between the State and either of the following: </P>
                            <P>(i) A PCCM who is a physician or may, at State option, be a physician assistant, nurse practitioner, or certified nurse-midwife. </P>
                            <P>(ii) A physician group practice, or an entity that employs or arranges with physicians to furnish the services. </P>
                            <P>(b) Primary care case management services may be offered by the State— </P>
                            <P>(1) As a voluntary option under the State plan; or </P>
                            <P>(2) On a mandatory basis under section 1932 (a)(1) of the Act or under section 1915(b) or section 1115 waiver authority.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="447">
                        <PART>
                            <HD SOURCE="HED">PART 447—PAYMENTS FOR SERVICES </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 447 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Sec. 1102 of the Social Security Act (42 U.S.C. 1302). </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="447">
                        <AMDPAR>2. A new § 447.46 is added to read as follows: </AMDPAR>
                        <SECTION>
                            <PRTPAGE P="41116"/>
                            <SECTNO>§ 447.46</SECTNO>
                            <SUBJECT>Timely claims payment by MCOs. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Basis and scope.</E>
                                 This section implements section 1932(f) of the Act by specifying the rules and exceptions for prompt payment of claims by MCOs. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Definitions.</E>
                                 “Claim” and “clean claim” have the meaning given those terms in § 447.45. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Contract requirements.</E>
                                 (1) 
                                <E T="03">Basic rule.</E>
                                 A contract with an MCO must provide that the organization will meet the requirements of §§ 447.45(d)(2) and (d)(3), and abide by the specifications of §§ 447.45(d)(5) and (d)(6). 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Exception.</E>
                                 The MCO and its providers may, by mutual agreement, establish an alternative payment schedule. 
                            </P>
                            <P>
                                (3) 
                                <E T="03">Alternative schedule.</E>
                                 Any alternative schedule must be stipulated in the contract.
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="447">
                        <SECTION>
                            <SECTNO>§ 447.53</SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                        </SECTION>
                        <AMDPAR>3. Section 447.53 is amended as follows: </AMDPAR>
                        <AMDPAR>A. In paragraph (b) introductory text, the parenthetical phrase is removed. </AMDPAR>
                        <AMDPAR>B. Paragraph (b)(6) is removed. </AMDPAR>
                        <AMDPAR>C. A new paragraph (e) is added to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 447.53</SECTNO>
                            <SUBJECT>Applicability; specification; multiple charges. </SUBJECT>
                            <STARS/>
                            <P>(e) No provider may deny services, to an individual who is eligible for the services, on account of the individual's inability to pay the cost sharing.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="447">
                        <SECTION>
                            <SECTNO>§ 447.58</SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                        </SECTION>
                        <AMDPAR>4. In § 447.58, “Except for HMO services subject to the copayment exclusion in § 447.53(b)(6), if” is removed and “If” is added in its place.</AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="447">
                        <AMDPAR>5. A new § 447.60 is added to subpart A to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 447.60</SECTNO>
                            <SUBJECT>Cost-sharing requirements for services furnished by MCOs. </SUBJECT>
                            <P>Contracts with MCOs must provide that any cost-sharing charges the MCO imposes on Medicaid enrollees are in accordance with the requirements set forth in §§ 447.50 and 447.53 through 447.58 for cost-sharing charges imposed by the State agency.</P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="42" PART="447">
                        <SECTION>
                            <SECTNO>§ 447.361</SECTNO>
                            <SUBJECT>[Removed] </SUBJECT>
                        </SECTION>
                        <AMDPAR>6. Section 447.361 is removed.</AMDPAR>
                    </REGTEXT>
                    <SIG>
                        <FP>(Catalog of Federal Domestic Assistance Program No. 93.778, Medical Assistance Program) </FP>
                        <DATED>Dated: April 17, 2002. </DATED>
                        <NAME>Thomas A. Scully, </NAME>
                        <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                        <DATED>Dated: May 14, 2002. </DATED>
                        <NAME>Tommy G. Thompson, </NAME>
                        <TITLE>Secretary. </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 02-14747 Filed 6-13-02; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 4120-01-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="41117"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P">Environmental Protection Agency</AGENCY>
            <CFR>40 CFR Part 63</CFR>
            <TITLE>National Emission Standards for Hazardous Air Pollutants for Secondary Aluminum Production; Final Rule and Proposed Rules</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="41118"/>
                    <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                    <CFR>40 CFR Part 63</CFR>
                    <DEPDOC>[FRL-7225-6]</DEPDOC>
                    <RIN>RIN 2060-AE77</RIN>
                    <SUBJECT>National Emission Standards for Hazardous Air Pollutants for Secondary Aluminum Production</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Environmental Protection Agency (EPA). </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Direct final rule; amendments. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>On March 23, 2000, the EPA issued national emission standards for hazardous air pollutants for secondary aluminum production under section 112 of the Clean Air Act (CAA). This action amends the standards to clarify compliance dates and defer certain early compliance obligations. These changes are being made as part of settlement agreements with industry trade associations, including the Aluminum Association and the American Foundrymen's Society. We are making these amendments by a direct final rule, without prior proposal, because we view these revisions as noncontroversial and anticipate no adverse comments. In addition, because we are publishing a separate proposal which includes substantive clarifications and revisions of the standard, we believe it will prevent confusion and disruption if we defer any compliance obligations until after that separate rulemaking can be completed. </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            This rule is effective on August 13, 2002 without further notice, unless EPA receives adverse written comment by July 15, 2002. If EPA receives such comments, it will publish a timely withdrawal of the direct final rule in the 
                            <E T="04">Federal Register</E>
                             and inform the public that the rule will not take effect.
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            <E T="03">Comments.</E>
                             By U.S. Postal Service, send comments (in duplicate, if possible) to: Air and Radiation Docket and Information Center (6102), Attention Docket No. A-2002-05, U.S. EPA, 1200 Pennsylvania Avenue, NW., Washington, DC 20460. In person or by courier, deliver comments (in duplicate if possible) to: Air and Radiation Docket and Information Center (6102), Attention Docket No. A-2002-05, Room M-1500, U.S. EPA, 401 M Street SW., Washington, DC 20460. The EPA requests that a separate copy also be sent to the contact person listed below (
                            <E T="03">see</E>
                              
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            ). 
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Mr. John Schaefer, U.S. EPA, Minerals and Inorganic Chemicals Group (C504-05), Emission Standards Division, Office of Air Quality Planning and Standards, Research Triangle Park, North Carolina 27711, telephone number (919) 541-0296, facsimile number (919) 541-5600, electronic mail address: 
                            <E T="03">schaefer.john@epa.gov.</E>
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        <E T="03">Comments.</E>
                         We are publishing this direct final rule without prior proposal because we view the amendments as noncontroversial and do not anticipate adverse comments. We consider these changes to be noncontroversial because the only effect is to defer certain early compliance obligations which might otherwise come due before we complete a separate rulemaking concerning substantive clarifications and revisions in the standards. The revisions adopted by this direct final rule retain the overall March 23, 2003 compliance date for existing sources. In the Proposed Rules section of this 
                        <E T="04">Federal Register</E>
                        , we are publishing a separate document that will serve as the proposal to make the amendments to the standards for secondary aluminum production set forth in this direct final rule in the event that timely and significant adverse comments are received. 
                    </P>
                    <P>
                        If we receive any relevant adverse comments on one or more distinct amendments, we will publish a timely withdrawal in the 
                        <E T="04">Federal Register</E>
                         informing the public which provisions will become effective and which provisions are being withdrawn due to adverse comment. We will address all public comments in a subsequent final rule based on the proposed rule. Any of the distinct amendments in today's rule for which we do not receive adverse comment will become effective on the date set out above. We will not institute a second comment period on this direct final rule. Any parties interested in commenting must do so at this time. 
                    </P>
                    <P>
                        <E T="03">Docket.</E>
                         The docket is an organized and complete file of the administrative record compiled by EPA in the development of this direct final rule. The docket is a dynamic file because material is added throughout the rulemaking process. The docketing system is intended to allow members of the public and industries involved to readily identify and locate documents so that they can effectively participate in the rulemaking process. Along with the proposed and promulgated rules and their preambles, the contents of the docket will serve as the record in the case of judicial review. The docket number for this rulemaking is A-2002-05. 
                    </P>
                    <P>
                        <E T="03">Worldwide Web (WWW).</E>
                         In addition to being available in the docket, an electronic copy of this action will also be available through the WWW. Following signature, a copy of this action will be posted on EPA's Technology Transfer Network (TTN) policy and guidance page for newly proposed or promulgated rules: 
                        <E T="03">http://www.epa.gov/ttn/oarpg.</E>
                         The TTN at EPA's web site provides information and technology exchange in various areas of air pollution control. If more information regarding the TTN is needed, call the TTN HELP line at (919) 541-5384. 
                    </P>
                    <P>
                        <E T="03">Regulated Entities.</E>
                         Entities potentially regulated by this action are secondary aluminum production facilities including those collocated at primary aluminum production facilities using clean charge, post-consumer scrap, aluminum scrap, ingots, foundry returns, dross, or molten metal as the raw material, and performing one or more of the following processes: aluminum scrap shredding, scrap drying/ delacquering/ decoating, thermal chip drying, furnace operations (
                        <E T="03">i.e.</E>
                        , melting, holding, refining, fluxing, or alloying), in-line fluxing, or dross cooling. Affected sources at facilities that are major sources of HAP are regulated under the final rule. In addition, emissions of dioxins and furans from affected sources at facilities that are area sources of hazardous air pollutants are also regulated. Regulated categories and entities include: 
                    </P>
                    <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,9,9,r100">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Category </CHED>
                            <CHED H="1">NAICS code </CHED>
                            <CHED H="1">SIC code </CHED>
                            <CHED H="1">Examples of regulated entities </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Industry </ENT>
                            <ENT>331314 </ENT>
                            <ENT>3341 </ENT>
                            <ENT>
                                Secondary smelting and alloying of aluminum facilities. 
                                <LI>Secondary aluminum production facility affected sources that are collocated at:</LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">  </ENT>
                            <ENT>331312 </ENT>
                            <ENT>3334 </ENT>
                            <ENT>Primary aluminum production facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">  </ENT>
                            <ENT>331315 </ENT>
                            <ENT>3353 </ENT>
                            <ENT>Aluminum sheet, plate, and foil manufacturing facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">  </ENT>
                            <ENT>331316 </ENT>
                            <ENT>3354 </ENT>
                            <ENT>Aluminum extruded product manufacturing facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">  </ENT>
                            <ENT>331319 </ENT>
                            <ENT>3355 </ENT>
                            <ENT>Other aluminum rolling and drawing facilities. </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="41119"/>
                            <ENT I="22">  </ENT>
                            <ENT>331521 </ENT>
                            <ENT>3363 </ENT>
                            <ENT>Aluminum die casting facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">  </ENT>
                            <ENT>331524 </ENT>
                            <ENT>3365 </ENT>
                            <ENT>Aluminum foundry facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">State/local/tribal governments </ENT>
                            <ENT>  </ENT>
                            <ENT>  </ENT>
                            <ENT>Not affected. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Federal government </ENT>
                            <ENT>  </ENT>
                            <ENT>  </ENT>
                            <ENT>Not affected. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        This table is not intended to be exhaustive, but rather provides a guide for readers regarding entities likely to be regulated by this action. This table lists the types of entities that the Agency is now aware could potentially be regulated by this action. Other types of entities not listed in the table could also be regulated. To determine whether your facility is regulated by this action, you should carefully examine the applicability criteria in § 63.1500 of the rule. If you have questions regarding the applicability of this action to a particular entity, consult the contact person listed in the preceding 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section. 
                    </P>
                    <P>
                        <E T="03">Judicial Review.</E>
                         Under section 307(b)(1) of the CAA, judicial review of this direct final rule is available only by filing a petition for review in the U.S. Court of Appeals for the District of Columbia Circuit by August 13, 2002. Under section 307(d)(7)(B) of the CAA, only an objection to this direct final rule that was raised with reasonable specificity during the period for public comment can be raised during judicial review. Moreover, under section 307(b)(2) of the CAA, the requirements established by this direct final rule may not be challenged separately in any civil or criminal proceedings brought by the EPA to enforce these requirements. 
                    </P>
                    <P>
                        <E T="03">Outline.</E>
                         The following outline is provided to aid in reading this preamble to this direct final rule. 
                    </P>
                    <EXTRACT>
                        <FP SOURCE="FP-1">I. Background </FP>
                        <FP SOURCE="FP-2">II. Amendments to the NESHAP for Secondary Aluminum Production </FP>
                        <FP SOURCE="FP1-2">A. How are we clarifying the compliance dates? </FP>
                        <FP SOURCE="FP1-2">B. How are we revising the requirements for submission of the OM&amp;M plan? </FP>
                        <FP SOURCE="FP1-2">C. How are we revising the performance test requirements? </FP>
                        <FP SOURCE="FP1-2">D. How are we revising the requirements for the notification of compliance status? </FP>
                        <FP SOURCE="FP-1">III. Administrative Requirements </FP>
                        <FP SOURCE="FP1-2">A. Executive Order 12866, Regulatory Planning and Review </FP>
                        <FP SOURCE="FP1-2">B. Executive Order 13132, Federalism </FP>
                        <FP SOURCE="FP1-2">C. Executive Order 13175, Consultation and Coordination with Indian Tribal Governments </FP>
                        <FP SOURCE="FP1-2">D. Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks </FP>
                        <FP SOURCE="FP1-2">E. Executive Order 13211, Actions Concerning Regulations that Significantly Affect Energy Supply, Distribution, or Use </FP>
                        <FP SOURCE="FP1-2">F. Unfunded Mandates Reform Act of 1995 </FP>
                        <FP SOURCE="FP1-2">
                            G. Regulatory Flexibility Act, as Amended by the Small Business Regulatory Enforcement Act of 1996 (SBREFA), 5 U.S.C. 601 
                            <E T="03">et seq.</E>
                        </FP>
                        <FP SOURCE="FP1-2">H. Paperwork Reduction Act </FP>
                        <FP SOURCE="FP1-2">I. National Technology Transfer and Advancement Act of 1995 </FP>
                        <FP SOURCE="FP1-2">J. Congressional Review Act </FP>
                    </EXTRACT>
                    <EXTRACT>
                        <HD SOURCE="HD1">I. Background </HD>
                        <P>On March 23, 2000, we promulgated the national emission standards for hazardous air pollutants (NESHAP) for secondary aluminum production (63 FR 15710). These standards were established under the authority of section 112(d) of the CAA to reduce emissions of hazardous air pollutants (HAP) from major and area sources. </P>
                        <P>
                            After promulgation of the NESHAP for secondary aluminum production, two petitions for judicial review of the standard were filed in the D.C. Circuit Court of Appeals. The first of these petitions was filed by the American Foundrymen's Society, the North American Die Casting Association, and the Non-Ferrous Founders' Society (
                            <E T="03">American Foundrymen's Society et al.</E>
                             v. 
                            <E T="03">U.S. EPA</E>
                            , Civ. No 00-1208 (D.C. Cir.)). A second petition for judicial review was filed by the Aluminum Association (
                            <E T="03">The Aluminum Association</E>
                             v. 
                            <E T="03">U.S. EPA</E>
                            , No. 00-1211 (D.C. Cir.)). There was no significant overlap in the issues presented by the two petitions, and the cases have never been consolidated. However, we did thereafter enter into separate settlement discussions with the petitioners in each case. 
                        </P>
                        <P>
                            The 
                            <E T="03">Foundrymen's</E>
                             case presented issues concerning the applicability of subpart RRR to aluminum die casters and aluminum foundries which were considered during the initial rulemaking process. Because aluminum die casters and foundries sometimes conduct the same type of operations as other secondary aluminum producers, we originally intended to apply the standards to these facilities, but only in those instances when they conduct such operations. However, representatives of the affected facilities argued that they should not be considered to be secondary aluminum producers and should be wholly exempt from the rule. During rulemaking development, we decided to permit die casters and foundries to melt contaminated internal scrap without being considered to be secondary aluminum producers, but their representatives insisted that too many facilities would still be subject to the standards. At the time of promulgation of the standards, in response to a request by the die casters and foundries, we announced we would withdraw the standards as applied to die casters and foundries and develop separate MACT (maximum available control technology) standards for these facilities. 
                        </P>
                    </EXTRACT>
                      
                    <P>
                        After the 
                        <E T="03">Foundrymen's</E>
                         case was filed, we negotiated an initial settlement agreement in that case which established a process to effectuate our commitment to develop new MACT standards. In that first settlement, EPA agreed that it would stay the current standards for these facilities, collect comprehensive data to support alternate standards, and promulgate alternate standards. We then published a proposal to stay the standards and an advance notice of proposed rulemaking (ANPR) announcing new standards. However, during the process of preparing for information collection, the petitioners concluded that the existing rule was not as sweeping in applicability as they had feared, and the parties then agreed to explore an alternate approach to settlement based on clarifications of the current standards. 
                    </P>
                    <P>
                        We subsequently reached agreement with the 
                        <E T="03">Foundrymen's</E>
                         petitioners on a new settlement. Pursuant to that settlement, we agreed to propose changes in the applicability of the present standards which would permit customer returns without solid paints or coatings to be treated like internal scrap, and would permit facilities operated by the same company at different locations to be aggregated for purposes of determining what is internal scrap. These revisions are addressed in separate proposed rule amendments published elsewhere in today's 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                    <P>
                        In the 
                        <E T="03">Foundrymen's</E>
                         settlement, we also agreed to defer the compliance date for new sources constructed or reconstructed at existing aluminum die casters, aluminum foundries, and aluminum extruders until the compliance date for existing sources, so 
                        <PRTPAGE P="41120"/>
                        that the rulemaking on general applicability issues could be completed first. This is the only element of that settlement which is implemented by this direct final rule. 
                    </P>
                    <P>
                        As required by section 113(g) of the CAA, we provided notice and an opportunity for comment concerning the 
                        <E T="03">Foundrymen's</E>
                         settlement (67 FR 9972, March 5, 2002). We received three adverse comments on the settlement, although none of these comments addressed the only element in the settlement which is implemented by this direct final rule. After reviewing these comments, we decided to proceed with settlement. A copy of these comments and of our responses to them is available in Docket No. A-2002-05 for the separate proposed rule concerning the applicability changes. 
                    </P>
                    <P>
                        In entirely separate discussions, we also agreed on a settlement of the 
                        <E T="03">Aluminum Association</E>
                         case. That settlement requires that we propose a number of substantive clarifications and revisions of the standards. These substantive changes are addressed by the same proposed rule as the applicability changes for aluminum die casters and foundries, which is published elsewhere in today's 
                        <E T="04">Federal Register</E>
                        . The 
                        <E T="03">Aluminum Association</E>
                         settlement also requires that we clarify and simplify the compliance dates for the standards, and defer certain early compliance obligations until after the substantive rulemaking can be completed. These compliance issues are addressed by this direct final rule. 
                    </P>
                    <P>
                        Pursuant to CAA section 113(g), we also provided notice and an opportunity for public comment concerning the 
                        <E T="03">Aluminum Association</E>
                         settlement (67 FR 16374, April 5, 2002). One adverse comment was received on that settlement, although the comment did not address the only element in the settlement which is implemented by this direct final rule. After reviewing the comment, we decided to proceed with settlement. A copy of the comment and of our response to the comment is available in Docket No. A-2002-05 for the separate proposed rule. 
                    </P>
                    <HD SOURCE="HD1">II. Amendments to the NESHAP for Secondary Aluminum Production </HD>
                    <HD SOURCE="HD2">A. How Are We Clarifying the Compliance Dates? </HD>
                    <P>A number of provisions in the existing secondary aluminum rule require compliance on and after the date of a successful initial performance test. Our intent in adopting this general approach was to assure that compliance with the standards would begin as soon as the facility had demonstrated its ability to comply. However, this approach has created confusion concerning the date when compliance will be expected, particularly since an affected facility may be unable to finalize its required operation, maintenance, and monitoring (OM&amp;M) plan until after evaluating the results of the initial performance test. This approach also may discourage facilities from conducting early performance tests, even though such early tests could facilitate identification and correction of problems before the compliance date. </P>
                    <P>The amendments in this direct final rule revise §§ 63.1505, 63.1506, 63.1510, and 63.1511 of 40 CFR part 63, subpart RRR, to specify that existing affected sources must meet the emission limitations and comply with applicable monitoring requirements by the compliance date in § 63.1501. If an initial performance test is required, the owner or operator of an existing affected source must conduct the test by the compliance date for existing affected sources in § 63.1501(a). If an initial performance test is required for a new affected source, the owner or operator must conduct the test within 90 days after the compliance date for new affected sources in § 63.1501(b). </P>
                    <P>The basic compliance dates for existing affected sources and new affected sources established by the current standards are not changed. Section 63.1501(a) of the rule sets the compliance date for existing affected sources at March 24, 2003 (3 years after promulgation). Under § 63.1501(b), the compliance date for a new affected source that began construction or reconstruction after February 11, 1999 is March 24, 2000 or the date of startup, whichever is later. </P>
                    <P>A new paragraph (c) is being added to the compliance dates section (§ 63.1501) that defers the compliance date for a new affected source which is constructed or reconstructed at an existing aluminum die casting facility, aluminum foundry, or aluminum extrusion facility that is subject to the rule. This type of new affected source must comply by March 24, 2003 or upon startup, whichever is later. This deferral of the compliance date until the rest of the facility must comply will eliminate uncertainty and confusion by assuring that the separate rulemaking concerning the applicability criteria for aluminum die casters, foundries, and extruders will be completed before compliance obligations are determined. </P>
                    <HD SOURCE="HD2">B. How Are We Revising the Requirements for Submission of the OM&amp;M Plan? </HD>
                    <P>
                        The provisions in the existing rule pertaining to OM&amp;M plans are ambiguous. Although the preamble to the final rule stated that submission of OM&amp;M plans would be required 6 months before the compliance date, the rule itself did not require this. This direct final rule clarifies the timing for submission of the OM&amp;M plan. In separate proposed rule amendments published elsewhere in today's 
                        <E T="04">Federal Register</E>
                        , we are clarifying the process for submission of OM&amp;M plans to the permitting authority and for adoption of any necessary revisions of such plans. 
                    </P>
                    <P>This action amends the standards to require the owner or operator of an existing affected source to submit the OM&amp;M plan to the responsible permitting authority no later than the compliance date established by § 63.1501(a). For a new affected source, the plant owner or operator must submit the OM&amp;M plan within 90 days after a successful initial performance test or within 90 days after the compliance date established by § 63.1501(b) if no initial performance test is required. </P>
                    <HD SOURCE="HD2">C. How Are We Revising the Performance Test Requirements? </HD>
                    <P>The existing rule contains provisions which have resulted in confusion regarding the timing of any required initial performance test. It was our intention to assure that the performance test would be completed before the compliance date, as indicated by the provisions in the existing rule requiring early compliance following a successful performance test. However, the existing rule also incorporates § 63.7 of the NESHAP General Provisions (40 CFR part 63, subpart A), which provides that performance tests must be completed within 180 days after the compliance date. We intended to adopt the general procedures established by § 63.7(c) for preparation and approval of a site-specific test plan and for actual conduct of the performance test, but not the timetable for the performance test established by § 63.7(a). We are, therefore, adopting amendments to clarify our original intent. </P>
                    <P>
                        The amendments clarify § 63.1511(a) to state that prior to conducting any performance test, the owner or operator must prepare a site-specific plan that meets the requirements of § 63.7(c) and obtain approval of the plan according to the procedures in § 63.7(c). The amendments also clarify § 63.1511(b) to specify that the owner or operator must conduct any performance test required 
                        <PRTPAGE P="41121"/>
                        for an existing affected source no later than the compliance date in § 63.1501(a). If a performance test is required for a new affected source, the owner or operator must conduct the test within 90 days after the compliance date in § 63.1501(b) of the rule. Because this timetable differs from the one established by the General Provisions, we are revising the table in appendix A to the rule, which shows which requirements of the General Provisions apply to affected sources. 
                    </P>
                    <HD SOURCE="HD2">D. How Are We Revising the Requirements for the Notification of Compliance Status? </HD>
                    <P>The amendments clarify the date by which the owner or operator must submit the notification of compliance status for an existing affected source and allow more time for submission of the report for a new affected source. Under § 63.1515(b) of the existing rule, the owner or operator is required to submit the report within 60 days of the compliance date in § 63.1501. The amendments clarify that the report for a plant with an existing affected source is required within 60 days after the compliance date in § 63.1501(a). However, the report for a new affected source is required within 90 days after conducting the initial performance test or within 90 days after the compliance date in § 63.1501(b) if no performance test is required. Because the period of time allowed for new affected sources differs in some instances from period provided by § 63.9(h) of the General Provisions in 40 CFR part 63, subpart A (i.e., up to 60 days of the performance test), we are revising the table in appendix A to the rule, which shows which requirements of the General Provisions apply to affected sources. </P>
                    <HD SOURCE="HD1">III. Administrative Requirements </HD>
                    <HD SOURCE="HD2">A. Executive Order 12866, Regulatory Planning and Review </HD>
                    <P>Under Executive Order 12866 (58 FR 5173, October 4, 1993), the EPA must determine whether the regulatory action is “significant” and therefore subject to Office of Management and Budget (OMB) review and the requirements of the Executive Order. The Executive Order defines “significant regulatory action” as one that is likely to result in standards that may: </P>
                    <P>(1) Have an annual effect on the economy of $100 million or more or adversely affect, in a material way, the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities; </P>
                    <P>(2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; </P>
                    <P>(3) Materially alter the budgetary impact of entitlement, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or </P>
                    <P>(4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in the Executive Order. </P>
                    <P>Pursuant to the terms of Executive Order 12866, it has been determined that these amendments do not constitute a “significant regulatory action” because they do not meet any of the above criteria. Consequently, this action was not submitted to OMB for review under Executive Order 12866. </P>
                    <HD SOURCE="HD2">B. Executive Order 13132: Federalism </HD>
                    <P>Executive Order 13132, entitled “Federalism” (64 FR 43255, August 10, 1999), requires EPA to develop an accountable process to ensure “meaningful and timely input by State and local officials in the development of regulatory policies that have federalism implications.” “Policies that have federalism implications” is defined in the Executive Order to include regulations that have “substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.” </P>
                    <P>These direct final rule amendments do not have federalism implications. They will not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132, because State and local governments do not own or operate any sources that would be subject to these amendments. Thus, the requirements of section 6 of the Executive Order do not apply to this rule. </P>
                    <HD SOURCE="HD2">C. Executive Order 13175, Consultation and Coordination With Indian Tribal Governments </HD>
                    <P>Executive Order 13175, entitled “Consultation and Coordination with Indian Tribal Governments” (65 FR 67249, November 6, 2000), requires EPA to develop an accountable process to ensure “meaningful and timely input by tribal officials in the development of regulatory policies that have tribal implications.” “Policies that have tribal implications” is defined in the Executive Order to include regulations that have “substantial direct effects on one or more Indian tribes, on the relationship between the Federal government and Indian tribes.” </P>
                    <P>These direct final rule amendments do not have tribal implications. They would not have substantial direct effects on tribal governments, on the relationship between the Federal government and Indian tribes, or on the distribution of power and responsibilities between the Federal government and Indian tribes, as specified in Executive Order 13175. No tribal governments own plants subject to the existing rule or proposed amendments. Thus, Executive Order 13175 does not apply to these direct final rule amendments. </P>
                    <HD SOURCE="HD2">D. Executive Order 13045, Protection of Children From Environmental Health Risks and Safety Risks </HD>
                    <P>Executive Order 13045 (62 FR 19885, April 23, 1997) applies to any rule that: (1) Is determined to be “economically significant,” as defined under Executive Order 12866, and (2) concerns an environmental health or safety risk that EPA has reason to believe may have a disproportionate effect on children. If the regulatory action meets both criteria, we must evaluate the environmental health or safety effects of the planned rule on children and explain why the planned regulation is preferable to other potentially effective and reasonably feasible alternatives considered by the Agency. </P>
                    <P>We interpret Executive Order 13045 as applying only to those regulatory actions that are based on health or safety risks, such that the analysis required under section 5-501 of the Executive Order has the potential to influence the regulation. This direct final rule is not subject to Executive Order 13045 because it is based on technology performance and not on health or safety risks. </P>
                    <HD SOURCE="HD2">E. Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy, Supply, Distribution, or Use </HD>
                    <P>This direct final rule is not subject to Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001) because it is not a significant regulatory action under Executive Order 12866. </P>
                    <HD SOURCE="HD2">F. Unfunded Mandates Reform Act of 1995 </HD>
                    <P>
                        Title II of the Unfunded Mandates Reform Act of 1995 (UMRA), Public Law 104-4, establishes requirements for Federal agencies to assess the effects of their regulatory actions on State, local, 
                        <PRTPAGE P="41122"/>
                        and tribal governments and the private sector. Under section 202 of the UMRA, the EPA generally must prepare a written statement, including a cost-benefit analysis, for proposed and final rules with “Federal mandates” that may result in expenditures to State, local, and tribal governments, in the aggregate, or to the private sector, of $100 million or more in any one year. Before promulgating an EPA rule for which a written statement is needed, section 205 of the UMRA generally requires the EPA to identify and consider a reasonable number of regulatory alternatives and adopt the least costly, most cost-effective or least burdensome alternative that achieves the objectives of the rule. The provisions of section 205 do not apply when they are inconsistent with applicable law. Moreover, section 205 allows the EPA to adopt an alternative other than the least costly, most cost-effective, or least burdensome alternative if the Administrator publishes with the final rule an explanation why that alternative was not adopted. Before the EPA establishes any regulatory requirements that may significantly or uniquely affect small governments, including tribal governments, it must have developed under section 203 of the UMRA a small government agency plan. The plan must provide for notifying potentially affected small governments, enabling officials of affected small governments to have meaningful and timely input in the development of EPA regulatory proposals with significant Federal intergovernmental mandates, and informing, educating, and advising small governments on compliance with the regulatory requirements. 
                    </P>
                    <P>The EPA has determined that this direct final rule does not contain a Federal mandate that may result in expenditures of $100 million or more for State, local, and tribal governments, in aggregate, or the private sector in any one year, nor does the rule significantly or uniquely impact small governments, because it contains no requirements that apply to such governments or impose obligations upon them. Thus, the requirements of the UMRA do not apply to this direct final rule. </P>
                    <HD SOURCE="HD2">G. Regulatory Flexibility Act, as Amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), 5 U.S.C. 601 et seq.</HD>
                    <P>The EPA has determined that it is not necessary to prepare a regulatory flexibility analysis in connection with today's direct final rule amendments. Because there is no cost associated with these amendments, the EPA has also determined that today's direct final rule amendments will not have a significant economic impact on a substantial number of small entities. For purposes of assessing the impacts of today's final rule amendments on small entities, small entities are defined as: (1) A small business that has fewer than 750 employees; (2) a small governmental jurisdiction that is a government of a city, county, town, school district or special district with a population of less than 50,000; and (3) a small organization that is any not-for-profit enterprise which is independently owned and operated and is not dominant in its field. </P>
                    <P>After considering the economic impacts of today's direct final rule amendments on small entities, the EPA has concluded that this action will not have a significant impact on a substantial number of small entities. </P>
                    <HD SOURCE="HD2">H. Paperwork Reduction Act </HD>
                    <P>
                        This action does not impose any new information collection burden. Today's action consists primarily of clarifications to the final rule that impose no new information collection requirements on industry or EPA. However, the Office of Management and Budget (OMB) has previously approved the information collection requirements contained in the existing regulations under the provisions of the Paperwork Reduction Act, 44 U.S.C. 3501 et seq. and assigned OMB control No. 2060-0433, EPA ICR No. 1894.01. Copies of the ICR document may be obtained from Susan Auby by mail at the Office of Environmental Information, Collection Strategies Division, U.S. Environmental Protection Agency (2822T), 1200 Pennsylvania Avenue, NW, Washington DC 20460, by email at 
                        <E T="03">auby.susan@epamail.epa.gov,</E>
                         or by calling (202) 566-1672. A copy may also be downloaded from the internet at 
                        <E T="03">http://www.epa.gov/icr.</E>
                         Burden means the total time, effort, or financial resources expended by persons to generate, maintain, retain, or disclose or provided information to or for a Federal agency. This includes the time needed to review instructions; develop, acquire, install, and utilize technology and systems for the purposes of collecting, validating, and verifying information, processing and maintaining information, and disclosing and providing information; adjust the existing ways to comply with any previously applicable instructions and requirements; train personnel to be able to respond to a collection of information; search data sources; complete and review the collection of information; and transmit or otherwise disclose the information.
                    </P>
                    <P>An Agency may not conduct or sponsor, and a person is not required to respond to a collection of information unless it displays a currently valid OMB control number. The OMB control numbers for EPA's regulations are listed in 40 CFR Part 9 and 48 CFR Chapter 15.</P>
                    <HD SOURCE="HD2">I. National Technology Transfer and Advancement Act </HD>
                    <P>Because today's action contains no new test methods, sampling procedures or other technical standards, there is no need to consider the availability of voluntary consensus standards. </P>
                    <HD SOURCE="HD2">J. Congressional Review Act </HD>
                    <P>
                        The Congressional Review Act, 5 U.S.C. 801 
                        <E T="03">et seq.</E>
                        , as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. The EPA will submit a report containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the 
                        <E T="04">Federal Register</E>
                        . This direct final rule is not a “major rule” as defined by 5 U.S.C. 804(2). 
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 40 CFR Part 63 </HD>
                        <P>Environmental protection, Administrative practice and procedure, Air pollution control, Hazardous substances, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Dated: May 31, 2002. </DATED>
                        <NAME>Christine Todd Whitman, </NAME>
                        <TITLE>Administrator.</TITLE>
                    </SIG>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>For the reasons stated in the preamble, title 40, chapter I, part 63 of the Code of Federal Regulations is amended as follows: </AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 63—[AMENDED] </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 63 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                42 U.S.C. 7401 
                                <E T="03">et seq.</E>
                            </P>
                        </AUTH>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <SUBPART>
                            <HD SOURCE="HED">Subpart RRR—[AMENDED] </HD>
                        </SUBPART>
                        <AMDPAR>2. Section 63.1501 is revised to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.1501 </SECTNO>
                            <SUBJECT>Dates. </SUBJECT>
                            <P>
                                (a) The owner or operator of an existing affected source must comply with the requirements of this subpart by March 24, 2003. 
                                <PRTPAGE P="41123"/>
                            </P>
                            <P>(b) Except as provided in paragraph (c) of this section, the owner or operator of a new affected source that commences construction or reconstruction after February 11, 1999 must comply with the requirements of this subpart by March 24, 2000 or upon startup, whichever is later. </P>
                            <P>(c) The owner or operator of any affected source which is constructed or reconstructed at any existing aluminum die casting facility, aluminum foundry, or aluminum extrusion facility which otherwise meets the applicability criteria set forth in § 63.1500 must comply with the requirements of this subpart by March 24, 2003 or upon startup, whichever is later. </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>3. Section 63.1505 is amended by: </AMDPAR>
                        <AMDPAR>a. Revising the introductory text of paragraphs (b), (c), (d), and (e); </AMDPAR>
                        <AMDPAR>b. Revising paragraph (f)(2); and </AMDPAR>
                        <AMDPAR>c. Revising the introductory text of paragraphs (g), (h), and (k). </AMDPAR>
                        <P>The revisions read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 63.1505</SECTNO>
                            <SUBJECT>Emission standards for affected sources and emission units. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Aluminum scrap shredder.</E>
                                 On and after the compliance date established by § 63.1501, the owner or operator of an aluminum scrap shredder at a secondary aluminum production facility that is a major source must not discharge or cause to be discharged to the atmosphere: 
                            </P>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Thermal chip dryer.</E>
                                 On and after the compliance date established by § 63.1501, the owner or operator of a thermal chip dryer must not discharge or cause to be discharged to the atmosphere emissions in excess of: 
                            </P>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Scrap dryer/delacquering kiln/decoating kiln.</E>
                                 On and after the compliance date established by § 63.1501: 
                            </P>
                            <STARS/>
                            <P>
                                (e) 
                                <E T="03">Scrap dryer/delacquering kiln/decoating kiln: alternative limits.</E>
                                 The owner or operator of a scrap dryer/ delacquering kiln/decoating kiln may choose to comply with the emission limits in this paragraph as an alternative to the limits in paragraph (d) of this section if the scrap dryer/delacquering kiln/decoating kiln is equipped with an afterburner having a design residence time of at least 1 second and the afterburner is operated at a temperature of at least 750 °C (1400 °F) at all times. On and after the compliance date established by § 63.1501: 
                            </P>
                            <STARS/>
                            <P>
                                (f) 
                                <E T="03">Sweat furnace.</E>
                                 * * * 
                            </P>
                            <P>
                                (2) On and after the compliance date established by § 63.1501, the owner or operator of a sweat furnace at a secondary aluminum production facility that is a major or area source must not discharge or cause to be discharged to the atmosphere emissions in excess of 0.80 nanogram (ng) of D/F TEQ per dscm (3.5 × 10
                                <E T="51">−10</E>
                                 gr per dscf) at 11 percent oxygen (O
                                <E T="52">2</E>
                                ). 
                            </P>
                            <P>
                                (g) 
                                <E T="03">Dross-only furnace.</E>
                                 On and after the compliance date established by § 63.1501, the owner or operator of a dross-only furnace at a secondary aluminum production facility that is a major source must not discharge or cause to be discharged to the atmosphere: 
                            </P>
                            <STARS/>
                            <P>
                                (h) 
                                <E T="03">Rotary dross cooler.</E>
                                 On and after the compliance date established by § 63.1501, the owner or operator of a rotary dross cooler at a secondary aluminum production facility that is a major source must not discharge or cause to be discharged to the atmosphere: 
                            </P>
                            <STARS/>
                            <P>
                                (k) 
                                <E T="03">Secondary aluminum processing unit.</E>
                                 On and after the compliance date established by § 63.1501, the owner or operator must comply with the emission limits calculated using the equations for PM and HCl in paragraphs (k)(1) and (2) of this section for each secondary aluminum processing unit at a secondary aluminum production facility that is a major source. The owner or operator must comply with the emission limit calculated using the equation for D/F in paragraph (k)(3) of this section for each secondary aluminum processing unit at a secondary aluminum production facility that is a major or area source. 
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>4. Section 63.1506 is amended by revising paragraph (a)(1) to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.1506</SECTNO>
                            <SUBJECT>Operating requirements. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Summary.</E>
                                 (1) On and after the compliance date established by § 63.1501, the owner or operator must operate all new and existing affected sources and control equipment according to the requirements in this section. 
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>5. Section 63.1510 is amended by revising paragraphs (a) and </AMDPAR>
                        <P>(b) introductory text to read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 63.1510</SECTNO>
                            <SUBJECT>Monitoring requirements. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Summary.</E>
                                 On and after the compliance date established by § 63.1501, the owner or operator of a new or existing affected source or emission unit must monitor all control equipment and processes according to the requirements in this section. Monitoring requirements for each type of affected source and emission unit are summarized in Table 3 to this subpart. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Operation, maintenance, and monitoring (OM&amp;M) plan.</E>
                                 The owner or operator must prepare and implement for each new or existing affected source and emission unit, a written operation, maintenance, and monitoring (OM&amp;M) plan. The owner or operator of an existing affected source must submit the OM&amp;M plan to the responsible permitting authority no later than the compliance date established by § 63.1501(a). The owner or operator of any new affected source must submit the OM&amp;M plan to the responsible permitting authority within 90 days after a successful initial performance test under § 63.1511(b), or within 90 days after the compliance date established by § 63.1501(b) if no initial performance test is required. Each plan must contain the following information: 
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>6. Section 63.1511 is amended by revising paragraphs (a) and (b) introductory text to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.1511</SECTNO>
                            <SUBJECT>Performance test/compliance demonstration general requirements. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Site-specific test plan.</E>
                                 Prior to conducting any performance test required by this subpart, the owner or operator must prepare a site-specific test plan which satisfies all of the requirements, and must obtain approval of the plan pursuant to the procedures, set forth in § 63.7(c) in subpart A of this part. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Initial performance test.</E>
                                 Following approval of the site-specific test plan, the owner or operator must demonstrate initial compliance with each applicable emission, equipment, work practice, or operational standard for each affected source and emission unit, and report the results in the notification of compliance status report as described in § 63.1515(b). The owner or operator of any existing affected source for which an initial performance test is required to demonstrate compliance must conduct this initial performance test no later than the date for compliance established by § 63.1501(a). The owner or operator of any new affected source for which an initial performance test is required must conduct this initial performance test within 90 days after the date for compliance established by § 63.1501(b). Except for the date by which the performance test must be conducted, the owner or operator must conduct each performance test in accordance with the 
                                <PRTPAGE P="41124"/>
                                requirements and procedures set forth in § 63.7(c). Owners or operators of affected sources located at facilities which are area sources are subject only to those performance testing requirements pertaining to D/F. Owners or operators of sweat furnaces meeting the specifications of § 63.1505(f)(1) are not required to conduct a performance test. 
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>7. Section 63.1515 is amended by removing the first sentence in the introductory text of paragraph (b) and adding, in its place, two new sentences to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 63.1515</SECTNO>
                            <SUBJECT>Notifications. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Notification of compliance status report.</E>
                                 Each owner or operator of an existing affected source must submit a notification of compliance status report within 60 days after the compliance date established by § 63.1501(a). Each owner or operator of a new affected source must submit a notification of compliance status report within 90 days after conducting the initial performance test required by § 63.1511(b), or within 90 days after the compliance date established by § 63.1501(b) if no initial performance test is required. * * * 
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="40" PART="63">
                        <AMDPAR>8. Appendix A to subpart RRR is amended by revising the entries for § 63.7(a)-(h) and § 63.9(h)(1)-(3) to read as follows: </AMDPAR>
                        <GPOTABLE COLS="4" OPTS="L1,i1" CDEF="s50,r50,r50,r50">
                            <TTITLE>Appendix A to Subpart RRR of Part 63.—General Provisions Applicability to Subpart RRR </TTITLE>
                            <BOXHD>
                                <CHED H="1">Citation </CHED>
                                <CHED H="1">Requirement </CHED>
                                <CHED H="1">Applies to RRR </CHED>
                                <CHED H="1">Comment </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="22">  </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.7(a)-(h)</ENT>
                                <ENT>Performance Test Requirements-Applicability and Dates</ENT>
                                <ENT>Yes </ENT>
                                <ENT>Except § 63.1511 establishes dates for initial performance tests. </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22">  </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">§ 63.9(h)(1)-(3) </ENT>
                                <ENT>Notification of Compliance Status</ENT>
                                <ENT>Yes </ENT>
                                <ENT>Except § 63.1515 establishes dates for notification of compliance status reports. </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="22">  </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                        </GPOTABLE>
                    </REGTEXT>
                </SUPLINF>
                <FRDOC>[FR Doc. 02-14625 Filed 6-13-02; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 6560-50-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June, 14, 2002</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="41125"/>
                    <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                    <CFR>40 CFR Part 63 </CFR>
                    <DEPDOC>[FRL-7225-5] </DEPDOC>
                    <RIN>RIN 2060-AE77 </RIN>
                    <SUBJECT>National Emission Standards for Hazardous Air Pollutants for Secondary Aluminum Production </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Environmental Protection Agency (EPA). </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule; amendments. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            On March 23, 2000, the EPA issued national emission standards for hazardous air pollutants for secondary aluminum production facilities under section 112 of the Clean Air Act (CAA). This proposed rule would amend the applicability provisions for aluminum die casters, foundries, and extruders. This proposal would also add new provisions governing control of commonly-ducted units; revise the procedures for adoption of operation, maintenance, and monitoring plans; revise the criteria concerning testing of representative emission units; amend the standard for unvented in-line flux boxes; and clarify the control requirements for sidewell furnaces. These changes are being proposed pursuant to settlement agreements in two cases seeking judicial review of the secondary aluminum standards. Elsewhere in today's 
                            <E T="04">Federal Register</E>
                            , we are publishing a separate direct final rule and accompanying parallel proposal to clarify compliance dates and defer certain early compliance obligations which might otherwise come due while we are completing this rulemaking. 
                        </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            <E T="03">Comments.</E>
                             Submit comments on or before August 13, 2002. 
                        </P>
                        <P>
                            <E T="03">Public Hearing.</E>
                             If anyone contacts the EPA requesting to speak at a public hearing by June 28, 2002, a public hearing will be held on July 12, 2002. 
                        </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            <E T="03">Comments.</E>
                             By U.S. Postal Service, send comments (in duplicate, if possible) to: Air and Radiation Docket and Information Center (6102), Attention Docket No. A-2002-06, U.S. EPA, 1200 Pennsylvania Avenue, NW., Washington, DC 20460. In person or by courier, deliver comments (in duplicate, if possible) to: Air and Radiation Docket and Information Center (6102), Attention Docket No. A-2002-06, Room M-1500, U.S. EPA, 401 M Street, SW., Washington, DC 20460. We request a separate copy of each public comment be sent to the contact person listed below (see 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            ). 
                        </P>
                        <P>
                            <E T="03">Public Hearing.</E>
                             If a public hearing is held, it will be held at the EPA Office of Administration Auditorium, Research Triangle Park, North Carolina or an alternative site nearby beginning at 10 a.m. Persons interested in attending the hearing or wishing to present oral testimony should notify Tanya Medley, U.S. EPA, Research Triangle Park, NC 27711, telephone (919) 541-5422. 
                        </P>
                        <P>
                            <E T="03">Docket.</E>
                             Docket No. A-2002-06 contains supporting information used in developing the proposed amendments. The docket is located at the U.S. EPA, 401 M Street, SW, Washington, DC 20460 in room M-1500, Waterside Mall (ground floor), and may be inspected from 8:30 a.m. to 5:30 p.m., Monday through Friday, excluding legal holidays. 
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Mr. John Schaefer, U.S. EPA, Minerals and Inorganic Chemicals Group, Emission Standards Division (Mail Code C504-05), Office of Air Quality Planning and Standards, Research Triangle Park, NC 27711, telephone number (919) 541-0296, electronic mail address, 
                            <E T="03">schaefer.john@epa.gov.</E>
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        <E T="03">Comments.</E>
                         Comments and data may be submitted by electronic mail (e-mail) to 
                        <E T="03">air-and-r-docket@epa.gov.</E>
                         Electronic comments must be submitted as an ASCII file to avoid the use of special characters and encryption problems and will also be accepted on disks in WordPerfect ® file format. All comments and data submitted in electronic form must note the docket number: A-2002-06. No confidential business information (CBI) should be submitted by e-mail. Electronic comments may be filed online at many Federal Depository Libraries.
                    </P>
                    <P>Commenters wishing to submit proprietary information for consideration must clearly distinguish such information from other comments and label it as CBI. Send submissions containing such proprietary information directly to the following address, and not to the public docket, to ensure that proprietary information is not inadvertently placed in the docket: Roberto Morales, U.S. EPA, OAQPS Document Control Officer (C404-02), Research Triangle Park, NC 27711, Attn: John Schaefer. The EPA will disclose information identified as CBI only to the extent allowed by the procedures set forth in 40 CFR part 2. If no claim of confidentiality accompanies a submission when it is received by EPA, the information may be made available without further notice to the public. </P>
                    <P>
                        <E T="03">Docket.</E>
                         The docket is an organized and complete file of the administrative record compiled by EPA in the development of the proposed rule amendments. The docket is a dynamic file because information is added throughout the rulemaking process. The docketing system is intended to allow members of the public and industries involved to readily identify and locate documents so they can effectively participate in the rulemaking process. Along with the proposed and promulgated standards and their preambles, the contents of the docket will serve as the record in the case of judicial review. (See section 307(d)(7)(A) of the CAA.) The regulatory text and other materials related to this rulemaking are available for review in the docket or copies may be mailed on request from the Air Docket by calling (202) 260-7548. A reasonable fee may be charged for copying docket materials. 
                    </P>
                    <P>
                        <E T="03">Worldwide Web (WWW).</E>
                         In addition to being available in the docket, an electronic copy of today's proposal will also be available on the WWW through the Technology Transfer Network (TTN). Following signature, a copy of these actions will be posted on the TTN's policy and guidance page for newly proposed rules at 
                        <E T="03">http://www.epa.gov/ttn/oarpg.</E>
                         The TTN provides information and technology exchange in various areas of air pollution control. If more information regarding the TTN is needed, call the TTN HELP line at (919) 541-5384. 
                    </P>
                    <P>
                        <E T="03">Regulated Entities.</E>
                         The proposed amendments would change the applicability provisions of the NESHAP for three types of facilities: aluminum extruded product manufacturing facilities (NAICS 331316/SIC 3354), aluminum die casting facilities (NAICS 331521/SIC 3363), and aluminum foundry facilities (NAICS 331524/SIC 3365). Consequently, categories and entities potentially regulated by this proposed action include: 
                    </P>
                    <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,10,10,r150">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Category </CHED>
                            <CHED H="1">NAICS code </CHED>
                            <CHED H="1">SIC code </CHED>
                            <CHED H="1">Examples of regulated entities </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Industry </ENT>
                            <ENT>331314 </ENT>
                            <ENT>3341 </ENT>
                            <ENT>Secondary smelting and alloying of aluminum facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT> </ENT>
                            <ENT> </ENT>
                            <ENT>Secondary aluminum production facility affected sources that are collocated at: </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>331312</ENT>
                            <ENT>3334</ENT>
                            <ENT>Primary aluminum production facilities. </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="41126"/>
                            <ENT I="22"> </ENT>
                            <ENT>331315</ENT>
                            <ENT>3353</ENT>
                            <ENT>Aluminum sheet, plate, and foil manufacturing facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>331319</ENT>
                            <ENT>3355</ENT>
                            <ENT>Other aluminum rolling and drawing facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>331521</ENT>
                            <ENT>3363</ENT>
                            <ENT>Aluminum die casting facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>331524</ENT>
                            <ENT>3365</ENT>
                            <ENT>Aluminum foundry facilities. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        This table is not intended to be exhaustive, but rather provides a guide for readers regarding entities likely to be regulated by this action. To determine whether your facility is regulated by this action, you should examine the applicability criteria in § 63.1500 of the national emission standards for secondary aluminum production. If you have any questions regarding the applicability of this action to a particular entity, consult the person listed in the preceding 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section. 
                    </P>
                    <P>
                        <E T="03">Outline.</E>
                         The information presented in this preamble is organized as follows:
                    </P>
                    <EXTRACT>
                        <FP SOURCE="FP-2">I. Background </FP>
                        <FP SOURCE="FP-2">II. Summary of the Proposed Amendments </FP>
                        <FP SOURCE="FP1-2">A. How are we proposing to amend the applicability provisions? </FP>
                        <FP SOURCE="FP1-2">B. What amendments are we proposing concerning control of commonly-ducted units? </FP>
                        <FP SOURCE="FP1-2">C. How are we proposing to amend the procedures for adoption of an operation, maintenance, and monitoring plan? </FP>
                        <FP SOURCE="FP1-2">D. How are we proposing to amend the provisions concerning testing of representative emission units? </FP>
                        <FP SOURCE="FP1-2">E. How are we proposing to amend the standard for unvented in-line flux boxes? </FP>
                        <FP SOURCE="FP1-2">F. How are we proposing to clarify the control requirements for sidewell furnaces? </FP>
                        <FP SOURCE="FP1-2">G. What other amendments are we proposing? </FP>
                        <FP SOURCE="FP-2">III. Administrative Requirements </FP>
                        <FP SOURCE="FP1-2">A. Executive Order 12866, Regulatory Planning and Review </FP>
                        <FP SOURCE="FP1-2">B. Executive Order 13132, Federalism </FP>
                        <FP SOURCE="FP1-2">C. Executive Order 13175, Consultation and Coordination with Indian Tribal Governments </FP>
                        <FP SOURCE="FP1-2">D. Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks </FP>
                        <FP SOURCE="FP1-2">E. Unfunded Mandates Reform Act of 1995 </FP>
                        <FP SOURCE="FP1-2">
                            F. Regulatory Flexibility Act (RFA), as Amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), 5 U.S.C. 
                            <E T="03">et seq.</E>
                        </FP>
                        <FP SOURCE="FP1-2">G. Paperwork Reduction Act </FP>
                        <FP SOURCE="FP1-2">H. National Technology Transfer and Advancement Act </FP>
                        <FP SOURCE="FP1-2">I. Executive Order 13211, Actions Concerning Regulations that Significantly Affect Energy Supply, Distribution, or Use </FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. Background </HD>
                    <P>On March 23, 2000 (63 FR 15690), we promulgated the national emission standards for hazardous air pollutants (NESHAP) for secondary aluminum production (40 CFR part 63, subpart RRR). These standards were established under the authority of section 112(d) of the CAA to reduce emissions of hazardous air pollutants (HAP) from major and area sources.</P>
                    <P>
                        After promulgation of the NESHAP for secondary aluminum production, two petitions for judicial review of the standards were filed in the D.C. Circuit Court of Appeals. The first of these petitions was filed by the American Foundrymen's Society, the North American Die Casting Association, and the Non-Ferrous Founders' Society (
                        <E T="03">American Foundrymen's Society et al.</E>
                         v. 
                        <E T="03">U.S. EPA,</E>
                         Civ. No 00-1208 (D.C. Cir.)). A second petition for judicial review was filed by the Aluminum Association (
                        <E T="03">The Aluminum Association</E>
                         v. 
                        <E T="03">U.S. EPA,</E>
                         No. 00-1211 (D.C. Cir.)). There was no significant overlap in the issues presented by the two petitions, and the cases have never been consolidated. However, we did thereafter enter into separate settlement discussions with the petitioners in each case. 
                    </P>
                    <P>
                        The 
                        <E T="03">Foundrymen's</E>
                         case presented issues concerning the applicability of subpart RRR to aluminum die casters and aluminum foundries which were considered during the initial rulemaking development. Because aluminum die casters and foundries sometimes conduct the same type of operations as other secondary aluminum producers, we originally intended to apply the standards to these facilities, but only in those instances where they conduct such operations. However, representatives of the affected facilities argued that they should not be considered to be secondary aluminum producers and should be wholly exempt from the NESHAP. During the rulemaking development, we decided to permit die casters and foundries to melt contaminated internal scrap without being considered to be secondary aluminum producers, but their representatives insisted that too many facilities would still be subject to the NESHAP. At the time of promulgation of the standards, in response to a request by the die casters and foundries, we announced we would withdraw the standards as applied to die casters and foundries and develop separate maximum achievable control technology (MACT) standards for these facilities. 
                    </P>
                    <P>
                        After the 
                        <E T="03">Foundrymen's</E>
                         case was filed, we negotiated an initial settlement agreement in that case which established a process to effectuate our commitment to develop new MACT standards. In that first settlement, EPA agreed that it would stay the current standards for these facilities, collect comprehensive data to support alternate standards, and promulgate alternate standards. We then published a proposal to stay the standards for these facilities (65 FR 55491, September 14, 2000) and an advanced notice of proposed rulemaking (ANPR) announcing new standards for these facilities (65 FR 55489, September 14, 2000). 
                    </P>
                    <P>
                        During the subsequent process of preparing for information collection, the petitioners concluded that the present rule was not as sweeping in applicability as they had feared, and the parties then agreed to explore an alternate approach to settlement based on clarifications of the current standards. We subsequently reached agreement with the 
                        <E T="03">Foundrymen's</E>
                         petitioners on a new settlement which entirely supplants the prior settlement. Accordingly, we are publishing elsewhere in today's 
                        <E T="04">Federal Register</E>
                         a notice withdrawing the proposed stay of the present standards for aluminum die casters and foundries, and announcing that we are taking no further action on new standards for these facilities. 
                    </P>
                    <P>In the new settlement, we agreed to propose some changes in the applicability provisions of the present standards concerning aluminum die casters and foundries. These changes include permitting customer returns without solid paints or coatings to be treated like internal scrap, and permitting facilities operated by the same company at different locations to be aggregated for purposes of determining what is internal scrap. These revisions of the applicability criteria are included in this proposed rule. </P>
                    <P>
                        In the 
                        <E T="03">Foundrymen's</E>
                         settlement, we also agreed to defer the compliance date for new sources constructed or reconstructed at existing aluminum die casters, foundries, and extruders until the compliance date for existing sources, so that the rulemaking on general applicability issues could be completed first. That element of the 
                        <PRTPAGE P="41127"/>
                        <E T="03">Foundrymen's</E>
                         settlement is incorporated in a direct final rule and parallel proposal published elsewhere in today's 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                    <P>
                        As required by section 113(g) of the CAA, we provided notice and an opportunity for comment concerning the 
                        <E T="03">Foundrymen's</E>
                         settlement (67 FR 9972, March 5, 2002). We received three adverse comments on the settlement. After reviewing these comments, we decided to proceed with settlement. A copy of these comments and of our responses to them is available in the docket for this proposed rule. 
                    </P>
                    <P>
                        In entirely separate discussions, we also agreed on a settlement of the 
                        <E T="03">Aluminum Association</E>
                         case. That settlement requires that we propose a number of substantive clarifications and revisions of the standards which are also addressed by this proposed rule. The 
                        <E T="03">Aluminum Association</E>
                         settlement also requires that we clarify and simplify the compliance dates for the standards, and defer certain early compliance obligations which might otherwise come due during the rulemaking process. These compliance issues are also addressed in the direct final rule and parallel proposal published elsewhere in today's 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                    <P>
                        Pursuant to CAA section 113(g), we also provided notice and an opportunity for public comment concerning the 
                        <E T="03">Aluminum Association</E>
                         settlement (67 FR 16374, April 5, 2002). One adverse comment was received on that settlement, although the comment did not address the only element in the settlement which is implemented by this direct final rule. After reviewing the comment, we decided to proceed with settlement. A copy of the comment and of our response to the comment is available in Docket No. A-2002-06 for the separate proposed rule. 
                    </P>
                    <HD SOURCE="HD1">II. Summary of the Proposed Amendments </HD>
                    <HD SOURCE="HD2">A. How Are We Proposing To Amend the Applicability Provisions? </HD>
                    <P>We originally intended to regulate aluminum die casting facilities, aluminum foundries, and aluminum extruders under subpart RRR only when they engage in the same types of operations as other secondary aluminum producers. We decided during rulemaking development that such facilities should be permitted to melt their own internally-generated scrap without being automatically treated the same as secondary aluminum producers, who typically process contaminated aluminum scrap obtained from other sources. Thus, § 63.1500(d) in the current standards exempts such facilities if:</P>
                    <P>• The facility does not melt any materials other than clean charge and materials generated within the facility; and </P>
                    <P>• The facility does not operate a thermal chip dryer, sweat furnace, or scrap dryer/delacquering kiln/decoating kiln. </P>
                    <P>However, it became apparent during discussions with representatives of these facilities that some aluminum die casting facilities that do not otherwise engage in secondary aluminum operations might fall within the rule solely because they melt certain materials which do not fit clearly within the phrase “materials generated within the facility.” In particular, some facilities routinely have defective or incorrect aluminum castings returned by customers and then remelt them. In addition, some companies conduct operations at multiple locations and may melt scrap initially generated at one location at a different location. </P>
                    <P>To address these issues, we agreed to propose new applicability language which permits aluminum die casters, foundries, and extruders to melt customer returns which contain no paint or other solid coatings without thereby becoming subject to the standards. We also agreed to propose a new definition of internal scrap which includes all scrap originating from aluminum castings or extrusions that remains at all times within the control of the company that produced the castings or extrusions. We do not regard either of these changes in the applicability language as materially altering our original intent to only cover those aluminum die casters, foundries, and extruders who conduct secondary aluminum operations. Under the language we are proposing, customer returns would not qualify if they have been painted or are contaminated with other solid coatings because these castings would normally require prior cleaning to avoid excess emissions. Moreover, scrap obtained from an external source does not qualify unless it fits within the definition of clean charge. </P>
                    <P>We are proposing changes in the existing definitions of “secondary aluminum production facility,” “clean charge,” “internal runaround” (now called “runaround scrap”), and “thermal chip dryer,” as well as adding new definitions of “customer returns” and “internal scrap.” In the aggregate, these revisions clarify the circumstances when aluminum die casters, foundries, and extruders would be considered to be secondary aluminum production facilities and, thus, within the applicability of the rule. </P>
                    <P>We are also proposing to add a new section to the general applicability provisions which permits aluminum die casters, foundries, and extruders which are area sources to operate thermal chip dryers subject to the requirements of the rule without automatically subjecting their furnace operations to the rule. We agreed to propose this change to eliminate an incentive which might otherwise exist for small facilities, which are otherwise outside the applicability of the rule, to discontinue their use of chip dryers. As long as such chip dryers are operated in conformity with the rule, we think their use will promote safety and lower emissions at some small operations. </P>
                    <P>We are mindful that some may question why contaminated internal scrap generated by aluminum die casters, foundries, and extruders should be treated differently than external scrap with similar contamination levels which is processed by the secondary aluminum industry. We stress that the decision we made during the original secondary aluminum rulemaking process to make this distinction was based on the qualitative differences in the operations being undertaken by the facilities in question, rather than on any conclusions regarding the likely magnitude of emissions from such operations. Moreover, we think that the additional revisions and clarifications of applicability for aluminum die casters, foundries, and extruders which we have agreed to make are reasonable clarifications and fully consistent with that original decision. </P>
                    <HD SOURCE="HD2">B. What Amendments Are We Proposing Concerning Control of Commonly-Ducted Units? </HD>
                    <P>The current rule permits secondary aluminum producers to combine existing group 1 furnaces and in-line fluxers within a particular facility in a “secondary aluminum processing unit” or SAPU. The facility can then demonstrate compliance by determining the permissible emissions for the entire SAPU and then controlling emissions for the SAPU to that level. This broader definition of the affected source which must be controlled gives a secondary aluminum production facility added flexibility in fashioning the most cost-effective control strategies which will meet the standards. </P>
                    <P>
                        The existing rule also permits new group 1 furnaces and new in-line fluxers to be included in a new SAPU. However, it does not afford a facility the latitude to combine new and existing sources in the same SAPU. This is 
                        <PRTPAGE P="41128"/>
                        because the respective standards for existing sources and new sources are separate legal requirements, and we construe the CAA to require that standards be separately applied to all affected units. 
                    </P>
                    <P>Because the standards for an existing SAPU and the standards for a new SAPU happen to be identical in this instance, the legal constraints on combining existing emission units with new emission units have been understandably frustrating to some facilities. Moreover, in some facilities it may make the most sense from an engineering perspective to manifold emissions from units which are subject to differing standards to the same emission control device. In order to help facilities meet the standards in the most efficient and cost-effective manner, we agreed to develop and propose some additional language pertaining to commonly-ducted units. The new language reflects two different approaches to this problem. A facility subject to the standards may use either approach or both approaches if it wishes. </P>
                    <P>First, the proposed amendments would add a new paragraph to § 63.1505(k) for SAPU. The new paragraph (k)(6) would allow the owner or operator to redesignate any existing group 1 furnace or in-line fluxer at a secondary aluminum processing facility as a new emission unit. Any redesignated emission unit may then be included in a new SAPU at that facility. Any such redesignation (which would require prior approval of the responsible permitting authority) would only apply under subpart RRR and would be irreversible. </P>
                    <P>Second, we are also adding new language which clarifies the procedures by which units which are subject to differing standards but are manifolded to the same control device can demonstrate compliance. We believe that this new language is not required to permit this type of combined compliance demonstration, but we think it will give useful additional guidance to permitting authorities in establishing sound and defensible procedures for documenting compliance when units are commonly-ducted but subject to separate standards. </P>
                    <P>We are proposing to add two new paragraphs to § 63.1511 pertaining to compliance demonstrations for commonly-ducted units. The first of these paragraphs simply confirms other provisions of the rule which provide that aggregate emissions can be measured to demonstrate compliance for all emission units within a SAPU. </P>
                    <P>The second new paragraph covers those situations where commonly-ducted units are not within a single existing or new SAPU. In this instance, the following criteria would apply: </P>
                    <P>• Testing must be designed to verify that each affected source or emission unit individually satisfies all applicable emission requirements. </P>
                    <P>• Emissions must be tested at the outlet of each individual affected source or emission unit while it is operating under the highest load or capacity reasonably expected to occur, prior to the point that the emissions are combined with those from other affected sources or emission units. </P>
                    <P>• Combined emissions for the affected sources and emission units must be tested at the outlet of the control device while they are operating simultaneously under the highest load or capacity reasonably expected to occur. </P>
                    <P>• When determining compliance for a commonly-ducted unit, emissions of a particular pollutant from the individual unit would be presumed to be controlled by the same percentage as total emissions of that pollutant from all commonly-ducted units. </P>
                    <HD SOURCE="HD2">C. How Are We Proposing to Amend the Procedures for Adoption of an Operation, Maintenance, and Monitoring Plan? </HD>
                    <P>
                        In a direct final rule and parallel proposal published elsewhere in today's 
                        <E T="04">Federal Register</E>
                        , we are clarifying the timing of submission of an operation, maintenance, and monitoring (OM&amp;M) plan to the permitting authority, which is ambiguous in the existing rule. In this action, we are proposing to clarify the procedures by which a facility submits an OM&amp;M plan to the permitting authority and by which the permitting authority can require any necessary revisions of the plan. 
                    </P>
                    <P>Section 63.1505(k) of the existing rule refers to approval of an OM&amp;M plan by the permitting authority, and the necessary elements of an OM&amp;M plan are described in § 63.1510(b), but the procedures for submission and approval of the plan are not specified. We are proposing an amendment to correct that omission. </P>
                    <P>Under the proposed amendments, the facility would be required to certify that the OM&amp;M plan it is submitting complies with all requirements of the standards and complies with the OM&amp;M plan as submitted to the permitting authority, unless and until the plan is revised. If the permitting authority determined that any revisions of the plan are necessary to satisfy the requirements of the standards, the facility would be required to promptly make all necessary revisions and resubmit the revised plan. If the facility itself determined that revisions of the OM&amp;M plan are necessary, such revisions would not become effective until the owner or operator submitted a description of the changes and a revised plan incorporating them to the permitting authority. These same general procedures would also apply to the site-specific monitoring plan, which is one element of the OM&amp;M plan. </P>
                    <HD SOURCE="HD2">D. How Are We Proposing to Amend the Provisions Concerning Testing of Representative Emission Units? </HD>
                    <P>Section 63.1511(f) of the existing rule establishes a procedure which permits a secondary aluminum production facility to test a representative group 1 furnace or in-line flux box in order to determine the emission rate for other units of the same type at that facility. We are proposing to clarify the criteria for demonstrating compliance by testing of representative emission units. </P>
                    <P>In particular, the existing rule provides that the emission unit being tested must use “identical feed/charge and flux materials in the same proportions” as those emission units it represents. Industry representatives have expressed concern that this language could be given an unduly restrictive construction. To clarify our original intent, we are proposing to amend the criteria to require “feed materials and charge rates which are comparable” and “the same type of flux materials in the same proportions” as the emission units the tested unit represents. </P>
                    <HD SOURCE="HD2">E. How Are We Proposing To Amend the Standards for Unvented In-Line Flux Boxes? </HD>
                    <P>The existing rule requires that all in-line flux boxes meet the same emission standards and be tested in the same manner. Industry representatives have argued that the testing procedures in the rule are not practicable for in-line flux boxes which are unvented (units which have no ventilation ductwork manifolded to an outlet or emission control device). Documenting compliance with the particulate matter (PM) standard for such units might require construction of a temporary enclosure around the unit to capture and measure emissions. </P>
                    <P>
                        Industry representatives have also argued that the emissions of hydrogen chloride (HCl) and PM from such units are intrinsically low, but we believe it is quite possible for the HCl emissions from such units to exceed the applicable standards. The existing rule provides a 
                        <PRTPAGE P="41129"/>
                        procedure by which a facility can demonstrate compliance for HCl by limiting its use of reactive chlorine flux and then assuming that all chlorine used is emitted as HCl. However, because of the greater complexity of the reactions which generate PM emissions, there is no analogous procedure for PM. 
                    </P>
                    <P>While we do not agree with the industry that all emissions from unvented in-line flux boxes are intrinsically low, we do agree that the physical characteristics of these units and the nature of the reactions that generate PM mean that we can reliably conclude that an unvented unit which demonstrates compliance with the emission standards for HCl by limiting reactive chlorine flux will also be in compliance with the emission standards for PM. Therefore, we are proposing to add new language to § 63.1512(h) which will permit a facility with an unvented in-line flux box, which demonstrates compliance with the emission standards for HCl by limiting use of reactive chlorine flux, to infer compliance with the emission standards for PM as well. This would give facilities an alternative to testing of actual emissions, which could require costly construction of an enclosure around the unit or other engineering modifications. In such circumstances, the facility would be required to use the maximum permissible PM emission rate for the flux box when determining the total emissions for any secondary aluminum processing unit which includes the flux box. </P>
                    <HD SOURCE="HD2">F. How Are We Proposing To Clarify the Control Requirements for Sidewell Furnaces? </HD>
                    <P>Industry representatives have pointed out that the existing § 63.1506(m)(6) includes language that could require installation of an additional control device on sidewell furnaces whenever the level of molten metal is permitted to fall below the passage between the sidewell and the hearth, or reactive flux is added in the hearth. While we believe that a control device will sometimes be necessary in these circumstances, this result was not our intent. </P>
                    <P>As indicated in the preamble to our original proposal, we believe that there is a potential for additional emissions if the level of molten metal is permitted to fall below the top of the passage between the sidewell and the hearth, or if reactive flux is added in the hearth. Therefore, if these events occur, the emissions from both the sidewell and the hearth must be captured and tested in order to demonstrate compliance with the applicable emission standards. If the emission tests show that a control device is necessary to attain compliance, it must be installed. We are proposing to revise the language in question to clarify our intent. </P>
                    <P>In addition, we are proposing to amend § 63.1505(i)(7) to correct an erroneous cross-reference. As amended, certain sidewell group 1 furnaces would be required to meet the limits in paragraphs (i)(1) through (4) rather than (j)(1) through (4). </P>
                    <HD SOURCE="HD2">G. What Other Amendments Are We Proposing? </HD>
                    <P>We are proposing to amend § 63.1510(w) to clarify the procedures for obtaining approval of alternative monitoring methods. The new language makes it clear that this section refers to alternative monitoring methods other than those which may be separately authorized pursuant to § 63.1510(j)(5) or § 63.1510(v). </P>
                    <P>We are also proposing to clarify the recordkeeping requirements for in-line fluxers which do not use reactive flux. Section 63.1517(b)(11) would be amended to permit the facility to document that a particular in-line fluxer does not use reactive flux using operating logs that show that no source of reactive flux was present, labels that prohibit use of reactive flux, or operating logs which document the fluxes used during each operating cycle. </P>
                    <P>We are proposing to amend § 63.1505(f)(1), which establishes emission standards for sweat furnaces, to correct an erroneous residence time.</P>
                    <P>We are proposing to clarify the definition of a melting/holding furnace in § 63.1503.</P>
                    <P>We are also proposing minor amendments to correct printing or technical errors in the final rule. These include:</P>
                    <P>• Revising Tables 2 an 3 of subpart RRR to correct entries which were inadvertently printed in the wrong columns.</P>
                    <P>
                        • Republishing Equation 2 of § 63.1505(k)(2) to clearly display the HC1 emission limit (L
                        <E T="52">cHC1</E>
                        ).
                    </P>
                    <P>• Revising the entry for § 63.14 in appendix A to subpart RRR to include incorporation by reference for a second document. </P>
                    <P>• Clarifying the rule requirement that both major and minor sources must keep a copy of the OM&amp;M on-site by deleting language in § 63.1517(b)(16)(ii) that requires only major sources to keep a copy of the OM&amp;M plan on-site.</P>
                    <HD SOURCE="HD1">III. Administrative Requirements </HD>
                    <HD SOURCE="HD2">A. Executive Order 12866, Regulatory Planning and Review </HD>
                    <P>Under Executive Order 12866 (58 FR 51735, October 4, 1993), the EPA must determine whether the regulatory action is “significant” and therefore subject to review by the Office of Management and Budget (OMB) and the requirements of the Executive Order. The Executive Order defines a “significant regulatory action” as one that is likely to result in a rule that may: </P>
                    <P>(1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or State, local, or tribal governments or communities; </P>
                    <P>(2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another agency; </P>
                    <P>(3) Materially alter the budgetary impact of entitlement, grants, user fees, or loan programs or the rights and obligations of recipients thereof; or </P>
                    <P>(4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in the Executive Order.</P>
                    <P>Pursuant to the terms of Executive Order 12866, it has been determined that the proposed action is not a “significant regulatory action” and was not submitted to OMB for review. </P>
                    <HD SOURCE="HD2">B. Executive Order 13132, Federalism </HD>
                    <P>Executive Order 13132, entitled “Federalism” (64 FR 43255, August 10, 1999), requires EPA to develop an accountable process to ensure “meaningful and timely input by State and local officials in the development of regulatory policies that have federalism implications.” “Policies that have federalism implications” is defined in the Executive Order to include regulations that have “substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government.” </P>
                    <P>Under section 6 of Executive Order 13132, EPA may not issue a regulation that has federalism implications, that imposes substantial direct compliance costs, and that is not required by statute, unless the Federal government provides the funds necessary to pay the direct compliance costs incurred by State and local governments, or EPA consults with State and local officials early in the process of developing the proposed regulation. The EPA also may not issue a regulation that has federalism implications and that preempts State law unless the EPA consults with State and local officials early in the process of developing the proposed regulation. </P>
                    <P>
                        These proposed rule amendments do not have federalism implications. They 
                        <PRTPAGE P="41130"/>
                        would not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132. None of the affected plants are owned or operated by State governments. Thus, the requirements of section 6 of the Executive Order do not apply to these proposed rule amendments. 
                    </P>
                    <HD SOURCE="HD2">C. Executive Order 13175, Consultation and Coordination With Indian Tribal Governments </HD>
                    <P>Executive Order 13175, entitled “Consultation and Coordination with Indian Tribal Governments” (65 FR 67249, November 6, 2000), requires EPA to develop an accountable process to ensure “meaningful and timely input by tribal officials in the development of regulatory policies that have tribal implications.” “Policies that have tribal implications” is defined in the Executive Order to include regulations that have “substantial direct effects on one or more Indian tribes, on the relationship between the Federal government and Indian tribes.” </P>
                    <P>These proposed rule amendments do not have tribal implications. They would not have substantial direct effects on tribal governments, on the relationship between the Federal government and Indian tribes, or on the distribution of power and responsibilities between the Federal government and Indian tribes, as specified in Executive Order 13175. No tribal governments own plants subject to the existing rule or proposed amendments. Thus, Executive Order 13175 does not apply to these proposed rule amendments. </P>
                    <HD SOURCE="HD2">D. Executive Order 13045, Protection of Children From Environmental Health Risks and Safety Risks </HD>
                    <P>Executive Order 13045 (62 FR 19885, April 23, 1997) applies to any rule that: (1) Is determined to be “economically significant,” as defined under Executive Order 12866, and (2) concerns an environmental health or safety risk that EPA has reason to believe may have a disproportionate effect on children. If the regulatory action meets both criteria, we must evaluate the environmental health or safety effects of the planned rule on children and explain why the planned regulation is preferable to other potentially effective and reasonably feasible alternatives. </P>
                    <P>We interpret Executive Order 13045 as applying only to those regulatory actions that are based on health or safety risks, such that the analysis required under section 5-501 of the Executive Order has the potential to influence the regulation. This proposed rule is not subject to Executive Order 13045 because it is based on technology performance and not on health or safety risks. </P>
                    <HD SOURCE="HD2">E. Unfunded Mandates Reform Act of 1995 </HD>
                    <P>Title II of the Unfunded Mandates Reform Act of 1995 (UMRA), Public Law 104-4, establishes requirements for Federal agencies to assess the effects of their regulatory actions on State, local, and tribal governments and the private sector. Under section 202 of the UMRA, the EPA generally must prepare a written statement, including a cost-benefit analysis, for proposed and final rules with “Federal mandates” that may result in expenditures by State, local, and tribal governments, in the aggregate, or by the private sector, of $100 million or more in any 1 year. Before promulgating an EPA rule for which a written statement is needed, section 205 of the UMRA generally requires the EPA to identify and consider a reasonable number of regulatory alternatives and adopt the least costly, most cost-effective, or least-burdensome alternative that achieves the objectives of the rule. The provisions of section 205 do not apply when they are inconsistent with applicable law. Moreover, section 205 allows the EPA to adopt an alternative other than the least-costly, most cost-effective, or least-burdensome alternative if the Administrator publishes with the final rule an explanation why that alternative was not adopted. Before the EPA establishes any regulatory requirements that may significantly or uniquely affect small governments, including tribal governments, it must have developed under section 203 of the UMRA a small government agency plan. The plan must provide for notifying potentially affected small governments, enabling officials of affected small governments to have meaningful and timely input in the development of EPA regulatory proposals with significant Federal intergovernmental mandates, and informing, educating, and advising small governments on compliance with the regulatory requirements. </P>
                    <P>The EPA has determined that these proposed rule amendments do not contain a Federal mandate that may result in estimated costs of $100 million or more to either State, local, or tribal governments, in the aggregate, or to the private sector in any 1 year. No costs are attributable to these proposed amendments. In addition, these proposed amendments would not significantly or uniquely affect small governments because they contain no requirements that apply to such governments or impose obligations upon them. Therefore, the requirements of the UMRA do not apply to these amendments. </P>
                    <HD SOURCE="HD2">F. Regulatory Flexibility Act (RFA), as Amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), 5 U.S.C. et seq. </HD>
                    <P>The RFA generally requires an agency to prepare a regulatory flexibility analysis of any rule subject to notice and comment rulemaking requirements under the Administrative Procedure Act or any other statute unless the agency certifies that the rule will not have a significant economic impact on a substantial number of small entities. Small entities include small businesses, small not-for-profit enterprises, and small governmental jurisdictions. </P>
                    <P>For purposes of assessing the impacts of today's proposed rule amendments on small entities, a small entity is defined as: (1) A small business whose parent company has fewer than 750 employees; (2) a small governmental jurisdiction that is a government of a city, county, town, school district or special district with a population of less than 50,000; or (3) a small organization that is any not-for-profit enterprise which is independently owned and operated and is not dominant in its field. </P>
                    <P>As discussed in the preamble to the final rule (65 FR 15690), subpart RRR was projected to potentially impact firms producing products in SIC codes 3341 (secondary smelting and refining of nonferrous metals), 3353 (aluminum sheet, plate, and foil), 3334 (primary aluminum production), 3354 (aluminum extruded products), 3363 (aluminum die casting), 3365 (aluminum foundries), 4953 (refuse systems—materials recovery facilities), 5093 (scrap and waste materials), and 5015 (motor vehicle parts—used). The EPA concluded that the existing rule would not result in a significant economic impact for a substantial number of small entities. This assessment was based on information on representative facility practices provided to EPA by these industries. For more detailed information, please see “Economic Impact Analysis for the Secondary Aluminum NESHAP Final Report,” October 1999 (Docket A-92-61). </P>
                    <P>
                        Following promulgation of subpart RRR, affected facilities in the aluminum die casting and foundry industries expressed concern that the information and assumptions upon which EPA has relied may be incomplete or may not 
                        <PRTPAGE P="41131"/>
                        adequately represent the facilities and emissions.
                    </P>
                    <P>There are 320 aluminum die casting companies and approximately 1,530 aluminum foundries currently operating domestically. The vast majority of these firms are small businesses employing less than 500 employees. No small businesses within aluminum die casting companies or aluminum foundries were specifically identified that are impacted by the final rule. Many of these firms would be exempt from the final rule for the reasons discussed in the Economic Impact Analysis document. </P>
                    <P>The proposed amendments do not create any new costs on affected firms, large or small. In fact, the proposed amendments would substantially reduce the economic impact on small businesses because of the exemption for die casters, extruders, and foundries. Because these plants will not incur any significant costs or economic impact, EPA determined that it is not necessary to prepare a regulatory flexibility analysis, and the Administrator certifies that this action will not have a significant economic impact on a substantial number of small entities. </P>
                    <HD SOURCE="HD2">G. Paperwork Reduction Act </HD>
                    <P>
                        The information collection requirements in subpart RRR have been submitted for approval to OMB under the requirements of the Paperwork Reduction Act, 44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                         The proposed amendments would not change the information collection requirements in subpart RRR, but would reduce the number of facilities subject to the rule. An amended Information Collection Request (ICR) document has been prepared by EPA (ICR No. ____), and a copy may be obtained from Susan Auby by mail at U.S. EPA, Office of Environmental Information, Collection Strategies Division (2822T), 1200 Pennsylvania Avenue, NW., Washington, DC 20460, by e-mail at 
                        <E T="03">auby.susan@epa.gov,</E>
                         or by calling (202) 566-1672. A copy may also be downloaded off the internet at 
                        <E T="03">http://www.epa.gov.icr</E>
                        . By U.S. Postal Service, send comments on the ICR to the Director, Collection Strategies Division, U.S. EPA (2822T), 1200 Pennsylvania Avenue, NW., Washington DC 20460; or by courier, send comments on the ICR to the Director, Collection Strategies Division, U.S. EPA (2822T), 1301 Constitution Avenue, NW., Room 6143, Washington DC 20460 (202) 566-1700. 
                    </P>
                    <P>The information requirements in the existing rule include mandatory notifications, records, and reports required by the NESHAP General Provisions (40 CFR part 63, subpart A). These information requirements are needed to confirm the compliance status of major sources, to identify any nonmajor sources not subject to the standards and any new or reconstructed sources subject to the standards, and to confirm that emission control devices are being properly operated and maintained. Based on the recorded and reported information, EPA can decide which facilities, records, or processes should be inspected. These recordkeeping and reporting requirements are specifically authorized under section 114 of the CAA. All information submitted to EPA for which a claim of confidentiality is made will be safeguarded according to Agency policies in 40 CFR part 2, subpart B. </P>
                    <P>Under the proposed amendments, fewer facilities would be subject to the testing, monitoring, recordkeeping, and reporting requirements. For this reason, the overall burden estimate for the existing rule would be reduced by approximately 20 percent. </P>
                    <P>As a result of these proposed amendments, the annual public reporting and recordkeeping burden for this collection of information (averaged over the first 3 years after the effective date of the rule) is estimated to decrease by 28,000 labor hours per year and $8.5 million per year. Total capital costs associated with monitoring requirements over the 3-year period of the ICR remain unchanged at an estimated $1.3 million; this estimate includes the capital and startup costs associated with installation of monitoring equipment. </P>
                    <P>Burden means the total time, effort, or financial resources expended by persons to generate, maintain, retain, or disclose or provide information to or for a Federal agency. This includes the time needed to review instructions; develop, acquire, install, and utilize technology and systems for the purpose of collecting, validating, and verifying information; process and maintain information and disclose and provide information; adjust the existing ways to comply with any previously applicable instructions and requirements; train personnel to respond to a collection of information; search existing data sources; complete and review the collection of information; and transmit or otherwise disclose the information. </P>
                    <P>An Agency may not conduct or sponsor, and a person is not required to respond to a collection of information unless it displays a currently valid OMB control number. The OMB control numbers for EPA's regulations are listed in 40 CFR part 9 and 48 CFR chapter 15. </P>
                    <HD SOURCE="HD2">H. National Technology Transfer and Advancement Act </HD>
                    <P>Section 12(d) of the National Technology Transfer and Advancement Act (NTTAA) of 1995 (Public Law 104-113; 15 U.S.C 272 note), directs EPA to use voluntary consensus standards in their regulatory and procurement activities unless to do so would be inconsistent with applicable law or otherwise impracticable. Voluntary consensus standards are technical standards (such as material specifications, test methods, sampling procedures, business practices) developed or adopted by one or more voluntary consensus bodies. The NTTAA requires Federal agencies to provide Congress, through annual reports to OMB, with explanations when an agency does not use available and applicable voluntary consensus standards. </P>
                    <P>The EPA's response to the NTTTA requirements are discussed in the preamble to the final rule (65 FR 15690). The proposed amendments do not change the required methods or procedures, but would expand provisions for the use of alternative methods. If a plant wishes to use an alternative method other than those identified in the existing rule, the owner or operator may submit an application to EPA according to the procedures described in the existing rule. </P>
                    <HD SOURCE="HD2">I. Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use </HD>
                    <P>These proposed rule amendments are not subject to Executive Order 13211 (66 FR 28355, May 22, 2001) because they are not a significant regulatory action under Executive Order 12866. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 40 CFR Part 63 </HD>
                        <P>Environmental protection, Administrative practice and procedure, Air pollution control, Hazardous substances, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Dated: May 31, 2002. </DATED>
                        <NAME>Christine Todd Whitman, </NAME>
                        <TITLE>Administrator.</TITLE>
                    </SIG>
                    <P>For the reasons stated in the preamble, title 40, chapter I, part 63 of the Code of Federal Regulations is proposed to be amended as follows: </P>
                    <PART>
                        <HD SOURCE="HED">PART 63—[AMENDED] </HD>
                        <P>1. The authority citation for part 63 continues to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                42 U.S.C. 7401 
                                <E T="03">et seq.</E>
                            </P>
                        </AUTH>
                        <SUBPART>
                            <PRTPAGE P="41132"/>
                            <HD SOURCE="HED">Subpart RRR—[Amended] </HD>
                        </SUBPART>
                        <P>2. Section 63.1500 is amended by: </P>
                        <P>a. Revising paragraph (a); </P>
                        <P>b. Removing existing paragraph (d); </P>
                        <P>c. Redesignating existing paragraphs (e) and (f) as (d) and (e); and </P>
                        <P>d. Adding new paragraph (f). </P>
                        <P>The addition and revision reads as follows: </P>
                        <SECTION>
                            <SECTNO>§ 63.1500 </SECTNO>
                            <SUBJECT>Applicability. </SUBJECT>
                            <P>(a) The requirements of this subpart apply to the owner or operator of each secondary aluminum production facility as defined in § 63.1503. </P>
                            <STARS/>
                            <P>(f) An aluminum die casting facility, aluminum foundry, or aluminum extrusion facility shall be considered to be an area source if it does not emit, or have the potential to emit considering controls, 10 tons per year or more of any single listed HAP or 25 tons per year of any combination of listed HAP from all emission sources which are located in a contiguous area and under common control, without regard to whether or not such sources are regulated under this subpart or any other subpart. In the case of an aluminum die casting facility, aluminum foundry, or aluminum extrusion facility which is an area source and is subject to regulation under this subpart only because it operates a thermal chip dryer, no furnace operated by such a facility shall be deemed to be subject to the requirements of this subpart if it melts only clean charge, internal scrap, or customer returns. </P>
                            <P>3. Section 63.1503 is amended by: </P>
                            <P>a. Adding in alphabetical order new definitions for the terms “aluminum scrap,” “customer returns,” “internal scrap,” and “runaround scrap”; and </P>
                            <P>b. Revising definitions for the terms “clean charge,” “cover flux,” “group 1 furnace,” “group 2 furnace,” “melting/holding furnace,” “reactive fluxing,” “scrap dryer/delacquering kiln/decoating kiln,” “secondary aluminum processing unit (SAPU),” “secondary aluminum production facility,” and “thermal chip dryer.” </P>
                            <P>The additions and revisions read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 63.1503</SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <STARS/>
                            <P>
                                <E T="03">Aluminum scrap</E>
                                 means fragments of aluminum stock removed during manufacturing (i.e., machining), manufactured aluminum articles or parts rejected or discarded and useful only as material for reprocessing, and waste and discarded material made of aluminum. 
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Clean charge</E>
                                 means furnace charge materials including molten aluminum; T-bar; sow; ingot; billet; pig; alloying elements; 
                                <E T="03">aluminum scrap</E>
                                 known by the owner or operator to be entirely free of paints, coatings, and lubricants; uncoated/unpainted aluminum chips that have been thermally dried or treated by a centrifugal cleaner; 
                                <E T="03">aluminum scrap</E>
                                 dried at 343 °C (650 °F) or higher; 
                                <E T="03">aluminum scrap</E>
                                 delacquered/decoated at 482 °C (900 °F) or higher, and 
                                <E T="03">runaround scrap.</E>
                            </P>
                            <P>
                                <E T="03">Cover flux</E>
                                 means salt added to the surface of molten aluminum in a 
                                <E T="03">group 1</E>
                                 or 
                                <E T="03">group 2 furnace</E>
                                , without agitation of the molten aluminum, for the purpose of preventing oxidation. 
                            </P>
                            <P>
                                <E T="03">Customer returns</E>
                                 means any aluminum product which is returned by a customer to the aluminum company that originally manufactured the product prior to resale of the product or further distribution in commerce, and which contains no paint or other solid coatings (i.e., lacquers). 
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Group 1 furnace</E>
                                 means a furnace of any design that melts, holds, or processes aluminum that contains paint, lubricants, coatings, or other foreign materials with or without 
                                <E T="03">reactive fluxing</E>
                                , or processes 
                                <E T="03">clean charge</E>
                                 with 
                                <E T="03">reactive fluxing.</E>
                            </P>
                            <P>
                                <E T="03">Group 2 furnace</E>
                                 means a furnace of any design that melts, holds, or processes only 
                                <E T="03">clean charge</E>
                                 and that performs no 
                                <E T="03">fluxing</E>
                                 or performs 
                                <E T="03">fluxing</E>
                                 using only nonreactive, non-HAP-containing/non-HAP-generating gases or agents. 
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Internal scrap</E>
                                 means all aluminum scrap regardless of the level of contamination which originates from castings or extrusions produced by an aluminum die casting facility, aluminum foundry, or aluminum extrusion facility, and which remains at all times within the control of the company that produced the castings or extrusions. 
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Melting/holding furnace</E>
                                 means a 
                                <E T="03">group 1 furnace</E>
                                 that processes only 
                                <E T="03">clean charge</E>
                                , performs melting, holding, and fluxing functions, and does not transfer molten aluminum to or from another furnace except for purposes of alloy changes, off-specification product drains, or maintenance activities. 
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Reactive fluxing</E>
                                 means the use of any gas, liquid, or solid flux (other than cover flux) that results in a HAP emission. Argon and nitrogen are not reactive and do not produce HAP. 
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Runaround scrap</E>
                                 means scrap materials generated on-site by aluminum casting, extruding, rolling, scalping, forging, forming/stamping, cutting, and trimming operations and that do not contain paint or solid coatings. Uncoated/unpainted aluminum chips generated by turning, boring, milling, and similar machining operations may be clean charge if they have been thermally dried or treated by a centrifugal cleaner, but are not considered to be 
                                <E T="03">runaround scrap.</E>
                            </P>
                            <P>
                                <E T="03">Scrap dryer/delacquering kiln/decoating kiln</E>
                                 means a unit used primarily to remove various organic contaminants such as oil, paint, lacquer, ink, plastic, and/or rubber from 
                                <E T="03">aluminum scrap</E>
                                 (including used beverage containers) prior to melting. 
                            </P>
                            <P>
                                <E T="03">Secondary aluminum processing unit (SAPU).</E>
                                 An existing SAPU means all existing 
                                <E T="03">group 1 furnaces</E>
                                 and all existing 
                                <E T="03">in-line fluxers</E>
                                 within a 
                                <E T="03">secondary aluminum production facility.</E>
                                 Each existing 
                                <E T="03">group 1 furnace</E>
                                 or existing 
                                <E T="03">in-line fluxer</E>
                                 is considered an 
                                <E T="03">emission unit</E>
                                 within a 
                                <E T="03">secondary aluminum processing unit.</E>
                                 A new 
                                <E T="03">SAPU</E>
                                 means any combination of individual 
                                <E T="03">group 1 furnaces</E>
                                 and 
                                <E T="03">in-line fluxers</E>
                                 within a 
                                <E T="03">secondary aluminum processing facility</E>
                                 which either were constructed or reconstructed after February 11, 1999, or have been permanently redesignated as new emission units pursuant to § 63.1505(k)(6). Each of the 
                                <E T="03">group 1 furnaces</E>
                                 or 
                                <E T="03">in-line fluxers</E>
                                 within a new 
                                <E T="03">SAPU</E>
                                 is considered an 
                                <E T="03">emission unit</E>
                                 within that 
                                <E T="03">secondary aluminum processing unit.</E>
                            </P>
                            <P>
                                <E T="03">Secondary aluminum production facility</E>
                                 means any establishment using 
                                <E T="03">clean charge</E>
                                , 
                                <E T="03">aluminum scrap</E>
                                , or dross from aluminum production, as the raw material and performing one or more of the following processes: scrap shredding, scrap drying/delacquering/decoating, thermal chip drying, furnace operations (i.e., melting, holding, sweating, refining, fluxing, or alloying), recovery of aluminum from dross, in-line fluxing, or dross cooling. A 
                                <E T="03">secondary aluminum production facility</E>
                                 may be independent or part of a primary aluminum production facility. For purposes of this subpart, aluminum die casting facilities, aluminum foundries, and aluminum extrusion facilities are not considered to be secondary aluminum production facilities if the only materials they melt are 
                                <E T="03">clean charge</E>
                                , customer returns, or internal scrap, and if they do not operate sweat furnaces, thermal chip dryers, or scrap dryers/delacquering kilns/decoating kilns. The determination of whether a facility is a 
                                <E T="03">secondary aluminum production facility</E>
                                 is only for purposes of this subpart and any regulatory 
                                <PRTPAGE P="41133"/>
                                requirements which are derived from the applicability of this subpart, and is separate from any determination which may be made under other environmental laws and regulations, including whether the same facility is a “secondary metal production facility” as that term is used in 42 U.S.C. 7479(1) and 40 CFR 52.21(b)(1)(i)(A) (“prevention of significant deterioration of air quality”). 
                            </P>
                            <STARS/>
                            <P>
                                <E T="03">Thermal chip dryer</E>
                                 means a device that uses heat to evaporate oil or oil/water mixtures from unpainted/uncoated aluminum chips. Pre-heating boxes or other dryers which are used solely to remove water from aluminum scrap are not considered to be thermal chip dryers for purposes of this subpart. 
                            </P>
                            <STARS/>
                            <P>4. Section 63.1505 is amended by: </P>
                            <P>a. Revising the section heading; </P>
                            <P>b. Revising paragraph (f)(1); </P>
                            <P>c. Revising paragraph (i)(7); </P>
                            <P>d. Republishing the introductory text of paragraph (k)(2) and revising Equation 2; and </P>
                            <P>e. Adding new paragraph (k)(6).</P>
                            <P>The revisions and addition read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 63.1505</SECTNO>
                            <SUBJECT>Emission standards for affected sources and emission units. </SUBJECT>
                            <STARS/>
                            <P>
                                (f) 
                                <E T="03">Sweat furnace.</E>
                                 * * * 
                            </P>
                            <P>(1) The owner or operator is not required to conduct a performance test to demonstrate compliance with the emission standard of paragraph (f)(2) of this section, provided that, on and after the compliance date of this rule, the owner or operator operates and maintains an afterburner with a design residence time of 0.8 seconds or greater and an operating temperature of 1600 °F or greater. </P>
                            <STARS/>
                            <P>
                                (i) 
                                <E T="03">Group 1 furnace.</E>
                                 * * * 
                            </P>
                            <P>(7) The owner or operator of a sidewell group 1 furnace that conducts reactive fluxing (except for cover flux) in the hearth, or that conducts reactive fluxing in the sidewell at times when the level of molten metal falls below the top of the passage between the sidewell and the hearth, must comply with the emission limits of paragraphs (i)(1) through (4) of this section on the basis of the combined emissions from the sidewell and the hearth. </P>
                            <STARS/>
                            <P>
                                (k) 
                                <E T="03">Secondary aluminum processing unit.</E>
                                 * * * 
                            </P>
                            <P>(2) The owner or operator must not discharge or allow to be discharged to the atmosphere any 3-day, 24-hour rolling average emissions of HCl in excess of: </P>
                            <MATH SPAN="1" DEEP="59">
                                <MID>EP14JN02.000</MID>
                            </MATH>
                            <STARS/>
                            <P>(6) With the prior approval of the responsible permitting authority, an owner or operator may redesignate any existing group 1 furnace or in-line fluxer at a secondary aluminum production facility as a new emission unit. Any emission unit so redesignated may thereafter be included in a new SAPU at that facility. Any such redesignation will be solely for the purpose of this MACT standard and will be irreversible. </P>
                            <STARS/>
                            <P>5. Section 63.1506 is amended by: </P>
                            <P>a. Removing existing paragraph (a)(2); </P>
                            <P>b. Redesignating existing paragraphs (a)(3) through (a)(5) as paragraphs (a)(2) through (a)(4); and </P>
                            <P>c. Revising paragraphs (m)(6)(i) and (ii). </P>
                            <P>The revisions read as follows. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 63.1506</SECTNO>
                            <SUBJECT>Operating requirements. </SUBJECT>
                            <STARS/>
                            <P>
                                (m) 
                                <E T="03">Group 1 furnace with add-on air pollution control devices.</E>
                                 * * * 
                            </P>
                            <P>(6) * * * </P>
                            <P>(i) The level of molten metal remains above the top of the passage between the sidewell and hearth during reactive flux injection, unless emissions from both the sidewell and the hearth are included in demonstrating compliance with all applicable emission limits. </P>
                            <P>(ii) Reactive flux is added only in the sidewell, unless emissions from both the sidewell and the hearth are included in demonstrating compliance with all applicable emission limits. </P>
                            <STARS/>
                            <P>6. Section 63.1510 is amended by:</P>
                            <P>a. Removing the last sentence in the introductory text of paragraph (b), “Each plan must contain the following information”, and adding, in its place, five new sentences;</P>
                            <P>b. Revising the introductory text of paragraph (o)(1); and</P>
                            <P>c. Revising the introductory text of paragraph (w). </P>
                            <P>The revisions read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 63.1510</SECTNO>
                            <SUBJECT>Monitoring requirements. </SUBJECT>
                            <STARS/>
                            <P>(b) * * * The plan must be accompanied by a written certification by the owner or operator that the OM&amp;M plan satisfies all requirements of this section and is otherwise consistent with the requirements of this subpart. The owner or operator must comply with all of the provisions of the OM&amp;M plan as submitted to the permitting authority, unless and until the plan is revised in accordance with the following procedures. If the permitting authority determines at any time after receipt of the OM&amp;M plan that any revisions of the plan are necessary to satisfy the requirements of this section or this subpart, the owner or operator must promptly make all necessary revisions and resubmit the revised plan. If the owner or operator determines that any other revisions of the OM&amp;M plan are necessary, such revisions will not become effective until the owner or operator submits a description of the changes and a revised plan incorporating them to the permitting authority. Each plan must contain the following information: </P>
                            <STARS/>
                            <P>(o) * * * </P>
                            <P>(1) The owner or operator must develop, in consultation with the responsible permitting authority, a written site-specific monitoring plan. The site-specific monitoring plan must be submitted to the permitting authority as part of the OM&amp;M plan. The site-specific monitoring plan must contain sufficient procedures to ensure continuing compliance with all applicable emission limits and must demonstrate, based on documented test results, the relationship between emissions of PM, HCl, and D/F and the proposed monitoring parameters for each pollutant. Test data must establish the highest level of PM, HCl, and D/F that will be emitted from the furnace. This may be determined by conducting performance tests and monitoring operating parameters while charging the furnace with feed/charge materials containing the highest anticipated levels of oils and coatings and fluxing at the highest anticipated rate. If the permitting authority determines that any revisions of the site-specific monitoring plan are necessary to meet the requirements of this section or this subpart, the owner or operator must promptly make all necessary revisions and resubmit the revised plan to the permitting authority. </P>
                            <STARS/>
                            <P>
                                (w) 
                                <E T="03">Alternative monitoring methods.</E>
                                 If an owner or operator wishes to use an alternative monitoring method to demonstrate compliance with any emission standard in this subpart, other than those alternative monitoring methods which may be authorized pursuant to paragraph (j)(5) and (v) of this section, the owner or operator may submit an application to the Administrator. Any such application will be processed according to the 
                                <PRTPAGE P="41134"/>
                                criteria and procedures set forth in paragraphs (w)(1) through (6) of this section. 
                            </P>
                            <STARS/>
                            <P>7. Section 63.1511 is amended by revising paragraph (f) and adding paragraphs (h) and (i) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 63.1511</SECTNO>
                            <SUBJECT>Performance test/compliance demonstration general requirements. </SUBJECT>
                            <STARS/>
                            <P>
                                (f) 
                                <E T="03">Testing of representative emission units.</E>
                                 With the prior approval of the permitting authority, an owner or operator may utilize emission rates obtained by testing a particular type of group 1 furnace which is not controlled by any add-on control device, or by testing an in-line flux box which is not controlled by any add-on control device, to determine the emission rate for other units of the same type at the same facility. Such emission test results may only be considered to be representative of other units if all of the following criteria are satisfied: 
                            </P>
                            <P>(1) The tested emission unit must use feed materials and charge rates which are comparable to the emission units that it represents; </P>
                            <P>(2) The tested emission unit must use the same type of flux materials in the same proportions as the emission units it represents; </P>
                            <P>(3) The tested emission unit must be operated utilizing the same work practices as the emission units that it represents; </P>
                            <P>(4) The tested emission unit must be of the same design as the emission units that it represents; and </P>
                            <P>(5) The tested emission unit must be tested under the highest load or capacity reasonably expected to occur for any of the emission units that it represents. </P>
                            <STARS/>
                            <P>
                                (h) 
                                <E T="03">Testing of commonly-ducted units within a secondary aluminum processing unit.</E>
                                 When group 1 furnaces and/or in-line fluxers are included in a single existing SAPU or new SAPU, and the emissions from more than one emission unit within that existing SAPU or new SAPU are manifolded to a single control device, compliance for all units within the SAPU is demonstrated if the total measured emissions from all controlled and uncontrolled units in the SAPU do not exceed the emission limits calculated for that SAPU based on the applicable equation in § 63.1505(k). 
                            </P>
                            <P>
                                (i) 
                                <E T="03">Testing of commonly-ducted units not within a secondary aluminum processing unit.</E>
                                 With the prior approval of the permitting authority, an owner or operator may do combined performance testing of two or more individual affected sources or emission units which are not included in a single existing SAPU or new SAPU, but whose emissions are manifolded to a single control device. Any such performance testing of commonly-ducted units must satisfy the following basic requirements: 
                            </P>
                            <P>(1) All testing must be designed to verify that each affected source or emission unit individually satisfies all emission requirements applicable to that affected source or emission unit; </P>
                            <P>(2) All emissions of pollutants subject to a standard must be tested at the outlet from each individual affected source or emission unit while operating under the highest load or capacity reasonably expected to occur, and prior to the point that the emissions are manifolded together with emissions from other affected sources or emission units; </P>
                            <P>(3) The combined emissions from all affected sources and emission units which are manifolded to a single emission control device must be tested at the outlet of the emission control device; </P>
                            <P>(4) All tests at the outlet of the emission control device must be conducted with all affected sources and emission units whose emissions are manifolded to the control device operating simultaneously under the highest load or capacity reasonably expected to occur; and </P>
                            <P>(5) For purposes of demonstrating compliance of a commonly-ducted unit with any emission limit for a particular type of pollutant, the emissions of that pollutant by the individual unit shall be presumed to be controlled by the same percentage as total emissions of that pollutant from all commonly-ducted units are controlled at the outlet of the emission control device. </P>
                            <P>8. Section 63.1512 is amended by revising paragraph (h) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 63.1512</SECTNO>
                            <SUBJECT>Performance test/compliance demonstration requirements and procedures. </SUBJECT>
                            <STARS/>
                            <P>
                                (h) 
                                <E T="03">In-line fluxer.</E>
                                 (1) The owner or operator of an in-line fluxer that uses reactive flux materials must conduct a performance test to measure emissions of HCl and PM or otherwise demonstrate compliance in accordance with paragraph (h)(2) of this section. If the in-line fluxer is equipped with an add-on control device, the emissions must be measured at the outlet of the control device. 
                            </P>
                            <P>(2) The owner or operator may choose to limit the rate at which reactive chlorine flux is added to an in-line fluxer and assume, for the purposes of demonstrating compliance with the SAPU emission limit, that all chlorine in the reactive flux added to the in-line fluxer is emitted as HCl. Under these circumstances, the owner or operator is not required to conduct an emission test for HCl. If the owner or operator of any in-line flux box which has no ventilation ductwork manifolded to any outlet or emission control device chooses to demonstrate compliance with the emission limit for HCl by limiting use of reactive chlorine flux and assuming that all chlorine in the flux is emitted as HCl, compliance with the HCl limit shall also constitute compliance with the emission limit for PM, and no separate emission test for PM is required. In this case, the owner or operator of the unvented in-line flux box must utilize the maximum permissible PM emission rate for the in-line flux boxes when determining the total emissions for any SAPU which includes the flux box. </P>
                            <STARS/>
                            <P>9. Section 63.1515 is amended by revising paragraphs (b)(8) and (b)(9) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 63.1515 </SECTNO>
                            <SUBJECT>Notifications. </SUBJECT>
                            <STARS/>
                            <P>(b) * * * </P>
                            <P>(8) Manufacturer's specification or analysis documenting the design residence time of no less than 0.8 seconds and design operating temperature of no less than 1,600 °F for each afterburner used to control emissions from a sweat furnace that is not subject to a performance test. </P>
                            <P>(9) The OM&amp;M plan (including site-specific monitoring plan for each group 1 furnace with no add-on air pollution control device). </P>
                            <STARS/>
                            <P>10. Section 63.1517 is amended by revising paragraphs (b)(11) and (b)(16)(ii) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 63.1517 </SECTNO>
                            <SUBJECT>Records. </SUBJECT>
                            <STARS/>
                            <P>(b) * * * </P>
                            <P>(11) For each in-line fluxer for which the owner or operator has certified that no reactive flux was used: </P>
                            <P>(i) Operating logs which establish that no source of reactive flux was present at the in-line fluxer; </P>
                            <P>(ii) Labels required pursuant to § 63.1506(b) which establish that no reactive flux may be used at the in-line fluxer; or </P>
                            <P>(iii) Operating logs which document each flux gas, agent, or material used during each operating cycle. </P>
                            <STARS/>
                            <P>(16) * * * </P>
                            <P>(ii) OM&amp;M plan; and </P>
                            <STARS/>
                            <P>
                                11. Table 2 to subpart RRR is amended under the entry for “Group 1 
                                <PRTPAGE P="41135"/>
                                furnace with lime-injected fabric filter (including those that are part of a secondary aluminum processing unit)” by revising in column 2 the entry “Fabric filter inlet temperature” to read as follows: 
                            </P>
                            <GPOTABLE COLS="3" OPTS="L1,i1" CDEF="s100,r100,r100">
                                <TTITLE>Table 2 To Subpart RRR of Part 63.—Summary of Operating Requirements for New and Existing Affected Sources and Emission Units </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Affected source/emission unit </CHED>
                                    <CHED H="1">Monitor type/operation/process </CHED>
                                    <CHED H="1">Operating requirements </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="22">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         *</ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Group 1 furnace with lime-injected fabric filter (including those that are part of a secondary aluminum processing unit)</ENT>
                                    <ENT O="oi0">*  *  *  *  *</ENT>
                                    <ENT O="oi0">*  *  *  *  * </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22"> </ENT>
                                    <ENT>Fabric filter inlet temperature</ENT>
                                    <ENT>
                                        Maintain average fabric filter inlet unit temperature for each 3-hour period at or below average temperature during the performance test +14 °C (+25 °F). 
                                        <LI O="oi0">*  *  *  *  * </LI>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         *</ENT>
                                </ROW>
                            </GPOTABLE>
                            <P>12. Table 3 to subpart RRR is amended by: </P>
                            <P>
                                a. Under the entry for “Group 1 furnace with lime-injected fabric filter”, revising in column 2 the entry “Reactive flux injection rate Weight measurement device accuracy of +1%
                                <SU>b</SU>
                                ; calibrate every 3 months; record weight and type of reactive flux added or injected for each 15-minute block period while reactive fluxing occurs; calculate and record total reactive flux injection rate for each operating cycle or time period used in performance test; or Alternative flux injection rate determination procedure per § 63.1510(j)(5).”; and 
                            </P>
                            <P>b. Under the entry for “Group 1 furnace without add-on controls”, adding an entry in the third column for the entry in the second column “Feed material (melting/holding furnace)”. </P>
                            <P>The revisions read as follows: </P>
                            <GPOTABLE COLS="3" OPTS="L1,i1" CDEF="s100,r100,r100">
                                <TTITLE>Table 3 to Subpart RRR of Part 63.—Summary of Monitoring Requirements for New and Existing Affected Sources and Emission Units </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Affected source/emission unit</CHED>
                                    <CHED H="1">Monitor type/operation/process </CHED>
                                    <CHED H="1">Monitoring requirements </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="22">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         *          </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Group 1 furnace with lime-injected fabric filter</ENT>
                                    <ENT O="oi0">
                                        *  *  *  *  * 
                                        <LI O="xl">Reactive flux injection rate</LI>
                                        <LI O="oi0">*  *  *  *  *</LI>
                                    </ENT>
                                    <ENT O="oi0">
                                        *  *  *  *  * 
                                        <LI O="xl">
                                            Weight measurement device accuracy of ±1%
                                            <E T="51">b</E>
                                            ; calibrate every 3 months; record weight and type of reactive flux added or injected for each 15-minute block period while reactive fluxing occurs; calculate and record total reactive flux injection rate for each operating cycle or time period used in performance test; or 
                                        </LI>
                                        <LI>Alternative flux injection rate determination procedure per § 63.1510(j)(5). </LI>
                                        <LI O="oi0">*  *  *  *  * </LI>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">Group 1 furnace without add-on controls</ENT>
                                    <ENT O="oi0">
                                        *  *  *  *  *
                                        <LI O="oi0">Feed material (melting/holding furnace).</LI>
                                    </ENT>
                                    <ENT O="oi0">
                                        *  *  *  *  *
                                        <LI O="xl">Record type of permissible feed/charge material; certify charge materials every 6 months. </LI>
                                    </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         * </ENT>
                                </ROW>
                            </GPOTABLE>
                        </SECTION>
                    </PART>
                    <WIDE>
                        <P>13. Appendix A to subpart RRR is amended by revising the entry for § 63.14 to read as follows:</P>
                    </WIDE>
                    <GPOTABLE COLS="4" OPTS="L1,i1" CDEF="xs50,xs80,xs50,r100">
                        <TTITLE>Appendix A to Subpart RRR of Part 63.—General Provisions Applicability to Subpart RRR </TTITLE>
                        <BOXHD>
                            <CHED H="1">Citation </CHED>
                            <CHED H="1">Requirement </CHED>
                            <CHED H="1">Applies to RRR </CHED>
                            <CHED H="1">Comment </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="22">  </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *          </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">§ 63.14 </ENT>
                            <ENT>Incorporation by reference</ENT>
                            <ENT>Yes </ENT>
                            <ENT>Chapters 3 and 5 of ACGIH Industrial Ventilation Manual for capture/collection system; and Interim Procedures for Estimating Risk Associated with Exposure to Mixtures of Chlorinated Dibenzofurans (CDDs and CDFs) and 1989 Update (incorporated by reference in § 63.1502). </ENT>
                        </ROW>
                        <ROW>
                            <PRTPAGE P="41136"/>
                            <ENT I="22">  </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="28">*         *         *         *         *         *         *          </ENT>
                        </ROW>
                    </GPOTABLE>
                </SUPLINF>
                <FRDOC>[FR Doc. 02-14627 Filed 6-13-02; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 6560-50-P</BILCOD>
            </PRORULE>
            <PRORULE>
                <PREAMB>
                    <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                    <CFR>40 CFR Part 63 </CFR>
                    <DEPDOC>[FRL-7225-7] </DEPDOC>
                    <RIN>RIN 2060-AE77 </RIN>
                    <SUBJECT>National Emission Standards for Hazardous Air Pollutants for Secondary Aluminum Production </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Environmental Protection Agency (EPA). </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule; amendments. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>On March 23, 2000, the EPA issued national emission standards for hazardous air pollutants for secondary aluminum production under section 112 of the Clean Air Act (CAA). This proposal would amend the standards to clarify compliance dates and defer certain early compliance obligations. These amendments are proposed as part of settlement agreements with industry trade associations, including the Aluminum Association and the American Foundrymen's Society. </P>
                        <P>
                            In the Rules and Regulations section of to 
                            <E T="04">Federal Register</E>
                            , we are making these amendments in a direct final NESHAP without prior proposal because we view the revisions as noncontroversial and anticipate no adverse comments. We have explained our reasons for these revisions in the direct final rule. If we receive no significant adverse comments, we will take no further action on this proposed rule. If we receive significant adverse comments, we will withdraw only those provisions on which we received significant adverse comments. We will publish a timely withdrawal in the 
                            <E T="04">Federal Register</E>
                             indicating which provisions will become effective and which provisions are being withdrawn. If part or all of the direct final rule in the Rules and Regulations section of today's 
                            <E T="04">Federal Register</E>
                             is withdrawn, all comments pertaining to those provisions will be addressed in a subsequent final rule based on this proposed rule. 
                        </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            <E T="03">Comments.</E>
                             We must receive written comments on or before July 15, 2002, unless a hearing is requested by June 24, 2002. If a timely hearing request is submitted, we must receive written comments on or before July 29, 2002. 
                        </P>
                        <P>
                            <E T="03">Public Hearing.</E>
                             If anyone contacts the EPA requesting to speak at a public hearing by June 24, 2002, a public hearing will be held on June 28, 2002. 
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            <E T="03">Comments.</E>
                             By U.S. Postal Service, send comments (in duplicate, if possible) to: Air and Radiation Docket and Information Center (6102), Attention Docket No. A-2002-05, U.S. EPA, 1200 Pennsylvania Avenue, NW., Washington, DC 20460. In person or by courier, deliver comments (in duplicate, if possible) to: Air and Radiation Docket and Information Center (6102), Attention Docket No. A-2002-05, Room M-1500, U.S. EPA, 401 M Street, SW., Washington, DC 20460. We request a separate copy of each public comment be sent to the contact person listed below (see 
                            <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                            ). 
                        </P>
                        <P>
                            <E T="03">Public Hearing.</E>
                             If a public hearing is held, it will be held at the EPA Office of Administration Auditorium, Research Triangle Park, North Carolina beginning at 10 a.m. 
                        </P>
                        <P>
                            <E T="03">Docket.</E>
                             Docket No. A-2002-05 contains supporting information used in developing the amendments. The docket is located at the U.S. EPA, 401 M Street, SW., Washington, DC 20460 in room M-1500, Waterside Mall (ground floor), and may be inspected from 8:30 a.m. to 5:30 p.m., Monday through Friday, excluding legal holidays. 
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Mr. John Schaefer, U.S. EPA, Minerals and Inorganic Chemicals Group, Emission Standards Division (Mail Code C504-05), Office of Air Quality Planning and Standards, Research Triangle Park, NC 27711, telephone number (919) 541-0296, electronic mail address, 
                            <E T="03">schaefer.john@epa.gov.</E>
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        <E T="03">Comments.</E>
                         Comments and data may be submitted by electronic mail (e-mail) to 
                        <E T="03">air-and-r-docket@epa.gov.</E>
                         Electronic comments must be submitted as an ASCII file to avoid the use of special characters and encryption problems and will also be accepted on disks in WordPerfect® file format. All comments and data submitted in electronic form must note the docket number: A-2002-05. No confidential business information (CBI) should be submitted by e-mail. Electronic comments may be filed online at many Federal Depository Libraries. 
                    </P>
                    <P>Commenters wishing to submit proprietary information for consideration must clearly distinguish such information from other comments and label it as CBI. Send submissions containing such proprietary information directly to the following address, and not to the public docket, to ensure that proprietary information is not inadvertently placed in the docket: Mr. Roberto Morales, OAQPS Document Control Officer (C404-02), U.S. EPA, Research Triangle Park, NC 27711, Attn: Mr. John Schaefer. The EPA will disclose information identified as CBI only to the extent allowed by the procedures set forth in 40 CFR part 2. If no claim of confidentiality accompanies a submission when it is received by EPA, the information may be made available without further notice to the public. </P>
                    <P>
                        <E T="03">Public Hearing.</E>
                         Persons interested in attending the hearing or inquiring as to whether a hearing is to be held should notify Ms. Tanya Medley, U.S. EPA, Minerals and Inorganic Chemicals Branch (C504-05), Emission Standards Division, Office of Air Quality Planning and Standards, Research Triangle Park, NC 27711, telephone (919) 541-5422, at least 2 days in advance of the hearing. Persons interested in attending the public hearing should also call Ms. Tanya Medley to verify the time, date, and location of the hearing. The public hearing will provide interested parties the opportunity to present data, views, or arguments concerning these proposed amendments. 
                    </P>
                    <P>
                        <E T="03">Docket.</E>
                         The docket is an organized and complete file of the administrative record compiled by EPA in the development of these amendments. The docket is a dynamic file because information is added throughout the rulemaking process. The docketing system is intended to allow members of the public and industries involved to readily identify and locate documents 
                        <PRTPAGE P="41137"/>
                        so they can effectively participate in the rulemaking process. Along with the direct final rule and preamble and this accompanying proposal, the contents of the docket will serve as the record in the case of judicial review. (See section 307(d)(7)(A) of the Clean Air Act.) The regulatory text and other materials related to this rulemaking are available for review in the docket or copies may be mailed on request from the Air Docket by calling (202) 260-7548. A reasonable fee may be charged for copying docket materials. 
                    </P>
                    <P>
                        <E T="03">Worldwide Web (WWW).</E>
                         In addition to being available in the docket, an electronic copy of today's proposal will also be available on the WWW through the Technology Transfer Network (TTN). Following signature, a copy of these actions will be posted on the TTN's policy and guidance page for newly proposed rules at 
                        <E T="03">http://www.epa.gov/ttn/oarpg.</E>
                         The TTN provides information and technology exchange in various areas of air pollution control. If more information regarding the TTN is needed, call the TTN HELP line at (919) 541-5384. 
                    </P>
                    <P>
                        <E T="03">Regulated Entities.</E>
                         Entities potentially regulated by this action are the same as the existing rule in 40 CFR part 63, subpart RRR. These include secondary aluminum production facilities using clean charge, post-consumer scrap, aluminum scrap, ingots, foundry returns, dross, or molten metal as the raw material, and performing one or more of the following processes: aluminum scrap shredding, scrap drying/delacquering/decoating, thermal chip drying, furnace operations (i.e., melting, holding, refining, fluxing, or alloying), in-line fluxing, or dross cooling. Affected sources at facilities that are major sources of HAP are regulated under the final rule. Secondary aluminum production facilities that are collocated with primary aluminum production also are regulated under today's final rule. In addition, emissions of dioxins and furans from affected sources at facilities that are area sources of HAPs are also regulated. Regulated categories and entities include: 
                    </P>
                    <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,10,10,r75">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Category </CHED>
                            <CHED H="1">NAICS code </CHED>
                            <CHED H="1">SIC code </CHED>
                            <CHED H="1">Examples of regulated entities </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">Industry </ENT>
                            <ENT>331314 </ENT>
                            <ENT>3341 </ENT>
                            <ENT>
                                Secondary smelting and alloying of aluminum facilities. 
                                <LI>Secondary aluminum production facility affected sources that are collocated at: </LI>
                            </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">  </ENT>
                            <ENT>331312 </ENT>
                            <ENT>3334 </ENT>
                            <ENT>Primary aluminum production facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22">  </ENT>
                            <ENT>331315 </ENT>
                            <ENT>3353 </ENT>
                            <ENT>Aluminum sheet, plate, and foil manufacturing facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>331316 </ENT>
                            <ENT>3354 </ENT>
                            <ENT>Aluminum extruded product manufacturing facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>331319 </ENT>
                            <ENT>3355 </ENT>
                            <ENT>Other aluminum rolling and drawing facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>331521 </ENT>
                            <ENT>3363 </ENT>
                            <ENT>Aluminum die casting facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="22"> </ENT>
                            <ENT>331524 </ENT>
                            <ENT>3365 </ENT>
                            <ENT>Aluminum foundry facilities. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">State/local/tribal governments </ENT>
                            <ENT/>
                            <ENT/>
                            <ENT>Not affected. </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Federal government </ENT>
                            <ENT/>
                            <ENT/>
                            <ENT>Not affected. </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>
                        This table is not intended to be exhaustive, but rather provides a guide for readers regarding entities likely to be regulated by this action. This table lists the types of entities that the Agency is now aware could potentially be regulated by this action. Other types of entities not listed in the table could also be regulated. To determine whether your facility is regulated by this action, you should carefully examine the applicability criteria in § 63.1500 of the rule. If you have questions regarding the applicability of this action to a particular entity, consult the contact person listed in the preceding 
                        <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                         section. 
                    </P>
                    <P>
                        A direct final rule identical to this proposal is published in the Rules and Regulations section of today's 
                        <E T="04">Federal Register</E>
                        . If we receive any significant adverse comment pertaining to one or more distinct amendments in this proposal, we will publish a timely notice in the 
                        <E T="04">Federal Register</E>
                         informing the public which amendments will become effective and which amendments are being withdrawn due to adverse comment. We will address all public comments concerning any withdrawn amendments in a subsequent final rule. If no relevant adverse comments are received, no further action will be taken on this proposal and the direct final rule will become effective as provided in that notice. 
                    </P>
                    <P>
                        The regulatory text for this proposal is identical to that for the direct final rule published in the Rules and Regulations section of today's 
                        <E T="04">Federal Register</E>
                        . For further supplementary information, see the direct final rule. 
                    </P>
                    <P>
                        <E T="03">Administrative Requirements.</E>
                         The Regulatory Flexibility Act (RFA), as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (SBREFA), 5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        , generally requires an agency to prepare a regulatory flexibility analysis of any rule subject to notice and comment rulemaking requirements under the Administrative Procedure Act or any other statute unless the Agency certifies that the rule will not have a significant economic impact on a substantial number of small entities. Small entities include small businesses, small organizations, and small governmental jurisdictions. 
                    </P>
                    <P>For purposes of assessing the impacts of today's proposed rule amendments on small entities, a small entity is defined as: (1) A small business whose parent company has fewer than 750 employees; (2) a small governmental jurisdiction that is a government of a city, county, town, school district or special district with a population of less than 50,000; or (3) a small organization that is any not-for-profit enterprise which is independently owned and operated and is not dominant in its field. </P>
                    <P>We believe there will be little or no impact on small entities because the purpose of today's proposed amendments is to clarify the rule, and the changes will not impose new requirements or compliance costs on industry. The Administrator certifies that this action will not have a significant economic impact on a substantial number of small entities. </P>
                    <P>
                        For information regarding other administrative requirements for this action, please see the direct final rule located in the Rules and Regulations section of today's 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 40 CFR Part 63 </HD>
                        <P>Environmental protection, Administrative practice and procedure, Air pollution control, Hazardous substances, Recordkeeping and reporting requirements.</P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Dated: May 31, 2002. </DATED>
                        <NAME>Christine Todd Whitman, </NAME>
                        <TITLE>Administrator. </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 02-14626 Filed 6-13-02; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 6560-50-P</BILCOD>
            </PRORULE>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="41138"/>
                    <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                    <CFR>40 CFR Part 63 </CFR>
                    <DEPDOC>[FRL-7225-4] </DEPDOC>
                    <RIN>RIN 2060-AJ09 and 2060-AJ11 </RIN>
                    <SUBJECT>National Emission Standards for Hazardous Air Pollutants for Secondary Aluminum Production </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Environmental Protection Agency (EPA). </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Withdrawal of proposed rule. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            This document withdraws a previously published proposed rule to stay the national emission standards for hazardous air pollutants (NESHAP) for secondary aluminum production, as applied to aluminum die casters and aluminum foundries. This document also announces that we do not intend to take any further action with respect to an advance notice of proposed rulemaking in which we announced our intention to remove aluminum die casters and aluminum foundries from the secondary aluminum NESHAP and to promulgate a separate NESHAP for these facilities. We published these actions pursuant to a settlement agreement with the petitioners in 
                            <E T="03">American Foundrymen's Society et al.</E>
                             v. 
                            <E T="03">EPA,</E>
                             Civ. No. 00-1208 (D.C. Cir.), a case seeking judicial review of the secondary aluminum NESHAP. That settlement agreement has now been entirely supplanted by a new agreement to propose certain amendments to the existing standards. 
                        </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>The proposed rule to stay the applicability of 40 CFR part 63, subpart RRR, is withdrawn as of June 14, 2002. </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSEES:</HD>
                        <P>
                            <E T="03">Docket.</E>
                             Docket No. A-2000-31, containing information pertaining to the advance notice of proposed rulemaking, and Docket No. A-2000-35, containing information pertaining to the proposed rule to stay the applicability of subpart RRR, are available for public inspection between 8:00 a.m. to 5:30 p.m., Monday through Friday, except Federal holidays, at the following address: U.S. EPA, Air and Radiation Docket and Information Center (6102), 401 M Street, SW., Washington, DC 20460, telephone (202) 260-7548. The dockets are located at the above address in room M-1500, Waterside Mall (ground floor). A reasonable fee may be charged for copying docket materials. 
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Mr. John Schaefer, U.S. EPA, Minerals and Inorganic Chemicals Group, Emission Standards Division (Mail Code C504-05), Office of Air Quality Planning and Standards, Research Triangle Park, NC 27711, telephone number (919) 541-0296, electronic mail address, schaefer.john@epa.gov. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>On March 23, 2000 (65 FR 15690), we promulgated the NESHAP for secondary aluminum production (40 CFR part 63, subpart RRR) under the authority of section 112(d) of the Clean Air Act (CAA). </P>
                    <P>
                        After promulgation of the NESHAP for secondary aluminum production, a petition for judicial review of the standards was filed in the D.C. Circuit Court of Appeals by the American Foundrymen's Society, the North American Die Casting Association, and the Non-Ferrous Founders' Society (
                        <E T="03">American Foundrymen's Society et al.</E>
                         v. 
                        <E T="03">U.S. EPA,</E>
                         Civ. No 00-1208 (D.C. Cir.)). 
                    </P>
                    <P>
                        The 
                        <E T="03">Foundrymen's</E>
                         case presented issues concerning the applicability of subpart RRR to aluminum die casters and aluminum foundries which were considered during the initial rulemaking development. Because aluminum die casters and foundries sometimes conduct the same type of operations as other secondary aluminum producers, we originally intended to apply the standards to these facilities, but only in those instances where they conduct such operations. However, representatives of the affected facilities argued that they should not be considered to be secondary aluminum producers and should be wholly exempt from the rule. During the rulemaking development, we decided to permit die casters and foundries to melt contaminated internal scrap without being considered to be secondary aluminum producers, but their representatives insisted that too many facilities would still be subject to the NESHAP. After promulgation, we announced that we would withdraw the standards as applied to die casters and foundries and develop separate MACT (maximum achievable control technology) standards for these facilities. 
                    </P>
                    <P>
                        After the 
                        <E T="03">Foundrymen's</E>
                         case was filed, we negotiated an initial settlement agreement which established a process to effectuate our commitment to develop new MACT standards. In that first settlement, EPA agreed that it would stay the current standards for these facilities, collect comprehensive data to support alternate standards, and promulgate alternate standards. We then published a proposed rule to stay the applicability of the standards for aluminum die casters and aluminum foundries (65 FR 55491, September 14, 2000) and an advance notice of proposed rulemaking (ANPR) announcing our intent to develop new standards for these facilities (65 FR 55489, September 14, 2000). 
                    </P>
                    <P>
                        During the subsequent process of preparing for information collection, the petitioners concluded that the present rule was not as sweeping in applicability as they had feared, and the parties then agreed to explore an alternate approach to settlement based on clarifications of the current standards. We subsequently reached agreement with the 
                        <E T="03">Foundrymen's</E>
                         petitioners on a new settlement which entirely supplants the prior settlement. The current settlement requires us to propose certain amendments clarifying and modifying the existing secondary aluminum standards, rather than developing and promulgating new standards for aluminum die casters and aluminum foundries. 
                    </P>
                    <P>
                        As required by section 113(g) of the CAA, we provided notice and an opportunity for comment concerning the 
                        <E T="03">Foundrymen's</E>
                         settlement (67 FR 9972, March 5, 2002). We received three adverse comments on the settlement. After reviewing these comments, we decided to proceed with settlement. A copy of these comments and of our responses to them is available in Docket No. A-2002-06 for proposed rule amendments to the existing standards, and in Docket No. A-2002-05 for a direct final rule and parallel proposal to effectuate the new settlement, all of which are being publishing elsewhere in today's 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                    <P>Pursuant to the new settlement agreement, we are today withdrawing the proposed rule to stay the applicability of 40 CFR part 63, subpart RRR, for aluminum die casting facilities and aluminum foundries which we published on September 14, 2000. In addition, we are announcing that we will take no further action with respect to the ANPR announcing our intention to develop separate NESHAP for aluminum die casters and foundries, which we also published on September 14, 2000. </P>
                    <SIG>
                        <DATED>Dated: May 31, 2002. </DATED>
                        <NAME>Christine Todd Whitman, </NAME>
                        <TITLE>Administrator. </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 02-14628 Filed 6-13-02; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 6560-50-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="41139"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Department of Justice</AGENCY>
            <CFR>28 CFR Part 105</CFR>
            <TITLE>Screening of Aliens and Other Designated Individuals Seeking Flight Training; Interim Final Rule and Proposed Rule</TITLE>
            <TITLE>Rescission of Second Notice of Advance Consent for Providing Certain Aviation Training; Notice</TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="41140"/>
                    <AGENCY TYPE="S">DEPARTMENT OF JUSTICE </AGENCY>
                    <CFR>28 CFR Part 105 </CFR>
                    <DEPDOC>[OAG 104; AG Order No. 2590-2002] </DEPDOC>
                    <RIN>RIN 1105-AA80 </RIN>
                    <SUBJECT>Screening of Aliens and Other Designated Individuals Seeking Flight Training </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Department of Justice. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Interim final rule with request for comments. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>Under section 113 of the Aviation and Transportation Security Act, certain aviation training providers subject to regulation by the Federal Aviation Administration (“FAA”) are prohibited from providing training to aliens and other designated individuals in the operation of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more, unless the aviation training provider notifies the Attorney General of the identity of the alien seeking training and the Attorney General does not direct the aviation training provider within 45 days that the alien presents a risk to aviation or national security. This interim final rule implements a process by which aviation training providers would provide the required notification for specific categories of aliens, the Attorney General would respond, and the aviation training providers would begin or resume instruction for candidates who the Attorney General has determined do not present a risk to aviation and national security as a result of the risk assessment conducted pursuant to section 113 of the Aviation and Transportation Security Act. </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>
                            <E T="03">Effective date:</E>
                             This interim rule is effective June 14, 2002. 
                        </P>
                        <P>
                            <E T="03">Comment date:</E>
                             Written comments on the interim final rule must be submitted on or before July 15, 2002. Written comments only on the proposed information collection must be submitted on or before August 13, 2002. 
                        </P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>Please submit written comments to Aviation Training Security, U.S. Department of Justice, 950 Pennsylvania Avenue, NW, Washington, DC 20530. </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Steven C. McCraw, Director, Foreign Terrorist Tracking Task Force, U.S. Department of Justice, Telephone (703) 414-9535. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        On November 19, 2001, Congress enacted the Aviation and Transportation Security Act (“ATSA”), Pub. L. No. 107-71. Upon enactment, section 113 of ATSA, 49 U.S.C. 44939, imposed notification and reporting requirements on certain persons who provide aviation training to aliens and other specified individuals. By its terms, section 113 of ATSA applies to anyone “subject to regulation under this part.” The reference to “this part” refers to Title 49, Subtitle VII, Part A, of the U.S. Code, entitled “Air Commerce and Safety.” Any entity regulated by any portion of Part A, comprising section 40101 through section 46507 of Title 49, must comply with the requirements of section 113 of ATSA. Persons subject to regulation under these provisions include individual training providers, training centers, certificated carriers, and flight schools (hereinafter collectively referred to as “Providers”). Thus, virtually all private flight instructors located in the United States are covered by section 113 of ATSA and therefore are subject to this rule. In addition, section 113 of ATSA does not exclude private providers of flight instruction located in countries outside the United States if these providers are authorized by the FAA to award United States licenses, certificates, or ratings. Providers outside the United States are not covered with regard to a particular instance of training, however, if that training will not lead to an FAA license, certificate or rating, regardless of whether the provider also has authority to issue such licenses, certificates or ratings. When the Department of Defense or the U.S. Coast Guard, or an entity providing training pursuant to a contract with the Department of Defense or the U.S. Coast Guard, provides training for a military purpose, such training is not subject to FAA regulation and therefore these entities, when providing such training, are not “person[s] subject to regulation under this part” within the meaning of section 113. 
                        <E T="03">See, e.g.,</E>
                         49 U.S.C. 44701(a) (Administrator's jurisdiction extends to promoting “safe flight of civil aircraft in air commerce”); 14 CFR part 61 (provisions concerning certification of pilots, flight instructors, and ground instructors do not apply where training is not for purpose of FAA certification). 
                    </P>
                    <P>Failure to comply with this rule may result in penalties being imposed in conformance with section 140(d) of ATSA. Pursuant to 49 U.S.C. 46301, persons violating this section are subject to civil penalties. </P>
                    <P>Pursuant to section 113 of ATSA, if an alien (defined in 8 U.S.C. 1101(a)(3) as “any person not a citizen or national of the United States”) or other person specified by the Under Secretary of Transportation for Security (collectively “candidates”) seeks instruction from a Provider in the operation of an aircraft with a maximum certificated takeoff weight of 12,500 pounds or more, the Provider must notify the Attorney General and must submit identifying information for the candidate in such form as the Attorney General may require in order to initiate a security risk assessment by the Department of Justice (the “Department”). </P>
                    <P>Once the Attorney General has been notified and all the required identifying information has been submitted, the Attorney General then has 45 days to inform the Provider that the candidate should not be given the requested training because he or she presents a risk to aviation or national security. If the Attorney General does not indicate that the candidate presents a risk to aviation or national security by the end of this 45-day review period, then the Provider may proceed with training. The Attorney General, however, may interrupt the training if he later determines that the candidate presents a risk to aviation or national security. The Attorney General has delegated his authority under section 113 of ATSA to conduct security risk assessments of individuals seeking flight training and to determine whether such individuals present a risk to aviation or national security to the Director of the Foreign Terrorist Tracking Task Force (“FTTTF”). </P>
                    <P>The Department recognized that section 113 of ATSA became immediately effective, and that Providers had been forced to suspend the training of aliens covered by ATSA pending the implementation of the process for notification to the Attorney General and the determination by the Attorney General whether the individual seeking training presents a risk to aviation or national security. The Department issued a notice on January 16, 2002 (“First Advance Consent Notice”) that stated that the Department was granting a provisional advance consent for the training of three categories of aliens, based on an initial determination they did not appear to present a risk to aviation or national security. 67 FR 2238. The First Advance Consent Notice was subsequently superseded, and the categories of advance consent modified in a notice published on February 8, 2002 (“Second Advance Consent Notice” or “Second Notice”). 67 FR 6051 (Feb. 8, 2002). The Second Notice is rescinded as of June 14, 2002. </P>
                    <P>
                        This interim final rule with request for comments (“interim rule”) rescinds the Second Advance Consent Notice and imposes notification requirements for aliens within one of the three 
                        <PRTPAGE P="41141"/>
                        categories eligible for expedited processing pursuant to this interim rule. Providers who currently are training any aliens in one of the four categories described in the Second Notice must suspend training until the Attorney General authorizes it to continue. This interim rule implements an expedited processing procedure for aliens in two of the four categories listed in the Second Notice and adds one additional category. Aliens in those three categories cannot be trained until the Provider notifies the Department in accordance with this rule and either the Attorney General authorizes training to proceed or 45 days from the date of notification elapses. 
                    </P>
                    <P>Although this regulation is being issued as an interim rule, the Department is committed to issuing a final rule that addresses comments from the public and the aviation industry. The Department plans to issue a final rule addressing these comments as soon as possible after the comment period closes. </P>
                    <HD SOURCE="HD1">Expedited Processing for Aviation Training of Certain Aliens </HD>
                    <P>The Department believes that the primary intent of Congress was to protect aviation and national security by preventing aliens who present a risk to aviation or national security from being taught how to pilot aircraft with a maximum certificated takeoff weight of 12,500 pounds or more. The Department has determined that providing aviation training for certain categories of aliens presents little risk to aviation or national security because these aliens already have been trained as pilots. In this interim rule, the Department establishes an expedited processing procedure for those categories of aliens. These three categories of aliens are: </P>
                    <P>(1) Foreign nationals who are current and qualified as pilot in command, second in command, or flight engineer with respective certificates with ratings recognized by the United States for aircraft with a maximum certificated takeoff weight of 12,500 pounds or more, or who are currently employed by U.S. air carriers as pilots on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more; </P>
                    <P>(2) Commercial, governmental, corporate, or military pilots of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more who must receive familiarization training on a particular aircraft in order to transport it to the purchaser or recipient, provided that the training provided is limited to familiarization (familiarization training is limited to that required to become proficient in configurations and variations of an aircraft and does not include initial qualification or type rating for an aircraft); or </P>
                    <P>(3) Military or law enforcement personnel who must receive training on a particular aircraft given by the United States to a foreign government pursuant to a draw-down authorized by the President under section 506(a)(2) of the Foreign Assistance Act of 1961, as amended (22 U.S.C. 2318(a)(2)), provided that the training provided be limited to familiarization. </P>
                    <P>These three categories differ slightly from the categories described in the Second Notice. At the suggestion of the FAA, this interim rule expands category (1) in the Second Notice to include foreign nationals currently employed by U.S. air carriers as pilots on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more. Such individuals may have temporarily lost their current status or qualification either through personal or medical reasons. Nevertheless, as they are already fully trained pilots, requiring them to undergo a full investigation before regaining current status would create a hardship to the industry without bringing any significant benefit to national security. </P>
                    <P>
                        Category (2) of the Second Notice covered training being conducted directly by the United States Department of Defense or the U.S. Coast Guard. When the Department of Defense or the U.S. Coast Guard, or an entity providing training pursuant to a contract with the Department of Defense or the U.S. Coast Guard, provides training for a military purpose, such training is not subject to FAA regulation and therefore these entities, when providing such training, are not “person[s] subject to regulation under this part” within the meaning of section 113. 
                        <E T="03">See, e.g.,</E>
                         49 U.S.C. 44701(a) (Administrator's jurisdiction extends to promoting “safe flight of civil aircraft in air commerce”); 14 CFR part 61 (provisions concerning certification of pilots, flight instructors, and ground instructors do not apply where training is not for purpose of FAA certification). Accordingly, in the instant rule, the former Category (2) is not included. 
                    </P>
                    <P>One category in the Second Notice covering certain students scheduled for training pursuant to an export authorization issued by the Department of State will not be included in the interim rule. </P>
                    <P>Finally, Category (3) will allow expedited processing for law enforcement or military pilots of foreign countries who would receive familiarization training on aircraft given to those countries by the United States pursuant to draw-downs authorized by the President in support of the United States' anti-narcotics efforts. Such pilots are subject to careful evaluation by the State Department and, as they are fully qualified pilots seeking only familiarization training rather than basic flight instruction, no significant security benefits would be realized by requiring them to undergo a full investigation. </P>
                    <P>Providers wishing to furnish aviation training to candidates in any of these categories will need to provide the Department with certain minimal identification, including the candidate's name, date of birth, passport issuing authority, country of citizenship, dates of training, unique student identification number, and the expedited processing category under which the candidate qualifies. The unique student identification number must be created by the Provider as a means of identifying records concerning the candidate. The unique student identification number must correspond to records kept by the Provider containing basic data concerning the candidate, including date of birth, place of birth, passport issuing authority and passport number, and copies of any other documentation that the FAA may require. As soon as the Provider furnishes the information to the Department in accordance with section 105.12 of this interim rule, and receives a response from the Department indicating that the individual does not present a risk to aviation or national security as a result of the risk assessment conducted pursuant to section 113 of ATSA, the Provider immediately may begin training. Receipt of this response by the Department to the notification will be deemed approval by the Department to commence training. </P>
                    <P>
                        The Provider's notification must be sent electronically to the Department in accordance with this regulation. Certificated training Providers must receive initial access to the system through the FAA. Providers will be required to make appointments to register through their local Flight Standards District Offices. Upon registration, Providers will be e-mailed a password for accessing the system and verifying applicant submissions. Any electronic notifications submitted to the Department must be submitted from a registered e-mail address in a format provided by the Department or the FAA. Any submissions sent from an unregistered e-mail address or using an incorrect format will not constitute notification of the Department for purposes of this rule. 
                        <PRTPAGE P="41142"/>
                    </P>
                    <P>The Department intends for its review to be accomplished expeditiously and requests comments on what turnaround time is needed to minimize any burdens that may be experienced by the aviation industry. Providers should keep in mind that the required notifications may be provided in advance of the anticipated training. </P>
                    <P>Limiting submissions to electronic submissions placed by Providers will help to eliminate data-input errors, speed the processing of submissions, and aid the Department's ability to audit the process. In addition, the Department will be able to implement controls to help ensure the integrity of the submissions. A paper-based system likely would result in more errors and increased processing times, thus further burdening the flight instruction industry. </P>
                    <P>In order to ensure that the electronic submissions are made by certificated training providers, Providers must receive initial access to the system through the FAA. Providers will be required to make appointments to register through their local Flight Standards District Offices. Upon registration, Providers will be e-mailed a password for accessing the system. The Department believes that most, if not all, Providers furnishing instruction on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more already possess Internet access. Those Providers not possessing an e-mail address will need to obtain one if they wish to utilize this process. The Department also notes that free Internet access is available at many public facilities, such as public libraries, and that free e-mail services are available from some Internet Service Providers. The Department seeks comments from Providers and candidates on the impact of the requirement to provide notifications to the Department electronically. </P>
                    <HD SOURCE="HD1">Citizens and Nationals of the United States </HD>
                    <P>Citizens and nationals of the United States are not subject to section 113 of ATSA unless they are covered by a category designated by the Under Secretary of Transportation for Security. Accordingly, Providers may proceed with training for such individuals once they establish that they are citizens or nationals of the United States. </P>
                    <P>The Attorney General is requiring that all prospective trainees who claim to be citizens or nationals of the United States must present documents to the Provider (such as a passport or birth certificate) establishing that the trainee is a citizen or national of the United States. Proof of United States citizenship or nationality is mandatory for United States citizens or nationals seeking training in the operation of an aircraft with a maximum certificated takeoff weight of 12,500 pounds or more, because, with the exception of individuals designated by the Under Secretary of Transportation for Security, the Department will not conduct checks on citizens or nationals of the United States. This requirement is necessary to prevent aliens from falsely claiming to be United States citizens in order to evade the Department's security risk assessment. The Department also notes that aliens who falsely claim to be United States citizens in order to obtain flight training subject to section 113 of ATSA may be convicted of a felony under 18 U.S.C. 911 and will be permanently inadmissible to the United States under section 212(a)(6)(C)(ii) of the Immigration and Nationality Act, 8 U.S.C. 1182(a)(6)(C)(ii). </P>
                    <HD SOURCE="HD1">Risk Assessments for Aliens Not Granted Expedited Processing and Other Persons Specified by the Under Secretary of Transportation for Security </HD>
                    <P>The Department is issuing a separate proposed rule to address training for aliens who do not fall within a category of expedited processing in this interim rule. The proposed rule also addresses the notification process for individuals who may be specified by the Under Secretary of Transportation for Security. In accordance with ATSA, the Under Secretary of Transportation for Security may specify other individuals for whom the Department should conduct security risk assessments. At this time, however, no other individuals have been specified. </P>
                    <HD SOURCE="HD1">Attorney General Review </HD>
                    <P>After the Provider submits all the information that is required under this rule, the Attorney General will have 45 days to conduct a security risk assessment. The Department recognizes the economic burden imposed on Providers by the 45-day waiting period for those candidates who are subject to this notification requirement. The Department believes that it is unnecessary to make a candidate wait for the full 45-day period in order to begin training if the Department has completed its risk assessment. Accordingly, in most cases, the Department expects that the Provider will be authorized to commence training (or instructed to deny it) sooner than the 45 days allowed by the statute. </P>
                    <P>Providers training candidates qualifying for expedited processing who have notified the Department in accordance with section 105.12 may commence training immediately after they receive a response from the Department to their notification, indicating that the individual does not present a risk to aviation or national security as a result of the risk assessment conducted pursuant to section 113 of ATSA. In the event that the Attorney General does not instruct the Provider to deny training within 45 days of the submission of all the information required under this rule, the Provider may commence the requested training. </P>
                    <P>The information provided to the Department will be used to confirm the identity of the individuals being trained and to help assess the risk presented by the candidate. In the event the Department subsequently determines that a candidate being trained does, in fact, present a risk to aviation or national security and that training should be denied, the Department will notify the Provider to terminate training immediately. Appropriate measures will be taken with respect to any candidate who is determined to present a risk to aviation or national security or with respect to any candidate or Provider who knowingly or negligently provides false information to the Department. </P>
                    <HD SOURCE="HD1">Regulatory Procedures </HD>
                    <HD SOURCE="HD1">Good Cause </HD>
                    <P>This interim rule is effective immediately upon the date of publication. For the following reasons the Department finds that good cause exists for adopting this rule without the prior notice ordinarily required by 5 U.S.C. 553(b). Delay in the implementation of the rule will cause serious disruption in the aviation industry and the economy in general, will have a negative impact on public safety and national security, and will have a seriously adverse impact on the military and foreign affairs of United States. </P>
                    <P>
                        As a consequence of the notification requirement in section 113 of ATSA, Providers were prohibited from furnishing aviation training to aliens pending the implementation of a process for submitting training notifications to the Department. As a temporary measure to relieve the economic pressure on the aviation industry pending the promulgation of this rule, and based on a determination that the training of certain categories of aliens who already had flight skills did not pose any additional risk to aviation or national security within the meaning of the statute, the Department published two 
                        <E T="04">Federal Register</E>
                         Notices defining 
                        <PRTPAGE P="41143"/>
                        certain categories of “advance consent.” Providers subsequently provided training to pilots in those categories without first notifying the Department. This advance consent process, however, is terminated with the publication of this rule, based on an assessment of the requirements of the ATSA. 
                    </P>
                    <P>This rulemaking is being issued on an interim basis to prevent the burdens that would be imposed on the public and the aviation industry if the revocation were effected without immediate provision of a means for Providers to furnish the required training notifications to the Attorney General for those aliens who are within the categories described in the expedited processing provisions of the interim final rule. For the following reasons, advance notice and comment would be contrary to the public interest. </P>
                    <P>While the primary intent of Congress behind section 113 of ATSA was to protect aviation and national security, the public also has a strong interest in seeing that those aliens who do not present such risks are allowed to train. Because advance consent is being revoked, Providers who are prohibited from training aliens, airlines who regularly employ these pilots, and manufacturers who sell to these airlines would lose business every day that these regulations are not in effect. In addition, the inability to provide training would have a ripple effect on the United States economy. On the basis of available information, the Department believes that the aviation industry and the public would be affected severely if the Department were to eliminate advance consent without providing an immediate means of furnishing the required notifications to the Department. </P>
                    <P>First, flight schools will be harmed economically over the course of the 60 days that might be expected to elapse were this rule published as a proposed, rather than an interim, rule. Almost all aliens coming to this country who seek training in the operation of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more will use aircrew-training simulators, and a significant proportion of simulator time is used by aliens eligible for expedited processing pursuant to this interim final rule. A new simulator costs between $5.5 million and $19 million each, and therefore must generate substantial revenue to return a profit for a flight school. There are approximately 700 simulators in the United States. Financial difficulties accruing to Providers from lost opportunities due to restrictions on training aliens are confirmed by Pan Am International Flight Academy in Miami, Florida. In addition to the revenue they generate, simulators support the employment of numerous flight school employees. Simulators also support substantial demand for overnight accommodations, meals, and transportation, and related employment. The direct and indirect losses to the national economy caused by a 60-day delay in the effective date of this rule would be substantial. </P>
                    <P>Second, the training delays have direct adverse effects on air carriers and their ability to conduct their business. As discussed above, much of the training conducted by Providers to aliens is in the form of recurrent training offered to experienced pilots who are currently flying into and out of the United States. The Department has estimated that 50,500 aliens will be subject to the expedited processing provisions implemented in this rule. Although the requirements for recertification vary, the Department estimated that these 50,500 aliens will need to take recurrent training, on average, approximately three times each year. This suggests that an average of approximately 12,625 pilots may risk losing their current status for lack of the required recurrent training every month that the publication of an effective rule is delayed. The potential loss of the services of this number of pilots and flight crew would have a substantial negative effect on the aviation industry. Information provided by the industry reflects that some 5-10% of pilots employed by United States carriers are aliens. If these individuals were to lose their current flight status and be unable to fly, a loss in revenue could be expected. </P>
                    <P>Third, the domestic airplane manufacturing industry also is affected by the notification requirements of section 113 of ATSA. According to the FAA, the Commerce Department, and the industry, large purchase contracts of domestic airplane manufacturers involve not only the sale of aircraft, but also the training of pilots in the use of such aircraft. Indeed, according to one industry source, a contract for the sale of a large aircraft includes, in every instance, a certain amount of “entitlement training.” If overseas buyers are deterred from purchasing planes manufactured in the United States because they cannot have their pilots trained in the operation of such aircraft, expected losses would be severe. </P>
                    <P>Fourth, a delay in the effective date of a rule providing expedited processing for the three categories of aliens also would be contrary to the public's interest in aviation safety. Aviation training may be furnished outside the United States by flight schools not subject to section 113. Therefore, the lack of an effective rule would serve to encourage aliens who otherwise would be trained in the United States to seek training elsewhere. That decision not only risks the economic well being of domestic Providers, but increases the risk that these aliens would be trained by lower quality foreign flight schools that do not comply with FAA regulations. It clearly is in the interest of public safety for pilots to be trained by Providers regulated by the FAA. </P>
                    <P>Moreover, aliens in the three categories that would end up being trained by non-FAA regulated flight schools would avoid the risk assessments to which they would be subject if they sought training by Providers pursuant to these regulations. The loss of an opportunity to perform a risk assessment could mean that the Department would have no record of an attempt to seek training by an alien with ties to terrorism. </P>
                    <P>
                        Additionally, a delay in issuing a rule allowing current pilots to take training would discourage these pilots from seeking to improve and refresh their piloting skills. In addition, if pilots are unable to complete their recurrent training, the United States air carriers employing those pilots may be required under the laws and regulations governing the aviation industry to ground those current pilots, depending upon their individual circumstances, from flying into United States airspace until their recurrent training can be completed. 
                        <E T="03">See</E>
                         14 CFR part 121 and part 135. In turn, that action would cause the air carriers to begin to experience a shortage of available pilots. 
                    </P>
                    <P>Fifth, delay in the implementation of a notification process for aliens in the three categories also would injure the United States' military interests and would have a significant harmful effect on its foreign relations. The rulemaking requirements of 5 U.S.C. 553 do not apply to rules that involve “a military or * * * foreign affairs function of the United States.” 5 U.S.C. § 553(a). A number of the aliens subject to section 113 are being trained pursuant to agreements with the governments of other countries for both economic and military reasons. Indeed, this interim rule provides for expedited processing for a category of foreign military pilots. The delay in implementing this rule with respect to such pilots will have an increasingly serious adverse impact on the military interests and foreign affairs of the United States. </P>
                    <P>
                        The Department has consulted with the FAA and considered comments from representatives of the aviation industry 
                        <PRTPAGE P="41144"/>
                        during its development of a notification process. While the Department is soliciting further comments from the public regarding this interim rule, the Department believes, for all the foregoing reasons, that it would be contrary to the public's interest to issue this regulation as a proposed rule at this time. 
                    </P>
                    <P>Finally, the Department also has good cause to issue this interim rule with an immediate effective date, in accordance with 5 U.S.C. 553(d). As set forth above, the immediate publication of these regulations is in the public interest because it will prevent the imposition of burdens on the aviation industry, the economy, and the public in general that would occur were the advance consent revoked without the expedited processing made available through this interim final rule. The immediate publication of the rule also will limit a serious negative impact on military interests and foreign affairs of the United States. Because additional delay is contrary to the public interest, there is good cause under 5 U.S.C. 553(d) to make this rule effective as of June 14, 2002. </P>
                    <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                    <P>In accordance with the Regulatory Flexibility Act (5 U.S.C. 605(b)), the Attorney General, by approving this regulation, certifies that this rule will have a significant economic impact on a substantial number of small entities. Although the overall economic impact of this regulation will be beneficial toward small entities, the Department has prepared the following initial Regulatory Flexibility Act analysis in accordance with 5 U.S.C. 603. </P>
                    <P>The small entities affected by this rule include virtually all Providers furnishing flight instruction to aliens in the operation of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more. Pursuant to section 113 of ATSA, Providers are prohibited from furnishing any instruction to such aliens until the Attorney General is able to provide a means for determining whether the alien presents a risk to aviation or national security. Because this prohibition was so recently enacted, the Department is not aware of any studies or data detailing its effect on small entities. </P>
                    <P>The purpose of this rule is to provide a mechanism by which Providers may instruct aliens deemed by the Attorney General not to present a risk to aviation or national security as a result of the risk assessment conducted pursuant to section 113 of ATSA. This regulation will help the affected Providers to furnish instruction to most of the aliens in categories described in the Second Notice who had been receiving flight instruction. Thus, this regulation will have a beneficial effect on small businesses. The only costs incurred by Providers complying with this regulation will be the minimal costs they incur when providing the required notification to the Attorney General. </P>
                    <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995 </HD>
                    <P>This rule will not result in the expenditure by state, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more in one year, and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995. </P>
                    <HD SOURCE="HD1">Small Business Regulatory Enforcement Fairness Act of 1996 </HD>
                    <P>This rule is not a major rule as defined by section 251 of the Small Business Regulatory Enforcement Act of 1996. 5 U.S.C. 804. This rule will not result in an annual effect on the economy of $100 million or more; a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation; or on the ability of United States-based companies to compete with foreign-based companies in domestic and export markets. </P>
                    <HD SOURCE="HD1">Executive Order 12866 </HD>
                    <P>This rule is considered by the Department of Justice to be a significant regulatory action under Executive Order 12866, section 3(f), Regulatory Planning and Review. Accordingly, this regulation has been submitted to the Office of Management and Budget (“OMB”) for review. </P>
                    <HD SOURCE="HD1">Paperwork Reduction Act of 1995 </HD>
                    <P>The Department of Justice has submitted the following information collection requests to the Office of Management and Budget for review and approval in accordance with the Paperwork Reduction Act of 1995. This information collection has been approved and assigned OMB Control Number 1105-0074. As part of this information collection, the Office of Management and Budget has approved an emergency revision to this information collection. The proposed information collections are published to obtain comments from the public and affected agencies. Comments are encouraged and will be accepted for sixty days. This process is conducted in accordance with 5 CFR 1320.10. </P>
                    <P>If you have comments on the estimated public burden or associated response time, suggestions, or need a copy of one of the proposed information collection instruments with instructions or additional information, please contact Aviation Training Security; U.S. Department of Justice; 950 Pennsylvania Avenue, NW., Washington, DC 20530. Written comments and suggestions from the public and affected agencies concerning the proposed collections of information are encouraged. Your comments should address one or more of the following four points: </P>
                    <P>(1) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; </P>
                    <P>(2) Whether the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used, is accurate; </P>
                    <P>(3) How to enhance the quality, utility, and clarity of the information to be collected, and </P>
                    <P>
                        (4) How to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                        <E T="03">e.g.</E>
                        , permitting electronic submission of responses. 
                    </P>
                    <P>The following is an overview of this information collection: </P>
                    <P>
                        (1) 
                        <E T="03">Type of information collection:</E>
                         Revision of a currently approved collection. 
                    </P>
                    <P>
                        (2) 
                        <E T="03">The title of the form/collection:</E>
                         Flight Training Candidate Checks Program. 
                    </P>
                    <P>
                        (3) 
                        <E T="03">The agency form number, if any, and the applicable component of the Department sponsoring the collection:</E>
                         FTTTF-2; Foreign Terrorist Tracking Task Force, Aviation Training Security. 
                    </P>
                    <P>
                        (4) 
                        <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>
                         Primary: Federal Government—Federal Aviation Administration Flight Standards District Offices; Business or other for-profit—U.S.-based flight training providers offering instruction on the operation of aircraft having a maximum certificated takeoff weight of 12,500 pounds or more; Individuals—aliens seeking flight training in the United States on the operation of aircraft having a maximum certificated takeoff weight of 12,500 pounds or more. This information is being collected pursuant to section 113 of the Aviation and Transportation 
                        <PRTPAGE P="41145"/>
                        Security Act so that the Attorney General or his designee can determine the risk presented to aviation or national security by a foreign national receiving flight training in the United States. 
                    </P>
                    <P>
                        (5) 
                        <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond/reply:</E>
                         There are 86 Flight Standards District Offices in the United States. Representatives of each of these offices will log approximately one hour per year per office on the system covered by this notice. Although 83,000 flight training providers are authorized to furnish aviation training, the FAA estimates that only 10,000 of those offer training on aircraft subject to regulation by section 113 of the Aviation and Transportation Security Act. Projections for the annual number of alien applicants to the system vary from 3,000 to 50,000 (excluding those eligible for expedited review), but for purposes of estimation, the Department contends that some 50,500 candidates are expected to qualify for expedited review; Providers will submit form FTTTF-2 an average of three times per year for each of these candidates. It is estimated that only two minutes will be required from Providers for each submission of FTTTF-2. 
                    </P>
                    <P>
                        (6) 
                        <E T="03">An estimate of total public burden (in hours) associated with the collection:</E>
                         The total public burden to Flight Standards District Offices, flight training providers, and alien applicants for flight training subject to this regulation will be approximately 5,050 hours per year. 
                    </P>
                    <P>If additional information is required contact: Brenda E. Dyer, Department Deputy Clearance Officer, United States Department of Justice, Information Management and Security Staff, Justice Management Division, Suite 1600, Patrick Henry Building, 601 D Street NW., Washington, DC 20530. </P>
                    <HD SOURCE="HD1">Executive Order 13132 </HD>
                    <P>This rule will not have a substantial direct effect on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with section 6 of Executive Order 13132, it is determined that this rule does not have sufficient Federalism implications to warrant the preparation of a Federalism summary impact statement. </P>
                    <HD SOURCE="HD1">Executive Order 12988 </HD>
                    <P>This final rule meets the applicable standards set forth in sections 3(a) and 3(b)(2) of Executive Order 12988. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 28 CFR Part 105 </HD>
                        <P>Administrative practice and procedure, Airmen, Flight instruction, Risk Assessments, Reporting and recordkeeping requirements, Security measures.</P>
                    </LSTSUB>
                    <REGTEXT TITLE="28" PART="105">
                        <AMDPAR>Accordingly, chapter I of title 28 of the Code of Federal Regulations is amended by adding a new part 105 to read as follows: </AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 105—SECURITY RISK ASSESSMENTS </HD>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart A—[Reserved] </HD>
                            </SUBPART>
                            <CONTENTS>
                                <SUBPART>
                                    <HD SOURCE="HED">Subpart B—Aviation Training for Aliens and Other Designated Individuals </HD>
                                    <SECHD>Sec. </SECHD>
                                    <SECTNO>105.10 </SECTNO>
                                    <SUBJECT>Definitions, purpose, and scope. </SUBJECT>
                                    <SECTNO>105.11 </SECTNO>
                                    <SUBJECT>Individuals not requiring a security risk assessment. </SUBJECT>
                                    <SECTNO>105.12 </SECTNO>
                                    <SUBJECT>Notification for candidates eligible for expedited processing. </SUBJECT>
                                </SUBPART>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P>Section 113 of Public Law 107-71, 115 Stat. 622 (49 U.S.C. 44939). </P>
                            </AUTH>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Aviation Training for Aliens and Other Designated Individuals </HD>
                                <SECTION>
                                    <SECTNO>§ 105.10 </SECTNO>
                                    <SUBJECT>Definitions, purpose, and scope. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Definitions.</E>
                                    </P>
                                    <P>
                                        (1) 
                                        <E T="03">ATSA</E>
                                         means the Aviation and Transportation Security Act, Pub. L. 107-71. 
                                    </P>
                                    <P>
                                        (2) 
                                        <E T="03">Provider</E>
                                         means a person or entity subject to regulation under Title 49 Subtitle VII, Part A, United States Code. This definition includes individual training providers, training centers, certificated carriers, and flight schools. Virtually all private providers of instruction in the operation of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more are covered by section 113 of ATSA and are therefore subject to this rule. Providers located in countries other than the United States are included in this definition to the extent that they are providing training leading to a United States license, certification, or rating. Providers located in countries other than the United States who are providing training that does not lead to a United States license, certification, or rating are not included in this definition. When the Department of Defense or the U.S. Coast Guard, or an entity providing training pursuant to a contract with the Department of Defense or the U.S. Coast Guard, provides training for a military purpose, such training is not subject to FAA regulation and therefore these entities, when providing such training, are not “person[s] subject to regulation under this part” within the meaning of section 113. 
                                    </P>
                                    <P>
                                        (3) 
                                        <E T="03">Candidate</E>
                                         means any person who is an alien as defined in section 101(a)(3) of the Immigration and Nationality Act, 8 U.S.C. 1101(a)(3) who seeks training in the operation of an aircraft with a maximum certificated takeoff weight of 12,500 pounds or more from a Provider. 
                                    </P>
                                    <P>
                                        (4) 
                                        <E T="03">Certificates with ratings recognized by the United States</E>
                                         means a valid certificate with ratings issued by the United States, or a valid foreign license issued by a member of the Assembly of the International Civil Aviation Organization, as established by Article 43 of the Convention on International Civil Aviation. 
                                    </P>
                                    <P>
                                        (b) 
                                        <E T="03">Purpose and scope.</E>
                                    </P>
                                    <P>(1) Section 113 of ATSA prohibits Providers from furnishing aviation instruction to candidates on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more without the prior notification of the Attorney General. The purpose of this notification is to allow the Attorney General to determine whether such an individual presents a risk to aviation or national security before flight instruction may begin. The Department believes that it is unnecessary to make a candidate wait for 45 days in order to begin training if the Department has completed its risk assessment. Therefore, after providing the required notification to the Attorney General as described in this subpart, the Provider may begin instruction of a candidate if the Attorney General has informed the Provider that the candidate does not present a risk to aviation or national security as a result of the risk assessment conducted pursuant to section 113 of ATSA. If the Attorney General does not provide either an authorization to proceed with training or a notice to deny training within 45 days after receiving the required notification, the Provider may commence training at that time. All candidates must show a valid passport establishing their identity to a Provider before commencing training. </P>
                                    <P>(2) In the event the Attorney General subsequently determines that a candidate being trained does, in fact, present a risk to aviation or national security and that training should be denied, the Attorney General will instruct the Provider to terminate training. </P>
                                    <P>
                                        (3) Providing false information or otherwise failing to comply with section 113 of ATSA may present a threat to aviation or national security and is subject to both civil and criminal sanctions. The United States will take 
                                        <PRTPAGE P="41146"/>
                                        all necessary legal action to deter and punish violations of this section. 
                                    </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 105.11 </SECTNO>
                                    <SUBJECT>Individuals not requiring a security risk assessment. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Citizens and nationals of the United States.</E>
                                         A citizen or national of the United States is not subject to section 113 of ATSA. A Provider must determine whether a prospective trainee is a citizen or national of the United States prior to providing instruction on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more. To establish United States citizenship or nationality, the prospective trainee must show the Provider from whom he or she seeks training any of the following documents as proof of United States citizenship or nationality: 
                                    </P>
                                    <P>(1) A valid, unexpired United States passport; </P>
                                    <P>(2) An original or government-issued certified birth certificate with raised seal documenting birth in the United States or one of its territories, together with a government-issued picture identification of the individual named in the birth certificate; </P>
                                    <P>(3) An original United States naturalization certificate with raised seal, Form N-550 or Form N-570, together with a government-issued picture identification of the individual named in the certificate; </P>
                                    <P>(4) An original certification of birth abroad with raised seal, Form FS-545 or Form DS-1350, together with a government-issued picture identification of the individual named in the certificate; </P>
                                    <P>(5) An original certificate of United States citizenship with raised seal, Form N-560 or Form N-561, together with a government-issued picture identification of the individual named in the certificate; or </P>
                                    <P>(6) In the case of training provided to a federal employee (including military personnel) pursuant to a contract between a federal agency and a Provider, the agency's written certification as to its employee's United States citizenship/nationality, together with the employee's government-issued credentials or other federally-issued picture identification. </P>
                                    <P>(b) [Reserved] </P>
                                </SECTION>
                                <SECTION>
                                    <SECTNO>§ 105.12 </SECTNO>
                                    <SUBJECT>Notification for candidates eligible for expedited processing. </SUBJECT>
                                    <P>
                                        (a) 
                                        <E T="03">Expedited processing.</E>
                                         The Attorney General has determined that providing aviation training to certain categories of candidates is not likely to present a risk to aviation or national security because of the aviation training already possessed by these individuals or because of risk assessments conducted by other agencies. Therefore, the following categories of candidates are eligible for expedited processing: 
                                    </P>
                                    <P>(1) Foreign nationals who are current and qualified as pilot in command, second in command, or flight engineer with respective certificates with ratings recognized by the United States for aircraft with a maximum certificated takeoff weight of 12,500 pounds or more, or who are currently employed and qualified by U.S. air carriers as pilots on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more; </P>
                                    <P>(2) Commercial, governmental, corporate, or military pilots of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more who must receive familiarization training on a particular aircraft in order to transport it to the purchaser or recipient, provided that the training provided is limited to familiarization (familiarization training is limited to that required to become proficient in configurations and variations of an aircraft and does not include initial qualification or type rating for an aircraft); or </P>
                                    <P>(3) Military or law enforcement personnel who must receive training on a particular aircraft given by the United States to a foreign government pursuant to a draw-down authorized by the President under section 506(a)(2) of the Foreign Assistance Act of 1961, as amended (22 U.S.C. 2318(a)(2)), provided that the training provided be limited to familiarization. </P>
                                    <P>
                                        (b) 
                                        <E T="03">Notification.</E>
                                         Before a Provider may conduct training for a candidate eligible for expedited processing under paragraph (a) of this section, the Provider must submit the following information to the Department: 
                                    </P>
                                    <P>(1) The full name of the candidate; </P>
                                    <P>(2) An unique student identification number created by the Provider as a means of identifying records concerning the candidate; </P>
                                    <P>(3) Date of birth; </P>
                                    <P>(4) Country of citizenship; </P>
                                    <P>(5) Passport issuing authority; </P>
                                    <P>(6) Dates of training; and </P>
                                    <P>(7) The category of expedited processing under paragraph (a) of this section for which the candidate qualifies. </P>
                                    <P>
                                        (c) 
                                        <E T="03">Commencement of training.</E>
                                         The notification must be provided electronically to the Department by the Provider in the specific format and by the specific means identified by the Department. Notification must be made by e-mail. Only e-mail sent from an e-mail address registered as a Provider will be accepted. Specific details about the mechanism for the notification will be made available by the Department or the FAA. After the complete notification is furnished to the Department, the Provider may commence training the candidate as soon as the Provider receives a response from the Department that the individual does not present a risk to aviation or national security as a result of the risk assessment conducted pursuant to section 113 of ATSA and the candidate presents a valid passport establishing his or her identity to the Provider. Receipt of this response by the Department will be deemed approval by the Department to commence training. If the Department later determines that the candidate presents a risk to aviation or national security, it will immediately notify the Provider to cease training. A Provider so notified shall immediately cease providing any training to the person, regardless of whether or in what manner such training had been authorized. The Provider who submitted the candidate's identifying information will be responsible for ensuring that the training is promptly halted, regardless of whether another Provider is currently training the candidate. 
                                    </P>
                                    <P>
                                        (d) 
                                        <E T="03">Records.</E>
                                         When a Provider conducts training for a candidate eligible for expedited processing, the Provider must retain records to document how the Provider made the determination that the candidate was eligible. The Provider also must retain certain identifying records regarding the candidate, including date of birth, place of birth, passport issuing authority, and passport number. The Provider must be able to reference these records by the unique student identification number provided to the Department pursuant to this section. Providers also are encouraged to maintain photographs of all candidates trained by the Provider. Such records should be maintained for at least three years following the conclusion of training by the Provider. The Provider also should be able use the unique student identification number to cross-reference any other documentation that the FAA may require the Provider to retain regarding the candidate. 
                                    </P>
                                </SECTION>
                            </SUBPART>
                        </PART>
                    </REGTEXT>
                    <SIG>
                        <DATED>Dated: June 11, 2002 </DATED>
                        <NAME>John Ashcroft, </NAME>
                        <TITLE>Attorney General. </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 02-15060 Filed 6-11-02; 5:07 pm] </FRDOC>
                <BILCOD>BILLING CODE 4410-19-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="41147"/>
                    <AGENCY TYPE="S">DEPARTMENT OF JUSTICE </AGENCY>
                    <CFR>28 CFR Part 105 </CFR>
                    <DEPDOC>[OAG 104; AG Order No. 2591-2002] </DEPDOC>
                    <RIN>RIN 1105-AA80 </RIN>
                    <SUBJECT>Screening of Aliens and Other Designated Individuals Seeking Flight Training </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Department of Justice. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule with request for comments. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>Under section 113 of the Aviation and Transportation Security Act, certain aviation training providers subject to regulation by the Federal Aviation Administration (“FAA”) are prohibited from providing training to aliens and other designated individuals in the operation of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more, unless the aviation training provider notifies the Attorney General of the identity of the alien seeking training and the Attorney General does not direct the aviation training provider within 45 days that the alien presents a risk to aviation or national security. This proposed rule would implement a process by which aviation training providers would provide the required notification, the Attorney General would respond, and the aviation training providers would begin or resume instruction for candidates who do not present a to aviation and national security. </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Written comments on the proposed regulation must be submitted on or before July 15, 2002. Written comments only on the proposed information collection must be submitted on or before August 13, 2002. </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>Please submit written comments to Aviation Training Security, U.S. Department of Justice, 950 Pennsylvania Avenue, NW, Washington, DC 20530. </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Steven C. McCraw, Director, Foreign Terrorist Tracking Task Force, U.S. Department of Justice, Telephone (703) 414-9535. </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        On November 19, 2001, Congress enacted the Aviation and Transportation Security Act (“ATSA”), Pub. L. No. 107-71. Upon enactment, section 113 of ATSA, 49 U.S.C. 44939, imposed notification and reporting requirements on certain persons who provide aviation training to aliens and other specified individuals. By its terms, section 113 of ATSA applies to anyone “subject to regulation under this part.” The reference to “this part” refers to Title 49, Subtitle VII, Part A, of the U.S. Code, entitled “Air Commerce and Safety.” Any entity regulated by any portion of Part A, comprising section 40101 through section 46507 of Title 49, must comply with the requirements of section 113 of ATSA. Persons subject to regulation under these provisions include individual training providers, training centers, certificated carriers, and flight schools (hereinafter collectively referred to as “Providers”). Thus, virtually all private flight instructors in the United States are covered by section 113 of ATSA and therefore are subject to this rule. In addition, section 113 of ATSA does not exclude private providers of flight instruction located in countries outside the United States if these providers are authorized by the FAA to award United States licenses, certificates, or ratings. Providers outside the United States are not covered with regard to a particular instance of training, however, if that training will not lead to an FAA license, certificate or rating, regardless of whether the provider also has authority to issue such licenses, certificates or ratings. When the Department of Defense or the U.S. Coast Guard, or an entity providing training pursuant to a contract with the Department of Defense or the U.S. Coast Guard, provides training for a military purpose, such training is not subject to FAA regulation and therefore these entities, when providing such training, are not “person[s] subject to regulation under this part” within the meaning of section 113. 
                        <E T="03">See, e.g.,</E>
                         49 U.S.C. 44701(a) (Administrator's jurisdiction extends to promoting “safe flight of civil aircraft in air commerce”); 14 CFR part 61 (provisions concerning certification of pilots, flight instructors, and ground instructors do not apply where training is not for purpose of FAA certification). 
                    </P>
                    <P>Failure to comply with this rule may result in penalties being imposed in conformance with section 140(d) of ATSA. Pursuant to 49 U.S.C. 46301, persons violating this section are subject to civil penalties. </P>
                    <P>Pursuant to section 113 of ATSA, if an alien (defined in 8 U.S.C. 1101(a)(3) as “any person not a citizen or national of the United States”) or other person specified by the Under Secretary of Transportation for Security (collectively “candidates”) seeks instruction from a Provider in the operation of an aircraft with a maximum certificated takeoff weight of 12,500 pounds or more, the Provider must notify the Attorney General and must submit identifying information for the candidate in such form as the Attorney General may require in order to initiate a security risk assessment by the Department of Justice (the “Department”). </P>
                    <P>Once the Attorney General has been notified and all the required identifying information has been submitted, the Attorney General then has 45 days to inform the Provider that the candidate should not be given the requested training because he or she presents a risk to aviation or national security. If the Attorney General does not indicate that the candidate presents a risk to aviation or national security by the end of this 45-day review period, then the Provider may proceed with training. The Attorney General, however, may interrupt the training if he later determines that the candidate presents a risk to aviation or national security. The Attorney General has delegated his authority under section 113 of ATSA to conduct security risk assessments of individuals seeking flight training and to determine whether such individuals present a risk to aviation or national security to the Director of the Foreign Terrorist Tracking Task Force (“FTTTF”). </P>
                    <P>The notification requirement applies to aliens as set forth above. As also noted, the Under Secretary of Transportation for Security may specify other individuals for whom the Department should conduct security risk assessments; at this time, however, no other individuals have been specified. In the event that the Under Secretary of Transportation for Security specifies other individuals, these individuals will be subject to the requirements contained in this proposed rule. </P>
                    <P>
                        The Department recognized that section 113 of ATSA became immediately effective, and that Providers had been forced to suspend the training of aliens covered by ATSA pending the implementation of the process for notification to the Attorney General and the determination by the Attorney General whether the individual seeking training presents a risk to aviation or national security. The Department issued a notice on January 16, 2002 (“First Advance Consent Notice”) that stated that the Department was granting a provisional advance consent for the training of three categories of aliens, based on an initial determination they did not appear to present a risk to aviation or national security. 67 FR 2238 (Jan 16, 2002). The First Advance Consent Notice was subsequently superseded, and the categories of advance consent modified in a notice effective February 8, 2002 (“Second Advance Consent Notice” or 
                        <PRTPAGE P="41148"/>
                        “Second Notice”). 67 FR 6051 (Feb. 8, 2002). 
                    </P>
                    <P>The Department also published an interim final rule with a request for comments (“interim rule”) that rescinded the Second Advance Consent Notice. The interim rule, published concurrently with this rule, implemented an expedited processing procedure for aliens in two of the four categories listed in the Second Notice and added one additional category. </P>
                    <P>This proposed rule addresses those candidates not covered by the concurrently published interim rule and provides the process by which Providers may notify the Attorney General with respect to candidates who are not within any of the expedited processing categories. Providers may not train candidates in the operation of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more unless they have complied with this rule, or unless the candidate is included within a category of expedited processing and the Provider has been notified by the Department that the candidate has been found not to present a risk to aviation or national security as result of the risk assessment conducted pursuant to section 113 of ATSA. Because these candidates may present a greater risk to aviation or national security than candidates eligible for expedited processing, Providers planning to train these candidates will need to furnish more detailed information, including fingerprints, to the Department. </P>
                    <HD SOURCE="HD1">Availability of Flight Training Candidate Checks Program Notification System for Review </HD>
                    <P>
                        The notification system for pilots not eligible for expedited processing will be one of the first electronic-based systems developed by the Department. The Department wants to make sure that the public and the aviation industry had an opportunity to comment on this interface. As a result, the 
                        <E T="03">Flight Training Candidate Checks Program</E>
                         proposed notification system has been made available for public review. The public is welcome to access the system, but should refrain from submitting any data. No candidate forms should be submitted through this notification system until a final rule implementing the system is in effect. The submission of identifying applicant information through this system will not constitute notification of the Attorney General as required by section 113 of ATSA. Any notifications submitted to the Department for pilots eligible for expedited processing should be provided in accordance with the interim rule published concurrently with this proposed rule. 
                    </P>
                    <HD SOURCE="HD1">Risk Assessments for Aliens Not Granted Expedited Processing and Other Persons Specified by the Under Secretary of Transportation for Security </HD>
                    <P>
                        Providers wishing to train aliens who do not fall within a category of expedited processing, or any other individuals specified by the Under Secretary of Transportation for Security, will need to submit detailed identifying information to the Department before providing training. The information must be provided to the Department via electronic submission on the form titled 
                        <E T="03">Flight Training Candidate Checks Program,</E>
                         as described in section 105.13 of this rule. This form requests the submission of certain identifying data, including the covered candidate's name, address, and physical characteristics; various government-issued identification numbers; information regarding the source of the funds to pay for instruction; information about immediate family members; occupational and education information; and information regarding citizenship. The form is designed to be the first part of a two-part process; candidates also will be required to submit a set of fingerprints. 
                    </P>
                    <P>Limiting submissions to electronic submissions will speed the processing of submissions, and aid the Department's ability to audit the process. In addition, the Department will be able to implement controls to help ensure the integrity of the submissions. A paper-based system likely would result in more errors and vastly increased processing times, thus further burdening both the flight instruction industry and candidates. </P>
                    <P>
                        Certificated training Providers must receive initial access to the system through the FAA. Providers will be required to make appointments to register through their local Flight Standards District Offices. Upon registration, Providers will be e-mailed a password for accessing the system and verifying applicant submissions. The Department believes that most, if not all, Providers furnishing instruction on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more already possess Internet access. Those Providers not possessing an e-mail address will need to obtain one if they wish to utilize this process. The Department also notes that free Internet access is available at many public facilities, such as public libraries, and that free e-mail services are available from some Internet Service Providers. The Department seeks comments from Providers and candidates on the impact of the requirement to provide notifications to the Department electronically. In order to reduce the potential burden on Providers, candidates may complete the on-line form themselves. After the candidate completes the form, the Provider must verify that the candidate is a 
                        <E T="03">bona fide</E>
                         applicant for instruction and complete the submission process. 
                    </P>
                    <HD SOURCE="HD1">Fingerprinting Requirements for Candidates </HD>
                    <P>Aliens who do not fall within a category of expedited processing, and other individuals specified by the Under Secretary of Transportation for Security, also must submit fingerprints to the Federal Bureau of Investigation (“FBI”) prior to the commencement of instruction as part of the identification process. These fingerprints must be taken by federal, state, or local law enforcement agencies, or any other official approved by the Director of the FTTTF. The fingerprints must be taken under the direct observation of the official. Procedures by which such fingerprints may be taken currently exist in the states for many other purposes. The Department, however, welcomes comments regarding whether or how candidates might be allowed to have their fingerprints taken outside the United States. </P>
                    <P>The fingerprints must be recorded on fingerprint cards distributed by the Director of the FTTTF for that purpose, or processed by other means approved by the Director of the FTTTF. The fingerprint submissions must be forwarded to the FBI in a manner specified by the Director of the FTTTF. The Provider and the official taking the fingerprints will receive, through the FTTTF, explicit instructions for fingerprint submissions. Officials taking fingerprints should ensure that any fingerprints provided to the FBI are not placed within the control of the candidate or Provider at any time. Candidates must provide appropriate identification, including a passport if the candidate is an alien, at the time of fingerprinting. </P>
                    <P>
                        Candidates submitting fingerprints must pay for the costs associated with taking and processing the fingerprints in a form and manner approved by the FBI. This payment process may vary depending upon where the fingerprints are taken. In accordance with Pub. L. No. 101-515, as amended (28 U.S.C. 534 note), the Director of the FBI may establish and collect fees to process fingerprint identification records and name checks for certain purposes, including non-criminal justice and licensing purposes. In addition to the 
                        <PRTPAGE P="41149"/>
                        cost to the FBI for conducting its review, other fees may be imposed, including the cost of taking the fingerprints and the cost of processing the fingerprints and submitting them to the FBI for review. The federal component of this fee currently is $31. Depending on the entity taking the fingerprints, however, an additional fee also may be imposed for taking and submitting the fingerprints to the FBI. Because the total fee may vary by state, the candidate must check with the entity taking the fingerprints to determine the applicable total fee. This payment must be made at the designated rate for each set of fingerprints submitted. The procedure for taking and submitting fingerprints is described in section 105.13 of this rule. Fingerprints will be considered submitted for purposes of this rule once the Provider has provided on-line notification through the system to the Department that the candidate's fingerprints have been taken in accordance with section 105.13 of this rule. 
                    </P>
                    <P>The Department recognizes that some Providers furnish training to candidates at facilities located outside the United States. In those instances, it may be impracticable for a candidate to be fingerprinted in accordance with section 105.13 of this rule. Therefore, on a case-by-case basis, a Provider wishing to train a candidate outside the United States may request a waiver of the fingerprinting requirements from the FTTTF. The waiver request must detail why it is impracticable for the alien to be fingerprinted in accordance with section 105.13. </P>
                    <HD SOURCE="HD1">Attorney General Review </HD>
                    <P>After the Provider submits all the information that is required under this rule, including fingerprints, the Attorney General will have 45 days to conduct a security risk assessment. The Department recognizes the economic burden imposed on Providers by the 45-day waiting period for those candidates who are subject to this notification requirement. The Department believes that it is unnecessary to make a candidate wait for the full 45-day period in order to begin training if the Department has completed its risk assessment. Accordingly, in most cases, the Department expects that the Provider will be authorized to commence training (or instructed to deny it) sooner than the 45 days allowed by the statute. In the event that the Attorney General does not instruct the Provider to deny training within 45 days of the submission and verification of all the information required under this rule (including the submission of fingerprints), the Provider may commence the requested training. </P>
                    <P>The information provided to the Department will be used to confirm the identity of the individuals being trained and to help assess the risk presented by the candidate. In the event the Department subsequently determines that a candidate being trained does, in fact, present a risk to aviation or national security and that training should be denied, the Department will notify the Provider to terminate training immediately. Appropriate measures will be taken with respect to any candidate who is determined to present a risk to aviation or national security or with respect to any candidate or Provider who knowingly or negligently provides false information to the Department. </P>
                    <HD SOURCE="HD1">Regulatory Procedures </HD>
                    <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                    <P>In accordance with the Regulatory Flexibility Act (5 U.S.C. 605(b)), the Attorney General, by approving this regulation, certifies that this rule will have a significant economic impact on a substantial number of small entities. Although the overall economic impact of this regulation will be beneficial toward small entities, the Department has prepared the following initial Regulatory Flexibility Act analysis in accordance with 5 U.S.C. 603. </P>
                    <P>The small entities affected by this rule include virtually all Providers furnishing flight instruction to aliens in the operation of aircraft with a maximum certificated takeoff weight of 12,500 pounds or more. Pursuant to section 113 of ATSA, Providers are prohibited from furnishing any instruction to such aliens until the Attorney General is able to provide a means for determining whether the alien presents a risk to aviation or national security. Because this prohibition was so recently enacted, the Department is not aware of any studies or data detailing its effect on small entities. Anecdotal evidence, however, suggests that while some entities may have experienced no decline in business, other entities estimate that they may have experienced as much as a 30% loss of income because they are not able to provide flight instruction to aliens. </P>
                    <P>The purpose of this rule is to provide a mechanism by which Providers may instruct aliens deemed by the Attorney General not to present a risk to aviation or national security as a result of the risk assessment conducted pursuant to section 113 of ATSA. This regulation will help the affected Providers to furnish instruction to aliens who had been unable to receive flight instruction since section 113 of ATSA was enacted. Thus, this regulation will have a beneficial effect on small businesses. The only costs incurred by Providers complying with this regulation will be the minimal costs they incur when providing the required notification to the Attorney General. </P>
                    <HD SOURCE="HD1">Unfunded Mandates Reform Act of 1995 </HD>
                    <P>This rule will not result in the expenditure by state, local and tribal governments, in the aggregate, or by the private sector, of $100 million or more in one year, and it will not significantly or uniquely affect small governments. Therefore, no actions were deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995. </P>
                    <HD SOURCE="HD1">Small Business Regulatory Enforcement Fairness Act of 1996 </HD>
                    <P>This rule is not a major rule as defined by section 251 of the Small Business Regulatory Enforcement Act of 1996. 5 U.S.C. 804. This rule will not result in an annual effect on the economy of $100 million or more; a major increase in costs or prices; or significant adverse effects on competition, employment, investment, productivity, innovation; or on the ability of United States-based companies to compete with foreign-based companies in domestic and export markets. </P>
                    <HD SOURCE="HD1">Executive Order 12866 </HD>
                    <P>This rule is considered by the Department of Justice to be a significant regulatory action under Executive Order 12866, section 3(f), Regulatory Planning and Review. Accordingly, this regulation has been submitted to the Office of Management and Budget for review. </P>
                    <HD SOURCE="HD1">Paperwork Reduction Act of 1995 </HD>
                    <P>The Department of Justice has submitted the following information collection requests to the Office of Management and Budget for review and approval in accordance with the Paperwork Reduction Act of 1995. This information collection has been approved and assigned OMB Control Number 1105-0074. The proposed information collections are published to obtain comments from the public and affected agencies. Comments are encouraged and will be accepted for sixty days. This process is conducted in accordance with 5 CFR 1320.10. </P>
                    <P>
                        If you have comments on the estimated public burden or associated response time, suggestions, or need a 
                        <PRTPAGE P="41150"/>
                        copy of one of the proposed information collection instruments with instructions or additional information, please contact Aviation Training Security; U.S. Department of Justice; 950 Pennsylvania Avenue, NW; Washington, DC 20530. Written comments and suggestions from the public and affected agencies concerning the proposed collections of information are encouraged. Your comments should address one or more of the following four points: 
                    </P>
                    <P>(1) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility; </P>
                    <P>(2) Whether the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used, is accurate; </P>
                    <P>(3) How to enhance the quality, utility, and clarity of the information to be collected, and </P>
                    <P>
                        (4) How to minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                        <E T="03">e.g.,</E>
                         permitting electronic submission of responses. 
                    </P>
                    <P>The following is an overview of this information collection: </P>
                    <P>
                        (1) 
                        <E T="03">Type of information collection:</E>
                         Revision of a currently approved collection. 
                    </P>
                    <P>
                        (2) 
                        <E T="03">The title of the form/collection:</E>
                         Flight Training Candidate Checks Program. 
                    </P>
                    <P>
                        (3) 
                        <E T="03">The agency form number, if any, and the applicable component of the Department sponsoring the collection:</E>
                         FTTTF-1; Foreign Terrorist Tracking Task Force, Aviation Training Security. 
                    </P>
                    <P>
                        (4) 
                        <E T="03">Affected public who will be asked or required to respond, as well as a brief abstract:</E>
                         Primary: Federal Government—Federal Aviation Administration Flight Standards District Offices; Business or other for-profit—U.S.-based flight training providers offering instruction on the operation of aircraft having a maximum certificated takeoff weight of 12,500 pounds or more; Individuals—aliens seeking flight training in the United States on the operation of aircraft having a maximum certificated takeoff weight of 12,500 pounds or more. This information is being collected pursuant to section 113 of the Aviation and Transportation Security Act so that the Attorney General or his designee can determine the risk presented to aviation or national security by a foreign national receiving flight training in the United States. 
                    </P>
                    <P>
                        (5) 
                        <E T="03">An estimate of the total number of respondents and the amount of time estimated for an average respondent to respond/reply:</E>
                         There are 86 Flight Standards District Offices in the United States. Representatives of each of these offices will log approximately one hour per year per office on the system covered by this notice. Although 83,000 flight training providers are authorized to furnish aviation training, the FAA estimates that only 10,000 of those offer training on aircraft subject to regulation by section 113 of the Aviation and Transportation Security Act. Projections for the annual number of alien applicants to the system vary from 3,000 to 50,000 (excluding those eligible for expedited review), but for purposes of estimation, the Department contends that an average of 26,000 candidates will apply annually using the primary form, FTTTF-1, and that on average these candidates will apply twice per year. Because entries subsequent to the first will take less time, the Department estimates that each alien applicant using FTTTF-1 will spend approximately 45 minutes on the system per year. 
                    </P>
                    <P>
                        (6) 
                        <E T="03">An estimate of total public burden (in hours) associated with the collection:</E>
                         The total public burden to Flight Standards District Offices, flight training providers, and alien applicants for flight training subject to this regulation will be approximately 19,500 hours per year. 
                    </P>
                    <P>If additional information is required contact: Brenda E. Dyer, Department Deputy Clearance Officer, United States Department of Justice, Information Management and Security Staff, Justice Management Division, Suite 1600, Patrick Henry Building, 601 D Street NW, Washington, DC 20530. </P>
                    <HD SOURCE="HD1">Executive Order 13132 </HD>
                    <P>This rule will not have a substantial direct effect on the States, on the relationship between the National Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with section 6 of Executive Order 13132, it is determined that this rule does not have sufficient Federalism implications to warrant the preparation of a Federalism summary impact statement. </P>
                    <HD SOURCE="HD1">Executive Order 12988 </HD>
                    <P>This final rule meets the applicable standards set forth in sections 3(a) and 3(b)(2) of Executive Order 12988. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 28 CFR Part 105 </HD>
                        <P>Administrative practice and procedure, Airmen, Flight instruction, Risk Assessments, Reporting and recordkeeping requirements, Security measures.</P>
                    </LSTSUB>
                    <PART>
                        <HD SOURCE="HED">PART 105—SECURITY RISK ASSESSMENTS </HD>
                        <STARS/>
                        <EXTRACT>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart B—Aviation Training for Aliens and Other Designated Individuals </HD>
                            </SUBPART>
                        </EXTRACT>
                        <P>1. The Authority citation continues to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>Section 113 of Public Law 107-71, 115 Stat. 622 (49 U.S.C. 44939). </P>
                        </AUTH>
                        <P>2. Amend § 105.10 by revising paragraph (a)(3) and paragraph (b)(1) to read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 105.10 </SECTNO>
                            <SUBJECT>Definitions, purpose, and scope. </SUBJECT>
                            <P>(a) * * * </P>
                            <P>
                                (3) 
                                <E T="03">Candidate</E>
                                 means any person seeking training in the operation of an aircraft with a maximum certificated takeoff weight of 12,500 pounds or more from a Provider who is either: 
                            </P>
                            <P>(i) An alien as defined in section 101(a)(3) of the Immigration and Nationality Act, 8 U.S.C. 1101(a)(3); or </P>
                            <P>(ii) Is within a class of persons as specified by the Under Secretary of Transportation for Security, pursuant to section 113(a) of ATSA, 49 U.S.C. 44939(a). </P>
                            <STARS/>
                            <P>(b) * * * </P>
                            <P>
                                (1) Section 113 of ATSA prohibits Providers from furnishing aviation instruction to candidates on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more without the prior notification of the Attorney General. The purpose of this notification is to allow the Attorney General to determine whether such an individual presents a risk to aviation or national security before flight instruction may begin. The Department believes that it is unnecessary to make a candidate wait for 45 days in order to begin training if the Department has completed its risk assessment. Therefore, after providing the required notification to the Attorney General as described in this subpart, the Provider may begin instruction of a candidate if the Attorney General has informed the Provider that the candidate does not present a risk to aviation or national security as result of the risk assessment conducted pursuant to section 113 of ATSA. If the Attorney General does not provide either an authorization to proceed with training or a notice to deny training within 45 days after receiving the required notification, the Provider may commence training at that time. All candidates, including those 
                                <PRTPAGE P="41151"/>
                                granted expedited processing in accordance with § 105.12, must show a valid passport establishing their identity to a Provider before commencing training. Candidates who are citizens or nationals of the United States, but who were required to provide notification to the Attorney General may present a valid United States picture driver's license in lieu of a passport. 
                            </P>
                            <STARS/>
                            <P>3. Amend § 105.11 by revising the introductory text to paragraph (a) and adding a new paragraph (b) to read as follows; </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 105.11 </SECTNO>
                            <SUBJECT>Individuals not requiring a security risk assessment. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Citizens and nationals of the United States.</E>
                                 A citizen or national of the United States is not subject to section 113 of ATSA, unless designated by the Under Secretary of Transportation for Security. A Provider must determine whether a prospective trainee is a citizen or national of the United States prior to providing instruction on aircraft with a maximum certificated takeoff weight of 12,500 pounds or more. To establish United States citizenship or nationality, the prospective trainee must show the Provider from whom he or she seeks training any of the following documents as proof of United States citizenship or nationality: 
                            </P>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Exception.</E>
                                 Notwithstanding paragraph (a) of this section, a Provider is required to provide notification to the Attorney General with respect to any candidates who are within a class of persons designated by the Under Secretary of Transportation for Security. Individuals specified by the Under Secretary of Transportation for Security will be identified by procedures developed by the Department of Transportation and are not eligible for expedited processing. 
                            </P>
                            <STARS/>
                            <P>4. Amend § 105.12 by revising the introductory text to paragraph (a) as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 105.12 </SECTNO>
                            <SUBJECT>Notification for candidates eligible for expedited processing. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Expedited processing.</E>
                                 The Attorney General has determined that providing aviation training to certain categories of candidates is not likely to present a risk to aviation or national security because of the aviation training already possessed by these individuals or because of risk assessments conducted by other agencies. Therefore, candidates determined by Providers to be eligible for expedited processing are subject to the notification requirements of this section, but do not have to comply with the more detailed notification requirements of section 105.13, unless the candidates are within a class of persons as designated by the Under Secretary of Transportation for Security. The following categories of candidates are eligible for expedited processing: 
                            </P>
                            <STARS/>
                            <P>5. Adding a new § 105.13 to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 105.13 </SECTNO>
                            <SUBJECT>Notification for candidates not eligible for expedited processing. </SUBJECT>
                            <P>
                                (a) A Provider must submit a complete 
                                <E T="03">Flight Training Candidate Checks Program</E>
                                 form and arrange for the submission of fingerprints to the Department in accordance with this section prior to providing flight training, except with respect to persons whom the Provider has determined, as provided in § 105.11 or § 105.12, are not subject to a security risk assessment or are eligible for expedited processing. A separate form must be submitted for each course or instance of training requested by a candidate. Where a Provider enlists the assistance of another Provider in training a candidate, no additional request need be submitted, as long as the specific instance of training has been approved. 
                            </P>
                            <P>
                                (b) The completed form should be sent to the Attorney General via electronic submission at 
                                <E T="03">https://www.flightschoolcandidates.gov/insdoc/index.html</E>
                                . No paper submissions of this form will be accepted. 
                            </P>
                            <P>(1) In order to ensure that such electronic submissions are made by Federal Aviation Administration (FAA) certificated training providers, Providers must receive initial access to the system through the FAA. Providers should register through their local Flight Standards District Offices. The FAA has decided that registration will be by appointment only. Upon registration, Providers will be sent (via electronic mail) an access password to use the system. </P>
                            <P>
                                (2) Candidates may complete the online form at 
                                <E T="03">https://www.flightschoolcandidates.gov/insdoc/index.html</E>
                                 to reduce the burden on the Provider. After the form has been completed by a candidate, it will be forwarded electronically to the Provider for verification that the candidate is a bona fide applicant. Verification by the Provider will be considered submission of the form for purposes of paragraph (a) of this section. In order to reduce the burden on the candidates, personal information only needs to be updated, rather than reentered, for each subsequent training request. 
                            </P>
                            <P>(c) Candidates also must submit fingerprints to the Federal Bureau of Investigation (FBI) as part of the identification process. These fingerprints must be taken by a federal, state, or local law enforcement agency, or any other official approved by the Director of the Foreign Terrorist Tracking Task Force. In the case of candidates seeking training from providers located in countries other than the United States, fingerprints may be taken by officials at the nearest United States embassy or consulate. Law enforcement agencies are not required to participate in this process, but their cooperation is strongly encouraged. Any officials taking fingerprints as part of the notification process must comply with the following requirements when taking and processing fingerprints to ensure the integrity of the process: </P>
                            <P>(1) Candidates must provide two forms of identification at the time of fingerprinting. In the case of aliens, one of the forms of identification must be the individual's passport; in the case of United States citizens or nationals, a valid photo driver's license issued in the United States may be submitted in lieu of a passport. </P>
                            <P>(2) The fingerprints must be taken under the direct observation of a government official; </P>
                            <P>(3) The fingerprints must be recorded on fingerprint cards distributed by the Director of the Foreign Terrorist Tracking Task Force for that purpose, or processed by other means approved by the Director of the Foreign Terrorist Tracking Task Force; </P>
                            <P>(4) The fingerprint submissions must be forwarded to the FBI in the manner specified by the Director of the Foreign Terrorist Tracking Task Force; </P>
                            <P>(5) Officials taking fingerprints should ensure that any fingerprints provided to the FBI are not placed within the control of the candidate or the Provider at any time; and </P>
                            <P>(6) Candidates must pay for all costs associated with taking and processing their fingerprints. </P>
                            <P>
                                (d) In accordance with Public Law 101-515, as amended, the Director of the FBI is authorized to establish and collect fees to process fingerprint identification records and name checks for certain purposes, including non-criminal justice and licensing purposes. In addition to the cost to the FBI for conducting its review, other fees may be imposed, including the cost of taking the fingerprints and the cost of processing the fingerprints and submitting them to the FBI for review. Because the total fee may vary by state, the candidate must check with the 
                                <PRTPAGE P="41152"/>
                                entity taking the fingerprints to determine the applicable total fee. This payment must be made at the designated rate for each set of fingerprints submitted. 
                            </P>
                            <P>(e) In some cases, candidates seeking training from Providers abroad may be unable to obtain fingerprints. If a Provider located in a country other than the United States determines that compliance with the fingerprint requirement is not practicable, it may request, in writing, a waiver of the requirement, on a case-by-case basis, by contacting the Foreign Terrorist Tracking Task Force, Aviation Industry Liaison. In such a case, the Foreign Terrorist Tracking Task Force will have discretion to grant the waiver; deny the waiver; or prescribe a reasonable alternative manner of complying with the fingerprint requirement. </P>
                            <P>(f) The 45-day review period by the Department will not start until all the required information has been submitted, including fingerprints. </P>
                            <P>6. Adding a new § 105.14 to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 105.14 </SECTNO>
                            <SUBJECT>Risk assessment for candidates not granted expedited processing. </SUBJECT>
                            <P>
                                (a) It is the responsibility of the Department of Justice to conduct a risk assessment for each candidate. The Department has made an initial determination that providing training to the aliens in the categories set forth in § 105.12(a) presents little risk to aviation or national security and therefore has established an expedited processing procedure for these aliens. Based on the information contained in each 
                                <E T="03">Flight Training Candidates Checks Program</E>
                                 form and the corresponding set of fingerprints, the Department will determine whether a candidate not granted expedited processing presents a risk to aviation or national security. 
                            </P>
                            <P>
                                (b) After submission of the 
                                <E T="03">Flight Training Candidate Checks Program</E>
                                 form by the Provider, the Department will perform an interim risk assessment. 
                            </P>
                            <P>(1) If the Department determines that a candidate does not present a risk to aviation or national security as a result of the interim risk assessment, the candidate and/or the Provider will be notified electronically that the candidate may proceed to the Provider to receive appropriate materials to complete the fingerprinting process described in § 105.13(c) and (d). The Provider's e-mail also will provide a toll-free telephone number through which “fingerprint packets” will be provided. </P>
                            <P>(2) If the Department determines that the candidate presents a risk to aviation or national security, when appropriate, it will notify the Provider electronically that training is prohibited. </P>
                            <P>(3) For each training request, the Department will have 45 days from the date on which all required information, including fingerprints, is submitted to conduct an appropriate risk assessment. Every effort will be made to respond to a training request in the briefest time possible. If no notification or authorization by the Department has occurred within 45 days of submission of all the required information, the Provider may proceed with the training, upon establishing the candidate's identity in accordance with paragraph (d) of this section. </P>
                            <P>(c) Providers must ascertain the identity of each candidate. For candidates who are not citizens or nationals of the United States, a Provider must inspect the candidate's passport to verify the candidate's identity before providing training; candidates who are citizens or nationals of the United States must present either a valid United States passport or a valid United States picture driver's license. If the candidate's identity cannot be verified, then the Provider cannot proceed with training. </P>
                            <P>(d) If, at any time after training has begun, the Department determines that a candidate subject to this section being trained by a Provider presents a risk to aviation or national security, when appropriate, the Department shall notify the Provider to cease training. A Provider so notified shall immediately cease providing any training to the person, regardless of whether or in what manner such training had been authorized. The Provider who submitted the candidate's identifying information will be responsible for ensuring that the training is promptly halted, regardless of whether another Provider is currently training the candidate. </P>
                            <P>(e) With regard to any determination as to an alien candidate's eligibility for training, when appropriate, the Department will inform the Secretary of State and the Commissioner of the Immigration and Naturalization Service as to the identity of the alien and the determination made. </P>
                        </SECTION>
                        <SIG>
                            <DATED>Dated: June 11, 2002 </DATED>
                            <NAME>John Ashcroft, </NAME>
                            <TITLE>Attorney General. </TITLE>
                        </SIG>
                    </PART>
                </SUPLINF>
                <FRDOC>[FR Doc. 02-15061 Filed 6-11-02; 5:07 pm] </FRDOC>
                <BILCOD>BILLING CODE 4410-19-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>67</VOL>
    <NO>115</NO>
    <DATE>Friday, June 14, 2002</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NEWPART>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="41153"/>
                    <AGENCY TYPE="S">DEPARTMENT OF JUSTICE</AGENCY>
                    <SUBJECT>Notice of Rescission of Second Notice of Advance Consent for Providing Certain Aviation Training</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Department of Justice.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>
                            This document notifies the public that the Attorney General is rescinding a notice published in the 
                            <E T="04">Federal Register</E>
                             on February 8, 2002 (67 FR 6051-6052), entitled “Provision of Aviation Training to Certain Alien Trainees, Additional Categories of Provisional Advance Consent.” For additional information, see the Interim Final Rule entitled “Screening of Aliens and Other Designated Individuals Seeking Flight Training,” published elsewhere in this issue of the 
                            <E T="04">Federal Register</E>
                            .
                        </P>
                    </SUM>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Steven C. McCraw, Director, Foreign Terrorist Task Force, U.S. Department of Justice, 950 Pennsylvania Avenue, NW., Washington, DC 20530, telephone (703) 414-9535.</P>
                        <SIG>
                            <DATED>Dated: May 29, 2002.</DATED>
                            <NAME>Rosemary Hart,</NAME>
                            <TITLE>Senior Counsel, Office of Legal Counsel.</TITLE>
                        </SIG>
                    </FURINF>
                </PREAMB>
                <FRDOC>[FR Doc. 02-15062 Filed 6-11-02; 5:07 pm]</FRDOC>
                <BILCOD>BILLING CODE 4410-19-M</BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
</FEDREG>
