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

PowerApps Portal: The Successor to Microsoft Dynamics Portal

In case you have been reviewing Microsoft's new pricing for its Dynamics products which was released this month and have been unable to find Dynamics Portal, it has been rebranded as PowerApps Portal and shifted to the PowerApps side of the Microsoft product family.


Rebranding the portal product underscores the importance of app scenarios involving external users such as customers and suppliers.  It also provides a simpler interface than Dynamics 365 for occasional users.

The new portal pricing is based on the number of unique users who log into the portal each month (for authenticated users) and on the number of page views for anonymous users.  "A login provides an external authenticated user access to a single portal for up to 24 hours. Multiple logins during the 24-hour period count as 1 billable login. Internal users can be licensed either by the PowerApps per app or per users plans, or a qualifying Dynamics 365 subscription."

Pricing starts at $200/mo. for 100 dail…

ScreenMeet Remote Support Tool for Dynamics 365 Customer Service

I met Lou Guercia when he was president and CEO of Scribe Software, the leading CRM integration tool.  Scribe was acquired by TIBCO Software in 2018.  I recently reconnected with Lou and learned about ScreenMeet, the company he joined as chief operating officer.   The following is a description of the product provided by ScreenMeet:

ScreenMeet is a cloud-based remote support tool designed to integrate with Dynamics 365 Customer Service. By enabling customer service and IT support organizations to address critical technical issues directly from their CRM or ticketing platform, it streamlines the process and provides a fully browser-based support experience.

You can also use ScreenMeet with other CRM products or even on its own without a CRM.

Here is a short video demo of ScreenMeet with Dynamics integration:


ScreenMeet - Cloud-based Remote Support Integrated with Dynamics 365 Customer Support Once integrated with a Dynamics 365 CS organization, the ScreenMeet widget appears on Case pa…

Microsoft PowerApps and Microsoft Flow Licensing for Beginners

NOTE: Since this post was written, Microsoft has updated pricing.  For current pricing, see https://powerapps.microsoft.com/en-us/pricing

Next month marks two years since Microsoft announced the preview of its Flow workflow automation product.  Since then, PowerApps and Microsoft Flow have been gaining in popularity.

We at InfoStrat are receiving more questions from customers on how PowerApps and Flow are licensed by Microsoft.  This is a brief overview with links to authoritative Microsoft resources with all the details.

What are PowerApps and Flow? Microsoft PowerApps is a framework derived from Dynamics 365 (formerly Dynamics CRM) that allow you to build apps either with or without a form interface.  PowerApps works with Microsoft Flow.

Microsoft Flow is is a cloud software tool to build automated workflows that connect to many Microsoft and non-Microsoft systems and services.  For instance, you could write a workflow which would create a record in Dynamics 365 whenever a new file …