Paragon Rising | Healthcare Informatics Magazine | Health IT | Information Technology Skip to content Skip to navigation

Paragon Rising

October 28, 2008
by Brian Albright
| Reprints
A software product's dramatic rebirth provides lessons for vendors and hospitals

New software deployments present hospitals with both great opportunity and great risk. A few bad decisions early on can be costly in terms of both time and money, especially in the healthcare software market, where long development cycles and post-sales support issues are common.

When a software installation goes awry, the aftermath is seldom pretty for the customer or the vendor. Occasionally, though, a software company will emerge from these near-disasters with both a happy customer and a better product.

Such was the case with San Francisco-based McKesson Corp.'s Paragon Community Hospital Information System. While Paragon has been named Best in KLAS two years in a row and is quickly gobbling up market share in the community hospital space, there was a time when the product was near collapse. The software didn't work, customers had been left hanging, and McKesson executives were weighing whether to mothball the product or start over from scratch.

Paragon's rise from the ashes required both a commitment from McKesson and a leap of faith from its customers, and provides some important lessons in product development, software selection and collaboration for hospitals and software vendors alike.

Monumental problems

McKesson first acquired the software through its merger with Atlanta-based HBO and Co. (HBOC) in 1999. HBOC had introduced Paragon in 1996 as the next generation of its existing SAINT product line, promising that it would be a Windows-based, client/server system for smaller community hospitals, a few dozen of which eagerly signed up to migrate. Unfortunately, it didn't work.

“HBOC tried to tie the new Microsoft technology into the old technology, and then replace the modules as they became available,” says Jim Pesce, senior vice president and general manager of McKesson's Paragon group. “That led to monumental problems.”

The original Paragon team had oversold the capabilities of the product (a common practice among software vendors at the time), and started signing contracts before the software was near completion.

“They started these PowerPoint presentations at the trade shows, and sold it way before its time,” says Vince Ciotti, principal at H.I.S. Professionals, a consulting firm based in Santa Fe, N.M., and an HCI guest blogger ( “There were lots of bugs, and not a lot of applications.”

McKesson had three options: discontinue the Paragon line; move forward with the existing customers and hope to make the software work later; or pull it from the market and start over.

David Witton

David Witton

One of McKesson's executives called on a former business partner, industry veteran Pesce, to take a look at Paragon and make a recommendation.

“I instantly saw the problems, but more importantly I fell in love conceptually with what HBOC had been trying to build,” he says. “I thought that if McKesson could build a fully integrated clinical and financial product on the Microsoft platform, it would be light-years ahead of anything else in the industry.”

Pesce came on board to head up the rebuilding process. “Stabilizing the product provided the opportunity to demonstrate our commitment to our customers and the industry, and to build market share, and had the potential of producing something that would become a valuable asset to our company,” Pesce says.

McKesson suspended new sales and implementations of Paragon while the product was stabilized. About half of the existing customers received a refund, but the remaining hospitals agreed to stay onboard while the software was retooled.


The “new” Paragon system emerged in 2001 as a fully integrated clinical and financial HIS offering, built on Microsoft technology. And in 2004, McKesson's executive committee gave the go-ahead to start building a sales team and formally roll out the product to new customers.

“Paragon's reputation had suffered,” says Pesce. “But I was adamant that we not change the name. My belief was that if we turned this into a great product, it would be a better story and get more recognition than if we tried to introduce it as a new offering. But the hardest part was getting in the door.”

One of the first new customers to take a chance on Paragon was David Witton, director of information systems at St. John's Medical Center, a non-profit community hospital in Jackson Hole, Wyo.

Witton, himself a programmer, started looking at Paragon in 2002 and was aware of its history. “They were converting from a flat-file, siloed application to an object-oriented, relational database,” he says. “It looked like a trainwreck waiting to happen. But once they made that conversion, there was no reason it wouldn't be viable.”

Paragon was still missing some core modules at the time, but after speaking to some original customers who had already made the switch, Witton says he learned that McKesson was rapidly delivering new applications — a key factor in Witten's final decision. “The product did not have a materials management module in November 2002,” he says. “By the time we got to the final face off in May of 2003, they had built that product.”
George Sullivan

George Sullivan


Get the latest information on Health IT and attend other valuable sessions at this two-day Summit providing healthcare leaders with educational content, insightful debate and dialogue on the future of healthcare and technology.

Learn More