E-mail:
Jack Balkin: jackbalkin at yahoo.com
Bruce Ackerman bruce.ackerman at yale.edu
Ian Ayres ian.ayres at yale.edu
Corey Brettschneider corey_brettschneider at brown.edu
Mary Dudziak mary.l.dudziak at emory.edu
Joey Fishkin joey.fishkin at gmail.com
Heather Gerken heather.gerken at yale.edu
Abbe Gluck abbe.gluck at yale.edu
Mark Graber mgraber at law.umaryland.edu
Stephen Griffin sgriffin at tulane.edu
Jonathan Hafetz jonathan.hafetz at shu.edu
Jeremy Kessler jkessler at law.columbia.edu
Andrew Koppelman akoppelman at law.northwestern.edu
Marty Lederman msl46 at law.georgetown.edu
Sanford Levinson slevinson at law.utexas.edu
David Luban david.luban at gmail.com
Gerard Magliocca gmaglioc at iupui.edu
Jason Mazzone mazzonej at illinois.edu
Linda McClain lmcclain at bu.edu
John Mikhail mikhail at law.georgetown.edu
Frank Pasquale pasquale.frank at gmail.com
Nate Persily npersily at gmail.com
Michael Stokes Paulsen michaelstokespaulsen at gmail.com
Deborah Pearlstein dpearlst at yu.edu
Rick Pildes rick.pildes at nyu.edu
David Pozen dpozen at law.columbia.edu
Richard Primus raprimus at umich.edu
K. Sabeel Rahmansabeel.rahman at brooklaw.edu
Alice Ristroph alice.ristroph at shu.edu
Neil Siegel siegel at law.duke.edu
David Super david.super at law.georgetown.edu
Brian Tamanaha btamanaha at wulaw.wustl.edu
Nelson Tebbe nelson.tebbe at brooklaw.edu
Mark Tushnet mtushnet at law.harvard.edu
Adam Winkler winkler at ucla.edu
Media coverage of PPACA over the past week or so has been a mess. Fortunately, a few outlets are investing in technical coverage of HealthCare.Gov by people who actually know what they are talking about. Former programmer David Auerbach has a great series of pieces at Slate about the fiasco. I found this insight particularly important:
[On]ly 30% [of users] have been able to complete an actual insurance application. And that’s not even to say that the application is correct, owing to reports of children getting listed as multiple spouses and the like. . . . [W]hy on earth is the website still up? So people can play insurance-application roulette with 7–3 odds against them? Why not take the site down until it works?
Well, remember how there was very little testing done on the system? It seems that not only was very little testing done, but testing frameworks weren’t set up. That means the team fixing healthcare.gov not only has a lot of bugs to fix, but they don’t have infrastructure in place to identify and reproduce the bugs, which are the first step to fixing them. Under a tight deadline, any such infrastructure will be ad hoc and inadequate. So it’s important that healthcare.gov stays open simply so that potential applicants can run into bugs and report them.
One thing I plan to do over the next few weeks is to compare the types of testing of health IT that is required of IT vendors' software (before the providers that buy it can obtain "meaningful use" subsidies for health IT), and the types of testing that CMS did before launching the exchanges. On one level, this is an apples and oranges comparison: software for providing actual care is different than software that is guiding people through a maze of agencies, insurers and data brokers. On the other hand, the testing and certification of health IT involves a multistep process of delegation that has come under some criticism in the past. The larger, common issue is that a federal government that has become so reliant on contractors may be losing its ability to assess the functionality and value of contractors' handiwork. Posted
11:04 AM
by Frank Pasquale [link]