Event Information

Cloud computing services over the Internet have the potential to spur a significant increase in government efficiency and decrease technology costs, as well as to create incentives and online platforms for innovation. Adoption of cloud computing technologies could lead to new, efficient ways of governing.

On April 7, the Brookings Institution hosted a policy forum that examines the economic benefits of cloud computing for local, state, and federal government. Federal Chief Information Officer Vivek Kundra delivered a keynote address on the role of the government in developing and promoting cloud computing. Brookings Vice President Darrell West moderated a panel of experts and detailed the findings in his paper, "Saving Money through Cloud Computing," which analyzes its governmental cost-savings potential.

After the program, panelists took audience questions.

Video

• Cloud Computing a Fiscally Smart Move
• Cloud Computing Saves Money, Makes Government More Open
• Cloud Computing Will Fundamentally Change Government Operations
• Government on Cloud Will Yield Cost-Effective System

Audio

• The Economic Gains of Cloud Computing

Transcript

• Uncorrected Transcript (.pdf)

Event Materials

• 20100407_cloud_computing
• 0407_cloud_computing_kundra_remarks
• 0407_cloud_computing_kundra_presentation

EXECUTIVE SUMMARY

Many web services are examples of cloud computing, from storage and backup sites such as Flickr and Dropbox to online business productivity services such as Google Docs and Salesforce.com. Cloud computing offers a potentially attractive solution to customers keen to acquire computing infrastructure without large up-front investment, particularly in cases where their demand may be variable and unpredictable, as a means of achieving financial savings, productivity improvements and the wider flexibility that accompanies Internet-hosting of data and applications.

The greater flexibility of a cloud computing service as compared with a traditional outsourcing contract may be offset by reduced certainty for the customer in terms of the location of data placed into the cloud and the legal foundations of any contract with the provider. There may be unforeseen costs and risks hidden in the terms and conditions of such services.

This document reports on a detailed survey and analysis of the terms and conditions offered by cloud computing providers.

The survey formed part of the Cloud Legal Project at the Centre for Commercial Law Studies (CCLS), within the School of Law at Queen Mary, University of London, UK. Funded by a donation from Microsoft, but academically independent, the project is examining a wide range of legal and regulatory issues arising from cloud computing. The project's survey of 31 cloud computing contracts from 27 different providers, based on their standard terms of service as offered to customers in the E.U. and U.K., found that many include clauses that could have a significant impact, often negative, on the rights and interests of customers. The ease and convenience with which cloud computing arrangements can be set up may lull customers into overlooking the significant issues that can arise when key data and processes are entrusted to cloud service providers. The main lesson to be drawn from the Cloud Legal Project’s survey is that customers should review the terms and conditions of a cloud service carefully before signing up to it.

The survey found that some contracts, for instance, have clauses disclaiming responsibility for keeping the user’s data secure or intact. Others reserve the right to terminate accounts for apparent lack of use (potentially important if they are used for occasional backup or disaster recovery purposes), for violation of the provider’s Acceptable Use Policy, or indeed for any or no reason at all. Furthermore, whilst some providers promise only to hand over customer data if served with a court order, others state that they will do so on much wider grounds, including it simply being in their own business interests to disclose the data. Cloud providers also often exclude liability for loss of data, or strictly limit the damages that can be claimed against them – damages that might otherwise be substantial if a failure brought down an e-commerce web site.

Although in some U.S. states, in E.U. countries and in various other jurisdictions the validity of such terms may be challenged under consumer protection laws, users of cloud services may face practical obstacles to bringing a claim for data loss or privacy breach against a provider that seems local online but is, in fact, based in another continent. Indeed, service providers usually claim that their contracts are subject to the laws of the place where they have their main place of business. In many cases this is a US state, with a stipulation that any dispute must be heard in the provider’s local courts, regardless of the customer’s location.

Perhaps the most disconcerting discovery of the Cloud Legal Project’s survey was that many providers claimed to be able to amend their contracts unilaterally, simply by posting an updated version on the web. In effect, customers are put on notice to download lengthy and complex contracts, on a regular basis, and to compare them against their own copies of earlier versions to look for changes.

The cloud computing market is still developing rapidly, and potential cloud customers should be aware that there may be a mismatch between their expectations and the reality of cloud providers' service terms, and be alive to the possibility of unexpected changes to the terms.

Downloads

• Download the Full Paper

Cloud computing is becoming omnipresent in the private sector as companies latch on to this innovation as a way to manage scalability, improve flexibility, and reduce cost. Analysts at IDC predict that, over the next six years, nearly 90 percent of new spending on Internet and communications technology will be on cloud-based platforms. Apple, Google, Amazon, Microsoft, and hundreds of smaller companies are positioning themselves to dominate the estimated $5 trillion worldwide market. While few companies will provide numbers, it is estimated that Amazon and Google may run as many as 10 million servers while Microsoft runs close to one million. In short, it is an innovation that makes a mockery out of Moore’s law.

But, like all innovations, cloud computing has potential pitfalls. Public sector organizations in particular have had difficulty taking advantage of new technologies. The Heritage Foundation keeps a list over 50 examples of government ineptitude including $34 billion in fraudulent Homeland Security contracts, National Institutes of Health renting a lab that it neither needs nor can use for $1.3 million per month, and the Department of Agriculture wasting $2.5 billion in stimulus money on broadband internet. Technological ineptitude received special attention with the failed launch of the Healthcare.gov, the release of classified data from Edward Snowden, and the costly FBI virtual case file debacle.

Cloud computing is far more than just a simple technology change and requires a close examination of governance, sourcing, and security. We sought to understand how well state government is prepared to address the challenges of cloud computing.

The Approach

We have gathered and started to do a content analysis of the IT strategic plans for each state. For each plan, we performed a content analysis, which is looking for certain phrases or text within the IT strategic plan in order to have a structured way to understand the data. Details for our approach can be seen in our previous blog post.

How States Are Implementing the Cloud

We were not surprised to see a number of states preparing to study or embark on cloud computing.

While some states don’t mention it (e.g. Alabama), most states are eagerly exploring it. For example, North Dakota’s plan talks about cloud computing as an integral part of the future and seven of its thirteen major IT initiatives are centered on preparation for transitioning to the cloud “where and when it makes sense”.

Vermont puts itself squarely in the studying period. The plan describes that, “While the risks of enterprise-wide and cloud-based IT must be carefully managed, trends continue to just larger-scale operations.” Wisconsin also clearly lays out its view on cloud computing, writing that, “Flexibility and responsiveness (also) guide Wisconsin’s approach toward adoption of cloud services” and suggests that its version of a private cloud “…offers advanced security and service availability tailored for business needs.” West Virginia provides an equally balanced approach by requiring that only services with an acceptably low risk and cost-effective footprint will be moved to the cloud.

In short, all of the states that are considering cloud computing are taking a thoughtful and balanced approach.

The Good

One of the most critical aspects of cloud computing is security and, without question, states understand the importance of good security. A good example of this is Colorado who designates security as one of its four “wildly important goals” and sets the target of “10 percent reduction in information security risk for Colorado agencies by close of FY15”.

South Carolina echoed the same theme by asserting that security and confidentiality are “overriding priorities at every stage of development and deployment.” Connecticut’s plans explain the need to “continuously improve the security and safeguards over agency data and information technology assets”.

The Bad

Despite the interest in cloud computing, we were only able to find a single state (Georgia) that explicitly links governance to security and, to us, by extension to cloud computing. In Georgia’s plan, they start with the idea that “strong security programs start with strong governance” and then explicitly describe necessary changes in governance to improve security.

We were, however, impressed with the seriousness that New York, North Carolina and Massachusetts took governance but it was difficult to find many other states that did.

The Ugly

Unfortunately the results on sourcing were dismal. While a few states (e.g. Kansas, Ohio, and Massachusetts) specifically discuss partnerships, most states seemed to ignore the sourcing aspect of cloud computing. The most ominous note comes from Alabama where they make a statement that innovation in the state is being stifled by a lack of strong personnel.

While we have great enthusiasm for government to address cloud computing, some of the non-technical issues are lagging in the discussion. Good government requires that these items be addressed in order to realize the promise of cloud computing.

Introduction:

There is an Egyptian proverb that says those who worry about demons will tend to run into them. Like much folk wisdom, it has solid psychological foundations; the likelihood of a problem rearing its head often appears to be exacerbated by constantly fretting about it. Ever since Hosni Mubarak stepped down as president of Egypt on February 11, 2011, the demon named “Now What?” has been keeping the Israeli government up at night. On August 18, it finally leapt up at them.

That day, a group of armed men attacked Israeli buses, as well as civilian and military vehicles north of Eilat, near the Egyptian border. Eight Israelis, both civilians and soldiers, were killed. The Israel Defense Forces (IDF) set off in hot pursuit, shooting at the attackers from a helicopter. The helicopter crew either failed to notice, or ignored, that they were shooting over the Egyptian side of the border. In the pursuit, three Egyptians— an officer and two enlisted men—were killed and another three later died of their wounds. Israeli minister of defense Ehud Barak, while blaming Palestinian groups for the assault, made comments to the effect that the attacks were largely Egypt’s fault as there had been a major security collapse in Egypt since the former regime had been ousted six months earlier.

The way matters unfolded over the next few days pointedly illustrated the answer to a question that had been asked repeatedly both by international media and the Israeli government since Hosni Mubarak’s ouster: What did Egypt’s January 25 Revolution mean for Israel? The simplest answer is that it is no longer business as usual. The relationship between Egypt and Israel has changed and both countries will have to navigate new waters carefully and wisely.

Downloads

• Download the Full Memo

INTRODUCTION

A year after President Hosni Mubarak’s fall, U.S.-Egypt relations are at an all-time low. Not, as many expected, because of the rise of Islamist parties, but because America’s longtime allies in the Egyptian military have whipped up anti-American sentiment at a feverish pace. It may have started as a political ploy, a way to build support on the street and highlight the army’s nationalist credentials, but the generals soon lost control. In January, the Egyptian government announced that sixteen Americans—including the son of a top U.S. official— would be put on trial, facing up to five years in prison. Their apparent crime was working for American nongovernmental organizations (NGOs)—the National Democratic Institute, the International Republican Institute, and Freedom House—that offered support, funding, and election monitoring for Egypt’s uneven transition.

On March 1, the Egyptian government lifted the travel ban on seven Americans who were still in Egypt, allowing them to leave the country. A major diplomatic breach was avoided, giving the impression that the crisis had been resolved. This appears to be the interpretation of the Obama administration, which waived congressional conditions on military aid, citing the importance of maintaining a “strategic partnership” with Egypt.2 However, the charges against the Americans remain, and there is no sign that the American NGOs in question will be able to reopen anytime soon. More importantly, the vast majority of affected NGOs—which are Egyptian rather than American—still find themselves on trial and under attack.

The NGO episode, however worrying it is on its own, reflects something larger and more troubling: the slow descent from the national unity of the revolution to a fog of paranoia, distrust, and conspiracy theorizing. Who is with the revolution, and who isn’t? The roots of the problem lie in the uncertainly inherent in Egypt’s muddled transition. Unlike in Tunisia, where the Higher Committee for the Achievement of Revolutionary Objectives (HCARO)—accepted as legitimate by all of the country’s main political forces—was responsible for managing the transition, Egypt has featured various competing actors claiming their own distinct sources of power. The struggle for legitimacy between the Supreme Council of the Armed Forces (SCAF), the Muslim Brotherhood-dominated parliament, and the protest movement has created a fragmented political scene. Everyone wants to lead the transition, but no one wants to take full responsibility for the results.

Downloads

• Download the full paper

Introduction

The issue of Iran has become a central preoccupation for the international community in recent months, thanks to the intersection of the historic changes in the region, an American presidential election, sharpening rhetoric from Israel, and Tehran’s relentless determination to advance its nuclear capabilities. The focus of policymakers in Washington and around the world remains fixed on the options for forestalling Iran’s determined march toward a nuclear weapons capability. This is the appropriate objective; the best possible outcome for maintaining peace and security in the Gulf and avoiding a deeply destabilizing nuclear arms race remains a credible, durable solution that curtails Iran’s nuclear ambitions. And while achieving such an outcome remains profoundly problematic, largely as a result of Tehran’s intransigence, preventing Iran from crossing the nuclear weapons threshold—either through persuasion, coercion, or some combination of the two—remains fully and unambiguously within the capabilities of the international community.

The shadow cast by Tehran has created a particularly intense sense of existential anxiety for the smaller Gulf states, including Kuwait, Bahrain, the United Arab Emirates, Qatar, and Oman. After all, these are the same states whose civil orders were repeatedly disrupted by Iranian subversion and sponsorship of terrorism during the first decade after Iran’s Islamic revolution, and whose thriving economies rely on unimpeded access to the global commons. The events of the past decade have only exacerbated the smaller Gulf states’ endemic sense of insecurity. Iran has achieved a synergistic, sometimes even parasitic, relationship with the leadership of post-Saddam Iraq that, together with Tehran’s longstanding relationships with Syria and Lebanese Hizballah, greatly enables its bid for predominance in the heart of the Middle East. Today, the uncertainties surrounding the implications of regional flux have left Tehran simultaneously weakened and emboldened—a particularly dangerous combination for this particular array of Iranian leaders.

With Iran’s nuclear program advancing by the month and its efforts to tilt the regional balance in its favor growing more forceful, the small states of the Persian Gulf must face the distinct dilemma of preparing for the possible worst-case scenario of the nuclearization of their neighborhood, while participating ever more robustly in the international efforts to preclude that very possibility. In some respects, the Gulf states’ situation is unique. Unlike Israel, another small state that perceives an existential threat from Iran, the Gulf states cannot fall back upon either a presumptive nuclear deterrent or a primordial bond to the body politic of the world’s only remaining superpower. And in contrast to Iran’s other neighbors, the vast resources and history of ideological and territorial disputes between the Gulf states and Tehran significantly intensify the stakes. Even before the Gulf became the vital transportation corridor for global energy, the fault line in the regional balance of power had always run between the northern states and their southern rivals. The mere possibility that the north may gain a nuclear advantage is reshaping the security environment for Iran’s neighbors in the Gulf.

Because the threat of Iran looms large, the exigency of considering the widest possible array of alternative prospects for the evolution of this protracted crisis is important. This paper tackles the scenarios that successive American presidents have deemed unacceptable—an Iranian development or acquisition of a nuclear weapons capability or of nuclear weapons themselves—and the implications that such scenarios would have for the global nonproliferation regime and regional security, with a particular focus on the special challenges faced by Iran’s southern neighbors. To protect against threats along their borders, the Gulf states have traditionally hedged their bets by seeking balanced relations with their more powerful neighbors while cultivating extra-regional allies. That formula is already changing, as evidenced by a new assertiveness in Gulf states’ postures toward Tehran and a new creativity in deploying strategies for deterring and mitigating Iran’s efforts to extend its influence and/or destabilize its neighbors. The Gulf states must transform this tactical innovation into a full-fledged new hedging policy: one that deploys every possible tool to prevent a nuclear Iran while taking every possible step to prepare for such an eventuality.

Download » (PDF)

Downloads

• Thinking the Unthinkable: The Gulf States and a Nuclear Iran

For decades, we have been hearing that the baby-boom generation was like a pig moving through a python–bigger than the generations before and after.

That’s true. But that’s also a very misleading metaphor for understanding the demographic forces that are driving up federal spending: They aren’t temporary. The generation born between 1946 and 1964 is the beginning of a demographic transition that will persist for decades after the baby boomers die, the consequence of lengthening lifespans and declining fertility. Putting the federal budget on a sustainable course requires long-lasting fixes, not short-lived tweaks.  

First, a few demographic facts.

As the chart below illustrates, there was a surge in births in the U.S. at the end of World War II, a subsequent decline, and then an uptick as baby boomers began having children.

Although the population has been rising, the number of births in the U.S. the past few years has been below the peak baby-boom levels, possibly because many couples chose not to have children during bad economic times. More significant, fertility rates–roughly the number of babies born per woman during her lifetime–have fallen well below pre-baby-boom levels.

Meanwhile, Americans are living longer. In 1950, a man who made it to age 65 could expect to live until 78 and a woman until 81. Social Security’s actuaries project that a man who lived to age 65 in 2010 will reach 84 and a woman age 86.

Put all this together, and it’s clear that a growing fraction of the U.S. population will be 65 or older.   

The combination of longer life spans and lower fertility rates means the ratio of elderly (over 65) to working-age population (ages 20 to 64) is rising. As the chart below illustrates, the ratio will rise steadily as more baby boomers reach retirement age–and then it levels off.  

Simply put, this doesn’t look like a pig in a python.  

So what do these demographic facts portend for the federal budget?  In simple dollars and cents, the federal government spends more on the old than the young. More older Americans means more federal spending on Social Security and Medicare, the health insurance program for the elderly. On top of that, health care spending per person is likely to continue to grow faster than the overall economy.

The net result: 85 percent of the increase in federal spending that the Congressional Budget Office projects for the next 10 years, based on current policies, will go toward Social Security, Medicare and other major federal health programs, and interest on the national debt.

Restraining future deficits and the size of the federal debt mean restraining spending on these programs or raising taxes–and probably both. One-time savings or minor tweaks won’t suffice. Nor will limiting the belt-tightening to annually appropriated spending.

The fundamental fiscal problem is not coping with the retirement of the baby boomers and then going back to budgets that resemble those of the past. The fundamental fiscal problem is that retirement of the baby boomers marks a major demographic transition for the nation, one that will require long-lived changes to benefit programs and taxes.

Fee-for-service payments encourage high-volume services rather than high-quality care. Alternative payment models (APMs) aim to realign financing to support high-value services.

The 2 main components of gastroenterologic care, procedures and chronic care management, call for a range of APMs. The first step for gastroenterologists is to identify the most important conditions and opportunities to improve care and reduce waste that do not require financial support.

We describe examples of delivery reforms and emerging APMs to accomplish these care improvements. A bundled payment for an episode of care, in which a provider is given a lump sum payment to cover the cost of services provided during the defined episode, can support better care for a discrete procedure such as a colonoscopy. Improved management of chronic conditions can be supported through a per-member, per-month (PMPM) payment to offer extended services and care coordination.

For complex chronic conditions such as inflammatory bowel disease, in which the gastroenterologist is the principal care coordinator, the PMPM payment could be given to a gastroenterology medical home. For conditions in which the gastroenterologist acts primarily as a consultant for primary care, such as noncomplex gastroesophageal reflux or hepatitis C, a PMPM payment can support effective care coordination in a medical neighborhood delivery model. Each APM can be supplemented with a shared savings component.

Gastroenterologists must engage with and be early leaders of these redesign discussions to be prepared for a time when APMs may be more prevalent and no longer voluntary.

Download "Shifting Away From Fee-For-Service: Alternative Approaches to Payment in Gastroenterology" »

Downloads

• Download "Shifting Away From Fee-For-Service: Alternative Approaches to Payment in Gastroenterology"

Editor’s Note: This analysis is part of The Leonard D. Schaeffer Initiative for Innovation in Health Policy, which is a partnership between the Center for Health Policy at Brookings and the USC Schaeffer Center for Health Policy and Economics. The Initiative aims to inform the national health care debate with rigorous, evidence-based analysis leading to practical recommendations using the collaborative strengths of USC and Brookings.

The passage of the Medicare Access and CHIP Reauthorization Act (MACRA) just over a year ago signaled a strong and unique bipartisan agreement to move towards value-based care, but until recently, many of the details surrounding how it would be implemented remained unknown. But last week, the Centers for Medicare and Medicaid Studies (CMS) released roughly 1,000 pages that shed more light on how physician payment will hopefully dramatically change for the better.

Some Historical Context

Prior to MACRA, how doctors were paid for providing care to Medicare patients was subject to a reimbursement formula known as the Sustainable Growth Rate (SGR). Established in 1997 to control the rate of increase in spending on physician services, the SGR pegged total spending among all Medicare-participating physicians to an overall budget target. Yet in this “tragedy of the commons,” no one physician benefitted from her good stewardship of health care resources. Total physician spending often exceeded the overall budget target, triggering reimbursement rate cuts. However, lawmakers chose to push them off into the future through what were called “doc fixes,” deferring the rate cuts temporarily. The pending cut rose to over 21 percent before MACRA’s passage as a result of compounding doc fixes.

Moving Forward with MACRA

When it was signed into law on April 16, 2015, MACRA ended the SGR, its cuts, and many previous payment incentive programs. In their place, MACRA established two overarching payment incentive schemes for providers to choose from:

1. the Merit-Based Incentive Payment System (MIPS) program, which supplants three previous payment incentives and makes positive or negative adjustments to a physician’s payment based on her performance; or


2. the Alternative Payment Model (APM) program, which awards a 5 percent bonus through 2024—with higher annual payment updates thereafter—for having a minimum percentage of Medicare and/or all-payer revenue through eligible APMs. Base physician fee rates for all Medicare providers would be updated 0.5 percent for each of the first four years, followed by no increases until 2026, when base fees would increase at different rates depending on the payment incentive program in which a physician participates.

MIPS addresses providers’ longstanding complaints that reporting that reporting under the existing programs—the Physician Quality Reporting System, the Value-Based Modifier, and Meaningful Use — is duplicative and cumbersome. Under the new MIPS program, physicians report to the government payer directly (CMS) and receive a bonus or penalty based on performance on measures of quality, resource use, meaningful use of electronic health records, and clinical practice improvement activities. The bonus or penalty physicians may see starts at 4 percent of the fee schedule in 2019 (based on their performance two years prior—in this case 2017) and increases successively to 5 percent in 2020, 7 percent in 2021, and 9 percent from 2022 onward. From 2026 onward, MIPS providers would receive an annual increase of 0.25 percent on their base fee schedules rates.

In contrast, the APM incentive program awards qualifying physicians a fixed, annual bonus of 5 percent of their reimbursement from 2019- – 2024, and provides that their fee schedule rates grow 0.5 percentage points faster than those of MIPS in 2026 and beyond, in recognition of the risk they assume in these contracts.

Yet, according to MACRA, not all APMs are created equal. APMs eligible for this track must use quality measures similar to those of MIPS, ensure electronic health records are used, and either be an approved patient-centered medical home (PCMH) or require that the participating entity “bears more than nominal financial risk” for excessive costs. Then, in order to receive the APM track bonus, physicians must have a minimum of 25 percent of their revenue from Medicare come through eligible APMs in 2019, with the minimum increasing through 2023 up to 75 percent. In 2021, a new all-payer Advanced APM option becomes available, allowing providers in APM contracts with other payers to participate in the Advanced APM incentive. To do so, they must meet the same minimum thresholds—50 percent in 2021, 75 percent in 2023—but through all provider contracts, not solely Medicare revenue, while still meeting a significantly lower Medicare-specific threshold. By creating an all-payer option, CMS hopes to enable greater provider participation by allowing all payer revenue to count toward the same minimum threshold. Under the all-payer model in 2021, for example, providers must have no less than 25 percent of Medicare revenue through Advanced APMs and 50 percent of all revenue through Advanced APMs.

MACRA Implementation Details Revealed

The newly released proposed rule provides answers to significant questions that had been left unanswered in the law surrounding the specifics of implementation of MIPS and the APM incentives. At long last, providers are gleaning insight into how CMS intends to implement MIPS and the APM track. Given the fast-approaching MIPS performance period in January 2017, here are three key highlights providers need to know:

1. Qualifying for the APM incentive track—and getting out of MIPS—will be difficult. In order to qualify for the bonus-awarding Advanced APM designation, APMs must meet the “nominal financial risk” criteria, which will be measured in three ways: an APM’s marginal rate sharing for losses, minimum loss ratio (the threshold above which providers would begin sharing in losses), and total potential risk as a percent of expected costs. Clinicians must further have a minimum share of revenue that comes in through the designated APMs.


2. Providers will have fewer opportunities to see and improve their performance on MIPS. Despite calls from provider groups for more frequent reporting and feedback periods, MIPS reporting periods will be annual, not quarterly. This is true for performance feedback from CMS, as well, though they may explore more frequent feedback cycles in the future. Quarterly reporting and feedback periods could have made the incentive programs more “actionable” for providers, alerting them to their performance closer to the time the services were rendered and providing more opportunities to improve performance.


3. MIPS allows greater flexibility than previous programs. Put simply, MIPS is the performance incentive program clinicians will participate in if not on the Advanced APM track. While compelling participation, the proposed MIPS implementation also responds to stakeholder concerns that earlier performance incentive programs were onerous and sometimes irrelevant—MIPS reduces the number of measures required in some categories and allows physicians to select from a set of measures to report on based on relevancy to their practice.

With last week’s release of the proposed rule, the Leonard D. Schaeffer Initiative for Innovation in Health Policy is kicking off a series of work products that will focus dually on further MACRA implementation issues and on translating complex policy into providers’ experience. In the blogs and publications to follow, we will dive into greater detail and discussion of the pieces of MACRA implementation highlighted here, as well as many other emerging physician payment reform issues, as the law’s implementation unfolds.