|CASE: A Hospital Catches the “Millennium Bug”, by Janet Gogan|
“Bob Sadlemire completed the minutes of the May 1998 meeting of Fletcher Allen Health Care’s Year 2000 Steering Committee, and headed out for a lunch meeting with his boss, Mary Kay Boudewyns. Before walking up the hill to the Burlington, Vermont restaurant, he paused to take in the serene sight of Lake Champlain. Refreshed, he walked on, his thoughts turning to the upcoming June meeting of the Patient Care and Systems Improvement (PCSI) committee of the Board of Trustees, in a few days (Exhibit 1). Sadlemire would have 15 minutes to brief the committee on the status of the hospital’s Y2K project. Sadlemire — an employee of Jennings Consulting, Inc. – had been assigned to Fletcher-Allen as its Y2K Project Coordinator, on a contract that ran from July 1, 1997 through July 1, 1999. While much had been accomplished, he was quite concerned that the project was not proceeding forward as fast as necessary.”
For purposes of our discussion, you should assume the date is May, 1998. Note that Year 2000 (Y2K) compliance projects entailed the following technical steps, which applied to all categories of software (operating systems, transaction processing and decision support applications, vendor packages, user-developed applications, etc.), computing hardware (desktop, midrange and mainframe systems) and programmable devices – such as elevator controls – which contain date-sensitive microprocessors:
- Inventory: identify hardware and software that might give rise to Y2K problems.
- Analysis: examine code for date fields, determining which ones need to be fixed.
- Remediation: alter the code for Y2K compliance (“renovation” or “conversion”)
- Testing: ensure that altered code produces correct results
- Migration: put the new code into production
Answer the following questions:
- Who is the case protagonist?
- What is the case issue?
- What do you recommend the protagonist do next? Why?