Tap any paragraph to write a margin note. Your notes collect in the Desk below the text and file under cases with @. The side-by-side margin rail opens on a larger screen.

§
Marginalia
Code · REGISTER · 2008-05-28 · Nuclear Regulatory Commission · Notices

Notices. Issuance, Availability of Regulatory Guide 1

38,125 words·~173 min read·/register/2008/05/28/08-1298

A research copy — for the controlling text, always check the official state or federal source. Not legal advice.

BILLING CODE 7590-01-P NUCLEAR REGULATORY COMMISSION Notice of Issuance of Regulatory Guide AGENCY: Nuclear Regulatory Commission. ACTION: Issuance, Availability of Regulatory Guide 1.45, Revision 1. FOR FURTHER INFORMATION CONTACT: John Ridgely, Regulatory Guide Development Branch, Division of Engineering, Office of Nuclear Regulatory Research, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, telephone
(301)415-6555 or e-mail to *John.Ridgely@nrc.gov* . SUPPLEMENTARY INFORMATION: I. Introduction The U.S. Nuclear Regulatory Commission
(NRC)is issuing a revision to an existing guide in the agency's “Regulatory Guide” series. This series was developed to describe and make available to the public information such as methods that are acceptable to the NRC staff for implementing specific parts of the agency's regulations, techniques that the staff uses in evaluating specific problems or postulated accidents, and data that the staff needs in its review of applications for permits and licenses. Revision 1 of Regulatory Guide 1.45, “Guidance on Monitoring and Responding to Reactor Coolant System Leakage,” was issued with a temporary identification as Draft Regulatory Guide DG-1173. General Design Criterion
(GDC)14, “Reactor Coolant Pressure Boundary,” as set forth in Appendix A, “General Design Criteria for Nuclear Power Plants,” to Title 10, Part 50, of the *Code of Federal Regulations* (10 CFR part 50), “Domestic Licensing of Production and Utilization Facilities,” requires that the reactor coolant pressure boundary
(RCPB)shall be designed, fabricated, erected, and tested so as to have an extremely low probability of abnormal leakage, of rapidly propagating failure, and of gross rupture. As a result, these nuclear components are normally designed to the criteria established in Section III of the Boiler and Pressure Vessel Code promulgated by the American Society of Mechanical Engineers. During the design phase, degradation-resistant materials are normally specified for reactor coolant system
(RCS)components. However, materials can degrade as a result of the complex interaction of the materials, the stresses they encounter, and the normal and upset operating environments in which they are used. Such material degradation could lead to the leakage of the reactor coolant. Consequently, GDC 30, “Quality of Reactor Coolant Pressure Boundary,” of Appendix A to 10 CFR Part 50 requires that means shall be provided for detecting and, to the extent practical, identifying the location of the source of reactor coolant leakage. Additionally, 10 CFR 50.55a, “Codes and Standards,” requires the performance of inservice inspection and testing of nuclear power plant components. Thus, the concept of defense-in-depth is used to provide assurance that structural integrity of the RCPB is maintained. This guide describes methods that the staff of the NRC considers acceptable for implementing these requirements, with regard to selecting reactor coolant leakage detection systems, monitoring for leakage, and responding to leakage. This guide applies to light-water cooled reactors. II. Further Information In June 2007, DG-1173 was published with a public comment period of 60 days from the issuance of the guide. The public comment period closed on August 28, 2007. The staff's responses to the public comments are located in the NRC's Agencywide Documents Access and Management System (ADAMS), Accession Number ML073200289. Electronic copies of Regulatory Guide 1.45, Revision 1 are available through the NRC's public Web site under “Regulatory Guides” at *http://www.nrc.gov/reading-rm/doc-collections/.* In addition, regulatory guides are available for inspection at the NRC's Public Document Room (PDR), which is located at Room O-1F21, One White Flint North, 11555 Rockville Pike, Rockville, Maryland 20852-2738. The PDR's mailing address is USNRC PDR, Washington, DC 20555-0001. The PDR can also be reached by telephone at
(301)415-4737 or
(800)397-4209, by fax at
(301)415-3548, and by e-mail to pdr@nrc.gov. Regulatory guides are not copyrighted, and NRC approval is not required to reproduce them. Dated at Rockville, Maryland, this 21st day of May, 2008. For the Nuclear Regulatory Commission. Andrea D. Valentin, Chief, Regulatory Guide Development Branch, Division of Engineering, Office of Nuclear Regulatory Research. [FR Doc. E8-11847 Filed 5-27-08; 8:45 am] BILLING CODE 7590-01-P OFFICE OF PERSONNEL MANAGEMENT Submission for OMB Review; Comment Request for Extension, Without Change, of a Currently Approved Information Collection: RI 20-64, RI 20-64A and RI 20-64B AGENCY: Office of Personnel Management. ACTION: Notice. SUMMARY: In accordance with the Paperwork Reduction Act of 1995 (Pub. L. 104-13, May 22, 1995), this notice announces that the Office of Personnel Management
(OPM)has submitted to the Office of Management and Budget
(OMB)a request for extension, without change, of a currently approved information collection. RI 20-64, Letter Reply to Request for Information, is used by the Civil Service Retirement System to provide information about the amount of annuity payable after a survivor reduction, to explain the annuity reductions required to pay for the survivor benefit, and to give the beginning rate of survivor annuity. RI 20-64A, Former Spouse Survivor Annuity Election, is used by the Civil Service Retirement System to obtain a survivor benefits election from annuitants who are eligible to elect to provide survivor benefits for a former spouse. RI 20-64B, Information on Electing a Survivor Annuity for Your Former Spouse, is a pamphlet that provides important information to retirees under the Civil Service Retirement System who want to provide a survivor annuity for a former spouse. We estimate that 30 survivor elections on RI 20-64A will be processed per year and that of these eight will use RI 20-64 to ask for information about electing a smaller survivor benefit. Form RI 20-64A requires 45 minutes to complete for a burden of 23 hours. Form RI 20-64 requires 8 minutes to complete for a burden of 1 hour. The total burden is 24 hours. For copies of this proposal, contact Mary Beth Smith-Toomey on
(202)606-8358, FAX
(202)418-3251 or via E-mail to *MaryBeth.Smith-Toomey@opm.gov.* Please include a mailing address with your request. DATES: Comments on this proposal should be received within 30 calendar days from the date of this publication. ADDRESSES: Send or deliver comments to—Ronald W. Melton, Deputy Assistant Director, Retirement Services Program, Center for Retirement and Insurance Services, U.S. Office of Personnel Management, 1900 E Street, NW., Room 3305, Washington, DC 20415-3500; and Brenda Aguilar, OPM Desk Officer, Office of Information & Regulatory Affairs, Office of Management and Budget, New Executive Office Building, NW., Room 10235, Washington, DC 20503. *For Information Regarding Administrative Coordination—Contact:* Cyrus S. Benson, Team Leader, Publications Team, RIS Support Services/Support Group,
(202)606-0623. U.S. Office of Personnel Management. Howard Weizmann, Deputy Director. [FR Doc. E8-11840 Filed 5-27-08; 8:45 am] BILLING CODE 6325-38-P SECURITIES AND EXCHANGE COMMISSION [Release No. 34-57838; File No. SR-NYSEArca-2008-09] Self-Regulatory Organizations; NYSE Arca, Inc.; Order Granting Approval of Proposed Rule Change, as Modified by Amendment Nos. 1 and 2 Thereto, Relating to the Listing and Trading of Shares of the AirShares TM EU Carbon Allowances Fund May 20, 2008. I. Introduction On March 14, 2008, NYSE Arca, Inc. (“NYSE Arca” or “Exchange”), through its wholly owned subsidiary, NYSE Arca Equities, Inc. (“NYSE Arca Equities”), filed with the Securities and Exchange Commission (“Commission”), pursuant to Section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 1 and Rule 19b-4 thereunder, 2 a proposed rule change to:
(1)Adopt new NYSE Arca Equities Rule 8.204 relating to the listing and trading of Commodity Futures Trust Shares;
(2)incorporate cross-references to Commodity Futures Trust Shares and proposed NYSE Arca Equities Rule 8.204 in certain Exchange rules; and
(3)permit the listing and trading, or trading pursuant to unlisted trading privileges (“UTP”), of shares (“Shares”) of the AirShares TM EU Carbon Allowances Fund (“Fund”) under the proposed rule. On April 4, 2008, the Exchange filed Amendment No. 1 to the proposed rule change. The proposed rule change, as amended by Amendment No. 1 thereto, was published for comment in the **Federal Register** on April 15, 2008. 3 On May 14, 2008, the Exchange filed Amendment No. 2 to the proposed rule change. 4 The Commission received no comments regarding the proposal. This order approves the proposed rule change, as modified by Amendment Nos. 1 and 2 thereto. 1 15 U.S.C. 78s(b)(1). 2 17 CFR 240.19b-4. 3 *See* Securities Exchange Act Release No. 57636 (April 8, 2008), 73 FR 20344 (“Notice”). 4 In Amendment No. 2, the Exchange made minor, non-substantive changes to incorporate cross-references to Trust Units under NYSE Arca Equities Rule 8.500:
(1)in the list of securities for which the Core Trading Session (as defined herein) on the Exchange concludes at 4:15 p.m. Eastern Time (“ET”), as provided in NYSE Arca Equities Rule 7.34(a)(3);
(2)in the definition of “Derivative Securities Product” as set forth in NYSE Arca Equities Rule 7.34(a)(4); and
(3)in the list of securities included under the term “Derivative Securities Products” set forth in note 3 of the NYSE Arca Equities Schedule of Fees and Charges for Exchange Services. *See* Securities Exchange Act Release No. 57059 (December 28, 2007), 73 FR 909 (January 4, 2008) (SR-NYSEArca-2006-76) (approving, among other things, the adoption of NYSE Arca Equities Rule 8.500 relating to the listing and trading of Trust Units). In addition, the Exchange made clarifying changes to NYSE Arca Equities Rule 7.34(a) and the NYSE Arca Equities Schedule of Fees and Charges for Exchange Service to reflect the incorporation of cross-references to Managed Fund Shares under NYSE Arca Equities Rule 8.600 that was approved by the Commission subsequent to the date of the Notice. *See* Securities Exchange Act Release No. 57619 (April 4, 2008), 73 FR 19544 (April 10, 2008) (SR-NYSEArca-2008-25) (approving, among other things, the adoption of NYSE Arca Equities Rule 8.600 relating to the listing and trading of Managed Fund Shares). Amendment No. 2 is technical in nature, and therefore is not subject to notice and comment. II. Description of the Proposed Rule Change A. Proposed Listing Rules for Commodity Futures Trust Shares The Exchange proposes to adopt new NYSE Arca Equities Rule 8.204 to permit the listing and trading, or trading pursuant to UTP, of Commodity Futures Trust Shares. Proposed NYSE Arca Equities Rule 8.204(c) defines a Commodity Futures Trust Share as a security that:
(1)Is issued by a trust that
(a)is a commodity pool, as defined in the Commodity Exchange Act (“CEA”) and regulations thereunder, managed by a commodity pool operator registered with the Commodity Futures Trading Commission (“CFTC”), and
(b)holds positions in futures contracts 5 that track the performance of a specified commodity, or interests in a commodity pool which, in turn, holds such positions; and
(2)is issued and redeemed daily in specified aggregate amounts at net asset value (“NAV”). 5 For purposes of the proposed rule:
(1)The term “futures contract” is a “contract of sale of a commodity for future delivery” set forth in Section 2(a) of the CEA; and
(2)the term “commodity” is defined in Section 1(a)(4) of the CEA. Proposed NYSE Arca Equities Rule 8.204(d) provides that the Exchange may trade, either by listing or pursuant to UTP, Commodity Futures Trust Shares that are based on an underlying commodity futures contract. Each issue of Commodity Futures Trust Shares would be designated as a separate series and would be identified by a unique symbol. The criteria for listing and trading Commodity Futures Trust Shares are set forth in proposed NYSE Arca Equities Rule 8.204(e). Proposed NYSE Arca Equities Rule 8.204(e)(1) provides that the Exchange will establish a minimum number of Commodity Futures Trust Shares that will be required to be outstanding at the time of commencement of trading. The continued listing criteria in proposed NYSE Arca Equities Rule 8.204(e)(2) provide for the suspension of trading in, or removal from listing of, the Commodity Futures Trust Shares under any of the following circumstances: • If, following the initial 12-month period beginning upon the commencement of trading of the Shares:
(1)The trust has fewer than 50,000 Shares issued and outstanding;
(2)the market value of all Shares is less than $1,000,000; or
(3)there are fewer than 50 record and/or beneficial holders of Commodity Futures Trust Shares for 30 consecutive trading days; • If the value of the underlying futures contract is no longer calculated or available on at least a 15-second delayed basis during the Exchange's Core Trading Session, as defined in NYSE Arca Equities Rule 7.34(a), from a source unaffiliated with the sponsor, the trust, or the trustee; • If the NAV for the trust is no longer disseminated to all market participants at the same time; • If the Indicative Trust Value is no longer disseminated on at least a 15-second delayed basis during the Exchange's “Core Trading Session,” as defined in NYSE Arca Equities Rule 7.34(a); 6 or 6 The Core Trading Session on the Exchange is from 9:30 a.m. to 4 or 4:15 p.m. ET. *See* NYSE Arca Equities Rule 7.34(a). • If such other event shall occur or condition exists that, in the opinion of the Exchange, makes further dealings on the Exchange inadvisable. In addition, the Exchange will remove the Commodity Futures Trust Shares from listing upon termination of the trust. Proposed NYSE Arca Equities Rule 8.204(e)(3) provides that the term of a trust is as stated in the trust's prospectus, and that the trust may be terminated “earlier” as may be specified in the prospectus. Proposed NYSE Arca Equities Rule 8.204(e)(4) sets forth proposed requirements for the trustee of a trust:
(1)The trustee of a trust must be a trust company or banking institution having substantial capital and surplus and the experience and facilities for handling corporate trust business; in cases where, for any reason, an individual has been appointed as trustee, a qualified trust company or banking institution must be appointed co-trustee; and
(2)no change is to be made in the trustee of a listed issue without prior notice to and approval of the Exchange. Proposed NYSE Arca Equities Rule 8.204(e)(5) provides that voting rights will be as set forth in the applicable trust prospectus. Proposed NYSE Arca Equities Rule 8.204(f) sets forth certain restrictions on ETP Holders acting as registered Market Makers 7 in Commodity Futures Trust Shares to facilitate surveillance. Proposed NYSE Arca Equities Rules 8.204(f)(2)-(3) require that the ETP Holder acting as a registered Market Maker in the Commodity Futures Trust Shares provide the Exchange with necessary information relating to its trading in the underlying commodity, related futures or options on futures, or any other related derivatives. Proposed NYSE Arca Equities Rule 8.204(f)(4) prohibits the ETP Holder acting as a registered Market Maker in the Commodity Futures Trust Shares from using any material non-public information received from any person associated with an ETP Holder or employee of such person regarding trading by such person or employee in the underlying commodity, related futures or options on futures, or any other related derivative (including the Commodity Futures Trust Shares). In addition, proposed NYSE Arca Equities Rule 8.204(f)(1) prohibits the ETP Holder acting as a registered Market Maker in the Commodity Futures Trust Shares from being affiliated with a market maker in the underlying commodity, related futures or options on futures, or any other related derivative, unless adequate information barriers are in place, as provided in NYSE Arca Equities Rule 7.26. 7 Section 1.1(u) defines “Market Maker” as “an ETP Holder that acts as a Market Maker pursuant to Rule 7.” Proposed NYSE Arca Equities Rule 8.204(g) relates to the Exchange's limitation of liability. Proposed NYSE Arca Equities Rule 8.204(h) specifically provides that the Exchange will file separate proposals under Section 19(b) of the Act 8 before listing and trading separate and distinct series of Commodity Futures Trust Shares. 8 15 U.S.C. 78s(b). Commentary .01 to proposed NYSE Arca Equities Rule 8.204 requires ETP Holders to provide all purchasers of newly issued Commodity Futures Trust Shares with a prospectus. Commentary .02 to proposed NYSE Arca Equities Rule 8.204 provides that trading in the Commodity Futures Trust Shares will occur during the trading hours specified in NYSE Arca Equities Rule 7.34. Commentary .03 to proposed NYSE Arca Equities Rule 8.204 requires that if the Indicative Trust Value or the value of the underlying futures contract is not being disseminated as required, the Exchange may halt trading during the day in which the interruption to the dissemination of the Indicative Trust Value or the value of the underlying futures contract occurs. If the interruption to the dissemination of the Indicative Trust Value or the value of the underlying futures contract persists past the trading day in which it occurred, the Exchange will halt trading no later than the beginning of the trading day following the interruption. In addition, if the Exchange becomes aware that the NAV with respect to a series of Commodity Futures Trust Shares is not disseminated to all market participants at the same time, it will halt trading in such series until such time as the NAV or the Disclosed Portfolio is available to all market participants. Commentary .04 to proposed NYSE Arca Equities Rule 8.204 provides that the Exchange's rules governing the trading of equity securities apply to Commodity Futures Trust Shares. Commentary .05 to proposed NYSE Arca Equities Rule 8.204 provides that the Exchange will implement written surveillance procedures for Commodity Futures Trust Shares. B. Other Proposed Amendments 9 9 *See supra* note 4. The Exchange proposes to amend NYSE Arca Equities Rule 7.34(a)(3) to add references to Commodity Futures Trust Shares and proposed NYSE Arca Equities Rule 8.204 to the list of securities for which the Core Trading Session on the Exchange concludes at 4:15 p.m. ET. In addition, the Exchange proposes to amend NYSE Arca Equities Rule 7.34(a)(4) to include Commodity Futures Trust Shares under the definition of “Derivative Securities Product” with respect to trading halts of certain derivative securities products trading pursuant to UTP on the Exchange. The Exchange also proposes to add Commodity Futures Trust Shares to the securities included under the term “Derivative Securities Products” in note 3 of the NYSE Arca Equities Schedule of Fees and Charges for Exchange Services. Proposal To List and Trade the Shares of the Fund Pursuant to proposed NYSE Arca Equities Rule 8.204, the Exchange proposes to list and trade the Shares of the Fund. 10 The Exchange states that the Shares, which represent ownership of a fractional undivided beneficial interest in the net assets of the Fund, will conform to the initial and continued listing criteria under proposed NYSE Arca Equities Rule 8.204. 10 The Exchange states that the Fund is not an investment company registered under the Investment Company Act of 1940, according to the Registration Statement on Form S-1 for the Fund, which was filed with the Commission on December 14, 2007 (File No. 333-145448) (“Registration Statement”). The investment objective of the Fund is to provide investors with investment results that correspond generally, before payment of the Fund's expenses and liabilities, to the performance of a basket of exchange-traded futures contracts for carbon equivalent emissions allowances (“EUAs”) issued under the European Union Emissions Trading Scheme (“EU ETS”). 11 The EU ETS is a “cap and trade” emissions trading program instituted by the European Union (“EU”), in furtherance of the joint commitment of its member states under the Kyoto Protocol to achieve certain reductions in their emissions of greenhouse gases from 2008 to 2012. The Fund will not be actively managed in that it will not engage in activities designed to obtain a profit from, or to ameliorate losses caused by, changes in the value of its portfolio of EUAs. 11 According to the Registration Statement, while the investment objective of the Fund is to track generally the value of the underlying futures contracts, the Fund's portfolio of fixed income securities, as well as other factors such as the Fund's expenses and its hedging activities, may cause a lack of correlation between the NAV of the Shares and the value of the Fund's portfolio of futures contracts. The net assets of the Fund will consist of long positions in ICE Futures ECX Carbon Financial Instrument Futures Contracts (“ECX CFI Futures Contracts”). 12 The ECX CFI Futures Contracts are standardized contractual instruments for futures on deliverable EUAs issued under the EU ETS and developed by the European Climate Exchange (“ECX”). ECX CFI Futures Contracts are listed and admitted to trading on ICE Futures on the London-based electronic platform, owned and operated by Intercontinental Exchange, Inc. (also known as the ICE Platform). 13 Each ECX CFI Futures Contract provides for delivery of 1,000 EUAs on a specified date at a specified price, with each EUA being an entitlement to emit one ton of carbon dioxide equivalent gas. 14 The Exchange states that, if the Fund invests in EUAs other than ECX CFI Futures Contracts, it will file a Form 19b-4 under the Act 15 to obtain Commission approval for the continued listing and trading of the Shares. 16 12 The Fund represents that the ECX CFI Futures Contracts meets the definition of “futures contract” as set forth in Section 2(a) of the CEA. The Exchange further represents that carbon equivalent emissions allowances meet the definition of “commodity” as defined in Section 1(a)(4) of the CEA. 13 The ECX CFI Futures Contracts trade on the London-based ICE Platform from 7:00 a.m. to 5:00 p.m. Greenwich Mean Time. 14 The Exchange states that the ECX CFI Futures Contract had average daily trading volume of $135,717,089 (USD), or approximately 87,587,602 Euro, representing 3,551 contracts traded daily from January 1, 2008 through March 11, 2008. 15 15 U.S.C. 78a. 16 The Exchange also states that it will file a proposed change seeking approval to continue listing or trading the Shares if the Fund invests in EUAs that constitute more than 10% of the weight of the Fund and where the principal trading market for such component is not a member or affiliate member of the Intermarket Surveillance Group (“ISG”) or where the Exchange does not have a comprehensive surveillance sharing agreement with such market. More information about the structure of the Fund, the Kyoto Protocol, the EU ETS, the ECX CFI Futures Contracts, and the Fund's investment objective and strategy, as well as further descriptions of the Shares, risks, NAV, and procedures for creations and redemptions of Shares, can be found in the Notice 17 and the Registration Statement, 18 as applicable. 17 *See* Notice, *supra* note 3. 18 *See supra* note 9. Availability of Information Regarding the Fund and the Shares The daily settlement prices for the EUAs are publicly available on the ICE Futures Web site at *http://www.icefutures.com.* In addition, various market data vendors and news publications publish futures prices and related data. Quote and last-sale information for the EUAs are widely disseminated through a variety of market data vendors worldwide. ICE Futures also provides delayed futures information on current and past trading sessions and market news free of charge on its Web site. The specific contract specifications for the EUAs are also available on the ICE Futures Web site. The Web site for the Fund at *http://www.airsharesfund.com,* which is publicly accessible at no charge, will contain the following information:
(1)The prior business day's NAV per Share 19 and the reported closing price;
(2)the mid-point of the bid-ask price in relation to the NAV per Share as of the time the NAV is calculated (“Bid-Ask Price”); 20
(3)calculation of the premium or discount of such price against such NAV per Share;
(4)data in chart form displaying the frequency distribution of discounts and premiums of the Bid-Ask Price against the NAV per Share, within appropriate ranges for each of the four previous calendar quarters;
(5)the prospectus and the most recent periodic reports filed with the Commission or required by the CFTC; 21 and
(6)other applicable quantitative information. 19 The most recent end-of-day NAV of the Fund and NAV per Share will be published by the Fund sponsor as of 4 p.m. ET on Reuters and/or Bloomberg and on the Fund's Web site at * http://www.airsharesfund.com.* The end-of-day NAV per Share will also be published the following morning on the consolidated tape. 20 The Bid-Ask Price of Shares is determined using the highest bid and lowest offer as of the time of calculation of the NAV per Share. 21 Monthly account statements conforming to CFTC and National Futures Association requirements are posted on the Fund's Web site at * http://www.airsharesfund.com.* Additional reports may be posted on the Fund's Web site in the discretion of the Fund sponsor or as required by regulatory authorities. The Fund's total portfolio composition, consisting primarily of long positions in ECX CFI Futures Contracts and cash, will be disclosed each business day that the Exchange is open for trading on the Fund's Web site. The Fund has informed the Exchange that Web site disclosure of portfolio holdings will be made daily and will include, as applicable, the name and value of each EUA and amount of cash held in the portfolio of the Fund. As noted above, the Fund's NAV will be calculated and disseminated daily. 22 The Exchange will disseminate for the Fund on a daily basis by means of Consolidated Tape Association CQ High Speed Lines information with respect to the Indicative Fund Value (as discussed below), recent Fund NAV, Shares outstanding, and the Basket amount. The Exchange will also make available on its Web site daily trading volume, closing prices, and the Fund's NAV per Share. The closing price and settlement prices of the EUAs held by the Fund are also readily available from ICE Futures, automated quotation systems, published or other public sources, or on-line information services. 22 The Exchange will obtain a representation from the Fund that the Fund's NAV per Share will be calculated daily and made available to all market participants at the same time. *See* Notice at 20347, n.16. Information regarding market price and volume of the Shares is and will be continually available on a real-time basis throughout the day on brokers' computer screens and other electronic services. The previous day's closing price and trading volume information will be published daily in the financial section of newspapers. Quotation and last-sale information for the Shares will be available via the facilities of the Consolidated Tape Association. All pricing information will be quoted in U.S. dollars, other than the current trading value of the Euro-denominated EUAs, which will be quoted in Euro. The current trading price per Share will be published continuously as trades occur throughout each trading day on the consolidated tape, Reuters, and/or Bloomberg. The most recent trading value of each EUA is published on the Web site of the ECX at *http://www.ecxeurope.com,* under the heading “Market Data,” and each vintage futures contract in the Fund's portfolio will be published on the Fund's Web site at *http://www.airsharesfund.com,* or any successor thereto. To provide updated information relating to the Fund for use by investors, professionals and persons wishing to create or redeem the Shares, the Exchange or a major market data vendor will disseminate through the facilities of the Consolidated Tape Association an updated Indicative Fund Value (“Indicative Fund Value”). 23 The Indicative Fund Value, which is also known as intraday indicative value
(IIV)or intraday optimized portfolio value (IOPV), is an estimate, updated on a real-time basis at least every 15 seconds, of the NAV, which is disclosed only once per day. The Indicative Fund Value for the Fund will be disseminated on a per-Share basis at least every 15 seconds during the Exchange's Core Trading Session. The Indicative Fund Value will be calculated based on the previously-disclosed portfolio composition of the Fund, *i.e.* , the futures contracts in the Fund's portfolio, and will be adjusted to reflect the price changes of the relevant EUAs. 23 The Indicative Fund Value is referred to as the Indicative Trust Value in proposed new NYSE Arca Equities Rule 8.204(e)(2)(iv). The value of a Share may be influenced by the non-concurrent trading hours between the Exchange and the exchanges on which the EUAs trade. While the Shares will trade from 4 a.m. to 8 p.m. ET, the ECX CFI Futures Contracts, for example, trade on the London-based ICE Platform from 7 a.m. to 5 p.m. local time in London, England. When the ICE Platform and the Exchange are both open for trading, the Indicative Fund Value can be expected to closely approximate the NAV per Share. When the ICE Platform is closed and the Exchange is open, trading spreads and the resulting premium or discount on the Shares may widen and, therefore, increase the difference between the public trading price of the Shares and the NAV per Share. The Indicative Fund Value on a per-Share basis disseminated during the Exchange's Core Trading Session should not be viewed as a real-time update of the Fund's NAV, which is calculated only once a day. Trading Halts With respect to trading halts, the Exchange may consider all relevant factors in exercising its discretion to halt or suspend trading in the Shares. 24 Trading in the Shares will be halted if the circuit breaker parameters under NYSE Arca Equities Rule 7.12 are reached. Trading may also be halted because of market conditions or for reasons that, in the view of the Exchange, make trading in the Shares inadvisable. These may include:
(1)The extent to which trading is not occurring in the underlying EUA futures contracts; or
(2)whether other unusual conditions or circumstances detrimental to the maintenance of a fair and orderly market are present. Trading in the Shares also will be subject to Commentary .03 to proposed NYSE Arca Equities Rule 8.204, which sets forth circumstances under which trading in the Shares may be halted. 24 *See* Commentary .04 to NYSE Arca Equities Rule 7.12. Trading Rules Under proposed NYSE Arca Equities Rule 8.204(b), Commodity Futures Trust Shares are included within the Exchange's definition of “securities.” The Exchange deems the Shares to be equity securities, thus rendering trading in the Shares subject to the Exchange's existing rules governing the trading of equity securities. Commentary .02 to proposed NYSE Arca Equities Rule 8.204 provides that transactions in Commodity Futures Trust Shares will occur during the trading hours specified in Rule 7.34. Therefore, in accordance with such rule, the Shares will trade on the NYSE Arca Marketplace from 4 a.m. to 8 p.m. ET. The Exchange states that it has appropriate rules to facilitate transactions in the Shares during all three trading sessions. Surveillance The Exchange intends to utilize its existing surveillance procedures applicable to derivative products (which will include Commodity Futures Trust Shares) to monitor trading in the Shares. The Exchange represents that these procedures are adequate to properly monitor Exchange trading of the Shares in all trading sessions and to deter and detect violations of Exchange rules and applicable federal securities laws. The Exchange's current trading surveillance focuses on detecting securities trading outside their normal patterns. When such situations are detected, surveillance analysis follows and investigations are opened, where appropriate, to review the behavior of all relevant parties for all relevant trading violations. The Exchange may obtain information via the ISG from other exchanges who are members or affiliate members of the ISG. In addition, the Exchange has an information sharing agreement in place with ICE Futures for the purpose of providing information in connection with trading in, or related to, futures contracts traded on ICE Futures. The Exchange states that it will file a proposed change pursuant to Rule 19b-4 under the Act 25 seeking approval to continue trading the Shares if the Fund invests in EUAs (or pricing information is used for a new or existing component) that constitute more than 10% of the weight of the Fund where the principal trading market for such component is not a member or affiliate member of ISG or where the Exchange does not have a comprehensive surveillance sharing agreement with such market. In addition, the Exchange also has a general policy prohibiting the distribution of material, non-public information by its employees. 25 17 CFR 240.19b-4. Information Bulletin Prior to the commencement of trading, the Exchange will inform its ETP Holders 26 in an Information Bulletin (“Bulletin”) of the special characteristics and risks associated with trading the Shares. Specifically, the Bulletin will discuss the following:
(1)The risks involved in trading the Shares during the Opening and Late Trading Sessions 27 when an updated Indicative Fund Value will not be calculated or publicly disseminated;
(2)the procedures for purchases and redemptions of Shares (and that Shares are not individually redeemable);
(3)NYSE Arca Equities Rule 9.2(a), 28 which imposes a duty of due diligence on its ETP Holders to learn the essential facts relating to every customer prior to trading the Shares;
(4)the risk involved in trading the Shares during the Core and Late Trading Sessions when the ECX CFI Futures Contracts are not trading on the ICE Platform;
(5)how information regarding the Indicative Fund Value is disseminated;
(6)the requirement that ETP Holders deliver a prospectus to investors purchasing newly issued Shares prior to or concurrently with the confirmation of a transaction; and
(7)trading information. 26 *See* NYSE Arca Equities Rule 1.1(n) (defining ETP Holder). 27 The Opening Trading Session is from 4 a.m. to 9:30 a.m. ET and the Late Trading Session is from 4:15 p.m. to 8 p.m. ET. *See* NYSE Arca Equities Rule 7.34. 28 NYSE Arca Equities Rule 9.2(a) provides that ETP Holders, before recommending a transaction, must have reasonable grounds to believe that the recommendation is suitable for the customer based on any facts disclosed by the customer as to his other security holdings and as to his financial situation and needs. Further, the rule provides, with a limited exception, that prior to the execution of a transaction recommended to a non-institutional customer, the ETP Holder shall make reasonable efforts to obtain information concerning the customer's financial status, tax status, investment objectives, and any other information that the ETP Holder believes would be useful to make a recommendation. In addition, the Bulletin will reference that:
(1)The Fund is subject to various fees and expenses described in the relevant registration statement;
(2)that there is no regulated source of last-sale information regarding physical commodities;
(3)the Commission has no jurisdiction over the trading of EUAs; and
(4)the Financial Services Authority in the United Kingdom has regulatory jurisdiction over the trading of EUAs and related options. The Bulletin will also discuss any exemptive, no-action, and interpretive relief granted by the Commission from any rules under the Act and disclose that the NAV for the Shares will be calculated after 4: p.m. ET each trading day. III. Discussion and Commission's Findings The Commission has carefully reviewed the proposed rule change and finds that it is consistent with the requirements of Section 6 of the Act 29 and the rules and regulations thereunder applicable to a national securities exchange. 30 In particular, the Commission finds that the proposal is consistent with Section 6(b)(5) of the Act, 31 which requires, among other things, that the Exchange's rules be designed to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest. The Commission notes that it has approved similar NYSE Arca Equities rules to list and trade products based on or related to commodities. 32 29 15 U.S.C. 78f. 30 In approving this proposed rule change, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 15 U.S.C. 78c(f). 31 15 U.S.C. 78f(b)(5). 32 *See* Securities Exchange Act Release Nos. 54025 (June 21, 2006), 71 FR 36856 (June 28, 2006) (SR-NYSEArca-2006-12) (approving new NYSE Arca Equities Rule 8.203 “Commodity-Indexed Trust Shares” for trading pursuant to UTP the iShares GSCI Commodity-Indexed Trust); 51067 (January 21, 2005), 70 FR 3952 (January 27, 2005) (SR-PCX-2004-132) (approving new NYSE Arca Equities Rule 8.201 “Commodity-Based Trust Shares” for trading pursuant to UTP the iShares COMEX Gold Trust); 56041 (July 11, 2007), 72 FR 39114 (July 17, 2007) (SR-NYSEArca-2007-43) (approving listing of shares of iShares COMEX Gold Trust pursuant to NYSE Arca Equities Rule 8.201); 53875 (May 25, 2006), 71 FR 32164 (June 2, 2006) (SR-NYSEArca-2006-11) (approving new NYSE Arca Equities Rule 8.300 “Partnership Shares” for trading pursuant to UTP the United States Oil Fund, LP); and 53736 (April 27, 2006), 71 FR 26582 (May 5, 2006) (SR-PCX-2006-22) (approving new Commentary .02 to NYSE Arca Equities Rule 8.200 “Investment Shares” for trading pursuant to UTP the DB Commodity Index Tracking Fund). A. Proposed Amendments to NYSE Arca Equities Rules The Commission finds that NYSE Arca's proposal contains adequate rules and procedures to govern the listing and trading of Commodity Futures Trust Shares on the Exchange. Prior to listing and/or trading on the Exchange, NYSE Arca must file a separate proposed rule change pursuant to Section 19(b) of the Act for each series of Commodity Futures Trust Shares. 33 All such securities listed and/or traded under proposed NYSE Arca Equities Rule 8.204 will be subject to the full panoply of NYSE Arca rules and procedures that currently govern the trading of equity securities on the Exchange. 34 For the initial listing of each series of Commodity Futures Trust Shares under proposed NYSE Arca Equities Rule 8.204, the Exchange must establish a minimum number of Commodity Futures Trust Shares required to be outstanding at the commencement of trading on the Exchange. 35 33 *See* proposed NYSE Arca Equities Rule 8.204(h). 34 Commentary .04 to proposed NYSE Arca Equities Rule 8.204 provides that the Exchange's rules governing the trading of equity securities apply to Commodity Futures Trust Shares. 35 *See* proposed NYSE Arca Equities Rule 8.204(e)(1). The Commission believes that the proposed continued listing and trading standards under proposed NYSE Arca Equities Rule 8.204 are adequate to ensure transparency of key values and information regarding the securities. The Exchange may consider suspending trading in, or removing from listing, a series of Commodity Futures Trust Shares if:
(1)Following the initial twelve-month period beginning upon the commencement of trading of the Commodity Futures Trust Shares,
(a)The Trust has fewer than 50,000 Commodity Futures Trust Shares issued and outstanding;
(b)the market value of all Commodity Futures Trust Shares issued and outstanding is less than $1,000,000, or
(c)there are fewer than 50 record and/or beneficial holders of Commodity Futures Trust Shares for 30 consecutive trading days;
(2)the value of the underlying futures contracts is no longer calculated or available on at least a 15-second delayed basis during the Exchange's Core Trading Session, as defined in NYSE Arca Equities Rule 7.34(a), from a source unaffiliated with the sponsor, the trust or the trustee of the trust;
(3)the NAV for the trust is no longer disseminated to all market participants at the same time;
(4)the Indicative Trust Value is no longer disseminated on at least a 15-second delayed basis during the Corporation's Core Trading Session, as defined in NYSE Arca Equities Rule 7.34(a); or
(5)such other event shall occur or condition exists which in the opinion of the Corporation makes further dealings on the Corporation inadvisable. 36 36 *See* proposed NYSE Arca Equities Rule 8.204(e)(2)(i)-(v). The Commission finds that the Exchange's rules with respect to trading halts under proposed NYSE Arca Equities Rule 8.204 should help ensure the availability of key values and information relating to Commodity Futures Trust Shares. If the Indicative Trust Value or the value of the underlying futures contract is not being disseminated as required, the Exchange may halt trading during the day in which the interruption to the dissemination of the Indicative Trust Value or the value of the underlying futures contract occurs; if the interruption to the dissemination of the Indicative Trust Value or the value of the underlying futures contract persists past the trading day in which it occurred, the Exchange will halt trading no later than the beginning of the trading day following the interruption. 37 In addition, if the Exchange becomes aware that the NAV with respect to a series of Commodity Futures Trust Shares is not disseminated to all market participants at the same time, it will halt trading in such series until such time as the NAV is available to all market participants. 38 Lastly, the Exchange proposes to amend NYSE Arca Equities Rule 7.34(a)(4) to include Commodity Futures Trust Shares under “Derivative Securities Products” with respect to trading halts of certain derivative securities products trading pursuant to UTP on the Exchange. The Commission believes that the foregoing requirements of the Exchange's proposed rules should help to prevent trading when a reasonable degree of transparency cannot be assured and to maintain a fair and orderly market for Commodity Futures Trust Shares. 37 *See* Commentary .03 to proposed NYSE Arca Equities Rule 8.204. 38 *See id.* The Commission also believes that the proposed listing and trading rules for Commodity Futures Trust Shares are reasonably designed to promote a fair and orderly market for such securities by, among other things, requiring ETP Holders acting as registered Market Makers in Commodity Futures Trust Shares to be subject to certain restrictions in dealings and trading activities, to maintain and present, upon request, appropriate books and records, and to be subject to restrictions governing the use of any material, non-pubic information in connection with the trading of Commodity Futures Trust Shares and any underlying components. 39 The proposed rule also requires the implementation of written surveillance procedures 40 and prescribes prospectus delivery requirements for purchasers of each newly issued series of Commodity Futures Trust Shares. 41 39 *See* proposed NYSE Arca Equities Rule 8.204(f)(1)-(4). 40 *See* Commentary .05 to proposed NYSE Arca Equities Rule 8.204. 41 *See* Commentary .01 to proposed NYSE Arca Equities Rule 8.204. As proposed, the Exchange's listing fees will be applicable to a series of Commodity Futures Trust Shares under the Schedule of Fees and Charges for Exchange Services. In connection with proposed NYSE Arca Equities Rule 8.204, the Exchange also proposes to make certain technical revisions so that Commodity Futures Trust Shares are also included among the types of securities referenced in NYSE Arca Equities Rule 7.34 relating to trading hours and trading halts. The Commission finds that the changes made to the Exchange's listing fees and the technical revisions to NYSE Arca Equities Rule 7.34 are reasonable and promote transparency and consistent application of certain rules imposed with respect to a series of Commodity Futures Trust Shares. B. Proposal To List and Trade the Shares of the Fund The Commission finds that the proposal to list and trade the Shares on the Exchange is consistent with Section 11A(a)(1)(C)(iii) of the Act, 42 which sets forth Congress' finding that it is in the public interest and appropriate for the protection of investors and the maintenance of fair and orderly markets to assure the availability to brokers, dealers, and investors of information with respect to quotations for and transactions in securities. Quotations and last-sale information for EUAs are widely disseminated through a variety of market data vendors worldwide, and the daily settlement prices for the EUAs are publicly available on the ICE Futures Web site. In addition, quotations and last-sale information for the Shares will be available via the facilities of the Consolidated Tape Association. The daily NAV for the Fund will be calculated and disseminated publicly to all market participants at the same time, and the Exchange or a major market data vendor will disseminate through the facilities of the Consolidated Tape Association an updated Indicative Fund Value on a real-time basis at least every 15 seconds during the Exchange's Core Trading Session. The Fund's Web site will provide information relating to NAV, the Fund's daily total portfolio composition, the Fund's prospectus and other reports filed with the Commission, and other applicable quantitative information. Additionally, the Exchange will make available on its Web site daily trading volume of the Shares, closing prices of the Shares, and the Fund's NAV per Share. 42 15 U.S.C. 78k-1(a)(1)(C)(iii). Furthermore, the Commission believes that the proposal to list and trade the Shares is reasonably designed to promote fair disclosure of information that may be necessary to price the Shares appropriately and to prevent trading when a reasonable degree of transparency cannot be assured. The Commission notes that the Exchange will obtain a representation from the Fund that the NAV per Share for the Fund will be calculated daily and made available to all market participants at the same time. 43 The Exchange may consider the suspension of trading in, or removal from listing of, the Shares if the value of the underlying futures contracts, the NAV, or the Indicative Fund Value is no longer calculated or available as required under proposed NYSE Arca Equities Rule 8.204(e)(2). In addition, proposed NYSE Arca Equities Rule 8.204(f) restricts ETP Holders from engaging in certain trading activities with respect to dealings in Commodity Futures Trust Shares and prescribes certain other restrictions regarding the use of material, non-public information. 43 *See supra* note 22. For the reasons discussed above, the Commission believes that the Exchange's trading halt rules are reasonably designed to prevent trading in the Shares when transparency is impaired. Commentary .03 to proposed NYSE Arca Equities Rule 8.204 provides that, if the Indicative Fund Value or the value of the underlying futures contract is not being disseminated as required, the Exchange may halt trading during the day in which the interruption to the dissemination of the Indicative Fund Value or the value of the underlying futures contract occurs; if the interruption to the dissemination of the Indicative Fund Value or the value of the underlying futures contract persists past the trading day in which it occurred, the Exchange will halt trading no later than the beginning of the trading day following the interruption. 44 In addition, if the Exchange becomes aware that the NAV with respect to a series of Commodity Futures Trust Shares is not disseminated to all market participants at the same time, it will halt trading in such series until such time as the NAV is available to all market participants. 45 Trading in the Shares also will be halted if the circuit breaker parameters under NYSE Arca Equities Rule 7.12 are reached. Trading may also be halted because of market conditions or for reasons that, in the view of the Exchange, make trading in the Shares inadvisable. These may include:
(1)The extent to which trading is not occurring in the underlying EUA futures contracts; or
(2)whether other unusual conditions or circumstances detrimental to the maintenance of a fair and orderly market are present. 44 *See* Commentary .03 to proposed NYSE Arca Equities Rule 8.204. 45 *See id.* The Commission further believes that the trading rules and procedures to which the Shares will be subject pursuant to this proposal are consistent with the Act. The Exchange has represented that the Shares are equity securities subject to the Exchange's rules governing the trading of equity securities. In support of this proposal, the Exchange has made the following representations:
(1)The Shares will conform to the initial and continued listing criteria under proposed NYSE Arca Equities Rule 8.204(e).
(2)The Exchange's surveillance procedures applicable to derivative products (which will include Commodity Futures Trust Shares) are adequate to properly monitor Exchange trading of the Shares in all trading sessions and to deter and detect violations of Exchange rules and applicable federal securities laws.
(3)Prior to the commencement of trading, the Exchange will inform its ETP Holders in the Bulletin of the special characteristics and risks associated with trading the Shares. Specifically, the Bulletin will discuss, among other things, the following:
(a)The risks involved in trading the Shares during the Opening and Late Trading Sessions when an updated Indicative Fund Value will not be calculated or publicly disseminated;
(b)the procedures for purchases and redemptions of Shares (and that Shares are not individually redeemable);
(c)NYSE Arca Equities Rule 9.2(a), which imposes a duty of due diligence on its ETP Holders to learn the essential facts relating to every customer prior to trading the Shares;
(d)the risk involved in trading the Shares during the Core and Late Trading Sessions when the ECX CFI Futures Contracts are not trading on the ICE Platform;
(e)how information regarding the Indicative Fund Value is disseminated;
(f)the requirement that ETP Holders deliver a prospectus to investors purchasing newly issued Shares prior to or concurrently with the confirmation of a transaction; and
(g)trading information. This approval order is based on the Exchange's representations. The Commission believes that the proposal should help to facilitate the listing and trading of additional types of exchange-traded products that should enhance competition among market participants, to the benefit of investors and the marketplace. In addition, the Commission believes that the listing and trading criteria for Commodity Futures Trust Shares set forth in proposed NYSE Arca Equities Rule 8.204 are reasonably designed to protect investors and the public interest, as discussed herein. For the foregoing reasons, the Commission finds that the proposed rule change is consistent with the Act and the rules and regulations thereunder applicable to a national securities exchange, and, in particular, with Section 6(b)(5) of the Act. 46 46 15 U.S.C. 78f(b)(5). IV. Conclusion *It is therefore ordered,* pursuant to Section 19(b)(2) of the Act, 47 that the proposed rule change (SR-NYSEArca-2008-09), as modified by Amendment Nos. 1 and 2 thereto, be, and it hereby is, approved. 47 15 U.S.C. 78s(b)(2). For the Commission, by the Division of Trading and Markets, pursuant to delegated authority. 48 48 17 CFR 200.30-3(a)(12). Nancy M. Morris, Secretary. [FR Doc. E8-11832 Filed 5-27-08; 8:45 am] BILLING CODE 8010-01-P SMALL BUSINESS ADMINISTRATION [Disaster Declaration #11256 and #11257] Arkansas Disaster # AR-00020 AGENCY: U.S. Small Business Administration. ACTION: Notice. SUMMARY: This is a Notice of the Presidential declaration of a major disaster for the State of Arkansas (FEMA-1758-DR), dated 05/20/2008. *Incident:* Severe Storms, Flooding, and Tornadoes. *Incident Period:* 05/02/2008 and continuing. DATES: *Effective Date:* 05/20/2008. *Physical Loan Application Deadline Date:* 07/21/2008. *Economic Injury
(EIDL)Loan Application Deadline Date:* 02/20/2009. ADDRESSES: Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155. FOR FURTHER INFORMATION CONTACT: A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street, SW., Suite 6050, Washington, DC 20416. SUPPLEMENTARY INFORMATION: Notice is hereby given that as a result of the President's major disaster declaration on 05/20/2008, applications for disaster loans may be filed at the address listed above or other locally announced locations. The following areas have been determined to be adversely affected by the disaster: *Primary Counties (Physical Damage and Economic Injury Loans):* Benton, Cleburne, Conway, Crittenden, Grant, Lonoke, Mississippi, Pulaski, Saline, Van Buren. *Contiguous Counties (Economic Injury Loans Only):* Arkansas: Arkansas, Carroll, Cleveland, Craighead, Cross, Dallas, Faulkner, Garland, Hot Spring Independence, Jefferson, Lee, Madison, Perry, Poinsett, Pope, Prairie, Saint Francis, Searcy, Stone, Washington, White, Yell. Missouri: Barry, Dunklin, Mcdonald, Pemiscot. Mississippi: Desoto, Tunica. Oklahoma: Adair, Delaware. Tennessee: Dyer, Lauderdale, Shelby, Tipton. *The Interest Rates are:* Percent *For Physical Damage:* Homeowners With Credit Available Elsewhere 5.375 Homeowners Without Credit Available Elsewhere 2.687 Businesses With Credit Available Elsewhere 8.000 Other (Including Non-Profit Organizations) With Credit Available Elsewhere 5.250 Businesses and Non-Profit Organizations Without Credit Available Elsewhere 4.000 *For Economic Injury:* Businesses & Small Agricultural Cooperatives Without Credit Available Elsewhere 4.000 The number assigned to this disaster for physical damage is 11256B and for economic injury is 112570. (Catalog of Federal Domestic Assistance Numbers 59002 and 59008) James E. Rivera, Acting Associate Administrator for Disaster Assistance. [FR Doc. E8-11886 Filed 5-27-08; 8:45 am] BILLING CODE 8025-01-P SMALL BUSINESS ADMINISTRATION [Disaster Declaration #11254] Maine Disaster Number ME-00012 AGENCY: U.S. Small Business Administration. ACTION: Amendment 1. SUMMARY: This is an amendment of the Presidential declaration of a major disaster for Public Assistance Only for the State of Maine ( FEMA-1755-DR), dated 05/14/2008. *Incident:* Severe Storms and Flooding. *Incident Period:* 04/28/2008 through 05/14/2008. DATES: *Effective Date:* 05/14/2008. *Physical Loan Application Deadline Date:* 07/14/2008. ADDRESSES: Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155. FOR FURTHER INFORMATION CONTACT: A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street, SW., Suite 6050, Washington, DC 20416. SUPPLEMENTARY INFORMATION: The notice of the President's major disaster declaration for private non-profit organizations in the State of Maine, dated 05/14/2008, is hereby amended to establish the incident period for this disaster as beginning 04/28/2008 and continuing through 05/14/2008. All other information in the original declaration remains unchanged. (Catalog of Federal Domestic Assistance Number 59008) James E. Rivera, Acting Associate Administrator for Disaster Assistance. [FR Doc. E8-11885 Filed 5-27-08; 8:45 am] BILLING CODE 8025-01-P SMALL BUSINESS ADMINISTRATION [Disaster Declaration #11242 and #11243] Maine Disaster Number ME-00011 AGENCY: U.S. Small Business Administration. ACTION: Amendment 2. SUMMARY: This is an amendment of the Presidential declaration of a major disaster for the State of Maine (FEMA-1755-DR), dated 05/09/2008. *Incident:* Severe Storms and Flooding. *Incident Period:* 04/28/2008 and continuing through 05/14/2008. DATES: *Effective Date:* 05/14/2008. *Physical Loan Application Deadline Date:* 07/08/2008. *EIDL Loan Application Deadline Date:* 02/09/2009. ADDRESSES: Submit completed loan applications to: U.S. Small Business Administration, Processing and Disbursement Center, 14925 Kingsport Road, Fort Worth, TX 76155. FOR FURTHER INFORMATION CONTACT: A. Escobar, Office of Disaster Assistance, U.S. Small Business Administration, 409 3rd Street, SW., Suite 6050, Washington, DC 20416. SUPPLEMENTARY INFORMATION: The notice of the President's major disaster declaration for the State of Maine, dated 05/09/2008 is hereby amended to establish the incident period for this disaster as beginning 04/28/2008 and continuing through 05/14/2008. All other information in the original declaration remains unchanged. (Catalog of Federal Domestic Assistance Numbers 59002 and 59008) James E. Rivera, Acting Associate Administrator for Disaster Assistance. [FR Doc. E8-11887 Filed 5-27-08; 8:45 am] BILLING CODE 8025-01-P SOCIAL SECURITY ADMINISTRATION Agency Information Collection Activities: Comment Request The Social Security Administration
(SSA)publishes a list of information collection packages requiring clearance by the Office of Management and Budget
(OMB)in compliance with Public Law (Pub. L.) 104-13, the Paperwork Reduction Act of 1995, effective October 1, 1995. This notice includes new information collections, revisions to OMB-approved information collections and extensions (no change) of OMB-approved information collections. SSA is soliciting comments on the accuracy of the Agency's burden estimate; the need for the information; its practical utility; ways to enhance its quality, utility and clarity; and how to minimize the burden on respondents, including the use of automated collection techniques or other forms of information technology. Mail, e-mail or fax your comments and recommendations on the information collection(s) to the OMB Desk Officer and the SSA Reports Clearance Officer to the addresses or fax numbers listed below. (OMB), Office of Management and Budget, Attn: Desk Officer for SSA, Fax: 202-395-6974, E-mail address: *OIRA_Submission@omb.eop.gov.* (SSA), Social Security Administration, DCBFM, Attn: Reports Clearance Officer, 1333 Annex Building, 6401 Security Blvd., Baltimore, MD 21235, Fax: 410-965-6400, E-mail address: *OPLM.RCO@ssa.gov* . SSA has submitted the information collections listed below. Your comments on the information collections will be most useful if OMB and SSA receive them within 30 days from the date of this publication. You can request a copy of the information collections by e-mail, *OPLM.RCO@ssa.gov* , fax 410-965-6400, or by calling the SSA Reports Clearance Officer at 410-965-0454. **1. Report to United States Social Security Administration by Person Receiving Benefits for a Child or for an Adult Unable to Handle Funds/Report to the United States Social Security Administration—0960-0049** . SSA needs the information on Forms SSA-7161-OCR-SM and SSA-7162-OCR-SM to:
(1)Determine continuing entitlement to Social Security benefits:
(2)correct benefit amounts for beneficiaries outside the United States: and
(3)monitor the performance of representative payees outside the United States. The respondents are individuals living outside the United States who are receiving benefits on their own (or for someone else) under Title II of the Social Security Act. *Type of Request:* Extension of an OMB-approved information collection. Form number Number of respondents Frequency of response Average burden per response (minutes) Estimated annual burden (hours) SSA-7161-OCR-SM 28,461 1 15 7,115 SSA-7162-OCR-SM 247,136 1 5 20,595 Totals 275,597 27,710 **2. Questionnaire About Employment or Self-Employment Outside the United States—20 CFR 404.401(b)(1), 404.415 & 404.417—0960-0050.** SSA uses Form SSA-7163 to determine:
(1)Whether work performed by beneficiaries outside the United States is cause for deductions from their monthly benefits:
(2)which of two work tests (foreign or regular test) is applicable; and
(3)the number of months, if any, for SSA-imposed deductions. Respondents are beneficiaries living and working outside the United States. *Type of Request:* Revision of an OMB-approved information collection. *Number of Respondents:* 20,000. *Frequency of Response:* 1. *Average Burden Per Response:* 12 minutes. *Estimated Annual Burden:* 4,000 hours. **3. Petition to Obtain Approval of a Fee for Representing a Claimant before the Social Security Administration—20 CFR 404.1720, 404.1725, 416.1520 & 416.1525—0960-0104** . Representatives use Form SSA-1560 to charge a fee for representing a claimant in proceedings before SSA. A representative must file either a fee petition or fee agreement with SSA. If the representative files a fee petition (Form SSA-1560) to obtain approval of a fee, SSA reviews the information to determine a reasonable fee for the representative's services. Respondents are attorneys and non-attorneys who represent claimants for Social Security benefits. *Type of Request:* Revision of an OMB-approved information collection. *Number of Respondents:* 34,624. *Frequency of Response:* 1. *Average Burden Per Response:* 30 minutes. *Estimated Annual Burden:* 17,312 hours. **4. Annual Earnings Test Direct Mail Follow-Up Program Notices—20 CFR 404.452-404.455—0960-0369** . The Mid-Year Mailer ensures Social Security payments are correct. Beneficiaries under full retirement age
(FRA)use Forms SSA-L9778, SSA-L9779, and SSA-L9781 to update their current year estimate and their estimate for the following year. Beneficiaries use Mid-Year Mailer Forms SSA-L9784 and SSA-L9785 to request earnings estimates in the year of FRA for the period prior to the month of FRA. Beneficiaries will use new Form SSA-L9790 to report earnings information at the end of the year. The respondents are working Retirement Survivors Insurance beneficiaries with earnings over the exempt amount. *Type of Request:* Revision of an OMB-approved information collection. *Number of Respondents:* 460,000. *Frequency of Response:* 1. *Average Burden Per Response:* 10 minutes. *Estimated Annual Burden:* 76,667 hours. **5. Electronic Benefit Verification Information (BEVE)—20 CFR 401.40—0960-0595** . The electronic proof of income
(POI)verification Internet service, BEVE, provides beneficiaries the convenience of requesting a proof of income statement through the Internet. Beneficiaries often require a POI to obtain housing, food stamps, or other public services. SSA uses the information BEVE collects to provide the POI to the beneficiary, after verifying the requestor's identity. The respondents are Social Security Title II, Title XVI, and Medicare beneficiaries. *Type of Request:* Extension of an OMB-approved information collection. *Number of Respondents:* 314,974. *Frequency of Response:* 1. *Average Burden Per Response:* 5 minutes. *Estimated Annual Burden:* 26,248 hours. **6. Application for Survivors Benefits—20 CFR 404.611(a) and (c)—0960-0062** . Surviving family members of armed services personnel can file for Social Security and Veterans' benefits at SSA or the Veterans Administration (VA). If applicants go to the VA first, they complete Form SSA-24, the Application for Survivor's Benefits. The VA then forwards Form SSA-24 to SSA for processing. If applicants previously filed for benefits at SSA, the Agency disregards this form. The respondents are survivors of deceased armed services personnel who are applying for benefits at the VA. *Type of Request:* Extension of an OMB-approved information collection. *Number of Respondents:* 3,200. *Frequency of Response:* 1. *Average Burden Per Response:* 15 minutes. *Estimated Annual Burden:* 800 hours. **7. Quarterly Statistical Report on Recipients and Payments under State-Administered Assistance Programs for Aged, Blind and Disabled (Individuals and Couples) Recipients—20 CFR 416.2010, 20 CFR 416.2098—0960-0130** . States with agreements with SSA under the State supplementation provisions of the Social Security Act must provide statistical data to SSA. State Disability Determination Services
(DDS)inform SSA of expenditures and caseloads of State-administered supplements under the Supplemental Security Income program. SSA needs the data from this report to:
(1)Supplement the information it already has about federally-administered programs;
(2)more fully explain the effect of the public income support programs on the needy, aged, blind, and disabled; and
(3)monitor State compliance with the mandatory pass-along provision. States and other Federal agencies use data from this report as well for various purposes. The respondents are State DDSs. *Type of Request:* Extension of an OMB-approved information collection. *Number of Respondents:* 31. *Frequency of Response:* 4. *Average Burden Per Response:* 60 minutes. *Estimated Annual Burden:* 124 hours. **8. Employee Work Activity Questionnaire—20 CFR 404.1574, 404.1592—0960-0483** . Social Security disability claimants qualify for benefits when a verified physical or mental impairment prevents them from working. If disability claimants attempt to return to work after receiving disability benefits but are unable to continue working, they submit Form SSA-3033, the Employee Work Activity Questionnaire, so SSA can evaluate the work attempt. SSA also uses this form to evaluate unsuccessful subsidy work. Ultimately, SSA uses the form to determine applicants' continuing eligibility for disability benefits. The respondents are employers of Social Security disability beneficiaries who unsuccessfully attempted to return to work. *Type of Request:* Extension of an OMB approved information collection. *Number of Respondents:* 15,000. *Frequency of Response:* 1. *Average Burden Per Response:* 15 minutes. *Estimated Annual Burden:* 3,750 hours. **9. Medical Permit Parking Application—41 CFR 101-20.104-2—0960-0624** . SSA employees and contractors with a qualifying medical condition who park at SSA-owned and -leased facilities may receive a medical parking permit. SSA uses three forms as part of this program: SSA-3192, the Physician's Report (which the applicant's physician completes to verify the medical condition); Form SSA-3193, the Application and Statement (which the person seeking the permit completes when first applying for the medical parking space); and Form SSA-3194, the Renewal Certification (which medical parking permit holders complete to verify their continued need for the permit). The respondents are SSA employees and contractors seeking medical parking permits and their physicians. **Note** : Because SSA employees are federal workers and are PRA-exempt, the burden below is only for SSA contractors and physicians (of both SSA employees and contractors). *Type of Request:* Revision to an OMB-approved information collection. Number of respondents Frequency of response Average burden per response (minutes) Estimated annual burden (hours) SSA-3192 75 1 90 113 SSA-3193 75 1 30 38 SSA-3194 10 1 5 1 Totals 160 152 **10. Authorization to Obtain Earnings Data from the Social Security Administration—0960-0602** . A wage earner or an organization may request detailed earnings information from SSA. SSA collects the information on the SSA-581 to identify the earnings record, verify authorized access to the earnings record, and produce an itemized statement for release to the proper party. The respondents are various private/ public organizations/agencies needing detailed earnings information. *Type of Request:* Revision of an OMB-approved information collection. *Number of Respondents:* 33,000. *Frequency of Response:* 1. *Average Burden Per Response:* 2 minutes. *Estimated Annual Burden:* 1,100 hours. **11. Statement Regarding the Inferred Death of an Individual by Reason of Continued and Unexplained Absence—20 CFR 404.720 & 404.721—0960-0002** . Section 202(d)-(i) of the Social Security Act provides for the payment of various monthly survivor benefits and a lump sum death payment to certain survivors upon the death of an individual who dies fully or currently insured. If a person has been absent from his or her residence and has not been heard from for at least 7 years, SSA will presume he or she is deceased. SSA collects information on Form SSA-723-F4 to determine if SSA may presume a missing wage earner is deceased and, if so, to establish a date of presumed death. The respondents are persons having knowledge about the disappearance of a wage earner. *Type of Request:* Extension of an OMB-approved information collection. *Number of Respondents:* 3,000. *Frequency of Response:* 1. *Average Burden Per Response:* 30 minutes. *Estimated Annual Burden:* 1,500 hours. **12. Railroad Employment Questionnaire—20 CFR 404.1401, 404.1406-404.1408—0960-0078** . SSA uses the data on the SSA-671 to secure sufficient information to effect the required coordination with the Railroad Retirement Board for Social Security claims processing. SSA obtains data whenever claimants give indications of employment in the railroad industry. The respondents are applicants for Social Security benefits employed by a railroad or dependents of railroad workers. *Type of Request:* Extension of an OMB-approved information collection. *Number of Respondents:* 125,000. *Frequency of Response:* 1. *Average Burden Per Response:* 5 minutes. *Estimated Annual Burden:* 10,417 hours. **13. Government Pension Questionnaire—20 CFR 404.408a—0960-0160** . The Social Security Act and regulations provide an individual receiving spousal benefits and concurrently receiving a Government pension based on his or her own earnings not covered by Social Security may have the amount of the Social Security benefit reduced by two-thirds the amount of the Government pension. SSA uses the information on the SSA-3885 to determine whether the individual's Social Security benefit is subject to reduction, the amount of the reduction, the effective date of the reduction, and whether one of the exceptions in 20 CFR 404.408a applies. The respondents are individuals receiving spousal benefits and a Government pension. *Type of Request:* Extension of an OMB-approved information collection. *Number of Respondents:* 30,000. *Frequency of Response:* 1. *Average Burden Per Response:* 12.5 minutes. *Estimated Annual Burden:* 6,250 hours. **14. Teacher Questionnaire and Request for Administrative Information—20 CFR 416.1103(f)—0960-0646** . SSA must consider all relevant evidence when determining a child's disability under Title XVI of the Social Security Act. When determining the effects of a child's (or other individual's) impairment(s), SSA must obtain information about the child's functioning. Using Forms SSA-5665 and SSA-5666, SSA obtains formal testing results, teacher reports, therapy progress notes, individualized education program information and other records of a child's educational aptitude and achievement. The respondents are parents, teachers and other education personnel. *Type of Request:* Extension of an OMB-approved information collection. Form number Number of respondents Frequency of response Average burden per response (minutes) Total annual burden (hours) SSA-5665-BK 618,000 1 20 206,000 SSA-5666 615,000 1 15 153,750 Totals 1,233,000 359,750 SSA has made a correction to this Notice. Previously we inadvertently published the burden information for only one of the forms. We are now including a chart to show the information for both forms. **15. Statement of Income and Resources—20 CFR 416.207, 146.301—416.310, 416.704, and 416.708—0960-0124** . SSA collects information about income and resources on form SSA-8010-BK in Supplemental Security Income
(SSI)claims and redeterminations. SSA uses the information to make initial or continuing eligibility determinations for SSI claimants/recipients who are subject to deeming. The respondents are persons whose income and resources may be deemed (considered available) to applicants or beneficiaries of SSI benefits. *Type of Request:* Extension of an OMB-approved information collection. *Number of Respondents:* 341,000. *Frequency of Response:* 1. *Average Burden Per Response:* 26 minutes. *Estimated Annual Burden:* 147,767 hours. **16. Medicare Part D Subsidies Regulations—20 CFR Part 418—0960-0702** . The Medicare Prescription Drug Improvement, and Modernization Act of 2003
(MMA)established the Medicare Part D program for voluntary prescription drug coverage of premium, deductible, and co-payment costs for certain low-income individuals. The MMA also mandated the provision of subsidies for those individuals who qualify for the program and who meet eligibility criteria for help with premium, deductible, and/or co-payment costs. This law requires SSA to make eligibility determinations and to provide a process for appealing SSA's determinations. Regulation sections 418.3625(c), 418.3645, 418.3665(a), and 418.3670 contain public reporting requirements, listed below. Respondents are applicants for the Medicare Part D subsidies who request an administrative review hearing. *Type of Request:* Revision to an existing OMB-approved information collection. Section Annual number of respondents Frequency of response Average burden per response (minutes) Estimated annual burden (hours) § 418.3625(c) One may request in writing a change in date/time for an administrative review hearing 2,500 1 5 208 § 418.3645 One may request in writing a different person to conduct the administrative hearing if they suspect bias 10 1 20 3 § 418.3665(a) One may withdraw their request in writing for an administrative review hearing 1,000 1 5 83 § 418.3670 Applicants may ask SSA to vacate their previous request to dismiss an administrative review hearing 5 1 10 1 Total 3,515 295 Dated: May 22, 2008. Elizabeth A. Davidson, Reports Clearance Officer, Social Security Administration. [FR Doc. E8-11898 Filed 5-27-08; 8:45 am] BILLING CODE 4191-02-P DEPARTMENT OF STATE [Public Notice 6237] Determination on Provision of Assistance for Sudan Pursuant to section 451 of the Foreign Assistance Act of 1961, as amended (the “Act”)(22 U.S.C. 2261), and Section 1-100(a)(1) of Executive Order 12163, as amended, I hereby authorize, notwithstanding any other provision of law, the use of up to $3 million in Fiscal Year 2008 Peacekeeping Operations
(PKO)funds available under Chapter 6 of Part II of the Act, in order to provide, for any unanticipated contingencies, assistance authorized by Part I of the Act (which is deemed to include references to Chapter 6 of Part II) for Sudan. This determination shall be reported to Congress promptly and published in the **Federal Register** . Dated: April 25, 2008. John D. Negroponte, Deputy Secretary of State, Department of State. [FR Doc. E8-11894 Filed 5-27-08; 8:45 am] BILLING CODE 4710-26-P DEPARTMENT OF STATE [Public Notice 6238] Notice of Public Meeting on FY 2009 Refugee Admissions Program There will be a meeting on the President's FY 2009 Refugee Admissions Program on Wednesday, June 11, 2008 from 3 p.m. to 5 p.m. The meeting will be held at the Refugee Processing Center, 1401 Wilson Boulevard, Suite 700, Arlington, Virginia. The meeting's purpose is to hear the views of attendees on the appropriate size and scope of the FY 2009 Refugee Admissions Program. Seating is limited. Persons wishing to attend this meeting must notify the Bureau of Population, Refugees, and Migration at telephone
(202)663-1006 by 5 p.m. on Friday, May 30, 2008, to reserve a seat. Persons planning to present oral comments must notify us by 5 p.m. on Wednesday, June 4, 2008. Persons planning to submit written comments for consideration should provide those comments by 5 on Wednesday, June 4, 2008. All written comments should either be e-mailed to *spruellda@state.gov* or faxed to
(202)663-1364. If you have questions about the public meeting, please contact Delicia Spruell, PRM/Admissions Program Officer at
(202)663-1006. Information about the Refugee Admissions Program may be found at *http://www.state.gov/g/prm/.* Dated: May 16, 2008. Samuel Witten, Acting Assistant Secretary, Department of State. [FR Doc. E8-11857 Filed 5-27-08; 8:45 am] BILLING CODE 4710-33-P DEPARTMENT OF STATE [Public Notice 6226] Shipping Coordinating Committee; Notice of Subcommittee Meeting The Subcommittee on the Safety of Navigation of the Shipping Coordinating Committee
(SHC)will be holding an open meeting at 9:30 a.m. on Wednesday, June 11, 2008, in room 6215, U.S. Coast Guard Headquarters, 2100 Second Street, SW., Washington, DC. The purpose of the meeting is to prepare for the 54th session of the Subcommittee on Safety of Navigation
(NAV)of the International Maritime Organization
(IMO)which is scheduled for June 30-July 4, 2008, to be held at IMO Headquarters, 4 Albert Embankment, London SE1 7SR, United Kingdom. Items of principal interest on the agenda are: —Routing of ships, ship reporting and related matters; —Development of guidelines for integrated bridge systems (IBS), including performance standards for bridge alert management; —Amendments to the General Provisions on Ships' Routing; —Carriage requirements for a bridge navigational watch alarm system; —Review of the International Regulations for Preventing Collisions at Sea (COLREGs) regarding the right of way of vessels over pleasure craft; — Amendments to COLREG Annex I related to color specification of lights; — International Telecommunication Union
(ITU)matters, including Radiocommunication ITU-R Study Group 8; —Code of conduct during demonstrations/campaigns against ships on high seas; —Measures to minimize incorrect data transmissions by automatic identification system
(AIS)equipment; —Worldwide radio navigation system (WWRNS); —Development of an e-navigation strategy; —Development of carriage requirements for electronic chart display and information system (ECDIS); —Guidelines for uniform operating limitations of high-speed craft; —Guidelines on the layout and ergonomic design of safety centers on passenger Ships; —Review of vague expressions in the International Convention for the Safety of Life at Sea (SOLAS) regulation V/22; —Revision of the Guidance on the application of AIS binary messages; —Improved safety of pilot transfer arrangements; —Casualty analysis; and —Consideration of International Association of Classification Societies
(IACS)unified interpretations. Members of the public may attend these meetings up to the seating capacity of the room. Interested persons may seek information by writing: Mr. Edward J. LaRue, Jr., U.S. Coast Guard (CG-5413), Room 1407, 2100 Second Street, SW., Washington, DC 20593-0001 or by calling:
(202)372-1564. Dated: May 21, 2008. Mark Skolnicki, Executive Secretary, Shipping Coordinating Committee, Department of State. [FR Doc. E8-11895 Filed 5-27-08; 8:45 am] BILLING CODE 4710-09-P TENNESSEE VALLEY AUTHORITY Paperwork Reduction Act of 1995, as Amended by Public Law 104-13; Submission for OMB Review; Comment Request AGENCY: Tennessee Valley Authority. ACTION: Proposed collection; comment request. SUMMARY: The proposed information collection described below will be submitted to the Office of Management and Budget
(OMB)for review, as required by the Paperwork Reduction Act of 1995 (44 U.S.C Chapter 35, as amended). The Tennessee Valley Authority is soliciting public comments on this proposed collection as provided by 5 CFR 1320.8(d)(1). Requests for information, including copies of the information collection proposed and supporting documentation, should be directed to the Agency Clearance Officer: Mark R. Winter, Tennessee Valley Authority, 1101 Market Street (MP 3C), Chattanooga, Tennessee 37402-2801;
(423)751-6004. DATES: Comments should be sent to the Agency Clearance Officer no later than July 28, 2008. SUPPLEMENTARY INFORMATION: *Type of Request:* Regular Submission; extension without change, of a currently approved collection. *Title of Information Collection:* Reservoir Operations Study (ROS)—Recreation User Data. *Frequency of Use:* Annually. *Type of Affected Public:* Individual recreation users at public and commercial recreation areas and recreation users from private waterfront homes. *Small Business or Organizations Affected:* No. *Estimated Number of Annual Responses:* 3000. *Estimated Total Annual Burden Hours:* 990. *Estimated Average Burden Hours Per Response:* .33 hour. *Need For and Use of Information:* As part of system wide re-evaluation of TVA reservoirs and tailwaters, TVA conducted a survey of recreation use on 13 representative reservoirs and 6 representative tailwaters during calendar year 2002. Recreation use estimates were made for public use areas, commercial marinas, river outfitters, and private home owners. In each case, information was collected on the amount of recreation use, length of stay, facility preference, trip origin, expenditures and economic impact. These data now form the foundation for a TVA reservoir and tailwater recreation database. TVA recognizes the value of this database and proposes to keep it up-to-date and improving its utility by refining the survey design and conducting additional surveys of recreational use on representative reservoirs and tailwaters. Janice W. McAllister, Senior Manager, Enterprise IT Security, Information Services. [FR Doc. E8-11830 Filed 5-27-08; 8:45 am] BILLING CODE 8120-08-P DEPARTMENT OF TRANSPORTATION Federal Motor Carrier Safety Administration [Docket No. FMCSA-2008-0101] Agency Information Collection Activities; Revision of a Currently-Approved Information Collection: Licensing Applications for Motor Carrier Operating Authority AGENCY: Federal Motor Carrier Safety Administration (FMCSA), DOT. ACTION: Notice and request for information. SUMMARY: In accordance with the Paperwork Reduction Act of 1995, FMCSA announces its plan to submit the Information Collection Request
(ICR)described below to the Office of Management and Budget
(OMB)for its review and approval. The FMCSA seeks approval to revise an ICR entitled, “Licensing Applications for Motor Carrier Operating Authority,” that is used by for-hire motor carriers of regulated commodities, motor passenger carriers, freight forwarders, property brokers, and certain Mexico-domiciled motor carriers to register their operations with the FMCSA. The agency invites public comment on the ICR. DATES: We must receive your comments on or before *July 28, 2008.* ADDRESSES: You may submit comments bearing the Federal Docket Management System
(FDMS)Docket Number FMCSA-2008-0101 using any of the following methods: • Federal eRulemaking Portal: Go to *http://www.regulations.gov.* Follow the on-line instructions for submitting comments. • Mail: Docket Management Facility; U.S. Department of Transportation, 1200 New Jersey Avenue, SE., West Building Group Floor, Room W12-140, Washington, DC 20590-0001. • Hand Delivery: West Building Ground Floor, Room W12-140, 1200 New Jersey Avenue, SE., Washington DC, 20590, between 9 a.m. and 5 p.m., e.t., Monday through Friday, except Federal Holidays. • Fax: 1-202-493-2251. Each submission must include the Agency name and the docket number for this Notice. Please note that DOT posts all comments received without change to *http://www.regulations.gov,* including any personal information included in a comment. Please see the Privacy Act heading below. *Docket:* For access to the docket to read background documents or comments, go to *http://www.regulations.gov* at any time or Room W12-140 on the ground level of the West Building, 1200 New Jersey Avenue, SE., Washington, DC, between 9 a.m. and 5 p.m., Monday through Friday, except Federal holidays. The DMS is available 24 hours each day, 365 days each year. If you want acknowledgement that we received your comments, please include a self-addressed, stamped envelope or post card or print the acknowledgement page that appears after submitting your comment on-line. *Privacy Act:* Anyone may search the electronic form of all comments received into any of our dockets by the name of the individual submitting the comment (or of the person signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review the DOT's complete Privacy Act Statement in the **Federal Register** on April 11, 2000 (65 FR 19477). This information is also available at *http://docketsinfo.dot.gov.* FOR FURTHER INFORMATION CONTACT: Ms. Denise Ryan, Transportation Specialist, Office of Information Technology, Operations Division, Department of Transportation, Federal Motor Carrier Safety Administration, 6th Floor, West Building, 1200 New Jersey Ave., SE., Washington DC 20590. Telephone Number
(202)493-0242; E-mail Address *denise.ryan@dot.gov.* Office hours are from 9 a.m. to 5 p.m., e.t., Monday through Friday, except Federal Holidays. SUPPLEMENTARY INFORMATION: *Background:* The FMCSA is authorized to register for-hire motor carriers of regulated commodities and motor passenger carriers under the provisions of 49 U.S.C. 13902; freight forwarders under the provisions of 49 U.S.C. 13903; property brokers under the provisions of 49 U.S.C. 13904; and certain Mexico-domiciled motor carriers under the provisions of 49 U.S.C. 13902(c) and the North American Free Trade Agreement (NAFTA) motor carrier access provision. The forms used to apply for registration authority with the FMCSA are: Form OP-1 for motor property carriers and brokers; Form OP-1(P) for motor passenger carriers; Form OP-1(FF) for freight forwarders; and Form OP-1(MX) for certain Mexico-domiciled motor carriers. These forms request information on the applicant's identity, location, familiarity with safety requirements, and type of proposed operations. There are some differences on the forms due to specific statutory standards for registration of the different types of transportation entities. *Title:* Application for Certificate of Registration for Foreign Motor Carriers and Foreign Motor Private Carriers. *OMB Control Number:* 2126-0016. *Type of Request:* Revision of a currently-approved information collection. *Respondents:* Motor carriers, motor passenger carriers, freight forwarders, brokers, and certain Mexico-domiciled motor carriers. *Estimated Number of Respondents:* 43,810. *Estimated Time per Response:* 4 hours to complete Form OP-1(MX); and 2 hours to complete Forms OP-1, OP-1(FF), OP-1(P). *Expiration Date:* August 31, 2008. *Frequency of Response:* Other (as needed). *Estimated Total Annual Burden:* 71,218 hours [63 hours for Form OP-1(MX) + 68,010 hours for Form OP-1 + 1,085 hours for Form OP-1(FF) + 2,060 hours for Form OP-1(P) = 71,218]. *Public Comments Invited:* You are asked to comment on any aspect of this information collection, including:
(1)Whether the proposed collection is necessary for the agency to perform its mission;
(2)the accuracy of the estimated burden;
(3)ways for the FMCSA to enhance the quality, usefulness, and clarity of the collected information; and
(4)ways that the burden could be minimized without reducing the quality of the collected information. The agency will summarize or include your comments in the request for OMB's clearance of this information collection. Issued on: May 19, 2008. Michael S. Griffith, Acting Associate Administrator, Research and Information Technology. [FR Doc. E8-11890 Filed 5-27-08; 8:45 am] BILLING CODE 4910-EX-P DEPARTMENT OF TRANSPORTATION Federal Railroad Administration [Docket No. FRA-1999-6439, Notice No. 19] Adjustment of Nationwide Significant Risk Threshold AGENCY: Federal Railroad Administration (FRA), Department of Transportation (DOT). ACTION: Notice of Adjustment of the Nationwide Significant Risk Threshold. SUMMARY: In accordance with Title 49 Code of Federal Regulations Part 222, Appendix D, FRA is updating the Nationwide Significant Risk Threshold (NSRT). This action is needed to ensure that the public has the proper threshold of permissible risk for calculating quiet zones established in relationship to the NSRT. This is the second update to the NSRT since the final rule, titled “Use of Locomotive Horns at Highway-Rail Grade Crossings,” was amended in response to petitions for reconsideration on August 17, 2006 (71 FR 47614). This notice announces that the NSRT has fallen from 19,047 to 17,610. DATES: The effective date is May 28, 2008. FOR FURTHER INFORMATION CONTACT: Ronald Ries, Office of Safety, FRA, 1200 New Jersey Avenue, SE., Washington, DC 20590 (telephone:
(202)493-6299 or e-mail: *Ronald.Ries@dot.gov* ); or Kathryn Shelton, Office of Chief Counsel, FRA, 1200 New Jersey Avenue, SE., Washington, DC 20590 (telephone:
(202)493-6038 or e-mail: *Kathryn.Shelton@dot.gov* ). SUPPLEMENTARY INFORMATION: Background The NSRT is simply an average of the risk indexes for gated public crossings nationwide where train horns are routinely sounded. FRA developed this risk index to serve as one threshold of permissible risk for quiet zones established under this rule across the Nation. Thus, a community that is trying to establish and/or maintain its quiet zone pursuant to 49 CFR Part 222 can compare the Quiet Zone Risk Index calculated for its specific crossing corridor to the NSRT to determine whether sufficient measures have been taken to compensate for the excess risk that results from prohibiting routine sounding of the locomotive horn. (In the alternative, a community can establish its quiet zone in comparison to the Risk Index With Horns, which is a corridor-specific measure of risk to the motoring public when locomotive horns are routinely sounded at every public highway-rail grade crossing within the quiet zone.) In 2006, when the final rule, titled “Use of Locomotive Horns at Highway-Rail Grade Crossings” was amended, the NSRT was 17,030 (71 FR 47614, August 17, 2006). In 2007, FRA recalculated the NSRT to be 19,047 (72 FR 14850, March 29, 2007.) New NSRT Using collision data from 2002 to 2006, FRA has recalculated the NSRT based on formulas identified in 49 CFR Part 222, Appendix D. In making this recalculation, FRA noted that the total number of gated, nonwhistle ban crossings was 38,420. EN28MY08.002 Applying the fatality rate and injury rate to the probable number of fatalities and casualties predicted to occur at each of the 38,420 identified crossings and the predicted cost of the associated injuries and fatalities, FRA calculates the NSRT to be 17,610. Issued in Washington, DC on May 21, 2008. Grady C. Cothen, Jr., Deputy Associate Administrator for Safety Standards and Program Development. [FR Doc. E8-11848 Filed 5-27-08; 8:45 am] BILLING CODE 4910-06-P DEPARTMENT OF TRANSPORTATION Surface Transportation Board [STB Ex Parte No. 670 (Sub-No. 1)] Notice of Rail Energy Transportation Advisory Committee Meeting AGENCY: Surface Transportation Board. ACTION: Notice of Rail Energy Transportation Advisory Committee meeting. SUMMARY: Notice is hereby given of a meeting of the Rail Energy Transportation Advisory Committee (RETAC), pursuant to section 10(a)(2) of the Federal Advisory Committee Act, Public Law 92-463, as amended (5 U.S.C., App. 2). DATES: The meeting will be held on June 12, 2008, beginning at 9 a.m. ADDRESSES: The meeting will be held in the Surface Transportation Board's hearing room on the 1st floor of the agency's headquarters at Patriot's Plaza, 395 E Street, SW., Washington, DC 20423-0001. FOR FURTHER INFORMATION CONTACT: Scott M. Zimmerman at 202-245-0202. [Assistance for the hearing impaired is available through the Federal Information Relay Service
(FIRS)at:
(800)877-8339.] SUPPLEMENTARY INFORMATION: RETAC arose from a proceeding instituted by the Board, in *Establishment of a Rail Energy Transportation Advisory Committee,* STB Ex Parte No. 670. RETAC was formed to provide advice and guidance to the Board, and to serve as a forum for discussion of emerging issues regarding the transportation by rail of energy resources, particularly, but not necessarily limited to, coal, ethanol, and other biofuels. The purpose of this meeting is to continue discussions regarding issues such as rail performance, capacity constraints, infrastructure planning and development, and effective coordination among suppliers, carriers, and users of energy resources. The meeting, which is open to the public, will be conducted pursuant to RETAC's charter and Board procedures. Further communications about this meeting may be announced through the Board's Web site at *http://www.stb.dot.gov.* This action will not significantly affect either the quality of the human environment or the conservation of energy resources. Authority: 49 U.S.C. 721, 49 U.S.C. 11101; 49 U.S.C. 11121. Decided: May 22, 2008. By the Board, Anne K. Quinlan, Acting Secretary. Anne K. Quinlan, Acting Secretary. [FR Doc. E8-11878 Filed 5-27-08; 8:45 am] BILLING CODE 4915-01-P [] DEPARTMENT OF THE TREASURY Submission for OMB Review; Comment Request May 20, 2008. The Department of Treasury will submit the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Public Law 104-13 on or after the date of publication of this notice. 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 11000, 1750 Pennsylvania Avenue, NW. Washington, DC 20220. DATES: Written comments should be received on or before June 27, 2008 to be assured of consideration. United States Mint *OMB Number:* 1525-0012. *Type of Review:* Revision. *Title:* Generic Clearance for Voluntary Surveys to Implement E.O. 12882. Implemented by Sales and Marketing Division. *Description:* This is a revised Generic Clearance for an undefined number of customer satisfaction and opinion surveys or focus group interviews to be conducted over the next three years. The information collected from these surveys will be used to improve U.S. Mint products and services. *Respondents:* Individuals or households. *Estimated Total Reporting Burden:* 60,813 hours. *Clearance Officer:* Yvonne Pollard
(202)354-6784, United States Mint, 799 9th Street, NW., 4th Floor, Washington, DC 20220. *OMB Reviewer:* Alexander T. Hunt
(202)395-7316, Office of Management and Budget, Room 10235, New Executive Office Building, Washington, DC 20503. Robert Dahl, Treasury PRA Clearance Officer. [FR Doc. E8-11818 Filed 5-27-08; 8:45 am] BILLING CODE 4810-37-P 73 103 Wednesday, May 28, 2008 Rules and Regulations Part II Department of Health and Human Services Centers for Medicare & Medicaid Services 42 CFR Part 423 Medicare Program; Medicare Part D Claims Data; Final Rule DEPARTMENT OF HEALTH AND HUMAN SERVICES Centers for Medicare & Medicaid Services 42 CFR Part 423 [CMS-4119-F] RIN 0938-AO58 Medicare Program; Medicare Part D Claims Data AGENCY: Centers for Medicare & Medicaid Services (CMS), HHS. ACTION: Final rule. SUMMARY: This final rule allows the Secretary to collect claims data that are presently being collected for Part D payment purposes for other research, analysis, reporting, and public health functions. The Secretary needs to use these data because other publicly available data are not, in and of themselves, sufficient for the studies and operations that the Secretary needs to undertake as part of the Department of Health and Human Service's obligation to oversee the Medicare program, protect the public's health, and respond to Congressional mandates. These data will also be used to better identify, evaluate and measure the effects of the Medicare Modernization Act of 2003, (MMA). DATES: *Effective Date:* This regulation is effective June 27, 2008. *Date of Applicability:* This regulation applies to Part D claims data collected on or after January 1, 2006. Following the effective date of this final rule, we will recollect under section 1860D-12(b)(3)(D) of the Act any data that were first submitted prior to the effective date of this final rule by extracting them from the Part D claims data already collected for payment purposes. FOR FURTHER INFORMATION CONTACT: Alissa DeBoy,
(410)786-6041; Nancy DeLew,
(202)690-7351. SUPPLEMENTARY INFORMATION: Copies: To order copies of the **Federal Register** containing this document, send your request to: New Orders, Superintendent of Documents, P.O. 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 toll free at 1-888-293-6498) or by faxing to
(202)512-2250. The cost for each copy is $10. As an alternative, you can view and photocopy the **Federal Register** document at most libraries designated as Federal Depository Libraries and at many other public and academic libraries throughout the country that receive the **Federal Register** . This **Federal Register** document is also available from the **Federal Register** online database through GPO Access, a service of the U.S. Government Printing Office. The Web site address is: *http:// www.access.gpo.gov/fr/index.html.* I. Background A. Requirements for Issuance of Regulations Section 902 of the Medicare Prescription Drug, Improvement, and Modernization Act of 2003
(MMA)(Pub. L. 108-173) amended section 1871(a)(3) of the Social Security Act (the Act) and requires the Secretary, in consultation with the Director of the Office of Management and Budget (OMB), to establish and publish timelines for the publication of Medicare final regulations based on the previous publication of a Medicare proposed or interim final regulation. Section 1871(a)(3)(B) of the Act also states that the timelines for these regulations may vary, but shall not exceed 3 years after publication of the preceding proposed or interim final regulation, except under exceptional circumstances. This final rule finalizes provisions set forth in our October 18, 2006 proposed rule. In addition, this final rule is being published within the 3-year time limit imposed by section 1871(a)(3)(B) of the Act. Therefore, we believe that the final rule is in accordance with the Congress's intent to ensure timely publication of final regulations. B. General Overview As stated in the October 18, 2006 proposed rule, under the Act, the Secretary has the authority to include in Part D sponsor contracts any terms or conditions the Secretary deems necessary and appropriate, including requiring the organization to provide the Secretary with such information as the Secretary may find necessary and appropriate. (See section 1857(e)(1) of the Act as incorporated into Part D through section 1860D-12(b)(3)(D) of the Act.) We proposed to implement section 1860D-12(b)(3)(D) of the Act to allow the Secretary to collect the same claims information now collected under the authority of section 1860D-15 of the Act for purposes including reporting to the Congress and the public, conducting evaluations of the overall Medicare program, making legislative proposals to Congress, and conducting demonstration projects. While the purposes underlying such collection are discussed in more detail in this final rule, they include, but are not limited to, evaluating the effectiveness of the new prescription drug benefit and its impact on health outcomes, performing Congressionally mandated or other demonstration and pilot projects and studies, reporting to Congress and the public regarding expenditures and other statistics involving the new Medicare prescription drug benefit, studying and reporting on the Medicare program as a whole, and creating a research resource for the evaluation of utilization and outcomes associated with the use of prescription drugs. We note that because this final rule applies to all Part D sponsors, it applies to any entity offering a Part D plan, including both prescription drug plan sponsors and Medicare Advantage organizations offering qualified prescription drug coverage. We further note that the Part D prescription drug event data (hereinafter also referred to as “Part D claims data”) collected in accordance with section 1860D-12(b)(3)(D) of the Act will include 37 drug claim elements submitted by drug plan sponsors to the Secretary, which in accordance with § 423.100, include not only data from claims for drugs, but also data from claims for insulin, biological products, certain medical supplies, and vaccines. II. Provisions of the Proposed Rule With an Analysis of and Response to Public Comments We received approximately 118 items of timely correspondence containing comments on the October 18, 2006 proposed rule. Commenters included health policy organizations, pharmacies and pharmacy-related organizations, members of the Congress, researchers, insurance industry representatives, physicians and other health care professionals, beneficiary advocacy groups, representatives of hospitals, Part D beneficiaries, a pharmacy benefit managers’ trade association and others. In this final rule, we address all comments and concerns on the policies included in the proposed rule. The following lists the provisions of the proposed rule that received the most comments: • External access to the data • Uses for the data • Privacy protections for the data Generally, the vast majority of commenters expressed strong support for the proposed rule, declaring it essential for the success and accurate evaluation of the Medicare Part D program. There was also a significant amount of agreement among the commenters that external entities be allowed access to Part D claims data. Commenters pointed out that CMS could not possibly fund all the research needed, and because of that, allowing external entities access to these data is necessary in order to evaluate the many health care issues arising from the new prescription drug benefit. Commenters also noted that research by external entities is likely to result in lower government expenditures and better delivery of health care to beneficiaries. Many of the commenters supporting the rule cited multiple examples of the potential benefits to the public health that could result with the access to Part D claims data by qualified organizations and individuals, including assessing the impact prescription drugs have on the health outcomes of the elderly, cost efficiencies, quality of care measures, and the efficacy of prescription drugs. A number of comments addressed privacy protections, which impact the collection and release of claims data, and other commenters expressed concern about sensitive financial information being released. The majority of commenters acknowledged that a risk to protected information exists; however, they believed that the risk is no greater than the risk involved when allowing access to currently available Medicare data. Several commenters raised concerns about the inherent limitations associated with the use of claims data for research purposes and requested that we acknowledge these limitations. In the following sections, we address all of these comments. A. General Provisions 1. Statutory Basis On December 8, 2003, the Congress enacted the Medicare Prescription Drug, Improvement, and Modernization Act of 2003
(MMA)(Pub. L. 108-173). Title I of the MMA amended the Act to establish a new voluntary prescription drug benefit program, Medicare Part D. As we stated in the preamble to the January 28, 2005 final rule (70 FR 4197) implementing the new prescription drug benefit, we believe that the addition of outpatient prescription drug coverage to the Medicare program is the most significant change to the Medicare program since its inception in 1965. Unlike Parts A and B of the Medicare program, where Medicare acts as the payer and insurer and generally pays for items and services on a fee-for-service basis, the prescription drug benefit is based on a private market model. Under this model, CMS contracts with private entities—prescription drug plan
(PDP)sponsors, Medicare Advantage
(MA)organizations, as well as other types of Medicare health organizations—who then act as the payers and insurers for prescription drug benefits. These private entities are generally referred to as “Part D sponsors” in our rules. Section 1860D-12 of the Act contains the majority of provisions governing the contracts CMS enters into with the Part D sponsors. That section, entitled, “Requirements for and contracts with prescription drug plan
(PDP)sponsors,” incorporates by reference many of the contract requirements that previously were applicable to Medicare Advantage organizations. One of the incorporated provisions at section 1860D-12(b)(3)(D) of the Act, is section 1857(e)(1) of the Act, which provides broad authority for the Secretary to add terms to the contracts with Part D sponsors, including terms that require the sponsor to provide the Secretary “with such information * * * as the Secretary may find necessary and appropriate.” We believe that the broad authority of section 1860D-12(b)(3)(D) of the Act authorizes us to collect most of the information we currently collect to properly pay sponsors under the statute. However, section 1860D-15 of the Act contains provisions that might be viewed as limiting such collection. Therefore, we engaged in this rulemaking in order to resolve the statutory ambiguity, as well as to implement the broad authority of section 1860D-12(b)(3)(D) of the Act. Most of the payment provisions with respect to Part D sponsors are found in section 1860D-15 of the Act. 1 Subsections
(d)and
(f)of section 1860D-15 of the Act authorize the Secretary to collect any information he needs to carry out that section. However, those subsections also state that “information disclosed or obtained under [section 1860D-15 of the Act] may be used by officers, employees, and contractors of the Department of Health and Human Services only for the purposes of, and to the extent necessary in, carrying out [section 1860D-15 of the Act].” (Sections 1860D-15(d)(2)(B) and (f)(2) of the Act). 1 We note that there are other provisions outside of section 1860D-15 of the Act that also contain payment provisions. For example, section 1860D-14 of the Act discusses how CMS pays the low-income subsidy. In the January 28, 2005 Medicare prescription drug benefit final rule (70 FR 4399), we stated that the section 1860D-15 of the Act restriction applies only in cases where section 1860D-15 of the Act is the authority for collecting the information. When information is collected under an independent authority (even if the collected information duplicates the data collected under section 1860D-15 of the Act) the restrictions under 1860D-15 of the Act would not apply. In the January 28, 2005 final rule (70 FR 4399), we noted that because quality improvement organizations
(QIOs)have independent authority to collect Part D claims data in order to evaluate the quality of services provided by Part D sponsors, QIOs would not be barred from collecting such data despite the restrictions of section 1860D-15 of the Act. We refer readers to the October 18, 2006 proposed rule for the exact citation to the discussion in the January 28, 2005 final rule (71 FR 61447). Similar to the statutory provisions authorizing QIOs to collect the information they need to perform their statutory duties, section 1860D-12(b)(3)(D) of the Act recognizes that the Secretary will need to collect a broad array of data in order to properly carry out his responsibilities as head of the Department of Health and Human Services (DHHS). Thus, if the Secretary determines it is necessary and appropriate under section 1860D-12 of the Act for him to collect Part D claims data in order to carry out responsibilities outside section 1860D-15 of the Act, then section 1860D-15 of the Act would not serve as an impediment to such collections. As stated in the October 18, 2006 proposed rule, we also believe that language in sections 1860D-12(b)(3)(D) and 1857(e)(1) of the Act indicating that the authority to collect information exists only “except as otherwise provided,” and in a manner that is “not inconsistent with this Part,” would not serve as a hindrance to the independent collection of Part D claims data, since on its face, section 1860D-15 of the Act restricts use of information only when collected under that authority. As we stated in the proposed rule, the Congress most likely included the broad grant of authority in section 1860D-15 of the Act in order to ensure that the Secretary, without engaging in any rulemaking, would have the legislative authority to collect any necessary data in order to pay Part D sponsors correctly. However, we do not believe that the Congress intended to restrict the Secretary when the Secretary otherwise has independent authority to collect identical information to that collected under section 1860D-15 of the Act. Rather, we noted that the Secretary will need to evaluate Part D claims information in order to determine how access to Part D drug benefits affects beneficiary utilization of services under Parts A and B of the Medicare program. Specifically, when Congress enacted the MMA, one of the stated reasons was to ensure that “by lowering the cost of critical prescription drugs, seniors will better be able to manage their health care, and ultimately live longer, healthier lives.” (Press Release, House Ways and Means Committee, Seniors Wait for Affordable Rx Drugs Comes to an End. President Bush Signs Historic Medicare Bill into Law (December 8, 2003) (available at *http://waysandmeans.house.gov/news.asp* )). In order to determine whether lowering the costs of prescription drugs actually reduces health expenditures or improves health outcomes for beneficiaries, the Secretary will need to match individual level Parts A and B data with Part D claims data. In this way, the Secretary will be able to evaluate the effectiveness and efficiency of the Part D benefit and report to the Congress and others on the progress of the program. We are required to report to the Congress regarding whether mandated disease management demonstrations are budget neutral and whether beneficiaries in these demonstrations are on the appropriate medications. As we stated in the preamble of the proposed rule we may also need to make reports under the Part D program, for example, the publication of statistics detailing aggregate Medicare and beneficiary spending by class of drug, average number of drugs used by beneficiaries, total Medicare program spending, and other similar statistics. In order to derive such statistics, we would need to use Part D claims data. In the proposed rule, as well as in this final rule, we outlined a wide variety of situations in which it will be “necessary and appropriate” for CMS to evaluate the same information collected under section 1860D-15 of the Act, even though such information would not be used to implement section 1860D-15 of the Act. In these situations, we believe the clear language of section 1860D-12(b)(3)(D) of the Act provides the authority to collect the necessary information, and nothing about such collection will be inconsistent or in conflict with any other part of the statute. In addition, as discussed in this preamble, we are adding section 1106 of the Act as a statutory basis for this final rule, as that section authorizes release of data by the agency through regulation. *Comment:* Some commenters stated that the proposed rule was inconsistent with the statute. Commenters also asserted that the collection is neither necessary nor appropriate, and some contended that the rule would improperly allow the release of proprietary data. *Response:* We refer readers to our discussion of the statutory basis in both the proposed rule (71 FR 61446) and in section II.A.1. of this final rule. As noted in the proposed rule, section 1860D-12(b)(3)(D) of the Act (and its incorporation of section 1857(e)(1)) of the Act provide broad authority to the Secretary to require Part D sponsors to provide the Secretary with “such information as the Secretary may find necessary and appropriate.” In addition, sections 1860D-15(d)(2)(B) and (f)(2) of the Act, by their own terms, restrict information only when “disclosed or obtained under the provisions of [section 1860D-15 of the Act].” Thus, we continue to believe that when information is collected through a statutory authority independent of section 1860D-15 (such as in the case of QIOs, who have independent authority to collect data) the restrictions of section 1860D-15 of the Act would not apply, and nothing about the collection or use of the claims data would create an inconsistency or conflict in the statute. We also believe the collection of claims data under section 1860D-12 of the Act is both necessary and appropriate for the reasons discussed in the proposed rule and in this final rule. For example, the collection of such claims data will permit the Secretary to conduct high level, internal analyses of the Part D benefit, such as which drugs are commonly used by the Medicare population, the utilization of generic drugs in the Part D benefit, the effect of benefit design on catastrophic costs (costs for which reinsurance is available), the number of individuals who entered the catastrophic phase of the benefit, and many more types of analysis. Similarly, the Secretary will have the opportunity to crosswalk Part D claims data to Parts A and B data in order to analyze the effect of access to prescription drugs on utilization under hospital and supplementary medical insurance. We know that one of the stated reasons for the drug benefit was to modernize Medicare and ensure that beneficiaries were not enduring unnecessary hospitalizations due to failure to access preventive prescription drug regimens. At the time the prescription drug benefit was being enacted into law, then-chairman of the Senate Finance Committee, Senator Charles Grassley, stated: [T]his bill is about enhancing quality of life * * *. Today, the practice of medicine—and a lot of the thanks can go to prescription drugs—is to keep people out of hospitals and out of operating rooms. So people who cannot afford drugs, who go to the doctor very sick, are going to not only end up in a place they do not want to go, because people would rather not go to hospitals, rather not go to operating rooms. It is going to save our programs a lot of money, both private and public payment programs, for doctors and hospitals, when we can have people go into programs where they can get prescription drugs and keep their health up so they do not go to the hospital. (Medicare Prescription Drug, Improvement, and Modernization Act of 2003—Conference Report, 149 Cong. Rec. S15882-03, *S15883 and S15884 (November, 25, 2003)). Access to Parts A, B, and D claims data will allow the Secretary to analyze the prescription drug utilization of chronically ill patients over time, and determine whether increases in prescription drug utilization do, in fact, result in fewer hospitalizations. This is the type of analysis we believe the Congress expected the Secretary to engage in, and such analysis is both necessary and appropriate under the law. Finally, in response to concerns about releasing proprietary data to external entities as a result of this rulemaking, we note that data which could affect Medicare program spending, such as rebates, bids, reinsurance, and risk-sharing data, are not part of this rulemaking. In addition, as discussed later in this preamble, this rulemaking places certain limitations on data when released outside of CMS. We believe that it is in the interest of public health to share information collected under the regulations promulgated by this rule with entities outside of CMS for legitimate research, or in cases of other governmental agencies, for purposes consistent with their mission. Through the application of our “minimum data necessary policy”, with some additional restrictions to protect beneficiary confidentiality and commercially sensitive data of Part D sponsors, and our data sharing procedures (which ensure the agency's compliance with the Health Insurance Portability and Accountability Act of 1996 (HIPAA), the Privacy Act of 1974, and other applicable laws), we will limit the use and disclosure of Part D claims data to ensure that the data are only used or disclosed as permitted or required by applicable law, and not inappropriately disclosed in a manner which could undermine the competitive nature of the Part D program. *Comment:* One commenter requested that CMS postpone implementation of this regulation until the Congress clarifies CMS's statutory authority and that CMS answer certain questions in a second posting for comment. *Response:* We believe we have the authority to collect Part D claims data under sections 1860D-12 and 1860D-15 of the Act, and to disclose Part D claims data collected under section 1860D-12 of the Act, in accordance with section 1106 of the Act. This final rule is sufficiently related to the proposals in the proposed rule, which were the subject of vigorous review and comment by the public, and we are not posting the proposal for a second round of comments. *Comment:* One commenter questioned why we were equating collecting data with accessing data. *Response:* As stated in both the proposed rule and this final rule, in order to ensure that Part D sponsors are not required to submit a second set of the same data already collected under section 1860D-15, we would collect the data that are the subject of this final rule by extracting them from Part D claims data already collected for payment purposes. This is the same approach we used when we discussed QIO access to data in the January 28, 2005 Part D final rule (70 FR 4399), where we stated that “to the extent QIOs need access to data from the transactions between pharmacies and Part D sponsors, these data could be extracted from the claims data submitted to us”. Thus, in the preamble to this final rule, as in the preamble to the proposed rule (71 FR 61447), we may refer to “accessing” rather than “collecting” Part D data. 2. Information To Be Collected In the proposed rule, we proposed to independently collect the same claims information collected under section 1860D-15 of the Act under the authority of section 1860D-12(b)(3)(D) of the Act. The Part D claims data for 2006 and 2007 includes 37 data elements. We referred readers to the Prescription Drug Event data instructions which can be accessed at *http://www.cms.hhs.gov/DrugCoverageClaimsData/01_PDEGuidance.asp#TopOfPage* for a full description of this information. These instructions define each data element and its specific potential use for CMS's payment process. Generally stated, these data elements include the following: • Identification of the Part D sponsor and Part D plan through contract number and plan benefit package identification number. • Health insurance claim number, which identifies the particular beneficiary receiving the prescription. • Patient date of birth and gender. • Date of service. • Date paid by the plan. • Identification of pharmacy where the prescription was filled. • Identification of prescribing health care professional. • Identification of dispensed product using national drug code
(NDC)number. • Indication of whether drug was compounded or mixed. • Indication of prescriber's instruction regarding substitution of generic equivalents or order to “dispense as written.” • Quantity dispensed (for example, number of tablets, grams, milliliters, or other unit). • Days supply. • Fill number. • Dispensing status and whether the full quantity is dispensed at one time, or the quantity is partially filled. • Identification of coverage status, such as whether the product dispensed is covered under the plan benefit package or under Part D or both. This code also identifies whether the drug is being covered as part of a Part D supplemental benefit. • Indication of whether unique pricing rules apply, for example because of an out-of-network or Medicare as Secondary Payer services. • Indication of whether beneficiary has reached the annual out-of-pocket threshold, which triggers reduced beneficiary cost-sharing and reinsurance subsidy. • Ingredient cost of the product dispensed. • Dispensing fee paid to pharmacy. • Sales tax. • For covered Part D drugs, the amount of gross drug costs that are both below and above the annual out-of-pocket threshold. • Amount paid by patient and not reimbursed by a third party (such as copayments, coinsurance, or deductibles). • Amount of third party payment that would count toward a beneficiary's true out-of-pocket (TrOOP) costs in meeting the annual out-of-pocket threshold, such as payments on behalf of a beneficiary by a qualifying State Pharmaceutical Assistance Program (SPAP). • Low income cost sharing subsidy amount (if any). • Reduction in patient liability due to non-TrOOP-eligible payers paying on behalf of the beneficiary. This would exclude payers whose payments count toward a beneficiary's true out of pocket costs, such as SPAPs. • Amounts paid by the plan for basic prescription drug coverage and amounts paid by plan for benefits beyond basic prescription drug coverage. In 2008, the number of elements collected in the Part D claims data was expanded from 37 to 39. Specifically, we added additional elements to reflect the estimated rebate amount applied to the point-of-sale price and the vaccine administration fee. Because these elements were added for 2008, they were not addressed in the October 18, 2006 proposed rule. Furthermore, in the October 2006 proposed rule (71 FR 61447), we did not explicitly discuss how we would respond to future changes in the elements collected as part of the claim. Rather, the proposed rule included only a discussion of the 37 elements that then comprised the Part D claim and proposed that we would collect these 37 elements under section 1860D-12(b)(3)(D) of the Act. As a result, interested parties had an opportunity to comment only upon our proposal to collect the original 37 elements of the Part D claim under section 1860D-12(b)(3)(D) of the Act, and there has not been any similar opportunity for interested parties to submit comments on whether the two new elements should also be collected under section 1860D-12(b)(3)(D) of the Act, such that they may also be used for non-payment-related purposes. Accordingly, we will not be collecting these two data elements under section 1860-12(b)(3)(D) of the Act at this time. We are finalizing a regulation establishing our authority to collect under section 1860D-12(b)(3)(D) of the Act only those 37 data elements that were part of the prescription drug event
(PDE)record in 2006. Data regarding these 37 elements may be used for both payment-related and nonpayment-related purposes. As discussed later in this preamble, such use will be subject to our minimum necessary data policy, our data sharing procedures, and the encryption of certain identifiers and aggregation of cost data to protect beneficiary confidentiality and commercially sensitive data of Part D sponsors. Because data regarding the 38th and 39th elements will continue to be collected only under section 1860D-15(d)(2) and (f)(1) of the Act, consistent with § 423.322(b), these data may be used only for payment-related purposes. We note that this final rule does not extend to rebate or other price concession data, otherwise known as “direct or indirect remuneration” or “DIR”, with the exception of DIR that may be reflected in the negotiated price paid for a drug at the point of sale. Again, the collection of Part D data under the authority of section 1860D-12 of the Act in accordance with this final rule, is limited to the original 37 data elements collected as part of the Part D claims data. We have clarified this in response to comments and in the regulatory text. *Comment:* Commenters were generally supportive of CMS's proposal to access Part D claims data for research and non-research purposes, and agreed that the data will provide valuable information and be essential in the evaluation of the Part D benefit. Several commenters requested additional elements be added to the original 37 PDE elements outlined in the proposed rule. *Response:* We agree that the PDE data elements we now collect will provide a valuable tool for evaluating the Part D program, and appreciate the suggestions to add other elements for collection. This final rule is first and foremost a clarification of the statutory authority that allows us to collect the original 37 PDE elements outlined in the proposed rule and this final rule and to access them for purposes other than payment. Since these data are already being collected under the Part D program, we would access the already-collected data and make them available for research and non-research purposes, without undue burden to Part D sponsors or beneficiaries. As discussed above, in 2008, the number of PDE data elements was expanded to 39. In future years, we may revise our guidance on PDE Reporting to include additional elements on the claim beyond the elements presently collected. Through separate rulemaking, we will address whether we intend to collect any of these additional elements under our authority in section 1860D-12(b)(3)(D) of the Act. *Comment:* Several commenters noted that the proposed rule relates to drug claims and related information and asked for clarification as to what is meant by this phrase. A few commenters noted that the presence of this phrase in the proposed regulatory text suggests that CMS may be contemplating using and sharing rebate and other discount and pricing concession data. *Response:* Rebate and other price concession data are not the subject of this final rule. This rulemaking applies to Part D claims data only, and is limited to the original 37 elements reported on the PDE. To further clarify this point we are amending proposed § 423.505(f)(3) to delete the applicable reference to “related information.” *Comment:* Several commenters expressed concern about access to cost and pricing data. Several commenters noted that pricing data contained on the Part D claim are not an accurate reflection of the actual costs to plans. These commenters also requested clarification that the information we are proposing to collect and disclose relate only to Part D claims data, and not to competitively sensitive financial data regarding rebates, discounts or other negotiated price concessions. The commenters expressed a concern that release of competitively sensitive data could undermine the competitive bid process. They assert that plans will be able to adjust their bids on the basis of knowledge of each others' data, resulting in higher drug costs for all. *Response:* We share the commenters concerns about the need to protect the sensitive data under the Part D program. Because the Medicare drug benefit is based on a competitive business model, to release commercially or financially sensitive data to the public could negatively impact Part D sponsors' ability to negotiate for better prices, and ultimately affect the ability of sponsors to hold down prices for beneficiaries and taxpayers. Therefore, we have adopted a number of protections to mitigate these concerns. First, we have clarified that this final rule applies only to the 37 original elements of Part D claims data and not to rebate and other price concessions data. As discussed above, to the extent that the PDE record was amended in 2008 to include data on estimated rebates applied at the point of sale, we have clarified it in the regulation that we will not be collecting this information under that authority. In addition, we note that plan-specific bid information is not included on the claim, and therefore, would not be the subject of this rulemaking. Second, with respect to our disclosures of information collected under this rulemaking to external entities, we have developed an approach to minimize the risk of unauthorized disclosure of beneficiary identifiable information, as well as the use of commercially sensitive data of Part D sponsors. Similar to the process used under Parts A and B program: • We will require research using beneficiary identifiable data to be conducted by an experienced entity at a reputable organization, with an appropriate research design, and with assurances to protect beneficiary confidentiality. Research is to be made available to the public and identifiable data is not released for commercial purposes. • We will only release beneficiary identifiable data for research purposes if the CMS privacy board approves the data release and then, will only release the minimum data necessary for the study. • Requesters who receive identifiers to link to another dataset will be required to re-encrypt beneficiary identifiers, after data linkage, to minimize the risk of accidental disclosure. • Requesters will sign a data use agreement which carries penalties for misuse or intentional release of beneficiary identifiable information. In addition to these protections of beneficiary identifiable information, we plan to impose additional restrictions to further protect beneficiary confidentiality and plan commercially sensitive information. When releasing data to external entities, we will restrict releases according to the following principles: • Only the minimum necessary elements from the PDE will be released for a project. In accordance with this principle, cost data will not be released unless necessary for the project. • Drug cost elements (that is, ingredient cost, dispensing fee, and sales tax) will be aggregated. • Beneficiary identifiers, pharmacy identifiers and prescriber identifiers will be encrypted where not needed to link to other datasets. Additionally, an element representing the internal prescription service reference number assigned by pharmacies will not be released so as to not indirectly reveal pharmacy identifiers. • Plan identifiers will always be encrypted for external entities. We note that the internal plan identification numbers on the claim would also not be available to external entities as these represent reference numbers assigned by the plan at the time a drug is dispensed and release of such numbers could lead to a de facto identification of the plan. We also note that when we state in this preamble that an identifier will be encrypted, this means that it will be replaced with a non-identifiable number or code such that there is a low probability of assigning any meaning to the replacement number or code. Unless otherwise noted, encryption will occur without any decryption, and we would not provide a key that allows for an encrypted identifier to be converted back into its original form. We believe these restrictions will protect both the commercially sensitive data of Part D plans, such as the plan identifiers, pharmacy identifiers, prescriber identifiers and cost elements, as well as the beneficiary identifiable data included on the claim. Similar protections for both beneficiary identifiable information as well as commercially sensitive data of Part D sponsors will be in place for releases to governmental entities as well including States, Congress and other executive branch agencies. For both States and non-HHS executive branch agencies, the drug cost elements on the claim (ingredient cost, dispensing fee, and sales tax) will be aggregated together, and will not be available in a disaggregated format, except that, upon request, CMS will exclude sales tax from the aggregation at the individual claim level if necessary for the project. We believe this aggregation will serve to ensure that some of the most confidential data on the claim—the separate costs paid by Part D sponsors for ingredient cost or dispensing fee—will not be vulnerable to any unauthorized release. However, because these government agencies may need other data on the claim in order to coordinate treatment of beneficiaries or further study care received by individual beneficiaries, we will make the beneficiary, plan, pharmacy, and prescriber identifiers available to these entities where needed. For example, as discussed later in this preamble, States have specifically requested claims data for beneficiaries dually eligible for Medicaid and Medicare. By understanding the care received by these beneficiaries, the State Medicaid agencies may be able to better coordinate the medical costs they reimburse under Medicaid with the drug regimens being reimbursed under the Medicare Part D program. In coordinating care, these State agencies may need to understand which plan a beneficiary is enrolled in. Releases to Congressional oversight agencies are discussed in response to comment later in this preamble. We have included these restrictions in our amended regulations at § 423.505(m). The appendix to this rule also contains a CMS chart, explaining in more specific detail the restrictions relative to the available PDE elements for various parties. We will evaluate all requests for these data to ensure that any release is consistent with the restrictions contained in our regulations, and we will release only the minimum data that are necessary for the specific project. Additionally, as part of our data sharing procedures, we will ensure that any disclosure is for an appropriate purpose and does not undermine the competitive nature of the Part D program, such as a disclosure that would result in Part D sponsors being able to adjust their plan bids on the basis of knowledge of each others' data. Finally, while we agree with commenters that cost data on the Part D claim may not reflect the actual costs to plans, such data does reflect costs incurred at point-of-sale, and may be of use to CMS, other governmental entities, and other external entities for projects unrelated to a plan's total costs. *Comment:* One commenter asked that CMS appropriately use and differentiate between the terms “sex” and “gender” in its data collection process. *Response:* The Patient Gender Code field in the Part D claim is defined by the National Council of Prescription Drug Programs (NCPDP). We have found it helpful in working with the industry and other stakeholders to rely on the NCPDP industry standard whenever possible. The NCPDP data dictionary defines “Gender Code” under definition of field, “For eligibility, and identifying the gender of the member.” Values are: M=Male, F=Female, and U=Unknown. B. Purpose of CMS Collecting Information In the proposed rule, we outlined our intended use of Part D claims data for a wide variety of statutory and other purposes including— • Reporting to the Congress and the public on the overall statistics associated with the operation of the Medicare prescription drug benefit; • Conducting evaluations of the Medicare program; • Making legislative proposals with respect to the programs we administer, including the Medicare, Medicaid, and the State Children's Health Insurance Program; and • Conducting demonstration projects and making recommendations for improving the economy, efficiency, or effectiveness of the Medicare program. In the final rule, we continue to believe such uses are necessary and appropriate. In addition, as discussed below and later in this preamble, we also intend to use these data for “other studies addressing public health questions,” “pilot projects,” “supporting quality improvement and performance measurement activities,” and “populating personal health records,” and have added these purposes to the list in § 423.505(f)(3). *Comment:* Many commenters believe analyses of Part D claims data are necessary for CMS to administer the Medicare program, and for planning, evaluation, and policy development. Examples of program research and evaluation uses suggested by commenters include— • Assuring that Part D has not promoted adverse selection into certain health plans with less generous medication coverage; • Examining the effects of drug coverage and cost containment on Medicare spending and the health of vulnerable elderly and disabled persons; • Measuring the success of prescription drug plans in encouraging the use of generic medicines; • Examining the transition effects of moving dual eligibles from Medicaid programs to Part D; • Analyzing the effects of a coverage gap on drug utilization and spending; • Determining the impact of Part D coverage on non-pharmaceutical treatments and services use; • Evaluating the effect of changing copayments, copay structures, and coverage limits on beneficiary drug choices and compliance with drug regimens; • Assessing the extent to which risk adjustment methodology influences enrollment dynamics; • Assessing the impact of adding a prescription drug benefit on health outcomes of beneficiaries; • Researching the extent to which disparities in care (based on race, socioeconomic status, rural residence, etc.) might be affected by Part D; and • Understanding the impact of Part D on related public programs, such as the State Children's Health Insurance Program (SCHIP), SPAPs, Medicaid, and the VA. Commenters also noted that being able to explore how Part D functions on its own and in relation to other parts of the Medicare program is essential to guiding future policy decisions. They further assert that use of Part D claims data is critical to CMS's credibility and should be considered as part of the Secretary's value-based health care purchasing initiative. Without access to Part D claims data for research and other purposes, CMS will limit its ability to monitor expenditures for the new program, to study the impact of the program on public health, and to respond to Congressional requests for information. *Response:* We agree with the many comments that Part D claims data will be essential to us for reporting, conducting program evaluations and demonstrations, research analyses, and other public health functions. We also agree that research uses of these data should help promote and protect the health and well-being of Medicare beneficiaries. While we believe these uses were implied in the regulatory text set forth in the proposed rule, we are expanding the list of necessary and appropriate purposes for which data will be collected in this final rule to address public health functions specifically. *Comment:* Commenters expressed widespread support for using Part D claims data to improve our knowledge base on medication adherence and other aspects of pharmacotherapy among the elderly and disabled. Some specific suggested uses of Part D claims data for this purpose include the following: • Describing current medication use among the elderly and disabled and examining trends, specifically enhancing our awareness of poly-pharmacy, off-label uses, avoidance of contraindicated drugs and dangerous drug-drug interactions. • Examining the extent to which Medicare beneficiaries receive medicines according to evidence based guidelines. • Assessing whether beneficiaries are adhering to prescribed therapy, and if not, the clinical and economic impact of nonadherence. • Testing new interventions to improve medication prescribing and adherence. • Evaluating the impact of medication therapy management programs mandated under the new Medicare prescription drug benefit. *Response:* We consider examining medication use, inappropriate use, and factors influencing medication adherence in the Medicare population to be crucial aspects of Part D program monitoring and evaluation, and public health. As noted by commenters, the Congress mandated that we examine best practices of medication therapy management, and Part D claims data are critical for our being able to complete that study. *Comment:* A few commenters noted that sharing of research results is critical to CMS credibility and should be considered part of the transparency initiative. *Response:* We recognize Part D claims data research, and any subsequent results, are critical to evaluating multiple aspects of the Medicare Prescription Drug program. Many quality measures developed by the American Medical Association Physician Consortium and National Committee for Quality Assurance, and subsequently adopted by Ambulatory Care Quality Alliance, and the Hospital Quality Alliance require Part D claims data to run the measures. All of the following quality measures involve Part D claims data: Drug Therapy for Lowering Cholesterol, Beta-Blocker Therapy within 7 days post myocardial infarction, and Beta-Blocker therapy at 6 months post myocardial infarction. These measures will be used by many of the Better Quality Information to Improve Care for Medicare Beneficiaries Project pilots, including the new local collaboratives being chartered under the Secretary's value-based health care initiative to foster public reporting. All of this makes Part D claims data an integral part of our transparency efforts. Thus, in this final rule, we are clarifying our intent to use Part D data for these necessary and appropriate purposes by adding “supporting quality improvement and performance measurement activities” as an explicit use of these data under § 423.505(f)(3). *Comment:* A commenter asserts that we did not adequately justify the use of Part D claims data by the Secretary for public reporting purposes, apart from its use to develop reports to the Congress, which may become publicly available records. *Response:* As we stated in the proposed rule, we believe it is appropriate and necessary for the Secretary to use Part D claims data for the purposes of reporting to the Congress on the effectiveness and performance of the prescription drug benefit—including reporting that is not related to payment. In addition, we may need Part D claims data to report to the public on aggregate statistics associated with the Part D program. Finally, the Secretary has determined that it is necessary and appropriate, under section 1860D-12 of the Act, that the public should have access to certain data, so that the public may monitor the progress of the Part D program and, in fact, perform research that will improve the health of, not only Medicare beneficiaries, but all Americans. This is why we have created Part D-related public use files relating to plan benefits and formularies (for example, files such as geographic locator files, plan information files, formulary files, beneficiary cost files, pharmacy network files, and record layout files as described at *http://www.cms.hhs.gov/NonIdentifiableDataFiles/09_PrescriptionDrugPlanFormularyandPharmacyNetworkFiles.asp* .). We may also create additional public use files subsequent to the publication of this final rule. *Comment:* Several commenters suggested that the reporting of overall statistics and development of evaluations and/or legislative proposals can be achieved without CMS having to use or disclose the Part D sponsors' Part D claims data. The commenter suggested that CMS use information that is separately collected from the claim to develop statistics, noting however, that this information will not necessarily allow CMS to do every type of analysis described in the proposed rule. Additionally, CMS could partner with one or more sponsors to use their data, alone, or in combination, to do additional statistics and analysis. *Response:* Although we are willing to partner with plan sponsors as needed, we do not believe that voluntary cooperation by Part D sponsors would provide the kind of comprehensive data sets we need to perform the research, evaluations, reporting and other functions that are described this final rule. Voluntary agreements with plan sponsors would lead to an incomplete file of data. In addition, because we possess the authority under section 1860D-12(b)(3)(D) of the Act to collect Part D claims data, we do not believe an exclusive reliance on such voluntary agreements is necessary. *Comment:* A commenter noted that a recent Report to Congress recommended that the Secretary should have a process in place for the timely delivery of Part D data to congressional support agencies to enable them to report to the Congress on the drug benefit's impact on cost, quality, and access. *Response:* We agree that congressional support agencies should have timely access to appropriate Part D data. This final rule allows congressional oversight agencies access to all elements on the Part D claim in order to carry out their functions. Like other agencies outside of CMS, such congressional agencies would be subject to our minimum necessary policies and data sharing policies. Thus, we would release only the minimum amount of Part D claims information necessary to support given projects. In addition, as discussed later in this preamble, the Congressional Research Service has the authority to require data releases only when acting on behalf of a committee. Thus, that agency would be treated the same as a congressional oversight agency when acting on behalf of committee. Otherwise, it would be subject to the same restrictions that apply to external entities in our regulation. *Comment:* Several commenters requested that we establish specific, explicit procedures to ensure that if comparative effectiveness or safety research informs coverage or payment decisions for specific items and services (whether decisions are made by CMS or its agents under Parts A and B or by private plans under Part D), stakeholders have an opportunity to evaluate the evidentiary basis of proposed decisions and provide input. *Response:* Since our proposed rule did not address the development of national coverage or payment decisions, but rather our access to Part D claims data, we believe that our development of coverage or payment decisions is beyond the scope of this rulemaking. We do note that section 1860D-4(b)(3) of the Act requires pharmacy and therapeutic committees to base clinical formulary decisions on the strength of the scientific evidence and standards of practice. We have issued further formulary guidance available at *http://www.cms.hhs.gov/Pharmacy/07_Formulary%20Guidance.asp#TopOfPage* . *Comment:* Some commenters noted potential uses for Part D claims data, linked with Parts A and B data, which extend beyond research into the actual provision of care, including disease management. *Response:* We believe the implementation of disease management programs and the evaluation of these programs could potentially be strengthened by the use of Part D claims data. However, we believe these data must be used with caution for these purposes since we collect Part D claims data only for Medicare Part D enrollees. We do not collect drug claims data for those beneficiaries who receive their drug insurance solely from other sources, such as employer or retiree sponsored health plans, the Veterans Health Administration, or TRICARE. *Comment:* Some commenters noted that Part D claims data can help improve Medicare's current basis of risk adjustment for plan payments. *Response:* Section 1860D-15(d)(2)(B) of the Act provides us authority to use Part D claims data for determining Medicare payments to prescription drug plan sponsors. This includes their use for refining our drug plan payment system. Thus, when claims data are used for risk adjustment they are collected under section 1860D-15 of the Act, and not under section 1860D-12 of the Act. *Comment:* A commenter recommended adding the phrase “and pilot” into the text of the § 423.505(f)(3)(iv), so that the regulation would read “The Part D plan sponsor agrees to submit to CMS * * * [d]ata included in drug claims submitted by Part D plan sponsors, as the Secretary deems necessary and appropriate for purposes including but not limited to * * * [(f)(3)(iv) c]onducting demonstration *and pilot* projects and making recommendations for improving the economy, efficiency, or effectiveness of the Medicare program.” The commenter wants to ensure that Medicare Health Support Organizations are able to access Part D claims utilization data. *Response:* We agree that pilot projects, as appropriate, should have access to these data, as appropriate, and have added the phrase “and pilot” to § 423.505(f)(3)(iv). *Comment:* Several commenters requested that the list of purposes for which the data would be used be expanded to include program integrity. *Response:* We agree that it is important that our program integrity components have access to necessary data in order to protect the program. The existing regulation at § 423.322(b) already allows information collected under section 1860D-15 of the Act to be used in determinations of payments and payment-related oversight and program integrity activities. To the extent that program integrity activities may include investigations of issues that are not directly payment-related, this rule will provide access to Part D claims data for these purposes. *Comment:* One commenter requested we clarify in the final rule that Part D claims data can be used by CMS to oversee and protect the program. Other commenters stated that we should clarify that Medicare Drug Integrity Contractors (MEDICs) can obtain Part D claims data where necessary to fully investigate complaints and fraudulent claims. *Response:* Our regulations already address use of payment data for payment-related oversight. We are constantly working with our MEDICs to determine the types of data to which they will have access. However, we believe our interactions with our contractors involve internal agency procedures, and are not the subject of this final rule. C. Sharing Data With Entities Outside of CMS (Final § 423.505(f)(3) and
(l)Through (o)) As stated in the October 18, 2006 proposed rule, in addition to collecting Part D claims data for use in administering the Medicare Part D program under the authority of section 1860D-12(b)(3)(D) of the Act, we also believe that it is in the interest of public health to share the information collected under that authority with entities outside of CMS. When information is collected under the authority of section 1860D-12(b)(3)(D) of the Act, we do not believe that the statutory language in section 1860D-15(d) and
(f)of the Act (requiring the information collected under the authority of that section to be used only in implementing such section) would apply, since any collection would be effectuated outside of section 1860D-15 of the Act. Therefore, as we stated in the October 18, 2006 proposed rule, we proposed to add a new § 423.505(f)(5) to the regulations (now § 423.505(l) and (m)) that would specify that we could use and share the Part D claims information we collect under § 423.505(f)(3), without regard to any restriction included in § 423.322(b). In response to comments, we clarify in this final rule that our regulation permitting release of Part D claims data to other government agencies and outside entities is authorized by section 1106 of the Act. 1. Other Government Agencies We stated in the proposed rule that the Department of Health and Human Services’ (DHHS') public health agencies such as the National Institutes of Health (NIH), the Food and Drug Administration (FDA), and the Agency for Healthcare Research and Quality
(AHRQ)have, or support, researchers that would need to use Medicare Part D prescription drug event data for studies, and other projects, to improve public health consistent with the missions of these agencies. We also stated that oversight agencies may need access to both aggregated and non-aggregated claims data in order to conduct evaluations of the Part D program that are unrelated to payment and therefore not authorized under section 1860D-15 of the Act. In addition, agencies in the legislative branch, such as the GAO, MedPAC, and CBO, may need access to data in order to evaluate the program. We continue to believe this. We also continue to believe that other agencies within DHHS, such as the Centers for Disease Control and Prevention, the Health Resources and Services Administration, or the Office of the Assistant Secretary for Planning and Evaluation, may also need Part D claims data to perform evaluations or assess policies. However, we note specifically that OIG has independent authority to collect Part D claims data from Part D sponsors to perform its statutory duties in accordance with the Inspector General Act of 1978, as amended, 5 U.S.C. App. This final rule provides OIG an additional avenue for access to these data for both payment and nonpayment purposes. Given these necessities, we proposed to allow broad access for other Federal government executive branch agencies to our Part D claims data, linked to our other claims data files. As stated in the preamble of the proposed rule, other agencies generally would enter into a data sharing agreement, similar to what is used today. This would allow the sharing of event level cost data, protect the confidentiality of beneficiary information, and ensure that the use of Part D claims data serves a legitimate purpose. We also stated in the proposed rule that we would also ensure that any system of records with respect to Part D claims data is updated to reflect the most current uses of such data. In the proposed rule, we requested comments that would help us in our efforts to improve knowledge relevant to the public health. Specifically, we requested guidance on how we can best serve the needs of other agencies through the sharing of information we collect under section 1860D-12(b)(3)(D) of the Act, while at the same time addressing the legitimate concerns of the public and of Part D plan sponsors that we appropriately guard against the potential misuse of data in ways that would undermine protections put in place to ensure confidentiality of beneficiary information, and the nondisclosure of proprietary data submitted by Part D plans. After considering the comments received, we will make Part D claims data available under a process that builds upon the practice that is currently in place today with respect to the release of Medicare Parts A and B data. Thus, we specify in this final rule that, of the data we collect under the authority of section 1860D-12 of the Act, only the minimum information necessary, subject, in certain cases, to encryption and aggregation of certain elements, will be shared with other Federal executive branch agencies, which would include contractors acting on their behalf, in accordance with section 1106 of the Act, based on data sharing procedures established by CMS and agreed to by the Federal executive branch agency requesting the data. The attached appendix, as well as our amended rules at § 423.505(m), explain how in this final rule we would group the governmental entities outside of CMS that request access to the data collected under 1860D-12 of the Act. Agencies within HHS, as well as the Congressional oversight agencies (including CRS when acting on behalf of a committee) would receive only the elements of the PDEs on the claim that are minimally necessary for the applicable project. Plan, pharmacy, and prescriber identifiers would be encrypted unless necessary for the project. In addition, for States and non-HHS executive branches, the dispensing fee, ingredient cost and sales tax elements on the claim would be aggregated together prior to any release, except that, upon request, we will exclude sales tax from the aggregation at the individual claim level if necessary. *Comment:* One commenter objected to the use of the word “necessities,” stating that it is not necessary to allow broad access to Part D claims data. *Response:* We continue to believe that it is both necessary and appropriate for the Secretary to collect the Part D claims data under section 1860D-12(b)(3)(D) of the Act in order to carry out his broad range of duties under the Act, including the duties that are listed at § 423.505(f)(3). Once the Secretary collects the information for his own necessary and appropriate purposes, we do not believe that the external release of such information must be categorized as necessary in order for it to occur, as section 1860D-12(b)(3)(D) of the Act refers to the collection of, not the release of, data. Release of data will be authorized under section 1106 of the Act. In addition, any release will be intended for the benefit of the public health and welfare. *Comment:* Several commenters requested that the FDA play a central role in any use of Part D claims data for safety evaluations. Others requested that CMS issue a separate proposal to present CMS and FDA combined views on sharing of data for public comment. One commenter also contended that the FDA may not want to use Part D claims data because of alleged reliability problems and the fact that the FDA may have problems integrating the Part D claims data with its own databases. Finally, commenters requested that both agencies allow manufacturers to review the data and methods used for post-marketing surveillance. *Response:* We do not believe that the FDA's use of Part D claims data or how the claims data are used in safety evaluations is the subject of this proposed rule. However, we note that we plan to exchange Part D claims data with the FDA in accordance with applicable laws and our data sharing procedures, by entering into appropriate interagency agreements and data use agreements. Thus, our procedures for sharing data with the FDA will be the same as those developed for other government agencies. *Comment:* A commenter requested that the Congressional Research Service
(CRS)be able to access the same level of data as oversight agencies, such as the Office of the Inspector General (OIG), the Government Accountability Office (GAO), the Congressional Budget Office (CBO), and the Medicare Payment Advisory Commission (MedPAC). *Response:* In the proposed rule we stated that the Congressional oversight agencies (GAO, MedPAC, and CBO) may require access to data in order to evaluate the Part D program (71 FR 61452). Although we did not define CRS as a Congressional Oversight entity, like GAO, it does have statutory authority to request data (see 2 U.S.C. 166(d)(1)), but only when it is doing so on behalf of a committee. Accordingly, we are specifying that CRS will be considered a congressional oversight agency when the CRS is acting on behalf of committee under 2 U.S.C. 166(d)(1). Our regulations at § 423.505(m), as well as the attached appendix outline the data policies that would apply to congressional oversight agencies, including being subject to our minimum data necessary policy, our data sharing procedures, and applicable laws. For individually identifiable information or certain commercially or financially sensitive information, such as plan identifiers and cost information, these Congressional oversight agencies will be required to sign a Data Use Agreement (or provide assurances acceptable to CMS) to protect against disclosure of such data. When CRS is not acting as the agent of a committee, however, it does not have the same authority to request data from departments or agencies of the United States. Thus, we have specified that in these cases, CRS would be treated as an external entity, because the agency would essentially be performing research or analysis on behalf of an individual member of the congress. In addition, unlike States or other executive branch departments, the CRS should not need access to plan identifiers or other data on the claim in order to coordinate care on behalf of beneficiaries. Thus, we have specified that CRS will be restricted in the same manner as external researchers, and will not be treated similar to other executive branch agencies or States. *Comment:* A commenter asked CMS to allow for a process that permits access to Part D claims data in a highly organized way and enables external entities to replicate any results Federal agencies obtain using the data. *Response:* We believe that our approach to providing access to Part D claims data, which would follow a review of each request under our minimum necessary data policy with some additional encryption and aggregation restrictions based on type of requestor, balances the need for Part D data in order to conduct legitimate research with the needs to protect patient information and to preserve the competitive nature of the Part D program. Therefore, we will review legitimate research requests and decide whether to release Part D claims information, consistent with our regulation at § 423.505(m), as well as the guidance provided in the appendix to this final rule. We expect that external entities may be able to replicate the results of Federal analyses for many research questions, such as those relating to the utilization of specific drugs or classes of medications, comparative effectiveness or safety research. *Comment:* A few commenters asked that all applicable government agencies have broad access to the data in a timely fashion without having to enter into numerous data use agreements (DUA). *Response:* As illustrated in our regulation § 423.505(m), as well as in the appendix to this final rule, non DHHS entities will have access to the minimum Part D claims data necessary for a given project, except that certain elements may be encrypted or aggregated. In the event of a backlog of requests for Part D data under these rules, we plan to give government agencies first preference in the review process, and to require such agencies to abide by our data sharing policies, which generally require a data use agreement. We have modified or streamlined the data sharing process in the case of certain Federal law enforcement or oversight entities. For example, we have streamlined the DUA process for the Department of Justice (DOJ). DOJ provides a letter for each request for data, which CMS tracks and monitors. 2. External Entities As stated in the preamble of the proposed rule, external entities, such as researchers based in universities, regularly request and analyze Medicare data for their research studies, many of which are designed to address questions of clinical importance and policy relevance. We continue to believe researchers studying a broad range of topics need access to Part D claims linked to Parts A and B claims data. As stated in the preamble of the proposed rule, analyses of Parts A and B claims have contributed to significant improvements in the public health, have been critical in assessing the quality and costs of care for patients in the Medicare program, and have, in many cases, spurred other types of research. As such, we continue to believe that a data source that includes Parts A and B claims as well as their attendant Part D claims could be used in a similarly constructive manner, such that greater knowledge on a range of topics, both clinical and economic, would be generated. This knowledge is expected to contribute positively to the evaluation and functioning of the Medicare program, and to improve the clinical care of beneficiaries. Also, as stated in the preamble of the proposed rule, we will specifically address the needs of a segment of external entities as part of our implementation of section 723 of the MMA, which requires the Secretary to develop a plan to “improve the quality of care and reduce the cost of care for chronically ill Medicare beneficiaries.” The Congress specifically stated that the plan should provide for the collection of data in a data warehouse (under section 723(b)(3) of the MMA). Within the parameters of this regulation, we will implement section 723 of the MMA by populating a chronic care condition data warehouse
(CCW)which will be accessible by private researchers in order for such researchers to conduct studies related to improving quality and reducing costs of care for chronically ill Medicare beneficiaries. In addition to the section 723 of the MMA data warehouse, we stated in the proposed rule that we are planning to make Medicare Part D claims data linked to other Medicare claims files available to external entities on the same terms as other Medicare Parts A and B data are released today, with appropriate protections for beneficiary confidentiality. We requested comments on the proposed use of the data for research purposes that would help us in our efforts to improve knowledge relevant to the public's health, as well as comments on whether we should consider additional regulatory limitations for external entities beyond our existing data use agreement protocols in order to further guard against the potential misuse of data for non-research purposes, commercial purposes, or to ensure that proprietary plan data or confidential beneficiary data are not released. As explained in response to comments, we continue to maintain the discretion to release the 37 collected PDE elements for legitimate research purposes, subject to encryption of certain identifiers and aggregation of cost data to protect beneficiary confidentiality and commercially sensitive data of Part D sponsors. (These restrictions are outlined in our regulations at § 423.505(m) as well as in the appendix attached to this rule.) Furthermore, we also believe Part D claims data are necessary for use in personal health records and to ensure the public will be able to access the results of quality measurement and performance initiatives as discussed in the “Purpose of CMS Collecting Information” section of this preamble. We will release only the minimum information necessary for a given project. In addition, data will be disseminated in accordance with applicable laws via our established data sharing procedures. Thus, the requestor of data must agree to abide by the restrictions established by our data sharing procedures in order to receive access to Part D claims data. We will ensure that our system of records for Part D claims data would permit the uses of the data described in this final rule. *Comment:* In general, the importance of Part D claims data for improving aspects of public health was a recurring theme among many of the comments we received. Commenters noted the lack of a comprehensive source of prescription medication data as one of the greatest challenges to conducting meaningful research in the elderly. They noted that Part D claims data will be vital for enhancing disease surveillance, identifying rare complications of drug therapy, and improving knowledge about the effectiveness and safety of drugs. Several commenters underscored that knowledge based on selected aspects of pharmacotherapy in the elderly or disabled population is limited. They point out that the very old, patients with multiple chronic conditions, and those taking multiple medications are routinely excluded from clinical trials, and assert that research based on Part D claims data would provide a valuable supplement to the FDA's current post-marketing surveillance system. Other themes raised by commenters centered on the current fragmentation of our health care information and the lack of information on drug treatment in the elderly. These commenters suggested that analyses of Part D claims data linked with Parts A and B data could provide a comprehensive picture of disease treatment, help guard against siloed policy analyses, and support a broad, disease-centered research agenda that would advance the essential quality improvement goals highlighted by the Institute of Medicine in its report, Crossing the Quality Chasm: A New Health System for the 20th Century. Commenters also said analyses of Part D claims data would be beneficial for developing comprehensive estimates of the costs of care, revealing the most cost effective disease therapies, and understanding beneficiaries' sensitivity to changes in cost sharing for drugs. *Response:* We agree with the many comments that Part D claims data will be essential for research analyses involving the elderly and disabled, and for other public health functions. *Comment:* Two commenters suggested that CMS implement a tiered system of access to Part D claims data. Specifically, they suggested we establish separate tiers for accessing the data, taking into account the need for data and the opportunity for abuse, which would correlate to the following groups:
(1)Government agencies;
(2)contractors and researchers under contract with CMS or another government agency; and
(3)outside researchers. They suggest that Part D claims data be available to the above-listed entities within appropriate parameters, but not be available to entities, such as pharmaceutical manufacturers and others with strong proprietary interests. *Response:* We considered several alternatives to the Medicare A/B data release process including restricting: • Access to HHS agencies only, • Access to Federal Government agencies only, • Access to financial elements for outside researchers. We rejected these alternatives as too restrictive in light of the significant benefits to the Medicare program and the public's health in making Medicare Parts A, B, and D linked data available, with protections, to Federal and State government agencies, and external entities. We believe that our approach, which incorporates the Medicare A/B minimum necessary data policy with additional restrictions to protect privacy and plan commercially sensitive information, strikes an appropriate balance between these significant health benefits and the concerns regarding the release of proprietary data and preserving beneficiary confidentiality. Moreover, we believe this process has sufficient protections to ensure compliance with the applicable laws and guard against the potential misuse of data. External entities requesting access to Part D claims data will have to enter into an agreement with us that includes provisions protecting the data from improper release. Our regulation at § 423.505(m), as well as the attached appendix provides additional guidance on the additional limitations that would apply to external entities (which would include CRS when not acting on behalf of a committee as an agent, but would not include States or other executive-branch Federal agencies) requesting Part D data. Cost data (consisting of ingredient cost, dispensing fee, and sales tax) could be released only in aggregated form. In addition, plan and other identifiers generally would be encrypted. We also intend to only release the minimum data necessary for a given project. Additionally, we also note that if an entity involved in a data release of electronic protected health information
(EPHI)is a HIPAA-covered entity, the covered entity will have to comply with our HIPAA privacy and security standards. In addition, the covered entity should also follow the security guidance which was released in December 2006. The guidance reinforces our existing security standards to specifically address remote access and use of EPHI. This reinforcement of the HIPAA security standards, particularly related to data in transit, will further protect Part D claims data from inappropriate release, and therefore inappropriate use. For more information on this guidance, please log on to *http://www.cms.hhs.gov/SecurityStandard/.* *Comment:* We requested comments on whether we should consider additional regulatory limitations for external researchers beyond our existing data use agreement protocols in order to further guard against the potential misuse of data for non-research purposes, commercial purposes, or to ensure that proprietary plan data or confidential beneficiary data are not released. In response, a number of commenters requested that CMS define the term “commercial purposes” clearly and narrowly so that a broader range of entities would have access to the data, including pharmaceutical manufacturers, insurance companies, and pharmacy benefit managers. These commenters argue that instead of precluding certain types of entities from accessing Part D claims data, it would be better to focus on assuring researcher quality and integrity, and on ensuring that researchers adopt sound methodologies in conducting analyses. Therefore, the commenters request that the “clear bias” against pharmaceutical company supported research be removed from the CMS review criteria. As noted previously, other commenters suggested that the final regulation should deny access to data to organizations with strong proprietary interests, such as drug plan sponsors, pharmaceutical manufacturers, and other industry data collection entities that sell market research and sales data. *Response:* Under our current policies for Parts A and B data, we do not provide protected health information (PHI), as defined for purposes of HIPAA at 45 CFR 160.103, for commercial purposes, as we believe PHI should only be provided to entities conducting research that will result in generalizable knowledge in the public domain. We are concerned about the potential for conflicts of interest where commercial entities, whose primary purpose is not the creation of generalizable knowledge, might not publish results contrary to the firm's financial interest. However, we do allow external researchers to be funded by commercial firms, including pharmaceutical manufacturers, insurance companies, and pharmacy benefit managers when the research will contribute to general knowledge in the public domain and the researchers are free to publish the results of the research regardless of the findings. We continue to believe that any findings based on beneficiary identifiable data released by us should be unbiased by commercial incentives and should be in the public domain. The criteria governing releases of protected health information
(PHI)for research are designed to ensure that the HIPAA Privacy Rule's requirements, as defined at 45 CFR 164.512(i), as well as our own policies are met. In this final rule, we use the definition of research contained in the HIPAA Privacy Rule, which defines the term as “a systematic investigation, including research development, testing and evaluation, designed to develop or contribute to generalizable knowledge” (45 CFR 164.501). Thus, we do not release PHI to external entities when their research is not designed to develop or contribute to the generalizable knowledge. Nor do we release PHI to external entities for their commercial purposes or if they fail to demonstrate that they have a sound research methodology and that their research will produce findings relevant to the Medicare program and its beneficiaries. Therefore, we will continue to apply the same criteria in distinguishing between who may have access to data (researchers versus commercial interests), as we have been using for Parts A and B data. Because we intend to examine whether each proposed use of data meets the definition of research used under the HIPAA Privacy Rule, we will not be defining the term “commercial purposes” in this regulation. *Comment:* We received several comments relating to the Freedom of Information Act (FOIA), noting that releases under FOIA should not include information that would be considered proprietary in nature. *Response:* If a FOIA request is received, we will follow our ordinary FOIA procedures and not release under FOIA data the agency determines are trade secrets, or commercial or financial information protected by FOIA Exemption 4 (5 U.S.C. 552(b)(4)). These procedures were explained more fully in the preamble to the Part D final rule, where, in response to a question about protecting bid information under FOIA we stated: [B]idders can always seek to protect their information under the Freedom of Information Act and label truly proprietary information “confidential” or “proprietary”. When information is so labeled, the bidder is required to explain the applicability of the FOIA exemption they are claiming. When there is a request for information that is designated by the submitter as confidential or that could reasonably be considered exempt under Exemption 4, the Department is required by its FOIA regulation at 45 CFR § 5.65(d) and by Executive Order 12,600 to give the submitter notice before the information is disclosed. To determine whether the submitter's information is protected by Exemption 4, the submitter must show that
(1)disclosure of the information is likely to impair the government's ability to obtain necessary information in the future;
(2)disclosure of the information is likely to cause substantial harm to the competitive position of the submitter; or
(3)the records are considered valuable commodities in the marketplace which, once released through the FOIA, would result in a substantial loss of their market value. Consistent with our approach under the Part C program, we would not release information under the Part D program that would be considered proprietary in nature or that would tend to stifle the availability of discounts or rebates from pharmaceutical manufacturers negotiated by Part D plans. Bidders may identify trade secrets and confidential business information
(CBI)with their submission. However, if they have not we will give them another chance when a FOIA request has been made on their records. In this case we will notify the business submitters that we are in receipt of FOIA requests for their records. We will then provide the business submitters with instructions and ask them to identify any trade secret or CBI in order to justify our application of Exemption 4. We will then review their justifications and highlighted information against FOIA case law to see if we can support their requested redactions. Under Executive Order 12600, if the business submitters disagree with our Exemption 4 analysis (which includes their justification) of their identified trade secret or CBI, they are provided the opportunity to seek a restraining order or injunction in Federal court prohibiting us from releasing their records under FOIA. (70 FR 4294 through 4295) Thus, for example, we do not expect that any pricing data included on the claim that fits within FOIA Exemption 4 would be required to be released under FOIA. We also note that we do not view data releases made under the authority of the new § 423.505(m) as FOIA releases. Unlike FOIA releases, these releases are not required by law. Section 423.505(m) permits the release of data, but does not require it. *Comment:* A number of commenters underscored the importance of CMS making patient identifiers available in order to achieve the full potential of Part D data. One commenter stated prescription drug claims files by themselves lack the diagnostic, outcomes and other information to support the needed studies. However, when merged with other data, they can become a powerful tool for improving the public health. Reflecting the views of several other commenters, the commenter noted that Part D claims data could be linked to several other data sets such as: death and birth certificate files; nursing homes Minimum Data Set; home health care Outcome and Assessment Information Set files; disease registries such as the Surveillance, Epidemiology, and End Results-Medicare dataset developed by the National Cancer Institute to study outcomes of cancer therapies; geographical data on characteristics and health care resources of communities; information on characteristics of providers (for example, use of primary medical care versus specialty care); and Medicaid data on health care encounters and services not covered by Medicare. The commenter emphasized that linking Part D data to the above information is essential in order to provide accurate accounting for outcomes and to best address the many scientific pitfalls and potential threats to validity that emerge when one moves from experimental to observational studies, such as unobserved variable bias and confounding by indication or counter-indication. Another commenter stated that linkage of the Part D data to population-based surveys would provide invaluable sources for epidemiologic, health services and policy analyses and enable investigations into prevalence of diseases, their risk factors, progression, and trends in treatment and drug use. *Response:* We agree these data are more powerful when linked with other data sets. Linkage to Medicare Parts A and B data is essential for understanding the impact of the Part D benefit on use of other Medicare services. There are a host of other types of research studies that could not be completed without linked data. These include: studies examining the impact of changes in benefit structure on patient outcomes, research into the relative effectiveness of pharmacologic therapies or medication therapy management interventions, and pharmacovigilence studies. In many cases, Part A/B linked data provided through our chronic condition warehouse with encrypted identifiers will be sufficient to accomplish the research. In cases where beneficiary identifiers are essential for linkage with non-Medicare data bases, such as the National Center for Health Statistics Surveys, beneficiary-identifiable data may be released, but will be subject to the Privacy Act and HIPAA data security and privacy requirements consistent with those we require in our data release policies for identifiable Part A/B data. These requirements include a CMS Privacy Board review/approval, submission of a Data Use Agreement, and the justification of minimum data necessary to carry out the project. If the data is going to be linked to data collected under another federally funded study, the requestor must also secure the Federal project officer's concurrence and an Institutional Review Board
(IRB)approval. *Comment:* A few commenters were concerned that CMS had not adequately addressed the implications of expanding access to physician and patient information. They recommended that we specify more clearly the conditions under which physician data can be collected and used in performance programs, research studies, and demonstration projects, noting that revealing physician identification information will enable pharmaceutical companies and others to influence physicians' prescribing patterns and interfere with a physician's professional judgment. *Response:* We believe that an encrypted version of the physician identifier, which will allow for the linkage of all of a physician's claims without divulging the physician's identity, will meet the needs of most researchers. Accordingly, we will evaluate research requests for physician identifiers (for example, that could be used to link Medicare data at the physician level to other datasets) on a case-by-case basis and will only consider providing them if necessary for the study under our minimum data necessary policy and permitted under applicable law. In addition, we will continue our current practice of not providing identifiable data for commercial purposes. This limitation should address the concern regarding pharmaceutical company interference with medical practice. In addition to releasing physician identifiers in response to certain research requests, we anticipate releasing physician identifiers to States, and pilot and demonstration projects, as the ability to link all of a physician's claims may be necessary for care coordination and disease management purposes. Physician identifiers may also be used by or released to other government agencies or contractors, as part of populating personal health records, so that beneficiaries will have a record of who prescribed their drugs. Finally, we anticipate that they may be used in connection with or released to support the Secretary's Value-driven Health Care initiative which seeks to improve the quality and efficiency of health care delivery by making performance measurement information available to better support provider and consumer health care decision-making. One of the goals of the Secretary's Value-driven Health Care Initiative is to promote public reporting of performance measurement results at the provider and physician level that may be based on public sector claims, private sector claims, and other data in order to enable providers, including physicians, and consumers to make informed health care decisions. We envision using the claims data to develop provider and physician-level performance measurement results. *Comment:* A commenter supported CMS's use of Part D data to manage cost and clinical quality and argued that providing external parties access to linked physician identifiable claims in order to pool them with employer data would allow analysis to reduce the cost of care delivery and improve the quality of care. The commenter stated that increasing transparency of care in the outpatient sector is critical and that protecting physicians from oversight cannot continue. *Response:* We are undertaking a variety of pay for performance and value-based health care initiatives in an effort to encourage health care providers to furnish high quality health care and in order to provide cost and quality information to consumers. We intend to use the Part D claims data in these activities. Similarly, other Federal executive branch agencies (and their contractors) will have access to physician identifiers, if appropriate. We are working with external stakeholders, including multi-stakeholder coalitions that represent providers, consumers, employers, and health plans, regarding how to pool Medicare data with private data for analysis and how to make the results available to the public. As these plans mature, more information will be shared with the public. *Comment:* While many commenters supported the use of Part D claims data for detecting and analyzing unintended risks and benefits of medications, they also noted the limitations of claims-based research for answering questions about the comparative efficacy and safety of drugs. The commenters asserted that claims-based outcomes research, such as with Part D claims data, can reveal correlations between variables or events, but is often not sufficient to establish causation. They offered specific suggestions such as holding researchers to high methodological and ethical standards, creating study panels of qualified external stakeholder experts to review research protocols, and encouraging CMS to conduct an open and transparent process that will allow for external verification and replication of CMS's sponsored analyses. *Response:* We are well aware of the limitations involving retrospective, claims-based research. Our current data release policies for Parts A and B data for externally-funded research require that a requestor submit a detailed proposed research protocol. We review these proposals for the legitimacy and feasibility of the research, the strength of the proposed methods for guarding the privacy of the data, and the appropriateness of the research methods. Research requests for Part D claims data would be subject to the same type of review. *Comment:* Some commenters suggest that CMS make available the number of external requests it receives for claims data, the manner in which the agency responds to those requests, the timeliness of the approval process, and any fees charged for various types of data. They also believe that CMS should describe the Federal priorities for government-sponsored research using Medicare Part D claims data, and provide for public notice and comment on proposals based on processes already established by Agency for Health Research and Quality (AHRQ). *Response:* We already maintain data on the number of external research requests for our claims data, whether the request was approved, the timeliness of the approval process, and any fees charged for various types of data. We can make this information available to the public, upon request, and will explore posting it on our Web site. We do not believe we should establish Federal priorities for research using Part D claims data, just as we do not establish priorities for research using Medicare Parts A and B data. Much of our research agenda is determined by directives from the Congress for research studies, demonstrations and their evaluation. Accordingly, a public comment process on CMS-sponsored research is not necessarily feasible. However, other Federal government executive branch agencies that are likely to sponsor comparative effectiveness or safety research using Part D claims data, such as AHRQ, do have such priority-setting processes in place. We believe these processes are adequate to address the commenters' concerns. *Comment:* A few commenters suggested that we make available Part D claims data to State Medicaid directors for the purpose of monitoring and researching the dual eligible population. The commenters suggested we provide States with access to the drug utilization and spending data collected by the Medicare Part D prescription drug plans, as well as other data necessary for states to effectively coordinate the care of dual eligibles. *Response:* We believe that States may improve their disease management and other care coordination programs by examining utilization data of dual eligibles extracted from Part D claims. In this final rule, we have clarified that we will be permitted to use collected Part D claims data for care coordination and disease management purposes. Under § 423.505(m), we may release collected Part D claims data to States, consistent with our minimum data necessary policy, our data sharing procedures, applicable laws, and subject to encryption of certain identifiers and aggregation of cost data. We plan to explore the operational issues associated with such an exchange. As a result, we believe States will have appropriate access to Part D claims data for purposes of coordinating the care of dual eligible beneficiaries. Please see § 423.505(m), as well as the appendix to this final rule for additional explanation of how we would determine the data that would be released to States. *Comment:* Commenters requested further discussion on the types of entities to which collected Part D claims data will be released. A commenter also contends that the recipients of data could share the data with third parties of their choice. *Response:* Identifiable data are not released to all external requesters. Currently, for Parts A and B data, external researchers must request the identifiable data from us. Our privacy board reviews the request for beneficiary identifiable data to determine if the request is for an appropriate research purpose, whether the Privacy Rule's criteria are met, and that the request is consistent with our data release policies. Our data release policies do not allow us to release identifiable data for marketing or commercial purposes. Further, we do not approve requests from for-profit organizations or organizations that could profit from a study, although we do produce databases with identifiers stripped, as well as public use files, for any organization to use. We also have requirements for release of Parts A and B data to other Federal governmental entities and contractors for purposes not related to research. Generally, we use DUAs to track the disclosure of personally identifiable data to such entities. Under our data sharing policies, we generally require the requester not to disclose the data to third parties without specific written authorization from us. The release of data must also be permissible under the Privacy Act, the HIPAA Privacy Rule, the Trade Secrets Act, and any other applicable laws. *Comment:* A commenter recommended that CMS include a requirement that the recipient obtain a certification of confidentiality for all identifiable CMS data covered by the agreement or other data within the scope of the research project to protect researchers when compelled to release protected data. *Response:* Under section 301(d) of the Public Health Service Act (42 U.S.C. 241(d)) the Secretary of Health and Human Services may authorize persons engaged in biomedical, behavioral, clinical, or other research to protect the privacy of individuals who are the subjects of that research. This authority has been delegated to the National Institutes of Health (NIH). Certificates of confidentiality are issued to protect identifiable research information from forced disclosure. Certificates of confidentiality may be appropriate for research that combines the direct study of human subjects with the use of identifiable Part D data. They allow the investigator and others who have access to research records to refuse to disclose identifying information on research participants in any civil, criminal, administrative, legislative, or other proceeding, whether at the Federal, State, or local level. Certificates of confidentiality may be granted for studies collecting information that, if disclosed, could have adverse consequences for subjects or damage their financial standing, employability, insurability, or reputation. By protecting researchers and institutions from being compelled to disclose information that would identify research subjects, certificates of confidentiality help achieve the research objectives and promote participation in studies by assuring confidentiality and privacy to participants. The Department would encourage researchers to explore with their institutional review boards or other knowledgeable experts the use of certificates of confidentiality where appropriate. If a researcher has obtained a certificate of confidentiality for a human subjects study, its protection would extend to all individually identifiable data on the research subjects in that study (including Part D data.) maintained in the research records. Additional information about certificates of confidentiality is available on our Web site at *http://grants2.nih.gov/grants/policy/coc/* . *Comment:* Several commenters stated their concern that the proposal would run afoul of Federal confidentiality protections for substance abuse laws such as 42 CFR Part 2. *Response:* As the commenter notes, regulations at 42 CFR Part 2 “Confidentiality of Alcohol and Drug Abuse Patient Records,” establish restrictions on the disclosure and use of alcohol and drug abuse patient records that are maintained in connection with the performance of any Federally-assisted alcohol and drug abuse program. These regulations limit disclosures of any patient-identifying information acquired by a Federally-assisted facility that provides alcohol or drug abuse diagnosis, treatment, or referral for treatment. We will work with Part D sponsors to ensure that these specifically protected claims are not redisclosed for purposes other than payment. One option that we plan to explore to comply with these regulations is to identify a set of drugs which are used for the treatment of alcohol and substance abuse (that is, Anatabuse and Vivtrol) and exclude associated PDEs for these drugs from any sample of PDEs used for purposes other than carrying out section 1860D-15 of the Act (that is, for nonpayment purposes). *Comment:* We received a number of comments on how the rule will be implemented. Commenters requested that CMS ensure that: Part D claims data file formats are consistent with other CMS data files; limited data sets
(LDS)be available linking Medicare Parts A, B and D data; and files be in a clean format that is sufficiently detailed and secure. Other commenters requested that Part D claims data be made available in a linkable format that includes details of prescriptions by patient, time, and location, in order to address the shortcomings in the current management of chronic diseases. *Response:* We do not believe that the detailed formatting standards requested by the commenters are an appropriate subject of this final rule. However, we recognize the need to ensure appropriate security of data, and will apply the processes and procedures regarding the transmission and storage of data currently in place to protect Parts A and B data to Part D claims data. We also note that linked data files will contain both a patient's chronic conditions and detailed information regarding prescriptions. *Comment:* Several commenters recommended that CMS consider developing and releasing a summary file that parallels the current Physician Supplier Procedure Summary Master file along with a 5 percent sample standard analytical file. One commenter asked that both LDS files and Research Identifiable files be available and asked for clarification of the file types available from the CCW. *Response:* As stated, we do not believe that detailed formatting standards are the subject of this final rule. We also note that both LDS files and research identifiable files are available from the CCW. We anticipate filling most research requests for Part D claims data using LDS files available from the CCW or from other places. *Comment:* One commenter questioned how plan sponsors are to comply with applicable State privacy laws that may preclude disclosure of medical information for one or more of the purposes listed in the proposed regulatory text. The commenter requested that CMS explain whether any such conflicting state law prohibitions would be preempted by the proposed regulation, notwithstanding that § 423.136 of the regulations states that state confidentiality and disclosure laws are not preempted. *Response:* Part D sponsors should comply with all applicable Federal and state confidentiality and disclosure laws when not directly conflicting. Part D regulations specifically require prescription drug plans to comply with these laws. If there is a belief that a particular State law is in direct conflict with our Federal requirements, plan sponsors should bring those specific cases to our attention for individual review. *Comment:* One commenter contended that CMS can share Part D claims data freely with its contractors, who may also be researchers, under section 1860D-15 of the Act. *Response:* Section 1860D-15 of the Act only relates to disclosures necessary to carry out that section, which would permit sharing of Part D data with contractors only for payment purposes. This regulation, which is established under the authority of section 1860D-12 of the Act, would permit us to collect the original 37 PDE elements comprising the Part D claims data for nonpayment-related purposes, and allow the agency and its contractors to use them for nonpayment-related purposes (section 1874 of the Act permits the Secretary to perform his functions by contract). *Comment:* A commenter contends that it is impossible to assess the intent of CMS without the ability to review the system of record notice for data collected under Part D. The commenter wants CMS to republish the proposed rule along with the applicable system of records notice. *Response:* We believe the proposed rule contained enough information for interested parties to assess our intent. We plan to publish a revised system of records notice shortly to ensure that the regulation and its system of records are effective as close to the same time as possible. *Comment:* One commenter stated CMS should complete a Privacy Impact Assessment (“PIA”). *Response:* We annually update all appropriate PIAs. Accordingly, we will be updating the Drug Data Processing System PIA every year. *Comment:* A commenter recommended that the subjects of any data disclosed to a third party be parties to CMS's data use agreement, so that they may seek relief for a breach of the agreement. *Response:* The format and procedures for our data sharing agreements are not strictly within the scope of this final rule. Moreover, we do not believe the commenter's recommendation would be advisable because it may significantly hamper the ability of researchers to perform the activities that benefit the public's health under this rule. Researchers may ultimately expend an enormous amount of resources responding to third party claims. However, we do note that signatories of our data use agreements can be sanctioned if they violate the agreement or Federal law. *Comment:* We received several comments suggesting that we establish a process for reviewing research requests based on a `first in, first reviewed' process. *Response:* The internal procedures we use in reviewing requests for data are not strictly within the scope of this final rule, as the proposed rule did not make recommendations related to our data-sharing process. However, we do plan to continue the practice of giving government agencies first preference in the review process, and to require that such agencies abide by our data sharing procedures, which generally require a data sharing agreement. External research requests are usually reviewed in the month they are received with the exception of time sensitive research requests, which may be considered in an expedited manner, at our discretion. Because we expect a large volume of requests, there may be a delay between when a request is received, reviewed, and approved or denied. As we do currently with Parts A and B data requests, we will continue to carefully consider each research request with a review process that emphasizes compliance with applicable laws, including those governing the protection of privacy, first, followed by legitimacy of the requested study, and the requestor's expertise. D. Beneficiary Access to Part D Claims Data The proposed rule stated that we were considering the use of Part D claims data for projects involving the development or population of personalized health records, which include beneficiary medication history, which would be accessible by Medicare beneficiaries or their providers after the beneficiary consents to such a release. We requested comments on this proposed use of Part D claims data collected under the authority of section 1860D-12(b)(3)(D) of the Act. In this final rule, after considering the comments received, we are expanding the use of the collected Part D claims data so that we may authorize the use and release of these data to government contractors or external entities for the population of personal health records. *Comment:* Generally, commenters encouraged CMS to pursue projects of this nature, with one commenter in particular noting that the personalized medication history record could be linked to the *MyMedicare.gov* Web site and could include links to a beneficiary's Part D plan, its formulary, and the plan's instructions for prior authorization requests. A few commenters requested more detail regarding the development of PHRs, the protection of beneficiary health information, and the Web-based standards (that is, record security, record retrieval, browser compatibility, etc.) underlying the display of PHRs. They suggested that we use a transparent, public process for developing these ideas and allowing for public comments. One commenter referenced the URAC (the organization formerly known as the Utilization Review Accreditation Commission) standards for Web-based clinical content and another, the Medicare pilot demonstration project conducted by the United Mine Workers Health and Retirement Fund as a model of a project. *Response:* Currently, we are conducting pilot projects and studies on personal health records that include the disclosure of hospital and provider claims data (Part A and Part B) to populate beneficiaries' PHRs. However, until this rule is effective, we cannot include Part D claims data in these projects. When we have authority to disclose Part D claims data, we will provide the Part D claims data to populate PHRs only upon the authorization of the beneficiary. We require our partners in PHR pilots and studies to agree to strict privacy and security safeguards whenever receiving, using or disclosing beneficiary data. The pilots and studies are intended, in part, to help inform us in developing privacy rules and security arrangements that would be appropriate for a program of ongoing disclosures to populate and update the PHRs, as authorized by beneficiaries. In the area of health information technology, the Department has a history of developing policy in a collaborative, open, and transparent manner. In addition to obtaining public comment through notice in the **Federal Register** , such as this, the Department relies on its public advisory committees, relationships with industry, and participation in professional associations in developing policies and procedures with respect to the emerging health information environment. With regard to PHRs, the information we gather through this process will also help us determine future steps. *Comment:* Several commenters stated that beneficiary participation in such projects should not be mandatory, but voluntary. *Response:* We expect that any program we plan to undertake to make collected Part D claims data available to beneficiaries would be voluntary on the part of beneficiaries. *Comment:* A commenter noted that beneficiaries already have the right to request access to, inspect, and copy their medication histories and other PHI. *Response:* We appreciate the commenter's statements that beneficiaries already have access to their medical records, but believe that a centralized PHR that is easily accessible from a Web site, and that includes a more comprehensive set of data from multiple providers and prescribers, would be of use to beneficiaries. *Comment:* A commenter urged CMS to establish procedures where the data will be automatically available to other health care practitioners and institutions. The commenter stated that a beneficiary may be unable to release the record due to being unconscious or confused. Finally, the commenter noted reasons why, under Parts A and B, the personalized EHR is necessary, including the value of having a complete record in an emergency room situation and in instances when a physician administers medications incident to a physician visit. *Response:* Any PHI that CMS releases to providers or institutions would be authorized by the beneficiary or the beneficiary's authorized representative or would be otherwise permitted or required under the applicable laws and our policies. Moreover, we note that health care providers are not necessarily the intended users of PHR; rather, they are intended for use by the patient. We believe it more likely that emergency room and other health care providers would have access to patient's medication history from another source. *Comment:* One commenter noted that Part D claims data may be of limited value in creating a PHR. *Response:* We believe that access to medication history information, even of limited scope, is deemed one of the top priorities by emergency responders, emergency room personnel and physicians, in discussions regarding electronic PHRs. *Comment:* A commenter noted that PHR information shared with entities other than the beneficiary should only be released in an aggregated format without any physician identifiers. *Response:* We requested comments on the usefulness of creating a personalized beneficiary medication history record from the Part D claims data. We are uncertain as to why the commenter believes it would only be appropriate for physician information to be released at the aggregate level since the purpose of PHRs is to allow individuals and their providers to have access to information to improve the quality and delivery of care to the individual. Any sharing of this data with organizations that assist beneficiaries in developing their own PHR would need to be authorized by the individual to whom the record pertains, just as the individual would provide authorization for release of any other of his or her personal data held by Medicare. E. Applicability We stated in the proposed rule that the proposed revision does not affect the applicability of HIPAA to the DHHS or any other appropriate parties, nor does it affect the applicability of the Privacy Act (5 U.S.C. 552a) or the Trade Secrets Act (18 U.S.C. 1905). Thus, Part D claims data, like any personally identifiable information or PHI collected by the agency, are subject to protection under the HIPAA Privacy Rule, the Privacy Act and the Trade Secrets Act, and other laws, as applicable. In this final rule, we continue to take this position. *Comment:* One commenter stated that the proposed rule does not explain why HIPAA does not apply to Part D activities when HIPAA does apply to CMS activities for Parts A and B of Medicare. *Response:* The HIPAA Privacy Rule applies to covered entities and defines the term “covered entity” as
(1)a health plan,
(2)a health care clearinghouse, or
(3)a health care provider who transmits any health information in electronic form in connection with a covered transaction. (See 45 CFR 160.103.) HIPAA defines “health plan” as an individual or group plan that provides, or pays the cost of medical care, and specifically includes Part A and Part B of the Medicare program under title XVIII. (See section 1171(5) of the Act and 45 CFR 160.103 (definition of health plan).) With respect to Part D, because Part D sponsors meet the definition of health plan, they are covered entities subject to HIPAA. HIPAA does not apply to the component of CMS that administers the Part D program because it is does not pay claims directly. However, although Part D claims information held by this component is not directly subject to HIPAA, the Part D data are protected under the Privacy Act of 1974, which applies to all federal agencies' data collections of individually identifiable information in systems of records. The Privacy Act requires that CMS maintain Part D data in a protected system of records and may only use or disclose the data in accordance with the specific purposes which have been published in the **Federal Register** and with other uses and disclosures allowed by the Privacy Act, itself. See 5 U.S.C. 552a(b) and (e)(4). This rule will allow the Secretary to use the original 37 PDE elements that are being collected for Part D payment purposes for reporting to the Congress and the public, conducting evaluations of the overall Medicare program, making legislative proposals to Congress, and conducting demonstration projects. To the extent that such information becomes part of our administration of the Medicare Part A and Part B programs, HIPAA will apply to such information. Moreover, although Part D claims information held by the component of CMS that administers the Part D program are not directly subject to HIPAA, we are choosing to comply with HIPAA's limitations on the use and disclosure of PHI to ensure that beneficiaries' privacy interests are fully protected. In addition, we are choosing to impose standards similar to those applied when we release beneficiary identifiable information with respect to non-beneficiary identifiable Part D data, on the PDE, such as plan, prescriber, and pharmacy identifiable data. *Comment:* One commenter noted that many plan sponsors already share data with agencies such as the FDA, NIH, and AHRQ, and external entities subject to HIPAA, therefore there is no need for this rulemaking. *Response:* While plan sponsors may already share data with agencies such as FDA, NIH, and AHRQ, only CMS can share Part D claims data linked to Medicare Parts A and B data. Therefore, we maintain that this rulemaking is necessary. *Comment:* Some commenters expressed concern with CMS' use of data use agreements. They asked that CMS explain the steps we will undertake to ensure the confidentiality of individually identifiable beneficiary data. *Response:* In response to the commenter's concerns about CMS' reliance on data use agreements (DUAs), we administer DUAs for any data disclosures to external entities, including limited data sets that exclude certain personal identifiers. The DUA is a way to ensure that the data provided are only used for the purposes for which the data were disclosed. All external requests for personally identifiable data for research are subject to CMS' Privacy Board review and approval. Currently, for Parts A and B data, CMS restricts data releases to the minimum amount of information necessary for the requestor's specific research project. We intend to operate on the same basis, with some additional restrictions to protect privacy and commercially sensitive information as described our regulations at § 423.505(m) as well as in the appendix to this final rule, with respect to the release of collected Part D claims data. We anticipate that we will be able to satisfy many requests for Part D claims data using limited data sets, which exclude certain personal identifiers. *Comment:* A commenter was concerned with the release of prescriber identifiers, believing that the release of such data could be used to target marketing efforts and otherwise improperly affect a prescriber's judgment. *Response:* As explained previously in section II.B. of this final rule, we expect that the results of the Secretary's quality improvement and performance measurement initiatives may be made public in an effort to financially reward health care providers who provide high quality health care and to provide cost and quality information to consumers. Beyond that, we will encrypt prescriber identifiers as a general matter with limited exceptions (see 42 CFR 423.505(m), as well as the appendix to this final rule). Additionally, we will not release Part D claims information for commercial purposes. *Comment:* A commenter contended that for a HIPAA-covered entity the proposed rule will impose a substantial compliance burden and monetary costs to transform each prescription drug claim that a plan sponsor submits for payment purposes into an accountable disclosure that the plan sponsor would need to track in order to fulfill its accounting of disclosures obligations under the HIPAA Privacy Rule. The commenter also stated that the proposal may burden plan sponsors by possibly requiring many to distribute revised notices of privacy practices, which may cause beneficiary confusion. The commenter states that CMS should be precluded from implementing the proposed rule except at the beginning of a calendar year. *Response:* Regularly, laws and regulations intersect or overlap, and individuals and entities are required to dissect the application of such laws and regulations, as appropriate. This rule does not regulate how covered entities, subject to HIPAA compliance, must comply with the HIPAA Privacy Rule, nor was it intended to do so. As a general matter, Part D plan sponsors are subject to a wide range of Federal laws and regulations, including HIPAA, and in this instance there may be an intersection between such laws and regulations that requires analysis and consideration. As we noted in the preamble to the proposed rule, nothing in this final rule affects the applicability of HIPAA (or the Privacy Act) to the DHHS or any other appropriate parties. Since the proposed rule did state that it did not affect the applicability of HIPAA, we believe a brief discussion of the intersection between this rule and existing HIPAA rules is warranted. However, it is important to note that the Office for Civil Rights
(OCR)is the only agency within DHHS that can provide advice on and enforce the HIPAA Privacy Rule. Affected entities can obtain comprehensive information regarding the HIPAA Privacy Rule, including answers to frequently asked questions and information on the enforcement program, at *http://www.hhs.gov/ocr/hipaa/* . With this in mind, we believe that private plans are permitted by the HIPAA Privacy Rule to make the disclosures provided for in this Rule. The HIPAA Privacy rule permits disclosures for health oversight and as required by law. See 45 CFR 164.512(a) and 164.512(d). We are not suggesting that the HIPAA definition of “required by law” at 45 CFR 164.103 encompasses contractual requirements. Rather, we believe those disclosures required by contract, which are also mandated by statute or regulation or both, would be “required by law” under the HIPAA Privacy Rule. As noted previously above, plans disclosing data under this rule may face HIPAA compliance issues regarding accounting and Notice of Privacy Practices. We believe that most Part D plans very likely have a statement in their existing Notices of Privacy Practices that notifies enrollees of permitted disclosures for purposes of health oversight and as required by law, and therefore, are unlikely to have to modify their notices of privacy practices. An individual also has the right under the HIPAA Privacy Rule to receive an accounting of certain disclosures, including disclosures for health oversight purposes or disclosures required by law. It is each plan's responsibility to comply with the HIPAA Privacy Rule as it deems appropriate. Finally, we do not believe that any further delay in the effective date for this regulation is required. We believe the commenters are referencing the prohibition on mid-year significant regulatory requirements at 42 CFR 423.516. However, that regulation does not apply to already-existing regulations, such as HIPAA regulations, or the impact already-existing regulations will have on a new Part D regulation. Because we already collect Part D claims data, this regulation does not impose additional Part D requirements on Part D sponsors, and therefore, we do not view this regulation as constituting a significant midyear change for Part D sponsors. *Comment:* The commenter also questioned how CMS would notify beneficiaries that their data may be released for research purposes. *Response:* As a general matter, how we comply with our own HIPAA obligations is outside the scope of the proposed rule. To the extent HIPAA requires us to take any additional steps (including additional notification responsibilities) to ensure full compliance with HIPAA, we intend to do so. For instance, a covered entity is required to include in its notice of privacy practices a statement that PHI may be used for research purposes. CMS, as a covered entity for Medicare Parts A and B, currently provides such notice to beneficiaries annually. *Comment:* Several commenters requested that CMS discuss the regulation in light of the Trade Secrets Act, specifically with respect to pricing data. *Response:* Because our regulations at 42 CFR 423.505(f), (l), and
(m)are issued under the authority of section 1106 of the Act, any release of potentially proprietary data under these regulations would also be authorized by law under the Trade Secrets Act. As we have stated elsewhere in this preamble, we believe that our minimum data necessary policy with some additional restrictions to protect privacy and plan commercially sensitive information and our data sharing procedures will guard against any potential misuse or inappropriate disclosure of Part D claims data. F. Limitations This final rule in no way affects or limits our existing ability to collect non-payment data such as enrollment, formulary, price comparison, quality assurance and utilization review data. In such cases, even where the data collection is not specifically mandated by statute, we do not believe it is necessary to resolve any statutory ambiguity, because section 1860D-15 of the Act would not apply. In addition, it is important to note that this rule applies when collections of data occur under section 1860D-12 of the Act. The rule does not address collections that occur under other provisions of law. Thus, this rule also does not address uses or disclosures already permitted under section 1860D-15 of the Act, to carry out audits and evaluations necessary to ensure accurate and correct payment and to otherwise oversee Medicare reimbursement under Part D. These uses are already contemplated under both the statute and the regulations at § 423.322(b). Furthermore, section 1860D-15 of the Act and § 423.322(b) of our regulations do not limit the ability of OIG to access, use, or disclose Part D claims data as part of the Inspector General's statutory responsibilities to oversee the Medicare program. III. Provisions of the Final Regulations This final rule finalizes most of the provisions of the proposed rule. Those provisions of this final rule that differ from the proposed rule are as follows: • In part 423, adding section 1106 of the Act to the authority citation. • In § 423.1, adding section 1106 of the Act. • In § 423.505, making the following changes: ++ Revising paragraph (f)(3) to clarify that the regulatory provision is only applicable to Part D claims data and is limited to the original 37 elements reported on the PDE record; to add a reference to pilot projects, and to add care coordination and disease management activities, quality improvement and performance measurement activities, and the populating of personal health records to the list of necessary and appropriate purposes for the collection of this information. This list is not intended to be exclusive, and Part D claims data may be collected for other purposes that the Secretary deems necessary and appropriate. ++ Removing paragraph (f)(5) and incorporating the provisions of this paragraph in paragraphs
(l)and (m). ++ Adding a new paragraph
(l)to specify that CMS may use the data collected under § 423.505(f)(3). ++ Adding a new paragraph
(m)to specify that CMS may release the minimum data collected under § 423.505(f)(3) in accordance with applicable Federal laws, our established data sharing procedures, and subject to encryption of certain identifiers and aggregation of cost data to protect beneficiary confidentiality and commercially sensitive data of Part D sponsors. IV. Collection of Information Requirements Under the Paperwork Reduction Act of 1995, we are required to provide 30-day notice in the **Federal Register** and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget
(OMB)for review and approval. In order to fairly evaluate whether an information collection should be approved by OMB, section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 requires that we solicit comment on the following issues: • The need for the information collection and its usefulness in carrying out the proper functions of our agency. • The accuracy of our estimate of the information collection burden. • The quality, utility, and clarity of the information to be collected. • Recommendations to minimize the information collection burden on the affected public, including automated collection techniques. This document does not impose new information collection requirements on Medicare Part D plans. Medicare Part D plan sponsors already submit the information required to conduct the studies discussed earlier in the preamble of this document. Medicare Advantage prescription drug plan (MA-PD) sponsors, prescription drug plan
(PDP)sponsors, and Fallback plan sponsors, as required by the MMA, are required to submit payment-related data to CMS that include, but are not limited to, Part D claims data. The information collection requirements associated with the collection of prescription drug data from MA-PD, PDP and Fallback plan sponsors for Medicare Part D payments are currently approved under the Office of Management and Budget
(OMB)Control No. 0938-0982, with an expiration date of November 30, 2009. Additionally, we have included a discussion of the currently approved information collection requirements associated with the Medicare Part D reporting requirements and the plan benefit package
(PBP)and formulary submission for Medicare Advantage prescription drug plans (MA-PD) and prescription drug plans (PDPs). The information collection requirements
(ICRs)for the Part D reporting requirements and the plan benefit package are approved under OMB Control Nos. 0938-0992 and 0938-0763, respectively. A. ICRs Regarding Contract Provisions (§ 423.505) Section 423.505 discusses provisions that must be contained in contracts between Part D plan sponsors and CMS. Specifically, § 423.505(b)(8) requires that a Part D plan sponsor comply with the disclosure and reporting requirements in § 423.505(f), § 423.514, and § 423.329(b), respectively. Section 423.505(f) lists the information that Part D plan sponsors are required to disclose to CMS. This information includes but is not limited to the disclosure of certified financial information, the disclosure of all information necessary for us to administer and evaluate the program and to simultaneously establish and facilitate a process for current and prospective beneficiaries to exercise choice in obtaining prescription drug coverage, and the disclosure to its enrollees of all informational requirements under § 423.128 and, upon an enrollee's request, the financial disclosure information required under § 423.128(c)(4). B. ICRs Regarding Reporting Requirements (§ 423.514) Section 423.514 outlines the reporting requirements for Part D plan sponsors. Section 423.514(a) requires each Part D plan sponsor to have an effective procedure to develop, compile, evaluate, and report to CMS, to its enrollees, and to the general public, at the times and in the manner that CMS requires. Section 423.514(b) requires Part D plan sponsors to report to CMS annually, within 120 days of the end of its fiscal year, significant business transactions. In addition, § 423.514(c) sets forth the requirements for submitting combined financial statements. For any employees' health benefits plan that includes a Part D plan sponsor in its offerings, § 423.514(d) addresses the reporting and disclosure obligations under the Employee Retirement Income Security Act of 1974 (ERISA). Section 423.514(e) states that each Part D plan sponsor must notify CMS of any loans or other special financial arrangements it makes with contractors, subcontractors and related entities. Section 423.514(f) requires each Part D plan sponsor to make the information reported to CMS under this section available to its enrollees upon reasonable request. C. ICRs Regarding Determination of Payments (§ 423.329) Section 423.329(b) contains the reporting requirements for PDPs and MA-PDs for the purposes of determining health status risk adjustment. As stated in § 423.329(b)(3)(i), PDPs are required to submit data regarding drug claims that can be linked at the individual level to Part A and Part B data in a form and manner similar to the process provided under § 422.310 of this chapter and other information as we determine necessary. In addition, § 423.329(b)(3)(ii) requires MA organizations that offer MA-PD plans to submit data regarding drug claims that can be linked at the individual level to other data that the organizations are required to submit to CMS in a form and manner similar to the process provided under § 422.310 and other information as we determine necessary. D. ICRs Regarding Contract Provisions (§ 423.505(b)(8)) The burden associated with the requirements in § 423.505(b)(8) of this regulation is the time and effort associated with meeting the aforementioned requirements in § 423.505(f), § 423.514, and § 423.329(b). As stated earlier, these requirements are subject to the PRA; however, they are approved under existing OMB control numbers. The requirements in § 423.505(f) and § 423.514 are currently approved under OMB control number 0938-0992 with an expiration date of June 30, 2008. The information collection requirements contained in § 423.329(b) are currently approved under OMB control number 0938-0763, with an expiration date of November 30, 2009. Table 1.—Estimated Annual Reporting and Recordkeeping Burden Regulation section OMB Control number Number of respondents Number of responses Burden per response (hours) Total annual burden (hours) § 423.505 ** and § 423.514 ** 0938-0992 3,203 179,368 .69 123,764 § 423.329 ** 0938-0763 430 4,515 2.29 **10,319 Total 138,469 ** As specified by § 426.505(b)(8) As required by section 3504(h) of the Paperwork Reduction Act of 1995, we have submitted a copy of this document to the Office of Management and Budget
(OMB)for its review of these information collection requirements. V. Regulatory Impact Statement We have examined the impact of this rule as required by Executive Order 12866 (September 1993, Regulatory Planning and Review), 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), Executive Order 13132 on Federalism and the Congressional Review Act (5 U.S.C. 804 (2)). Executive Order 12866, as amended, 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). This final rule does not have economically significant effects of $100 million or more in any one year and therefore is not a major rule. We assessed alternatives, including, not releasing data to any entity meeting the applicable criteria. We determined that the approach that maximizes public health benefits is the approach taken in the final regulation, which would use a case-by-case evaluation approach similar to the process in use today for Medicare Parts A and B data, with some additional restrictions to protect privacy and commercially sensitive data of Part D sponsors. Weighing all factors, this approach limits the risk that sensitive Part D claims data will be released to inappropriate entities leading to the inappropriate use of this sensitive data, but maximizes the benefit that this data can provide in supporting research studies and other actions that will benefit the public. We do not believe that new costs associated with compliance under this regulation, if any, will be significant. As stated in section II. E. of this final rule, we expect risk and compliance burdens to be limited; therefore any costs associated with compliance or inappropriate use of data are expected to be limited, and because the use of these data according to applicable laws and CMS data release policies is expected to improve the public's health, this rule does not reach the economic threshold and thus is not considered a major rule requiring a RIA. The RFA requires agencies to analyze options for regulatory relief of small businesses. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. Most hospitals and most other providers and suppliers are small entities, either by nonprofit status or by having revenues of $6 million to $29 million in any 1 year. Individuals and states are not included in the definition of a small entity. While a number of Part D plan sponsors are small entities due to their nonprofit status, few, if any, of the Part D plan sponsors meet the size standard for a small insurance firm by having revenues of $6 million or less in any 1 year. Therefore, an analysis for the RFA will not be prepared because the Secretary has determined that this final rule will not have a significant economic impact on a substantial number of small entities. Furthermore, we believe, the rule does not create a significant economic impact on Part D plan sponsors. In addition, section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule 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. An analysis for section 1102(b) of the Act will not be prepared because the Secretary has determined that this final rule will not have a significant impact on the operations of a substantial number of small rural hospitals. In fact, we do not expect that it will have any impact on small rural hospitals because the rule relates to Part D plan sponsors, not small rural hospitals. Section 202 of the Unfunded Mandates Reform Act of 1995 also requires that agencies assess anticipated costs and benefits before issuing any rule whose mandates require spending in any 1 year of $100 million in 1995 dollars, updated annually for inflation. That threshold level is currently approximately $130 million. This final rule will not contain mandates having a negative effect on state, local, or tribal governments in the aggregate, or by the private sector, of $130 million. Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a final rule that imposes substantial direct requirement costs on state and local governments, preempts State law, or otherwise has Federalism implications. Even though states may incur costs associated with exchanging data, this regulation does not require states to request Part D claims data, but makes it an option, provided we can resolve any operational issues. In fact, even if States do request data, they may already have systems in place to receive data from CMS. Furthermore, we are not aware of any conflict between this final regulation and State privacy laws (with which Part D sponsors must comply per our regulations). Therefore, we do not believe this final regulation will implicate a Federalism issue through an impact on State privacy laws. Since this regulation does not impose any costs on state or local governments, the requirements of Executive Order 13132 are not applicable. We received the following comments regarding the impact analysis of the proposal rule: *Comment:* One commenter stated that because of the monetary cost and other compliance burdens associated with the implementation of this regulation due to HIPAA, this rule, if implemented, must be implemented at the beginning of a calendar year per § 423.516. *Response:* We address this comment in section II. E. of this final rule. *Comment:* A commenter stated that in determining whether the rulemaking met the $100 million threshold the value of the information to beneficiaries should have been considered. The commenter states that the value would surpass $100 million, since brokers rent lists potentially for $5 million per rental, often several times a year. *Response:* Under our data release policies, we would not allow the release of Part D claims data for commercial purposes. Thus, we do not believe the $100 million threshold would be met based on the example cited by the commenter. It is unlikely that list brokers will receive any nonpublic data from CMS. In accordance with the provisions of Executive Order 12866, this regulation was reviewed by the Office of Management and Budget. List of Subjects in 42 CFR Part 423 Administrative practice and procedure, Medicare, Prescription Drugs, Reporting and recordkeeping. For the reasons set forth in the preamble, the Centers for Medicare & Medicaid Services amends 42 CFR chapter IV as set forth below: PART 423—VOLUNTARY MEDICARE PRESCRIPTION DRUG BENEFIT 1. The authority citation for part 423 is amended to read as follows: Authority: Sections 1102, 1106, 1860D-1 through 1860D-42, and 1871 of the Social Security Act (42 U.S.C. 1302, 1306, 1395w-101 through 1395w-152, and 1395hh). Subpart A—General Provisions 2. Section 423.1 is amended by adding a new reference to paragraph (a)(1) in numerical order to read as follows: § 423.1 Basis and scope
(a)* * *.
(1)* * *. 1106. Disclosure of Information in Possession of Agency. Subpart K—Application Procedures and Contracts With Part D Plan Sponsors 3. Section 423.505 is amended by— A. Revising paragraph (b)(8). B. Redesignating paragraph (f)(3) as (f)(4). C. Adding new paragraph (f)(3). D. Adding new paragraphs
(l)and (m). The revisions and additions read as follows: § 423.505 Contract provisions.
(b)* * *
(8)Comply with the disclosure and reporting requirements in § 423.505(f), § 423.514, and the requirements in § 423.329(b) of this part for submitting current and prior drug claims and related information to CMS for its use in risk adjustment calculations and for the purposes of implementing § 423.505(f), (l), and
(m)and § 423.329(b) of this part.
(f)* * *
(3)The 37 original data elements included in all of its drug claims for purposes deemed necessary and appropriate by the Secretary, including, but not limited to, the following:
(i)Reporting to Congress and the public on overall statistics associated with the operation of the Medicare prescription drug program.
(ii)Conducting evaluations of the overall Medicare program, including the interaction between prescription drug coverage under Part D of Title XVIII of the Social Security Act and the services and utilization under Parts A, B, and C of title XVIII of the Act and under titles XIX and XXI of the Act, as well as other studies addressing public health questions.
(iii)Making legislative proposals to the Congress regarding Federal health care programs and related programs.
(iv)Conducting demonstration and pilot projects and making recommendations for improving the economy, efficiency, or effectiveness of the Medicare program.
(v)Supporting care coordination and disease management programs,
(vi)Supporting quality improvement and performance measurement activities, and;
(vii)Populating personal health care records.
(l)CMS may use the information collected under paragraph (f)(3) of this section. Any restriction set forth by § 423.322(b) of this part must not be construed to limit the Secretary's authority to use the information collected under paragraph (f)(3). (m)(1) CMS may release the minimum data necessary for a given purpose from the data collected under paragraph (f)(3) of this section to Federal executive branch agencies, congressional oversight agencies, States, and external entities in accordance with the following:
(i)Applicable Federal laws.
(ii)CMS data sharing procedures.
(iii)Subject, in certain cases, to encryption of certain identifiers and aggregation of cost data to protect beneficiary confidentiality and commercially sensitive data of Part D sponsors, in accordance with all of the following principles:
(A)Subject to the restrictions in this paragraph, all elements on the claim are available to congressional oversight agencies (as defined in paragraph (m)(1)(iv) of this section) and HHS.
(B)Cost data elements on the claim generally are aggregated for releases to other executive branch agencies, States, and external entities.
(C)Plan identifier elements on the claim are encrypted or unavailable for releases to external entities.
(D)Beneficiary, pharmacy, and prescriber identifier elements on the claim generally are encrypted for releases to external entities, except in limited circumstances, such as to link to another data set.
(iv)For purposes of paragraph (m)(1)(iii) of this section, congressional oversight agencies (the Congressional Budget Office, the Government Accountability Office, the Medicare Payment Advisory Commission, and the Congressional Research Service when acting on behalf of a congressional committee in accordance with 2 U.S.C. 166(d)(1)), States, and executive-branch Federal agencies are not considered to be external entities.
(2)Any restriction set forth by § 423.322(b) of this part must not be construed to limit the Secretary's authority to release the information collected under paragraph (f)(3) of this section. (Catalog of Federal Domestic Assistance Program No. 93.773, Medicare—Hospital Insurance; and Program No. 93.774, Medicare—Supplementary Medical Insurance Program) Dated: February 25, 2008. Kerry Weems, Acting Administrator, Centers for Medicare & Medicaid Services. Approved: March 17, 2008. Michael O. Leavitt, Secretary. The following appendix will not appear in the Code of Federal Regulations. Appendix—Data Element Availability Under Section 1860D-12 of the Social Security Act by Type of Requestor CMS and its contractors have access to all PDE elements. This chart shows the data elements that are available for release to other federal and state agencies and external entities in the final rule under our minimum necessary data policy subject, in certain cases, to encryption of certain identifiers and aggregation of cost data to protect beneficiary confidentiality and commercially sensitive data of Part D sponsors. Thus, a requestor would not automatically receive all of the available elements, but would only receive those necessary for their study. (Note: As stated in the preamble to the final rule, this chart applies only when data is collected under section 1860D-12 of the Act, and does not apply to any uses or disclosures already permitted under section 1860D-15 of the Act, including to carry out audits and evaluations necessary to ensure accurate and correct payment and to otherwise oversee Medicare reimbursement under Part D. These uses are already contemplated under both the statute and the regulations at § 423.322(b) and are not the subjects of this final rule.) Data elements Other (i.e., non-CMS) DHHS entities, and Congressional Oversight Agencies* See Note 1 Non-HHS Executive Branch Agencies and States External entities Identifiers Encryption permits analysis on a beneficiary, plan, prescriber, or pharmacy level without disclosure of the actual identifying information. CMS will link our data to other data files, to the extent feasible, to minimize the extent to which other parties need identifiers for data linkage purposes. CMS has the sole authority to determine whether a particular data element is needed for a request. Beneficiary ID (HIC Number, Cardholder ID, Patient date of birth) See Note 2 Encrypted, but available if needed Encrypted, but available if needed Encrypted, but available if needed to link to another dataset. Plan ID (PBP identifier, Contract identifier) See Note 3 Encrypted, but available if needed Encrypted, but available if needed Encrypted. Additionally, nonencrypted data will be available for purposes of performance measures Prescriber ID (Prescriber Identifier) See Note 4 Encrypted, but available if needed Encrypted, but available if needed Encrypted, but available if needed to link to another dataset. Additionally, nonencrypted data will be available for purposes of performance measures Pharmacy ID (Service provider identifier) See Note 5 Encrypted, but available if needed Encrypted, but available if needed Encrypted, but available if needed to link to another dataset. Qualifying Identifiers (Service & Prescriber Identifier Qualifiers—codes that denote whether NPI, NCPDP, UPIN, state license number, DEA, or non-standard code is used) Available Available Available. Internal plan/pharmacy prescription identification numbers (Claim Control Number—a code intended for the plan to identify unique events & Prescription Service Reference Number—a code assigned by the pharmacy at the time the prescription is filled) Available Unavailable Unavailable. Drug Utilization Information Date of Service Available Available Available. Drug information (Product/Service Identifier, Quantity Dispensed, Days Supply, Compound Code, Fill Number, Dispensing Status.) Available Available Available. Other utilization information (Dispense as Written/Product Selection Code, Drug Coverage Status Code) Available Available Available. Drug Cost Information Total Drug Costs (Ingredient Cost, Dispensing Fee, Total Amount Attributable to Sales Tax) See Note 6 Available, Disaggregated Available, Aggregated Available, Aggregated. Coverage Information Date Paid Available Available Available. Plan Paid Amounts (Covered D Plan Paid Amount, Non-covered Plan Paid Amounts) Available Available Available. Beneficiary cost sharing (Patient Pay Amount,) Available Available Available. Other Payer Amounts (Other True Out of Pocket Amount, Patient Liability due to Other Payer Amount) Available Available Available. Low-Income Subsidy Amount Available Available Available. Other Financial Information (Gross Drug Cost below Out-of-pocket Threshold, Gross Drug Cost above Out-of-pocket Threshold) Available Available Available. Other Descriptive Data Patient gender Available Available Available. Catastrophic Coverage Indicator (Catastrophic Coverage Code) Available Available Available. In-network versus OON or MSP claim (Pricing Exception code) Available Available Available. Electronic versus Paper Claim (Non-Standard format Code) Available Available Available. Original versus Adjusted PDE (Adjustment/Deletion code) Available Final Action claims would be provided, so this element should not be needed Final Action claims would be provided, so this element should not be needed. Generally, the notes apply to all columns across the row. Note 1 —Congressional oversight agencies include GAO, MedPAC, and CBO. CRS is considered a Congressional oversight agency, but only when acting on behalf of a committee pursuant to its authority in 2 U.S.C. § 166(d)(1). Otherwise, CRS is considered to be an external entity. Note also that OIG has authority independent of both sections 1860D-12 and 1860D-15 of the Social Security Act to collect data. Note 2 —CMS will encrypt all beneficiary identifiers unless they are needed. An example of where they might be needed is linkage to another dataset. When CMS sends real identifiers in order to permit the requestor to link files, CMS will encrypt identifiers during transmission, provide a link key to unencrypt the files, allow the linkage, and then require the requestor to re-encrypt identifiers. Public disclosure of research results will not include beneficiary identifying information. Note 3 —In general, CMS will link the Part D claims to plan level benefits and formulary data if needed by the requestor, and then encrypt the plan ID. However, CMS will not link certain information if it will lead to a de facto identification of the plan. CMS may develop plan specific performance measures which are publicly reported. Note 4 —CMS will link to physician characteristics from CMS files if needed by the requestor. Generally, when CMS sends real identifiers in order to permit the requestor to link files, CMS will encrypt identifiers during transmission, provide a link key to unencrypt the files, allow the linkage, and then require the requestor to re-encrypt identifiers. Note 5 —To the extent available, CMS will provide pharmacy characteristics from CMS files. However, CMS will not release pharmacy ID, together with drug cost information, in order to guard against the disclosure of negotiated price information. Note 6 —Generally, CMS will aggregate ingredient cost, dispensing fee, and sales tax at the individual claim level. Upon request, CMS will exclude sales tax from the aggregation at the individual claim level if necessary for the project. [FR Doc. 08-1298 Filed 5-22-08; 1:30 pm]
Connectionstraces to 36
Traces to 36 documents
CFR
U.S. Code
24 references not yet in our index
  • 10 CFR 50
  • Pub. L. 104-13
  • 17 CFR 240.19
  • 20 CFR 404.452-404
  • 41 CFR 101
  • 20 CFR 418
  • 5 CFR 1320.8(d)(1)
  • 49 CFR 222
  • Pub. L. 92-463
  • 49 USC 721
  • 42 CFR 423
  • Pub. L. 108-173
  • 45 CFR 160.103
  • 45 CFR 164.512(i)
  • 45 CFR 164.501
  • 45 CFR 5.65(d)
  • 42 CFR 2
  • 42 CFR 423.505(m)
  • 45 CFR 164.512(a)
  • 45 CFR 164.103
  • 42 CFR 423.516
  • 42 CFR 423.505(f)
  • Pub. L. 96-354
  • Pub. L. 104-4
Citation graph
cites case law
Notices
Issuance, Availability of Regulatory Guide 1
C.F.R.§ 50.55
U.S.C.§ 78s
U.S.C.§ 78a
U.S.C.§ 78f
U.S.C.§ 78c
U.S.C.§ 78k–1
C.F.R.§ 200.30-3
C.F.R.§ 404.401
C.F.R.§ 404.1720
Cite10 CFR 50
Pub. L.Pub. L. 104-13
Cite17 CFR 240.19
Cites 60 · showing 12Cited by 0 across 0 sources
★   the supreme law of the land   ★
Don't Tread on Me
E Pluribus Unum — out of many, one

"If you don't know your rights, you don't have any."

Marginalia · a citizen's law index
A research desk, not legal advice. Always read the cited source before relying on a summary.
Questions or an issue? support@self-law.org
disclaimerMarginalia is a research index, not a law firm. Nothing on this site is legal, tax, or financial advice and no attorney–client relationship is formed by using it. Statutes, regulations, and case law change; summaries, search results, AI output, and member posts may be incomplete, out of date, or wrong. Any interpretation drawn from material on this site should be validated by a licensed attorney in your jurisdiction before you act on it.