A Healthcare business and data automation company

,empowering health organizations to enable better

patient care and maximize industry savings.
 EVOLVING GHX’S BUSINESS MODEL

Market expansion Business exploration

Acquisition- Centrimed
2000

New Alliance- Neoforma,

AmeriNet,Broadlane
Merger- medibuy,
HealthNexus 2001-2002
Markets Product-Market Product Expansion
enhancements
Establishing GHX-
Same early 2000

Coalition of healthcare
standard(CHeS) -2003
Same New

Products
1. Do not hesitate to bring in the experts to make sure your network is configured
properly.
 Encourage external audits of your network
2. Do not let any one individual in your IT group become the sole point of failure.
3. Keep your working knowledge current.
4. Beware of users armed with just enough knowledge to be dangerous.
 Actively log all experiments on the network, while under supervision
5. Institute rigorous network change control – Have a robust downtime plan.
 Out of band diagnostics-communications occurring outside established
channel.

6. Adapt to externalities and examine all events in the outside environment for
possible impacts on existing IT functionality.
7. There are limits to customer centric responsiveness.
 A formal change-control process/protocol in place
8. Have backup procedures in which you can have confidence.
9. Component redundancy is not enough; you need alternative access methods.
Strategy Audit OPPORTUNITIES
1.Partnership with Cisco
2.Recovering economy (Q4, 2002)
3.Vendor to Walthamand Glover
4.Synergies from merger
5.Further cost cuts due to
leveraging IT
6.Many hospitals closing, leading
to less market saturations
Capability Audit STRENGTHS
1. Halamka’s leadership
2.Y2K Disaster Recovery Plan
3.Info.Week’s #1 IT organization
4.90% cut in capital expenditures
5.2ndlargest healthcare system in
the region
THREATS
1. Volatile time for industry
2.Stagnant industry growth
3.Mass. Gen.-Brigham and Women’s
merger
WEAKNESSES
1.Outdated network components
2.Weak financial statements
3.Inadequate security controls
4.Inadequate change controls
5.Lack of networking knowledge
6.Outdated Disaster Recovery Plan