President Trump Establishes Regulatory Budgets by Executive Order

law books, regulatory budgetAmid  all of the controversy surrounding President Trump’s Executive Order suspending immigration from seven countries, and his nomination of Judge Neil Gorsuch to the Supreme Court, another executive order that may be at least as significant in the long run to reining in the administrative state has not received much attention.  The Executive Order on “Reducing Regulation and Controlling Regulatory Costs,” issued on January 30 without much fanfare, did three things: (1) required every agency promulgating any new regulation to get rid of two existing regulations; (2) required that the projected cost to the economy of the regulations being eliminated must be at least as great as the costs of the new one, as computed under standard Office of Management and Budget (OMB) guidelines, and (3) authorized OMB to impose a regulatory budget on each agency.

The first point, sometimes called “one in, two out,” has garnered some media attention, but in the long run, the other two provisions limiting regulatory costs may be at least as significant, particularly for the Environmental Protection Agency, which has historically imposed about half the costs of federal government regulation on the economy.  But this Executive Order also takes us into new territory and raises a host of legal questions.

The idea of a “regulatory budget” to constrain the costs government imposes on the economy  has been discussed since the 1970’s.  The basic idea is to adopt Madison’s constitutional concept of “balancing ambition with ambition” to regulate the regulators.  However, in the past, establishing a regulatory budget has generally been thought to require legislation.  Although proposed on numerous occasions, statutory authority to impose regulatory budgets has never been enacted.  It remains to be seen whether the courts will allow a binding regulatory budget to be imposed on agencies by the White House acting alone.

The Administrative Procedure Act specifically creates a cause of action to “compel agency action unlawfully withheld” as well as a right to petition for new rules.  How will the courts react when agencies begin to turn down petitions for new rules because there is no room for them in the agency’s regulatory budget, or because the agency judges them to be less important than existing rules that would have to be eliminated to pay for the new regulations?

In Motor Vehicle Manufacturers Ass’n. State Farm Mutual Automobile Insurance Co., 463 U.S. 29 (1983), the Supreme Court rejected an attempt by the Reagan Administration unilaterally to rescind an existing rule requiring automatic seat belts.  That precedent appears to require not only notice and comment but also a rational basis in the record that will survive judicial review in order to eliminate a legislative rule previously promulgated through notice and comment procedures.  What weight will the courts give to agency proposals to eliminate existing rules because they are required to do so in order to promulgate new ones under the Trump Executive Order?  And what about emergency rules or rules required by statute?  Do those also require elimination of two existing regulations?

Even assuming that the courts do uphold President Trump’s authority to impose the requirements discussed above on agencies and departments “in” the Executive Branch, what about the “independent” agencies, such as the Federal Energy Regulatory Commission (FERC), the Consumer Product Safety Commission (CPSC) or the Federal Trade Commission (FTC)?   These agencies often consist of multi-member commissions, sometimes with staggered terms and members of different political parties and a statutory prohibition on firing except for good cause.  On its face, the Executive Order does not exempt them, but the President’s power to direct them is unclear.  In Humphrey’s Executor v. United States, 295 U.S. 602 (1935), the Supreme Court held that President Roosevelt could not fire the Chairman of the FTC for policy differences.  More recently, the Obama Administration issued an Executive Order stating that independent agencies “should” comply with prior executive directives regarding public participation, scientific integrity in the rule making process, and retrospective analyses.  A number of independent agencies followed President Obama’s Order, but have been careful to characterize it as “ask[ing]” or “request[ing],” not mandating, agency action.

There are also a host of implementation questions that will presumably have to be answered by the OMB guidance implementing the recent Executive Order.  Many regulations, particularly in the environmental area, require large initial capital costs, but much lower costs for on-going operation and maintenance expenses; for example, when installing new pollution control equipment.  In assessing whether the costs of the eliminated regulations balances the costs of the new regulations, may the agency take into account the historic costs that have already been incurred (what economists call “sunk costs”), or only the current on-going costs that would be eliminated if those regulations were rescinded (what economists call “avoided costs”)?

More broadly, this Executive Order, as well as prior executive actions relating to the Keystone and Dakota Access Pipelines and Infrastructure Permitting, provides insight into the strategy that the Trump Administration appears to intend to use to control the so-called “Administrative State.”  For years, Presidents have struggled to impose policy direction and control on the actions of agency bureaucrats whom they generally cannot fire due to civil service protections. Past approaches have included the creation of the Senior Executive Service who are subject to dismissal, the OIRA review process for new rules, and the White House “czars” created by the Obama Administration.  It is becoming increasingly clear that the Trump Administration intends to try to manage the agencies by Executive Order, a strategy that some legal scholars have questioned as constitutionally dubious if the President directs particular actions as opposed to establishing general principles.

© 2017 Covington & Burling LLP

Government Forces Awaken: Rise of Cyber Regulators in 2016

As the sun sets on 2015, but before it rises again in the New Year, we predict that, in the realm of cyber and data security, 2016 will become known as the “Rise of the Regulators.” Regulators across numerous industries and virtually all levels of government will be brandishing their cyber enforcement and regulatory badges and announcing: “We’re from the Government and we’re here to help.”

The Federal Trade Commission will continue to lead the charge in 2016 as it has for the last several years. Pursuing its mission to protect consumers from unfair trade practices, including from unauthorized disclosures of personal information, and with more than 55 administrative consent decrees and other actions booked so far, the FTC (for now) remains the most experienced cop on the beat.   As we described earlier this year, the FTC arrives with bolstered judicial-enforcement authority following the Third Circuit’s decision in the Wyndham Hotel case.  Notwithstanding the relatively long list of administrative actions and its published guidance – businesses that are hacked and that lose consumer data, are at risk of attracting the attention of FTC cops and of proving that their cyber-related systems, acts and practices were “reasonable.”

But the FTC is not alone. In electronic communications, the Federal Communications Commission (FCC) in 2015 meted out $30 million in fines to telecom and cable providers, including to AT&T ($25 million) and Cox Communications ($595K). And this agency, increasingly known for its enforcement activism, may have just begun.  Reading its regulatory authority broadly, the FCC has asserted a mandate to take “such actions as are necessary to prevent unauthorized access” to customers’ personally identifiable information. This proclamation, combined with the enlistment of the FCC’s new cyber lawyer/computer scientist wunderkind to lead that agency’s cyber efforts, places another burly cop on the cyber beat.

The Securities and Exchange Commission (SEC) will be patrolling the securities and financial services industries. Through its Office of Compliance Inspections and Examinations (OCIE), the SEC is assessing cyber preparedness in the securities industry, including investment firms’ ability to protect broker-dealer and investment adviser customer information. It has commenced at least one enforcement action based on the agency’s “Safeguards Rule” (Rule 30(a) of Regulation S‑P), which applies the privacy provisions in Title V of the Gramm-Leach-Bliley Act (GLBA) to all registered broker-dealers, investment advisers, and investment companies. With criminals hacking into networks and stealing customer and other information from financial services and other companies, expect more SEC investigations and enforcement actions in 2016.

Moving to the Department of Defense (DoD), new rules, DFARS clauses, and regulations (e.g., DFARS subpart 204.73, 252.204–7012, and  32 CFR § 236) are likely to prompt the DoD Inspector General and, perhaps, the Defense Contracting Auditing Agency (DCAA) to examine whether certain defense contractors have the required security controls in place.  Neither the DoD nor its auditors have taken action to date.  But don’t mistake a lack of overt action for a lack interest (or planning).  It would come as no surprise if, by this time next year, the DoD has launched its first cyber-regulation mission, be it by the False Claims Act, suspension and debarment proceedings, or through terminations for default.

In addition to these cyber guardians, other federal agencies suiting up for cyber enforcement include:

  • The Consumer Financial Protection Board’s (CFPB) growing Cybersecurity Program Management Office;

  • The Department of Energy’s (DOE) Office of Electricity Delivery and Energy Reliability, examining the security surrounding critical infrastructure systems;

  • The Office of Civil Rights (OCR) of the U.S. Department of Health and Human Services, addressing healthcare providers and health insurers’ compliance with health information privacy and security safeguard requirements; and

  • The Food and Drug Administration, examining the cybersecurity for networked medical devices containing off-the-shelf (OTS) software.

But these are just some of the federal agencies poised for action.   State regulators are imposing their own sector-specific cyber security regimes as well.   For example, the State of California’s Cybersecurity Task Force, New York’s Department of Financial Services, and Connecticut’s Public Utility Regulatory Agency are turning their attention toward cyber regulation. We believe that other states will join the fray in 2016.

At this relatively early stage of standards and practices development, the National Institute of Standards and Technology (NIST) 2014 Cyber Security Framework lays much of the foundation for current and future systems, conduct, and practices. The NIST framework is a “must read.” NIST, moreover, has provided additional guidance earlier this year in its June 2015 NIST Special Publication 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations.  While addressing security standards for nonfederal information systems (i.e., government contractors’ information systems), it also provides important guidance for companies who do not operate within the government contracts sphere.  Ultimately, this 2015 NIST publication may serve as an additional general standard against which regulators (and others) may assess institutional cybersecurity environments in 2016 – and beyond.

But for now, the bottom line is that in 2016 companies now must add to its list of actual or potential cyber risks and liability, the hydra-headed specter of multi-sector, multi-tiered government regulation – and regulators.

That Drone in Your Holiday Stocking Must Now Be Registered With FAA

Fearing for public safety over the explosion of hobby-type drones taking to the air, on December 14, 2015, the Federal Aviation Administration (FAA) issued the first rule1 of its kind directed squarely to owners and operators of hobby and recreational small unmanned aircraft systems (sUAS aka drones) that now requires their registration on the FAA’s new online drone registration portal.2 A second, more comprehensive drone rule is expected to issue in 2016 to allow the use of drones for certain commercial purposes where the risk to public safety is low.

In the meantime, the hobby drone rule, which goes into effect on December 21, 2015 ahead of the holiday rush, requires all hobby-type drones weighing between 0.55 pounds (about two sticks of butter) and 55 pounds that have flown prior to December 21, 2015 to be registered no later than February 19, 2016.3 For hobby drones in this weight class flying for the first time on or after December 21, 2015 (i.e. holiday stocking stuffers), the rule requires that the owner register the drone before the first flight.

The FAA structured the grace period to encourage registration of millions of pre-existing drones while also requiring that all new drones be registered before first flight. To further encourage registration, the $5.00 registration fee will be credited back to registrants if they register within the first 30 days. And to lessen the burden of registration, the rule provides that a single registration applies to as many drones as an owner/operator owns or operates. If these incentives are insufficient to prompt compliance, the rule provides civil penalties up to $27,500, and criminal penalties including fines up to $250,000 and/or imprisonment for up to three years.

U.S. citizens age 13 or older can register their drones at the FAA’s registration portal. The registrant will need to provide the FAA with their name, physical address, mailing address (if different) and email address. Upon completion of the registration process, the FAA will provide the registrant (or certificate holder, as the FAA calls them) with a unique registration number that must be affixed to each drone.4 In addition, each registration must be renewed every 3 years and will require an additional $5.00 renewal fee.

After the rule goes into effect on December 21, 2015, all operators of hobby drones falling within the weight limits of the rule must provide proof of registration in the form of a Certificate of Aircraft Registration, either in printed or electronic form—much the same way as an angler or a hunter currently provides proof of a state fishing license or a state hunting license to a game warden.5

A number of exceptions to the rule are worth mentioning. First, hobby drones that weigh less than 0.55 pounds (i.e. radio-controlled micro quadcopters that fit in the palm of your hand) do not require registration.6 The rule will not apply to drones flown solely indoors. The rule also does not apply to those who want to fly drones for commercial purposes (i.e. for pay and/or hire) or on behalf of a state or federal government agency (i.e. fire departments, police departments, etc.). Such operators must first obtain an exemption of the FAA’s rules applicable to, for example, passenger-carrying aircraft, that the FAA has interpreted as also being applicable to commercial operators of unmanned drones regardless of size and weight. In addition, any types of entities other than individual hobbyists—such as corporations, or anyone wanting to record a lease or security interest—cannot use the online registration portal.

The new rule is the first concrete step that the FAA has taken in response to Congress’ mandate to the FAA under Section 333 of the FAA Modernization and Reform Act of 2012 to integrate unmanned aircraft into the National Airspace System (NAS). The next big step will be the FAA’s issuance in 2016 of rules that provide a legal path for using drones for commercial purposes without having to obtain prior FAA approval. Those rules will likely have a sweeping impact on business owners of all types who want to buy and sell aerial imaging and/or aerial data transmission services, including large-scale land developers, shopping mall operators and owners of other large structures, real estate agents, wedding photographers, and live TV/radio broadcast providers, to name a few, as well as industries that support those businesses, including software and hardware component suppliers, venture capital and financing providers, accountants, and the like.

In the interim, the new rule will force a dramatic change in the way consumers think about small radio-controlled unmanned aircraft in the future—they’re not just toys anymore.


1 See FAA Interim Final Rule (IFR) available at: https://www.faa.gov/news/updates/media/20151213_IFR.pdf
2 The FAA’s drone registration portal is available at: https://www.faa.gov/uas/registration/
3 Model radio-controlled aircraft of all types, including the type of fixed wing, radio-controlled model aircraft that have flown in parks and fields for decades, fall under the new rule.
4 The unique registration number may be affixed via permanent marker, label, engraving or other means as long as the number is readily accessible and readable upon close visual inspection.
5 Although it is unlikely that the FAA will have the manpower to enforce the new rule against hobbyists who do not register their drones, the FAA nevertheless intends to employ a strategic approach to encourage compliance ranging from outreach and education programs to administrative and/or legal action should the facts of a case so warrant.
6 According to the FAA, most toy drones costing $100 or less will likely weigh less than 0.55 pounds (250 grams).

SEC Is Sued Again For Doing Nothing

Have you heard about a lawsuit filed earlier last week against the Securities and Exchange Commission due to its failure to respond to a petition asking the Commission to adopt political spending disclosure requirements?

SEC-logoGOLD

But must the Commission act on the petitions that are submitted to it?  Rule 192 of the Commission’s Rules of Practice requires only that the Commission acknowledge receipt and give notice of any action taken by the Commission:

The Secretary shall acknowledge, in writing, receipt of the petition and refer it to the appropriate division or office for consideration and recommendation.  Such recommendations shall be transmitted with the petition to the Commission for such action as the Commission deems appropriate.  The Secretary shall notify the petitioner of the action taken by the Commission.

At least three fundamental requirements are absent from Rule 192.  First, the rule doesn’t require the Commission to take action.  Second, the rule doesn’t require the Commission to act promptly. Finally, the rule doesn’t require the Commission to explain its reasons for denying a petition. Indeed, Rule 192 falls far short of the requirements of the Administrative Procedure Act as explained by then Circuit Court Judge Ruth Bader Ginsberg:

Section 4(e) of the Administrative Procedure Act, 5 U.S.C. § 553(e), commands that “[e]ach agency shall give an interested person the right to petition for the issuance … of a rule.”  Section 6(a), 5 U.S.C. § 555(e), requires “prompt notice” in the event an agency denies such a petition.  Further, section 6(a) directs that when a denial is not self-explanatory, “the notice shall be accompanied by a brief statement of the grounds for denial.”

Ass’n of Investment Bankers v. Securities and Exchange Commission, 676 F.2d 857, 864 (1982).

One obvious issue for the plaintiff in this most recent lawsuit is whether judicial review is even available.  The plaintiff doesn’t allege that the Commission has actually denied his petition.  To the contrary, the plaintiff admits that “To date, the SEC has given no indication it is still considering whether to recommend the issuance of such a proposed rule, nor has it otherwise responded to the pending rulemaking petitions”.  The complaint cites WWHT, Inc. v. Federal Communications Com., 656 F.2d 807 (D.C. Cir. 1981) but that case involved an actual order denying a petition for rulemaking.

Even if the court decides that a failure to respond is tantamount to a denial, plaintiff will still have an uphill climb.  As Judge Edwards observed in WWHT, Inc. review is “very limited”.  The court will also have to grapple with the conundrum of how to conduct a review when there is no record.

© 2010-2015 Allen Matkins Leck Gamble Mallory & Natsis LLP

DaVita Agree to $495 Million Settlement in Alleged Medicare Fraud Lawsuit Filed by Qui Tam Whistleblowers

On Monday, May 4, 2015, DaVita Kidney Care, a division of DaVita Healthcare Partners, Inc. (DaVita), and one of the leading dialysis services providers in the United States, agreed to pay the U.S. Government $450 million for allegedly violating the False Claims Act (FCA) when it continuously discarded good medicine and then billed Medicare and Medicaid for it. DaVita also agreed to pay $45 million for legal fees.

According to the lawsuit filed in 2011 by two former employees of DaVita, between 2003 and 2010, when DaVita administered iron and vitamin supplements such as Zemplar, Vitamin D, and Venofer, vials containing more than what the patients needed were used and the rest was thrown away. For example, if a patient only needed 25 milligrams of medicine, DaVita allegedly used a 100 milligram vial, administered only 25 mg, and tossed the rest in the trash. Although before 2001, this practice was condoned by the National Centers for Disease Control and Prevention (CDC) in order to prevent infectious outbreaks caused by the re-entry of the same vial of medicine, the CDC subsequently changed it policies to outlaw this practice.

This FCA lawsuit alleging that DaVita misused and mishandled of medicine, and overbilled Medicare and Medicaid is not the first such allegation against DaVita, which is not a stranger to FCA lawsuits. In fact, DaVita previously settled two other lawsuits in which it allegedly violated the FCA. In October 2014, DaVita agreed to pay the U.S. Government $350 million for allegedly persuading physicians or physician groups to refer their dialysis patients to DaVita by offering kickbacks for each patient referred. And in 2012, DaVita agreed to pay $55 million to the federal government for overbilling the government for Epogen, an anemia drug. These lawsuits were filed by former employees who decided to come forward as whistleblowers and to help to uncover what they considered to be illegal practices by DaVita. Under the FCA, such whistleblowers can bring what is known as a “qui tam” lawsuit, which is brought by a private citizen to recover money obtained by fraud on the government. As an incentive to bring qui tam lawsuits, the FCA provides that qui whistleblowers receive between 15 and 30 percent of the amount of funds recovered for the government.

Provisions of the FCA make it unlawful for a person or company to defraud governmental programs, such as Medicare or Medicaid.

Posted by the Whistleblower Practice Group at Tycko & Zavareei LLP

© 2015 by Tycko & Zavareei LLP

New York Implements Medical Marijuana Rules

The New York State Department of Health has issued regulations implementing the State’s medical marijuana law, enacted last July.

Published April 15 in the State Register, the regulations allow the use of marijuana for patients with cancer, AIDS, Lou Gehrig’s disease, Parkinson’s disease, multiple sclerosis, certain spinal cord injuries, epilepsy, inflammatory bowel disease, neuropathies, and Huntington’s Disease, and symptoms including severe or chronic pain, surgeries, severe nausea, persistent muscle spasms and wasting syndrome, who comply with the rules. The Commissioner of Health may add other conditions, symptoms or complications, under the regulations.

In accordance with the law, those patients will be able to use only non-smokable forms or marijuana, to be ingested or vaporized. “Smoking is not an approved route of administration.” However, even vaporization is banned in public places, and in no case may approved medical marijuana be consumed through vaporization in locations where smoking would be prohibited by the State’s Public Health Law, including places of employment. Products authorized by the regulations are restricted to liquids, oils or capsules. Unless the Commissioner approves, approved marijuana products may not be incorporated into edible food products by a registered organization.

Only five businesses or non-profits in the State may be licensed to grow, process of distribute approved marijuana. Each such enterprise may have four dispensing facilities. The Commissioner can consider permitting more dispensing facilities.

While implementation will not be immediate, employers should prepare for responding to employees taking marijuana under the law and regulations.

Authored by:  Roger S. Kaplan of Jackson Lewis P.C.

FAA Issues New Proposed Rules for Unmanned Aerial Systems (Drones)

Greenberg Traurig Law firm

The FAA Modernization and Reform Act of 2012 addressed the integration of civil unmanned aircraft systems, also known as UAS or drones, into the national airspace system. The Act requires the Secretary of Transportation to develop, among other things, a comprehensive integration plan and rules governing the operation of small UAS. On Feb. 15, 2015, the Federal Aviation Administration (FAA) issued its proposed rules. According to the Secretary of Transportation, UAS “technology is advancing at an unprecedented pace and this milestone allows federal regulations and the use of our national airspace to evolve to safely accommodate innovation.”

The Notice of Proposed Rulemaking will be available for public comment for 60 days following its publication in the Federal Register. Interested and affected companies have the opportunity to provide comments on the FAA proposal and shape the final UAS rule.

Permitted Vehicles

The proposed rules would permit the operation of UAS weighing less than 55 pounds. The UAS would not be required to have an airworthiness certificate, such as that required for an airplane, but they would have to display aircraft markings similar to other aircraft, and operators would be required to conduct a pre-flight safety check. The FAA is also soliciting public comment on further exemptions for “micro” UAS, weighing 4.4 pounds or less. The proposed rules do not apply to model aircraft and do not apply to private, recreational use of drones.

Operational Limits

The UAS could operate at speeds up to 100 mph, and at altitudes below 500 feet above ground level. Operations would be limited to daylight hours with visibility of at least 3 miles. The UAS would have to remain within the unaided visual line-of-sight of the operator; binoculars or an onboard camera would not satisfy this requirement. Operators could also use an observer to assist in maintaining visual contact, but would have to retain the ability to see the UAS themselves.

Licensed Operators

Operators would have to be licensed by the FAA, but they would not need a pilot’s license. Under existing regulations, operators can request an exemption from FAA regulations, but such exemptions are usually conditioned on possession of a pilot’s license by the operator. Under the proposed rules, operators would have to be at least 17 years old and be vetted by the Transportation Security Administration. They would be required to pass an initial aeronautical test at an FAA test site, with an update test every 2 years. The anticipated costs for the license are small, in the range of a few hundred dollars.

Flights over People and Property

The UAS would be prohibited from operating over any persons “not directly participating in the operation” or “not located under a covered structure that can provide reasonable protection.” This is a significant limitation, which would preclude flights over most public locations such as schools, beaches and parks, and might be read to limit flights over residential areas. Given the number of drone videos already posted online, this rule is likely to be broken, which, as noted below, may result in potential liability. The limitation on overflight of other persons also highlights privacy concerns. Although not directly addressed in the proposed rules, privacy issues will continue to be a point of friction between drone operators and those potentially affected, such as drone-operating photo-journalists and their news subjects.

Delivery Systems and Remote Monitoring

The line-of-sight requirement would likely preclude the type of remotely-piloted delivery systems envisioned by certain major sales and fulfillment services. This requirement may also limit the use of the proposed rules for authorizing remote monitoring of agricultural sites, pipelines and other areas that are out of the line-of-sight of the operator. However, in these situations, the FAA grants limited exemptions to existing FAA regulations for qualified operators, and the proposed rules do not preclude further development of rules for remote operation.

Liability and Insurance

A UAS weighing 50 pounds and traveling at 100 mph could represent a significant potential danger to persons and property. The proposed rules would require a report within 10 days of any accident involving injury to persons or property. Companies operating drones are cautioned that existing liability policies may not provide coverage for drones, particularly for those that are not operated in compliance with existing FAA regulations and exemptions. Some carriers are writing coverage specific to drones, and operators, as well as the companies that hire such operators, should consult with their insurance agents prior to commencing operations.

Ongoing Legal Issues and Interim Operations

The FAA rules are proposed rules, not authorizations for immediate operations. Therefore, companies that plan to use drones before the rules are finalized are cautioned that, unless they hold an existing FAA exemption, they may risk liability for the commercial use of drones. In addition to the FAA, state and local governments are currently exploring further restrictions on drone flights, including restrictions related to privacy, which are not directly addressed in the FAA proposed rules.

In addition to regulatory limitations, drone operations can create significant risks of liability for personal injury, property damage and other claims. These legal issues are likely to present risks even for companies that do not directly operate drones, but instead contract with drone operators.

Given the rapid development in both the technology and the rules and regulations, companies that plan to operate or hire drones should consult with counsel to get an up-to-date assessment of the regulatory environment and other legal risks pertaining to their particular location.

This Week in Congress – February 2, 2015 re: 2016 Budget Proposal, DHS, and more

Covington_NL

President Obama will release his Fiscal Year (FY) 2016 budget proposal today, requesting roughly $4 trillion in spending for the upcoming year and specifying the Administration’s views on how and from what sources the federal government should be raising money and how and on what it should be spending it for the fiscal year beginning October 1.  The President’s budget sets off a fiscal showdown with the Republican-led Congress, whose members generally view the Administration’s proposals as higher taxes and higher government spending.  Many of President Obama’s cabinet members will be on Capitol Hill this week and in the coming weeks, testifying before House and Senate committees as to the merits of the budget proposal and highlighting areas of potential compromise as Congress develops its own budget for FY 2016.  Treasury Secretary Jacob Lew will be before the House Ways and Means and Senate Budget Committees on Tuesday, while IRS Commissioner John Koskinen will be before the Senate Finance Committee.  On Wednesday, Shaun Donovan, Director of the Office of Management and Budget, is scheduled to appear before the House Budget Committee and Sylvia Mathews Burwell, Secretary of the Department of Health and Human Services, appears before the Senate Finance Committee.  In addition, the Senate Armed Services Committee will hold the confirmation hearing this week for Ashton Carter to serve as Secretary of Defense.  With Committee Chairman John McCain’s strong desire for increased defense spending, the budget will no doubt be front and center in that hearing as well.

The House of Representatives returns to legislative business on Monday taking up three bills concerning programs at the Department of Homeland Security.  On Tuesday, the House will vote on H.R. 596, a bill that would repeal the Affordable Care Act while directing House committees to develop alternatives.  Since the Affordable Care Act was signed into law in 2010, Congress has voted 54 times on measures to repeal, revamp, or make technical changes to it.  On Wednesday, members will consider H.R. 50, the Unfunded Mandates Information and Transparency Act of 2015, sponsored by Rep. Virginia Foxx.  This legislation, which passed the House in 2014 by a vote of 234-176, would impose stricter requirements for how and when federal agencies must disclose the cost of federal mandates and equips both Congress and the public with tools to determine the true costs of regulations.  On Thursday, the House will vote on H.R. 527, the Small Business Regulatory Flexibility Improvements Act of 2015, sponsored by Representative Steve Chabot, which requires federal agencies to consider the economic effects of regulations on small business before imposing overly burdensome mandates that prevent growth and job creation.  This legislation has also passed the Republican-controlled House in the two previous Congresses.

The Senate returns on Monday and is expected to vote on H.R. 203, the Clay Hunt Suicide Prevention for American Veterans Act, a bill that the House passed unanimously.  The bill would require annual evaluations of the Department of Veterans Affairs’ mental health and suicide prevention programs.  The Senate will then seek to turn to H.R. 240, an appropriations bill that will fund the Department of Homeland Security for the remainder of 2015; the current budget for DHS expires  Feb. 27. While the bill provides $40 in funding for DHS, it also blocks any of the funds from being used to carry out President Obama’s new immigration and deportation policy announced in an executive order last November.  President Obama has pledged to veto the measure if the immigration rider is included.  Leader McConnell is unlikely to be able to get the 60 votes needed on cloture on the motion to proceed to the appropriations bill.  Once the cloture vote fails, he will need to figure out an alternative means of considering the legislation.  He has put a clean Democratic DHS appropriations bill on the Senate Calendar under Rule 14, so moving to that bill after the failed cloture vote is one possibility.

In addition to the hearings focused on the President’s budget and on the Defense Secretary nomination, a list of other key congressional hearings this week is included below:

 Feb. 3

 House Committees

Global Threat Assessment
House Armed Services
Full Committee Hearing
Feb. 3, 10 a.m., 2118 Rayburn Bldg.

Flu Preparation and Prevention
House Energy and Commerce – Subcommittee on Oversight and Investigations
Subcommittee Hearing
Feb. 3, 10 a.m., 2123 Rayburn Bldg.

U.S. Interests in Western Hemisphere
House Foreign Affairs – Subcommittee on the Western Hemisphere
Subcommittee Hearing
Feb. 3, 11 a.m., 2172 Rayburn Bldg.

Immigration Law Assessment
House Judiciary
Full Committee Hearing
Feb. 3, 11 a.m., 2141 Rayburn Bldg.

Inspectors General Oversight
House Oversight and Government Reform
Full Committee Hearing
Feb. 3, 10:15 a.m., 2154 Rayburn Bldg.

NSF Research Facility Oversight
House Science, Space and Technology – Subcommittee on Oversight; House Science, Space and Technology – Subcommittee on Research and Technology
Committee Joint Hearing
Feb. 3, 10 a.m., 2318 Rayburn Bldg.

Energy and Transportation Issues
House Transportation and Infrastructure – Subcommittee on Railroads, Pipelines and Hazardous Materials
Subcommittee Hearing
Feb. 3, 10 a.m., 2167 Rayburn Bldg.

Fiscal 2016 Budget Issues – Treasury Secretary Jacob Lew
House Ways and Means
Full Committee Hearing
Feb. 3, 10 a.m., 1300 Longworth Bldg.

Airport Access Control Measures
House Homeland Security – Subcommittee on Transportation Security
Subcommittee Hearing
Feb. 3, 2 p.m., 311 Cannon Bldg.

Wounded Warrior Program
House Armed Services – Subcommittee on Military Personnel
Subcommittee Hearing
Feb. 3, 3:30 p.m., 2118 Rayburn Bldg.

Senate Committees

Military Compensation and Retirement Modernization Commission
Senate Armed Services
Full Committee Hearing
Feb. 3, 9:30 a.m., G-50 Dirksen Bldg.

Fiscal 2016 Budget – Treasury Secretary Jacob Lew
Senate Budget
Full Committee Hearing
Feb. 3, 10 a.m., 608 Dirksen Bldg.

U.S.-Cuba Relations
Senate Foreign Relations – Subcommittee on Western Hemisphere, Transnational Crime, Civilian Security, Democracy, Human Rights and Global Women’s Issues
Subcommittee Hearing
Feb. 3, 10 a.m., 419 Dirksen Bldg.

IRS Fiscal 2016 Budget Request – John Koskinen, Commissioner, Internal Revenue Service
Senate Finance
Full Committee Hearing
Feb. 3, 10:30 a.m., 215 Dirksen Bldg.

No Child Left Behind and Student Needs
Senate Health, Education, Labor and Pensions
Full Committee Hearing
Feb. 3, 10 a.m., 216 Hart Bldg.

Joint Committees
Veterans Affairs Issues
House Veterans’ Affairs; Senate Veterans’ Affairs
Committee Other Event
Feb. 3 TBA, Veterans Affairs, 810 Vermont Ave. NW

Feb. 4

House Committees

Military Compensation and Retirement Commission
House Armed Services
Full Committee Hearing
Feb. 4, 10 a.m., 2118 Rayburn Bldg.

Fiscal 2016 Budget Issues – Shaun L.S. Donovan, Director, Office of Management and Budget
House Budget
Full Committee Hearing
Feb. 4, 10:30 a.m., 210 Cannon Bldg.

U.S. Schools and Workplaces
House Education and the Workforce
Full Committee Hearing
Feb. 4, 10 a.m., 2175 Rayburn Bldg.

HUD Ethical Oversight
House Financial Services – Subcommittee on Oversight and Investigations
Subcommittee Hearing
Feb. 4, 10 a.m., 2167 Rayburn Bldg.

U.S.-Cuba Policy Assessment
House Foreign Affairs
Full Committee Hearing
Feb. 4, 10 a.m., 2172 Rayburn Bldg.

Legal Workforce Act
House Judiciary – Subcommittee on Immigration and Border Security
Subcommittee Hearing
Feb. 4, 10 a.m., 2141 Rayburn Bldg.

Furthering Asbestos Claim Transparency Act
House Judiciary – Subcommittee on Regulatory Reform, Commercial and Antitrust Law
Subcommittee Hearing
Feb. 4, 1 p.m., 2141 Rayburn Bldg.

Palestinian Authority and International Criminal Court
House Foreign Affairs – Subcommittee on the Middle East and North Africa
Subcommittee Hearing
Feb. 4, 2 p.m., 2172 Rayburn Bldg.

Senate Committees

Secretary of Defense Nomination
Senate Armed Services
Full Committee Confirmation Hearing
Feb. 4, 9:30 a.m., G-50 Dirksen Bldg.

HHS Fiscal 2016 Budget Request – Sylvia Mathews Burwell, Secretary, United States Department of Health and Human Services
Senate Finance
Full Committee Hearing
Feb. 4, 10 a.m., 215 Dirksen Bldg.

Cybersecurity and Private Sector Issues
Senate Commerce, Science and Transportation
Full Committee Hearing
Feb. 4, 10 a.m., 253 Russell Bldg.

Implications of Immigration Action
Senate Homeland Security and Governmental Affairs
Full Committee Hearing
Feb. 4, 10 a.m., 342 Dirksen Bldg.

Vessel Discharge Regulations
Senate Commerce, Science and Transportation – Subcommittee on Oceans, Atmosphere, Fisheries and Coast Guard
Subcommittee Hearing
Feb. 4, 2:30 p.m., 253 Russell Bldg.

Indian Affairs Legislation
Senate Indian Affairs
Full Committee Markup
Feb. 4, 2:30 p.m., 628 Dirksen Bldg.

Loan Leveraging Issues
Senate Indian Affairs
Full Committee Oversight Hearing
Feb. 4, 2:30 p.m., 628 Dirksen Bldg.

Financial Exploitation of Seniors
Senate Special Aging
Full Committee Hearing
Feb. 4, 2:15 p.m., 562 Dirksen Bldg.

Joint Committees

Proposed Waters Rule
Senate Environment and Public Works; House Transportation and Infrastructure
Committee Joint Hearing
Feb. 4, 10 a.m., HVC-210 Capitol Visitor Center

Feb. 5

House Committees

Drinking Water Protection Act
House Energy and Commerce – Subcommittee on Environment and the Economy
Subcommittee Hearing
Feb. 5, 10 a.m., 2123 Rayburn Bldg.

Senate Committees

Treasury Fiscal 2016 Budget Request – Treasury Secretary Jacob Lew
Senate Finance
Full Committee Hearing
Feb. 5, 10 a.m., 215 Dirksen Bldg.

Joint-Employer Standard
Senate Health, Education, Labor and Pensions
Full Committee Hearing
Feb. 5, 10 a.m., 430 Dirksen Bldg.

Judiciary Issues

Senate Judiciary
Full Committee Business Meeting
Feb. 5, 10:30 a.m., 226 Dirksen Bldg.

Kaitlyn McClure, Covington & Burling LLP Policy Advisor, co-authored this post.

OF

U.S. Department of Homeland Security Extends REAL ID Document Enrollment Dates Affecting State-Issued Driver’s Licenses and IDs

Greenberg Traurig Law firm

Pursuant to its phased implementation of the REAL ID Act, which establishes minimum standards for the production and issuance of state-issued driver’s licenses and identification cards and prohibits federal agencies from accepting non-compliant versions of these documents for official purposes, the U.S. Department of Homeland Security (DHS) recently announced an extension of document enrollment rules. According to current regulations, beginning Dec. 1, 2014, federal agencies may not accept state-issued driver’s licenses or identification cards for official purposes from individuals born after Dec. 1, 1964, unless the license or card is REAL ID-compliant and was issued by a compliant state as determined by DHS. In addition, as of Dec. 1, 2017, federal agencies will be prohibited from accepting any non-compliant documents for official purposes from any individual. Pursuant to this extension, both document enrollment dates have been moved to Oct. 1, 2020.

The implementation of the final rule, which goes into effect immediately, follows a multi-year plan to help budget-strapped states conform their document issuance and production processes to the standards set forth in the REAL ID Act. According to the DHS, this extension was granted due to the agency’s recognition that large numbers of residents from REAL ID Act-compliant states would be required to renew their driver’s licenses or identification cards prior to the end of the year or risk being unable to use them for official federal purposes as of Dec. 1, 2014. This would, in turn, impose significant burdens on compliant states due to the costs and operational difficulties of issuing high numbers of documents prior to the current regulatory deadline. In addition, the existence of two enrollment dates may complicate DHS’ enforcement objectives and diminish the agency’s opportunity to reasonably evaluate the impact of various enforcement phases.

The new rule does not impact the prohibition against federal agencies accepting licenses and identification cards issued by non-REAL ID Act-compliant states.

ARTICLE BY

OF

FTC Denies AgeCheq Parental Consent Application But Trumpets General Support for COPPA Common Consent Mechanisms

Covington BUrling Law Firm

The Federal Trade Commission (“FTC”) recently reiterated its support for the use of “common consent” mechanisms that permit multiple operators to use a single system for providing notices and obtaining verifiable consent under the Children’s Online Privacy Protection Act (“COPPA”). COPPA generally requires operators of websites or online services that are directed to children under 13 or that have actual knowledge that they are collecting personal information from children under 13 to provide notice and obtain verifiable parental consent before collecting, using, or disclosing personal information from children under 13.   The FTC’s regulations implementing COPPA (the “COPPA Rule”) do not explicitly address common consent mechanisms, but in the Statement of Basis and Purpose accompanying 2013 revisions to the COPPA Rule, the FTC stated that “nothing forecloses operators from using a common consent mechanism as long as it meets the Rule’s basic notice and consent requirements.”

The FTC’s latest endorsement of common consent mechanisms appeared in a letter explaining why the FTC was denying AgeCheq, Inc.’s application for approval of a common consent method.  The COPPA Rule establishes a voluntary process whereby companies may submit a formal application to have new methods of parental consent considered by the FTC.  The FTC denied AgeCheq’s application because it “incorporates methods already enumerated” in the COPPA Rule: (1) a financial transaction, and (2) a print-and-send form.   The implementation of these approved methods of consent in a common consent mechanism was not enough to merit a separate approval from the FTC .  According to the FTC, the COPPA Rule’s new consent approval process was intended to vet new methods of obtaining verifiable parental consent rather than specificimplementations of approved methods.  While AgeCheq’s application was technically “denied,” the FTC emphasized that AgeCheq and other “[c]ompanies are free to develop common consent mechanisms without applying to the Commission for approval.”  In support of common consent mechanisms, the FTC quoted language from the 2013 Statement of Basis and Purpose and pointed out that at least one COPPA Safe Harbor program already relies on a common consent mechanism.

OF