Sep 23

Designing a Data Entry System Properly; Overhauling the Healthcare.gov Web Site

Healthcare.govSince my original impression that the debut of the Healthcare.gov web site was a technological disaster, I’ve contended that the website could be created for much cheaper, and be much easier to use than the mess that was delivered.

New York TimesThere finally seems to be progress in this direction according to today’s New York Times article, HealthCare.gov Is Given an Overhaul. I was quoted by Robert Pear:

“Instead of being user-friendly, the original website was user-hostile”

Basics of Data Entry Systems

We at FMS have created countless database systems where data entry played an important role. Unlike fancy graphics filled systems that look nice, data entry systems must be designed with a focus on ease-of-use by the end-user to enter, review, and update their information. If there are many questions and complex relationships, users need to be able to see as much of that on one screen as possible. If multiple screens are required, being able to move back and forth between screens without losing data and having changes in one screen reflected on others is critical for an efficient and intuitive user experience.

Data Entry Systems Should Target Users with Large Screens

For complex tasks such as writing a paper or working on a large spreadsheet, computers remain the preferred platform for getting work done where people can have one or multiple large screens. Serious data entry applications should target that user.

Mobile Apps Have a Role, but Not for Serious Data Entry

While mobile applications have a place, it’s not appropriate for complicated data entry since one question per screen is very inefficient. Not being able to see previous entries and pressing Next and Back for each question drives users crazy. The original designers of the Healthcare.gov web site designed it as if it were a simple, consumer mobile app meant to be filled out with a few finger clicks. They were either paid by the screen or just clueless about what a business data entry system requires.

Initial Request for Information Should be Anonymous

The purpose of the public facing Healthcare.gov website should be focused on helping prospects with the buying process. People need to quickly browse the health insurance options that are available to them in their state and cost estimates. The initial data entry should be the minimal anonymous information necessary to produce those results such as gender, age, zip code, family size, etc. Nothing personal such as names, social security numbers, email address, etc.

Automating a Paper Form

National ArvhivesOnly after customers have made a decision to buy should they be required (and expect) to provide more detailed information. This application feature is the core of the public facing Healthcare.gov website and is simply the automation of a 12 page paper form. It shouldn’t be that difficult.

We at FMS have automated paper forms for decades. Recently, we did this for a series of paper documents at the National Archives. The cost of doing this was in the tens of thousands of dollars, not the hundred of millions that Healthcare.gov cost.

Separating Data Entry from Complex Validation

A high volume, data entry system like Healthcare.gov should be designed to collect the user’s information as quickly as possible without trying to validate everything with other government systems in real-time. The cross-validation of information against IRS, HHS, Homeland Security, and other databases should happen in a background process that can withstand slowdowns or down times of dependent systems. This separates the complexity and risk of linking multiple systems together, manages the load on the other systems, and lets the user get done quicker. If a problem is detected later, an email can be sent to the user to fix the mistake or invalidate their application. Regardless, none of that needs to happen while the user is entering their data. After all, it’s not as if they were going to get insurance immediately upon pressing Submit.

Taxpayer Abuse

It remains shocking to me that it cost taxpayers hundreds of millions of dollars initially for the broken Healthcare.gov site, and hundreds of millions dollars afterwards to the same contractors to fix it. The procurement process and incentives are completely inverted for creating and delivering quality software. It’s outright theft, but no one seems to be held responsible for it, and lots of people profiting mightily from it.

Conclusion: Data Entry Systems Aren’t Difficult If You Know What You’re Doing

Logistics Support SystemI’ve contended that we at FMS could have created the public facing Healthcare.gov site for $1 million. Some people scoff at that, but in our world and that of our customers, $1 million still goes a long ways. We created an international humanitarian relief logistics system for the United Nations for half that amount, and it supports full language localization as it’s deployed in 80+ countries. Healthcare.gov didn’t even support Spanish when it debuted, and that was one of its original requirements.

Creating a good data entry system is not rocket science. This is not something that needs to be done in Silicon Valley. What’s needed is a team who’ve done it before and know what they’re doing. Creating this type of solution requires a solid database foundation, understanding the user needs, creating an intuitive user experience, and building it so that it’s maintainable over time. It’s not something that can be created by people on their first paid programming job, but it’s not a rare skill. I’m proud that my development team at FMS have been with me for decades and continue to deliver systems that just work.

Aug 26

Free Update for Total Access Analyzer 2010 and 2007

Total Access AnalyzerTotal Access Analyzer is the most popular Microsoft Access add-in of all time. Analyzing all the objects and code in your database, Total Access Analyzer generates detailed documentation and detects 300+ ways to fix, improve, and speed up your Access applications.

We have released free updates of Total Access Analyzer 2007 and 2010 to existing customers:

The updates include the following fixes and enhancements:

  • Module Cross-Reference incorrectly listing procedures that didn’t exist when they existed
  • Improved SQL query parsing to better cross-reference table and field names passed as function parameters
  • For secure databases, document queries even when logged in without admin rights
  • Support documenting library references of long DLL file names and paths
  • Setup issues resolved for certain machines and motherboards
  • For Microsoft Access 2010’s 64-bit version, support for Windows 8

Existing customers were already notified with download instructions.

Aug 11

Speaking at the New York City Microsoft Access User Group on September 8

On Monday September 8, 2014, at 6:30 PM, I’m the featured guest speaker for the Microsoft Access User Group in New York City.

Microsoft Corporation Headquarters
11 Times Square
8th Avenue and 41st Street (NE Corner)

Hosted at Microsoft’s offices, I’ll showcase some of our Microsoft Access products. I’ll also answer any questions about my experiences with technology, media, and business.

Join me at this free event. More details to follow. Link to other Upcoming Events.

Aug 01

Total Access Statistics Ships for Microsoft Access 2013

Total Access StatisticsTotal Access Statistics is the most advanced data analysis program for Microsoft Access. It extends the power of Microsoft Access queries with a wide range of statistical calculations including percentiles, frequency distributions, correlations, regressions, rankings, running totals, financial cash flow analysis, data normalization, crosstabs with Chi-Square, t-Tests, ANOVA, non-parametrics, probabilities, and more.

Total Access Statistics is now available for Microsoft Access 2013. Total Access Statistics 2013 includes many enhancements since the prior release of Total Access Statistics 2010:

  • Support for the 32 and 64 bit versions of Access 2013 with separate add-ins for each
  • New redistributable runtime libraries to support Access 2013, 2010, 2007, and 2003
  • Support for Windows 8 (and all Windows versions supported by Access)
  • Improved performance when analyzing large data sets
  • For Percentiles, when assigning percentile values to a field in your table, you can specify calculations such as quartiles, quintiles, octiles, deciles, etc. rather than just percentile
  • Field format is set to Percent for percentage fields in the Frequency, Crosstab (when percentages are in columns), and Chi-Square details tables
  • When tables are generated from the add-in, the field column widths are resized to show the entire field name and data
  • Updated user manual and help file

Here’s a complete list of new features. For more information visit these resources:

Jul 10

Microsoft Access Class Not Registered Run-time Error -2147221164 (80040154) Class Not Registered

This error occurs in a Microsoft Access database that seems to work fine on every other machine but one. The MS Access database actually loads and runs, so the code is compiled and functional. Then it dies on some very common code such as CurrentProject.Connection for ADO to open a table or query recordset:

Microsoft Access "Class Not Registered" Run-time Error -2147221164 (80040154)

Confusion

The “Class Not Registered” is very confusing. It implies code that won’t compile or broken library references but that’s not the true cause. Is the Access database corrupt? No.

We’ve received reports for this error for years and were never able to reproduce it. We finally did and figured out why it occurs and how to fix it. Read our new paper Microsoft Access “Class Not Registered” Run-time Error ‘-2147221164 (80040154) to learn more.

Apr 14

Microsoft Access Videos from the SharePoint Conference

Microsoft Access ProductsMicrosoft SharePointThe Microsoft Access team has released videos of their presentations at the SharePoint Conference from Las Vegas, NV.

With Access 2013, Access web solutions are hosted in SharePoint and rather than using SharePoint lists as they did in Access 2010, they use a real SQL Server database hosted in SQL Azure. The database can also be linked from desktop copies of Access to create hybrid solutions that serve both the web and Windows.

The Microsoft Access program managers presented these four sessions:

Enjoy!

Other Videos from FMS

Mar 22

Total Visual Agent Ships for Microsoft Access 2013 and 2010

Microsoft Access Database SchedulerTotal Visual Agent for Microsoft Access DatabasesAutomate Microsoft Access Database Compact and Other Chores

We are very pleased to announce that Total Visual Agent 2013 is now shipping.

Don’t Forget System Administration for Microsoft Access Database Solutions

A professional Microsoft Access database application needs ongoing system administration. It’s an area that many MS Access developers neglect and causes problems when things go wrong (database corruption, missing backups, disaster recovery, etc.):

Enterprise Quality System Administration with Audit Logs and Email Alerts

Total Visual Agent has provided an Enterprise Quality solution for almost 20 years by giving organizations a reliable way to perform their critical tasks on a 24/7, 365 days a year basis. A detailed audit log documents each action that is performed, and sends emails if errors are encountered.

Schedule Events, Databases, and Actions to Perform

Total Visual Agent automates and schedules Microsoft Access tasks. It ensures repetitive tasks are completed reliably. Tasks such as database compact and repair, zipped backups, rolling backups (e.g. 7 copies for each day of the week), running macros, running Windows command lines, making copies of table data, collecting database statistics such as size and record counts, etc. Easily schedule tasks for the middle of the night and know they’ll be completed.

Events can be scheduled every X minutes, hourly, daily, weekly, monthly or just one time. You can specify the days of week and time periods that it runs to limit processing to off-hours. Select the databases and directories (including subdirectories) to manage with support for workgroup security and database passwords.

Includes a Windows Service for Secure Processing and Reliability

Once defined, the events and tasks can be run by our Monitor program that is a standard Windows program.

Alternatively, Total Visual Agent includes a Windows Service, so you can run your tasks without having anyone logged on the machine. The Windows service is a more secure, robust solution since it can automatically restart if the machine reboots.

New Features in the 2013 Version

A huge number of new features were added in this 2013 release from the previous 2007 version:

  • Microsoft Access 2013Support for Microsoft Access 2013 and 2010, plus 2007
  • Support for 64 bit Operating Systems
  • Simplified Startup and Easier Management of Multiple Microsoft Access Versions
  • Import Settings from Multiple Versions of Total Visual Agent
  • Test All Actions for an Event, Database, Directory or Task Group
  • Create Events that Run Every X Minutes
  • Create Events that are Limited to Periods Spanning Midnight
  • Process Directories with Managed Databases
  • Data Extract Tables are Keyed
  • Run Macros for Database Password Protected Databases
  • Pause for a Fractional Minute
  • Compressed Archive File Names Support Multiple Extensions
  • More Detailed Activity History Log with Deletions
  • More Detailed Database Statistics with Deletions
  • Add Your Comments to Events, Directories, and Actions
  • Simplified Addition of New Actions
  • More Modern and Improved User Interface
  • New User Manual and Help File

For complete list, visit New Features in Total Visual Agent 2013.

Download a Free Trial Version

A fully functional trial version is available for download so you can run it on your system with your databases.

Contact Us

  • Visit our Support Site if you would like to submit any questions to our technical support team.
  • Place an order online. Existing customers can upgrade at a discounted price.
Dec 15

Who Thinks the Relaunched Healthcare.gov Performance Metrics are Acceptable?

Healthcare.gov

HealthcareTechnical Evaluation of the Relaunched Healthcare.gov Web Site

On December 1, a updated version of Healthcare.gov was deployed which offers considerable improvements over the original October 1 launch. The administration and contractors issued some press releases and the general public and press just accepted it without really understanding the technical issues. Here’s my technical assessment of the published statements.


My Assessment of Healthcare.gov, Version 1, on October 1

As I described in my original blog post about Healthcare.gov, the site on October 1 was a technical disaster. I received a lot of criticism with my original assessment from those who thought I had a political agenda against ACA or people who simply wished the site was functional independent of the facts.

My assessment on October 1 was eventually vindicated. It took a few weeks for the media, general public, and administration to recognize that the issues were far more problematic than the politically attractive excuse of having too many users.

Will the Contractors Ever be Held Accountable?

The contractors who built the system didn’t seem to know what they were doing and didn’t prioritize the need to build a functional system. I wrote a blog post summarizing how these large IT government contractors often abuse taxpayers: Too Big to Fire: How Government Contractors on Healthcare.gov Maximize Profits

Unfortunately, the contractors who delivered the flawed system on October 1 were rewarded with additional contracts and funds to fix the mess they created. Our federal government procurement process actually gives them more money from their failure than if they did a good job. It’s no wonder that large IT government contractors continue to deliver technically mediocre results. As long as they make sure their lawyers are more powerful than the government lawyers, they can deflect ALL blame so they can continue to use their “unblemished” past performance to go after new contracts. We will see if any of the contractors here are held accountable for this fiasco when they seek future business. This contractor behavior extends across all branches of government.

It would be amazing to interview the developers who actually worked on the original project, discover what their prior experience was, what they were being paid, and how much the taxpayers were billed for their “expertise”. The contractors are enforcing confidentiality rules to prevent those people from talking to the press in the “interest” of protecting taxpayers. I thnk it’s pretty clear which interests they’re trying to protect.


Enhancements in Version 2

When the administration recognized the technical disaster, they brought in Jeff Zients to lead the disaster relief team. It’s a small world. Mr. Zients and I actually worked at the same firm (SPA/Mercer) before I started FMS, though I left a few years before he joined. Through his leadership, he added some experienced people and reorganized the team while using the same contractors. They issued a Progress and Performance Report which summarized their work:

  • System Stability: Uptime consistently above 90%
  • Reduced Error Rates: per page system time outs or failures from 6+% to 0.75%
  • System Capacity: 50,000 simultaneous users, 20-30 minutes per user for 800K per day
  • Software Fixes: 400+ Bugs Eliminated
  • Hardware Upgrades
  • Real-time Monitoring: Dedicated team focused on site monitoring and instant incident response
  • Improved Response Times: from 8 seconds to under 1 second
  • There was also Improved Window Shopping for users.

To a layman, these results seem adequate. To anyone familiar with commercial software development, they are far below what we or any of our clients would consider acceptable. This is not what professional software developers should deliver, nor what taxpayers should accept.

Review of Relaunch Accomplishments

I’m quite surprised others haven’t provided a technical review of the December 1 relaunch:

System Metrics: 90% up time (One Nine Availability is Awful)
Why do people think 90% availability is acceptable? Even their data showing 95% is awful for a web site. That’s not equivalent to an A in class.

90% up time means it’s down 10% or 2.4 hours per day. 95% is still down an hour. Most web sites have hosting uptime based on the number of 9’s. For instance, 3 nines means 99.9% up time. There are 8760 hours per year (365 days x 24 hours per day). A 99.9% availability means it’s down 8 hours a year. 99.99% availability is less than one hour down per year. High volume commercial web sites strive for 5 nines or less than 10 minutes of down time per year.

I have never heard of any web site or client expecting or satisfied with one 9 availability.

Error Rates Below 1% is Still Pretty Bad
99% sounds good for a class exam, but it’s not good for software. How can a production web site have a 0.75% error rate? The rate seems to be based on the number of pages which is far worse than users. If it’s based on users, with the 50,000 capacity, that’s 375 errors. But when it’s based on pages, assuming each user goes through 50 pages, 18,750 of their 2.5 million pages fail. That means 37.5% of users crash (18,750 divided by 50,000).

Of more concern is the cause of the errors. Software either works or it doesn’t. It doesn’t randomly fail. Is the platform failing 0.75% of the time without knowing why? That would be disturbing and could indicate lots of different bugs. If the contractors don’t know what’s causing the crashes in their buggy code, that raises very serious security implications.

Or do they know if people perform certain tasks that the system will always crash, and they expect people to do that only 0.75% of the time? Still not good, but better.

Beyond crashing bugs, the site may run without crashing but fail to perform properly such as the problems submitting accurate data to the insurance companies. Those non-crashing failures aren’t even part of this error rate which is already too high for a production system.

Capacity of only 50,000?
This is a very strange metric. One usually measures website traffic based on number of page views or transactions. The number of users can be supported by adding more bandwidth and instances of the application on more servers. The capacity issues comes from what people are doing. If they are browsing static pages (not entering data), the number of simultaneous users should be much larger. Even if they are entering data, the capacity to save the data should be much higher than 50,000.

It’s not clear what is causing the 50,000 bottleneck. It shouldn’t be the front-end web application. That should be designed to efficiently save user inputs. The users aren’t entering a lot of information in the grand scheme of data entry systems.

A well designed application would separate the real-time user experience from the more capacity constrained data lookup requirements that may have bottlenecks caused by slow legacy systems at the IRS, HHS, INS, etc. This simply means that the user would enter their information quickly, the system would process it offline, and an email would notify them when the verifications were complete.

Capacity Limitations are Odd
The Healthcare.gov web site begs the use of a commercial cloud provider that can automatically support the fluctuating volumes of users. A web site needs to accommodate the largest number of users, not the average. The large volume spike is ahead of us on the deadline date December 23rd. Volumes would drop considerably after that. By using a commercial cloud provider like Microsoft Azure or Amazon EC2, there would be no need to buy hardware to accommodate huge spikes in users or unnecessary after peak times.

We suspect it’s more profitable for the contractors to buy the extra hardware and configure it poorly than to use commercial cloud providers who would provide a better service for lower costs and profits. The contractors may have also implemented features that for “security reasons”, prevent the use of a commercial cloud provider. It could have justified the creation of their own private system even though it probably decreased security given the crashes they’ve experienced.

Software Fixes and Test Plan
Fixing over 400 bugs is obviously a very good thing, but is that enough? How did so many bugs slip through a Test Plan? And what critical bugs remain that they decided not to fix?

  • What was the test plan before October 1?
  • Were the tests conducted and what bugs were known before October 1?
  • How did they decide to release Healthcare.gov with those bugs?
  • How many bugs were found after October 1 and how were they identified?
  • Is the current Test Plan adequate?
  • What bugs were allowed in the relaunched version?
  • How are known and new bugs being handled?

Software development never reaches perfection but a good test plan covers the expected extremes to ensure the features work, unexpected errors are gracefully trapped, the system is scalable to support the expected number of users, and the site is secure.

In our experience, buggy software inevitably creates and reveals more bugs as bugs are addressed. Known problems with transmitting data to the insurance companies were already acknowledged. This implies this final step of the process was poorly tested, probably because all the preceding steps were failing. This would indicate many unknown issues that still need to be found and fixed.

If the original developers didn’t know what they were doing, trying to fix their work could be a waste of time. An experienced development team may be able to create a better solution in less time than fixing shoddy design and code from unqualified personnel.

Hardware: Do they Have Development, Testing and Staging Platforms?
The only reason I can see for such low availability is the lack of proper development, testing and staging environments. When we create web sites, our software developers need their own hardware to create and test their work without disrupting the production system. Testers need a separate platform to do their work and report back to the developers about the problems they encounter. And a staging site is necessary to review what’s about to be deployed. When the decision is made to release the new version, a switch can be made to make the staging site the new production one. In a modern host, the switch can be done almost instantaneously. Maybe it’s down for a short period to verify the new site is working, but it’s not down for extensive testing because the testing and staging environments already handle that.

Based on the information before the October 1 debut, it was clear that the standard software environment of development, testing, staging and production did not exist. How the managers of the project could have neglected this fundamental part of software development is beyond me, especially for the amount of money spent to build this site.

Without the proper platforms, it indicates the people didn’t even consider how they’d enhance and maintain the system over time, and further supports my contention that the people who created and managed this website had never been paid to build commercial database web sites before.

It really is software malpractice to not have the proper development, testing, staging and production platforms in place. The contractors should be liable for such neglect and reimburse the taxpayers.

Why Wasn’t the Site Redesigned for Simplicity, Performance, Scalability and Security?
There were many opportunities to redesign the site to make it more consumer friendly, reduce the amount of development and testing resources, support more users, and improve security. I list these missed opportunities based on what I have seen:

  • The account creation page should be one screen not three. We create multiple pages if entries in one screen impact the following screens. For the Healthcare.gov site, that’s not the case. For instance, if on the first page, you enter an email address that already exists in the system, you’re not told it’s invalid until you finish the third page and are forced to restart. That just adds load on the system. There’s also no need to create a different user name. Why not just use the email address? Most web sites have a one page account creation page, but we understand how having more pages is more profitable to the contractor.
  • The See Plans feature is a huge improvement for shopping. However, when someone finds and wants to buy a plan without a subsidy, there isn’t a way to do so without creating an account in the system. The site should simply direct the customer to the insurance company since the government is not involved with providing a subsidy. In addition to improving the customer experience, that would reduce the load on the Healthcare.gov web site so they can serve more customers. Get them off the site as quickly as possible!
  • There’s no need to ask for information that isn’t directly tied to calculating the subsidy. The “nice to have” questions on race can be discarded to improve response time, reduce the time it takes users to fill out the application form, and increase the number of users the site can support. It also increases capacity.

Conclusions

Over the years, we’ve helped lots of organizations design their software solutions, select technologies, specify architectures, and deliver solutions that are reliable, scalable, secure and maintainable. So much of the Healthcare.gov site seems to remain quite fragile.

I don’t mean to slam the many people worked hard to salvage the awful work of the initial developers. I’m sure they didn’t get to spend much time with their families over Thanksgiving. The relaunched site is definitely much better than the original version. But it only looks good when compared to that technical disaster. Can anyone claim the new metrics are acceptable for an enterprise quality, nationwide public site as important as this?

For more information, read my earlier blog post Too Big to Fire: How Government Contractors on Healthcare.gov Maximize Profits, and a newer post Designing a Data Entry System Properly; Overhauling the Healthcare.gov Web Site.

Dec 07

Too Big to Fire: How Government Contractors on Healthcare.gov Maximize Profits

Healthcare.govHow Could the Federal Government Spend So Much and Get So Little?

The government contractors in the Healthcare.gov project continue to make fortunes after delivering a technical disaster. Unfortunately, this is common among IT projects delivered by large government contractors. Each year the government spends billions for poorly designed or non-functional systems that never even get deployed.

When I wrote my original blog post about Healthcare.gov, I thought the web site was created by incompetent people. Now I believe that in addition to being incompetent or inexperienced, decisions were made to maximize contractor profits.

This is philosophically different from the way we think at FMS. We always want to deliver functional systems on-budget and on-time. We take pride in creating solutions that don’t require additional work to fix them. As a small firm, we’re held accountable for our deliverables. If we fail, we would never be invited back. For large government IT contractors, it’s a totally different world.

Blame Others

Over the years, many large IT government contractors have abused taxpayers so often that they forgot the public would actually use Healthcare.gov and judge their performance. Even now, with their legions of lawyers and media spin, they are deflecting the story to blame government officials, other contractors, etc. without taking any responsibility. I agree there were problems with other parties, but that’s in addition to their own behavior.

Charge Extra for What Should be Included

Government contractors are experts at adding change orders and generating more revenues for features that should be already included. For instance, we are now hearing about problems with data security for the Healthcare.gov site. Security should be implemented from the beginning. Anyone with any experience collecting personal information such as social security numbers and birthdays knows that. However, the government contractors who won these contracts based on “past performance” suddenly suggest others are to blame for not specifying it earlier. That’s like buying a car and discovering brakes were an add-on. No, it should be included without asking for it. Storing data requires doing it securely.

Too Big to Fire

Given the awful work delivered on October 1, there’s no chance that the same team can be trusted to deliver a functional system. They already showed the world what they considered shipping quality, yet they remain. Unfortunately, our existing procurement system keeps these large government contractors because they are simply Too Big to Fire.

No Accountability for Large Technology Contractors

A small government contractor that performed so badly would not be allowed back into these agencies. The large ones can deflect the blame and legally challenge any attempt to hold them accountable. They never issue refunds, and in fact, profit from their mistakes with awards of new contracts and change orders. They are effectively not held accountable for their awful past performance, so the disasters repeat themselves whether it’s at HHS, FBI, Air Force, IRS, etc. The federal government is littered with expensive projects that were never used or functional, but highly profitable for the contractors.

Our Government Contracting System Encourages This

What happened with Healthcare.gov is exactly what our system encourages contractors to do. Had the contractors finished on time and properly, they would have made less money than delivering a flawed system. The government has tried to privatize its services by using outside contractors. Unfortunately, these government contractors are specialists at getting government contracts and milking taxpayers more than their technical ability. They would never survive in the private sector.

Policy Makers Now Have Political Risk for Technology Decisions

This is the first time an administration has paid such huge political cost for mismanaging technology. Prior to this, Presidents understood they were responsible for the economy, jobs, wars, terrorism, crime, responding to natural disasters, etc. They never realized there was political risk with technology. President Reagan wasn’t blamed for the Space Shuttle exploding, but this administration has become responsible for this web site disaster.

Contractor Goals and Values Do Not Align with Policy Makers

Frankly, I don’t think the politicians have any better handle for designing rockets or web sites. They relied on contractors and these contractors misled them. The policy makers don’t realize the goals and values of the contractors differ from theirs. Watching our leaders say the self-serving things their contractors tell them is even more embarrassing. Those contractors are not your friends!

Lobbying and Post-Retirement Jobs Drive Business

Some government officials are swayed by promises of post-retirement jobs at the contractors they supervise. Look at all the former program managers, contracting officers, Congressmen, admirals and generals at these government contractors and their lobbyists to understand how business is done.

Contractors get on contracting vehicles like the IDIQ for Healthcare.gov (termed “Licenses to Hunt”), then send in their well connected people to get contracts directly or wire contracts by “helping” draft requests for proposals (RFPs) favoring their organization. Perfectly legal. Not taxpayer friendly.

Bipartisan Reform Required

This is a bipartisan issue because unless IT government contracting is reformed, this is going to bite future politicians/policymakers of both parties. They do not have the training or experience to manage these technology projects. Especially when the contractors are run by used car salesmen who say, “You should get the undercoating” and the government people are technically unqualified to say “No”.

Technology Accountability Office (TAO)

We need the creation of a Technology Accountability Office (TAO), similar to the GAO to help agencies properly manage and buy these solutions, or an agency that manages large IT projects so the Best Practices are dispersed across the agencies. Right now, politicians have no clue whether a project should cost $1 million or $100 million, and whether it can be done in 3 months or 3 years. It’s total chaos and taxpayers are paying the tab.


Related Resources

Here are a few opportunities where I’ve spoken about these issues.

fox-and-friendsNovember 30: Fox & Friends Live Interview with Clayton Morris

ObamaCare: Mistake or moneymaker?

A one-on-one interview with Clayton Morris for four minutes discussing how large government contractors profit from delivering systems that don’t work: “If we follow the money, we’ll see the stink in the system…Too Big to Fire”

fox-friends-2013-11-30-clayton-luke-graphic fox-friends-2013-11-30-luke


Greta van SusterenNovember 26: On the Record with Kimberly Guilfoyle

Will HealthCare.gov be in good health by Nov. 30?

Greta van Susteren is on vacation, so I chatted with Kimberly who was in New York City while I was on Greta’s studio in Washington, DC.

Kimberly-Guilfoyle-Luke Kimberly-Guilfoyle-Luke2

“Over time, I’m beginning to see that these government contractors who took over this project have essentially made every decision that favors them as much as possible – to maximize the cost to taxpayers, to maximize their profits.”

Related article by Greg Richter based on the broadcast: Software Developer: ACA Website Designers Just Lining Own Pockets


House Homeland Security CommitteeNovember 13: House Homeland Security Committee Testimony

I had the opportunity to discuss the problems with government IT contractors in my prepared testimony and questions from Chairman McCaul.

Homeland Security Committee Testimony

Testifying before the House Committee on Homeland Security


nj-star-ledgerDecember 17: The Star Ledger by Paul Mulshine

“Luke Chung is the best authority I’ve come across on the Obamacare software debacle.”

How contractors got rich by screwing up Obamacare


Additional Media Coverage for Changing the National Discourse on Healthcare.gov


Oct 14

Creating a Healthcare.gov Web Site that Works

Healthcare.gov

HealthcareBackground on the Healthcare.gov Technology Problems

My blog post on October 1st, Healthcare.gov is a Technological Disaster, described my experience using the Affordable Care Act’s Healthcare.gov website on its first day. Based on my experience, I could tell the Obamacare site was a technical mess independent of the number of users on the system. However, “Too many users” was a convenient and politically positive excuse the contractors and administration attributed to the failure of the website. It took about a week before the press began to understand that wasn’t the case. Because of my blog post, I ended up in a New York Times article, the national broadcasts of CBS, CNN and Fox News, and a few radio shows (links are in my prior blog post). I was also invited by the House Energy and Commerce Committee staffers on Capitol Hill to meet them to help them better understand what was and wasn’t working and why.

Solutions for Improving Healthcare.gov

I dislike complainers who don’t offer solutions, so I feel obligated to offer some constructive ideas for creating a functional Healthcare.gov website. I’m not being paid to work on the Healthcare.gov web site and don’t have the actual specifications of what needs to be created, but based on my experience building database solutions and understanding load balancing, I offer the following ideas to consider.

Understanding the Buying Process for Health Insurance

It’s important to understand what the web site should do. The primary mistake the designers of the system made was assuming that people would visit the web site, step through the process, see their subsidy, review the options, and select “buy” a policy. That is NOT how the buying process works. It’s not the way people use Amazon.com, a bank mortgage site, or other insurance pricing sites for life, auto or homeowner policies. People want to know their options and prices before making a purchase decision, often want to discuss it with others, and take days to be comfortable making a decision. Especially when the deadline is months away. What’s the rush?

The existing process acts as if a retail website asked for your credit card number before showing what you could buy and their prices. Almost all sites let you browse without creating a user name. Retailers want you to see what’s available as quickly and easily as possible. People often visit multiple times before buying. Only after making a purchase decision should personal information be collected to complete the transaction.

The web site needs to reflect this and support a more common buying process.

Conceptual Overview

Here’s an overview showing three distinct processes that flow into each other (or people buy a policy at their step and leave the system). A critical part is offering a comparison matrix at each level so consumers can quickly see the differences between the insurance policies.

Healthcare.gov Redesign
(click for larger image)

  1. The first one gives policy options and non-subsidized quotes. People can click to purchase the policy from the insurance company. If so, they leave Healthcare.gov and the government is no longer involved.
  2. The second provides a subsidy estimate and uses the same display as the first but with and without subsidized prices. People can also click to buy the policy without a subsidy and leave the system, or they can officially apply for a subsidy.
  3. The third is the actual application for the subsidy and the only path which collects Personally Identifiable Information (PII). Higher security is necessary for this.

The first two do not require PII and would not require high security. That means a commercial cloud service such as Microsoft Azure could be used to host the site and adjust to high traffic loads. It would support people shopping and browsing multiple times before buying without the need to invest in hardware or bandwidth.

With this improved design, only a small portion of the site’s traffic would be in the final subsidy application portion. That can be isolated with high security and for much lower volumes of users since people would only apply once. Hassling people at this stage with lots of personal questions is acceptable since people are serious about purchasing.

User Experience Goals

These are some objectives for creating a great user experience:

  • Quickly get the unsubsidized insurance rate quotes and policies (no login required)
  • Easily compare among insurance policies based on features and price
  • Easily select and subscribe with an insurance company without a subsidy
  • Quickly receive an estimate of a subsidy without having to provide personally identifiable, confidential information
  • Easily compare among insurance policies based on features and subsidized prices
  • Do not ask unnecessary questions such as race that don’t impact plans, prices, or subsidies
  • Formally apply for the subsidy (login and personal information required)
  • Select a subsidized policy and pass the appropriate information so the insurance company can validate the subscriber’s information and receive the subsidy
  • Once policy options are offered, allow users to create a login to save their inputs, and get back into the system to recover their work-in-progress. This would be required with the formal subsidy application but not necessary for the other options.

Technical “Back Office” Goals

  • Performance: The system should move people through the process as quickly as possible.
  • Collecting Information: It should not ask for any information that’s not required for generating the policy options and prices.
  • Fewer Screens: Rather than having one screen per question, multiple questions should be asked in as few screens as possible. People know how to scroll. Extra screens should only be added if they depend on answers from previous screens.
  • Data Security: The first part of data security is to NOT collect sensitive information. Sensitive information should only be collected from people actually applying for the subsidy.
  • Data Integrity: All database changes need to be in transactions with commitments and rollback on failure. Situations where accounts are partially created with a valid user name and no account details should never occur.
  • No Other Connections During Data Entry: The system should not be connecting to other data sources while the user is entering data. Just collect the data.
  • Offline Processing: Once the user enters all their data for a subsidy quote, a separate system processes the applications and interfaces with the other systems to validate the data and calculate the subsidy. By separating this process from the user’s online experience, problems with connections to other systems do not impact the user.
  • Email Notification: Once a subsidy is calculated, an email is sent to the user inviting them to log into the system to see their options
  • Notification to Insurers: Web pages and web services to allow real-time views of the status of applications selecting the insurer’s policies.
  • Commercial Cloud Hosting: Using a commercial cloud platform would provide automatic scalability to meet fluctuating levels of users without having to make hardware purchases. By eliminating the need to collect and store sensitive user data for most of the website, commercial cloud hosting and its benefits are available without security concerns.

Oversight Goals

Management and interested parties should have system dashboards:

  • Real-time Displays: Monitor user progress with summary tables and graphs showing the status of people moving through different stages of the system.
  • Basic Business Intelligence: Summary and drill-down details by state, date, hour, etc.
  • System Transparency: Provide a public view of some data in a cached mode (updated daily or hourly, but not real-time).

Design Overview

Here is how the goals could be implemented for the Healthcare.gov web site:

  1. The initial form asks people to select their state. If the visitor is in a state that has their own system, ship them to those sites, otherwise proceed with the next step in the federal system
  2. Collect the information necessary to create the unsubsidized options. I was told there were five or so pieces of information necessary to generate the unsubsidized rates (e.g. gender, year of birth, family status, smoking status, etc.)
  3. Display the available plans with options to compare and filter them easily based on plan level (gold, silver, bronze, etc.), provider, price, etc. Should be similar to retail web sites like Best Buy or Staples showing different products and their features in a matrix comparison, with buttons to get more details and a button to select one to buy. One would expect users to come to this site multiple times over multiple days to learn about their options before making a purchase.
  4. An option to save the inputs. This would be the first time to create a simple account to collect user information (which does not include things like social security numbers, birthdates, or names). A simple user name (email address) and password, with a standard email confirmation that doesn’t have a time limit. This would allow users to get back to the previous screen without re-entering their data.
  5. An option to get a subsidized price estimate. If the person chooses this option, they create a simple account because highly sensitive information will not be collected. The account is simply to retrieve the user’s entries. The user provides the information necessary to calculate the prices without having to lookup data from government sources. The user can enter their values for income and whatever other factors impact generating a subsidy estimate. Just like bank web sites let you enter basic information to get a mortgage or car loan rate before you apply, Healthcare.gov should do the same. This would allow the site to create quotes quickly without having to bog down or wait for the other sites such as the IRS, Experian, etc. This minimizes the impact of too many users. Once the estimated subsidies are calculated, a display similar to #3 above would show the options.
  6. Finally, applying for the subsidy. Once someone decides they want a particular policy, they can officially apply for a subsidy. This is the first time personal data needs to be entered. The system should collect the data as quickly as possible without having to validate the information while the user is entering it. Once all the data is collected, the user is informed via email when the subsidy calculation is ready.
  7. A separate background process calculates the subsidy requests and looks up the necessary data from the different sources. If any of those linked systems is unavailable, it’s no big deal since it doesn’t impact the user on the web site. The user is already gone and waiting for an email. Once the calculation is generated (or if it couldn’t be generated), the user is notified via email and they can view the results by logging back into their account.

For management, there should be dashboards with tables and graphs showing what’s happening. No more excuses of not knowing how many people are in each phase of the process, how many have received quotes or enrolled, etc. For transparency, some of this information should be publicly available updated at least daily.

Conclusions

I’m not sure whether the people designing and developing the site will find these suggestions helpful. There’s obviously lots of details not included in my proposal, but I’m confident my basic design is a significant improvement over the original site. It would provide a better user experience, be much easier and faster to develop, easier to test, and more scalable and secure. Was it that tough to envision earlier?

Let’s remember, this website remains the automation of a paper form. It’s not as hard as providing healthcare.

Related Blog Posts:
Too Big to Fire: How Government Contractors on Healthcare.gov Maximize Profits
Healthcare.gov is a Technological Disaster
Media Coverage for Changing the National Discourse on Healthcare.gov
Testifying before the House Committee on Homeland Security about Healthcare.gov