Skip to main content

Epic Fail -- Maryland Health Insurance Exchange

Maryland may have earned an unwanted distinction for its failed Health Insurance Exchange website -- one of the costliest and highest profile failed information technology projects in state government.  The health exchanges were challenging from the beginning, and many states , including Maryland, Hawaii, Minnesota, and Oregon apparently chose teams that were not capable of overcoming the tight deadlines and high performance requirements, prompting a Congressional hearing last week. 

The Washington Post reported that Maryland decided in March 2014 to scrap its work (at a cost of $125 million) and restart with the software used by Connecticut.  Fewer than 50,000 (out of the goal of 150,000) had signed up for coverage on the Maryland site, and most had ended up enrolling through manual processes such as on the phone.

The prime contractor that failed on the Maryland Health Insurance Exchange was Noridian Healthcare Solutions of Fargo, ND, whose contract was valued at $193 million.  They have been replaced with Optum/QSSI of Columbia, MD.

Noridian had hired Fort Lauderdale, FL based EngagePoint for $250,000 per month and EngagePoint in turn hired subcontractors.  EngagePoint moved its headquarters to Maryland following the contract award.

Noridian fired EngagePoint after the failed launch of the site in October 2013, prompting a lawsuit, in part over efforts by Noridian to hire EngagePoint employees. 

Now Maryland politicians are trying to distance themselves from this epic fail. 

Are there lessons from this failure?  EngagePoint accused Noridian of using the traditional waterfall methodology which finishes each step before starting the next.  Could the methodology have been at fault?  Was the team qualified to build the system?  Did the failed exchanges make the wrong hardware or software choices?



Popular posts from this blog

Key Concepts for Microsoft Dynamics 365: Tenant, Instance, App and Solution

To understand Microsoft Dynamics 365 (formerly Dynamics CRM), you need to learn some new terms and concepts that may be a bit different from what you know from databases and solutions that are hosted on premises. This post introduces some of the key terms and how these concepts are important for planning your implementation. While Dynamics 365 is available on premises, it is most commonly deployed on the Microsoft cloud.  This blog post discusses only cloud implementations. Microsoft has multiple clouds such as commercial and government community clouds. We start with a Microsoft tenant .  A tenant is the account you create in the Microsoft Online Services environment (such as Office 365) when you sign up for a subscription. A tenant contains uniquely identified domains, users, security groups, and subscriptions.  Your tenant has a domain name of .onmicrosoft.com such as acme.onmicrosoft.com.  User accounts belong to a tenant, and subscriptions are assigned to user accoun

Understanding Dynamics 365 and Office 365 Admin Roles

Managing Dynamics 365 instances If you run Microsoft Dynamics 365 (formerly Dynamics CRM) in the Microsoft cloud, you need to understand how your Dynamics instances relate to Office 365 and choose which of your administrators receives which roles and permissions to manage Dynamics 365. In on premises deployments, your network administrator would create and delete user accounts.  The Dynamics 365 admin would then assign permissions to users in Dynamics 365. This post explains three administrator roles: Office 365 Global Administrator Dynamics 365 System Administrator Dynamics 365 Service Administrator You may think that the Dynamics 365 system administrator would have power to do all the actions needed to manage Dynamics 365, but this is not the case. What's different in Microsoft cloud deployments is that licenses and user accounts are managed in Office 365 by an Office 365 Global Administrator.  This role is analogous to a network administrator for an on premises

Replacing Microsoft InfoPath with Power Apps

Source:  https://powerapps.microsoft.com/en-us/infopath/ Microsoft has offered a number of forms automation products over the years, and the most long running was InfoPath which was released as part of Office 2003.  InfoPath is a powerful and flexible product that stores user data in XML while offering form features such as rules, data validation, scripting, and integration with SharePoint.  The popularity of SharePoint resulted in many organizations standardizing on InfoPath for forms, especially internal forms which are hosted on an intranet such as employee reviews, leave and payment requests, and human resources forms. Microsoft has discontinued InfoPath, with mainstream support ending July 13th, 2021, and extended support ending July 14th, 2026. Microsoft has named Power Apps as the successor to InfoPath .  Power Apps has much in common with InfoPath.  Both products include integration with SharePoint.  Both are geared toward the citizen developer and do not require advan