They should indicate the current status and progress, including completed items and ongoing research. Reiterate the urgent and significant risks currently faced, as well as the matters that need to be addressed at present, such as freezing non-critical projects (such as telemedicine), reallocation resources to Y2K/ approval to provide additional funds for HIS repair and equipment upgrade.
In Bob’s report to the board, the key points include a summary of the overall project progress, such as the formulation of upgrade plans for core systems. Next, he should highlight the remaining risks in the project, such as delayed compliance verifications and incomplete emergency plans from suppliers, but emphasize that all risks are manageable and under control. Finally, he can request approval from the board for additional budget to replace equipment and ask for sufficient resource allocation to support the Y2K project.
Bob Sadlemire should provide a brief overview of the progress of the Y2K project since the last meeting, including the work that has been completed in the inventory preparation, analysis phase, and mention the key systems and equipment that have been identified. Identify the main challenges at hand and describe the serious impact on patient care, financial operations, and the reputation of the hospital if these challenges are not effectively addressed, and request the necessary support from the Board of Directors. This is followed by a concrete action plan, including speeding up the work of the unfinished parts, strengthening testing, and developing an emergency plan to deal with emergencies.
At the June meeting, Bob Sadlemire should define the Y2K problem and its impact on FAHC, display update on compliance progress across key domains, highlight critical risks and mitigation gaps, for example, resource conflicts, accountability gaps and testing limitations to the Board of Trustees. And request strategic support from the Board, convey confidence in the Plan while managing expectations.
At the June meeting with the Board of Trustees, Bob Sadlemire should present a clear and structured update on the Year 2000 (Y2K) compliance efforts while addressing both progress and challenges. In terms of progress, Sadlemire should highlight that: the scope of the Y2K project spans across IS-supported applications, technical infrastructure, clinical and non-clinical equipment, telecommunications, suppliers, and payors, all managed by the Year 2000 Task Force and Steering Committee. However, Sadlemire must candidly address challenges: limited top-down buy-in, delays in departmental inventory reporting, and resource competition from the $17 million Basic Infrastructure initiative. These factors threaten the project’s timeline. To conclude, Sadlemire should outline actionable next steps: accelerating inventory completion, prioritizing remediation of high-risk systems, and establishing contingency plans for critical failures. He should urge the Board to reinforce Y2K as the organization’s top priority, ensuring cross-departmental collaboration and dedicated funding to meet the December 31, 1999 deadline.
Bob Sadlemieux should report the progress of the Y2K project to the board, including the following:
Present the project scope: state what the project covers, which systems and clinical equipment are involved, and which third-party personnel are connected.
Highlight the importance of the Y2K project: explain the Y2K issue and its potential impact on hospital operations.
Progress description: list the current project achievements, which systems have been upgraded, which medical equipment has been handled, how much cost has been invested, and the time, manpower, money and resources required for the subsequent completion of the project.
He needs to report on the progress of the current project that has been completed, such as the evaluation of the application and the inventory of the physical equipment. Then needs to explain what are the challenges facing the project at this point. For example, incomplete program inventory, insufficient testing resources, and other things that are still outstanding. Finally, he should present his needs, i.e., the help he needs to accomplish his goals. For example, management needs to reallocate resources or assign more people to the Millennium Bug project. There is also a need to reprioritize the projects so that the Millennium Bug project is at the centre of attention.
1. Report on the current progress of the project;
2. Report current challenges, such as the project’s low priority and the complexity of the system making the project difficult to push;
3. Request for a higher priority and ask for more resource allocation;
4. Emphasize the importance and urgency of the project;
5. Express confidence in completing the project and achieving full-year 2000 compliance by December 31, 1999 with senior management’s support.
In Fletcher-Allen’s Y2K project, progress has been made in the inventory of IS and clinical equipment. However, there are difficulties in the inventory of departmental applications, high costs for remediating legacy systems, and resource-intensive external emergency measures. Currently, risks such as project delays, resource shortages, lack of departmental compliance, supplier instability, and priority confusion exist. Technical testing has been postponed, and the Meditech migration is uncertain. It is recommended that the Board reallocate resources to prioritize remediation, expand the team, establish an emergency fund, add compliance clauses to contracts, strengthen supervision, and issue a CEO-endorsed priority document. Although some achievements have been made, the unresolved departmental and external risks pose significant threats. Support from the Board is required; otherwise, costs will increase and patient safety will be endangered.
1. Current Status (Honest Assessment)：Report current status, project details.
2. Risks of Inaction: (explain the Y2K potential impact, current challenge, current existing problems. )
3. Ask for Support: (a higher priority or more resource allocation. )
Bob Sadlemieux should update the board on the Y2K project progress by first outlining its scope: detailing the systems and clinical equipment included (such as HIS, administrative applications, and ~6,000 medical devices), as well as any third-party vendors or personnel involved in compliance efforts. He must emphasize the project’s urgency by explaining the Y2K problem—specifically how date-related system failures could disrupt hospital operations, patient care, and incur legal/financial risks. For progress, he should itemize achievements like upgraded systems, remediated medical equipment, total costs incurred, and the remaining resources needed: specifying the timeline, staffing, budget, and infrastructure required to complete the project by the deadline. This comprehensive report will enable the board to understand the project’s scale, risks, and ongoing needs for informed decision-making.
At the June board meeting, Bob Sadlemire should report that 107 IS-supported applications have been inventoried and 4,000 clinical devices submitted for VHA compliance checks, with IDX and Peoplesoft projects progressing. However, departmental application remediation remains stalled, hardware checks are delayed, and a $400,000 device needs replacement. Risks include $26–40 million in potential payment delays from non-compliant payors, patient care disruptions, and legal liabilities. He should request 2 engineers from other projects and an extra $100,000 for HIS repairs, aiming to complete departmental app inventories by Q3 1998 and critical device fixes by Q1 1999. Citing a neighboring hospital’s Y2K failure as a warning, he should propose deferring non-essential infrastructure work. Additionally, he must present a New Year’s Eve manual date-switching plan with 10 nurses trained for emergencies, pledging to forfeit 5% of project bonuses if compliance isn’t certified by November 1999.
Tell them we’ve made some headway, but we’re still facing major hurdles. Mention the delays with critical projects like Meditech and the fact that hardware work is being pushed aside for other stuff.
Also, let them know that some managers aren’t taking Y2K seriously enough, and we’re running short on resources. But most importantly, stress how risky this is. If we don’t get our act together, the whole system could crash when the clock strikes 2000. We need their support to reprioritize and get the resources we need.
I believe Bob Sadlemire should clearly convey the following three core messages to the board:
1. Current progress: The key systems (such as HIS) have been thoroughly inspected, but there are still a large number of clinical equipment and department applications that have not completed the compliance verification, and some core projects (such as the Meditech system replacement) have a risk of delay;
2. Urgent threat: If not addressed promptly, the Y2K issue could lead to malfunctions of medical equipment, paralysis of the financial system, and even affect patient safety (referencing FDA warnings and cases of suppliers’ non-cooperation);
3. Action requirements:
Suspend non-urgent projects (such as network upgrades), and prioritize the allocation of manpower/funds for Y2K remediation.
At the June meeting, Bob Sadlemire should inform the Board of Trustees of the Y2K project’s progress, including the completion of inventories for critical systems and equipment and the launch of remediation plans, while highlighting challenges such as delays in replacing legacy systems, resource conflicts, and incomplete inventories of departmental applications. He must emphasize the systemic risks of Y2K issues to patient care, legal liability, and cash flow, recommending prioritization of compliance through strengthened risk assessment, integration of remediation into ongoing projects, implementation of cross-departmental accountability, and leveraging external resources to avoid operational disruptions and ensure completion of remediation by mid-1999. He should also report matters requiring the Board’s support, requesting a budget exceeding $100,000 for HIS system code remediation and coordinating resource prioritization to ensure the Y2K project is not sidelined by other initiatives.
At the June meeting, Sadlemire should first outline progress: inventory of IS-supported apps near-complete, clinical equipment assessment underway via VHA, and task forces formed. But he must stress critical risks: 4,000+ clinical devices need testing/upgrading, a $400K nuclear machine may require replacement, and departmental app inventories remain incomplete. He should highlight delays in technical upgrades due to competing infrastructure projects and warn that $26–$40M in payments could be delayed if payors aren’t compliant. Sadlemire must emphasize Y2K’s urgency, noting it’s treated as secondary to other projects, and request board support to prioritize resources, mandate cross-departmental accountability, and ensure timely remediation before 2000.
Bob Sadlemire should report at the June board meeting:
Progress: Indicates the status of the Y2K project’s initiation, progress, or completion, such as system evaluation, repair progress, and investment of human and financial resources.
Risk Challenge: Clarify compliance risks (systems, finance, reputation, etc.), as well as technical and coordination challenges encountered and response measures.
Future plan: List the remaining project timeline and key milestones, propose resource requirements (such as funding and manpower), and seek support from the board of directors.
Transparent communication: Clearly explain the communication situation and feedback impact of internal and external stakeholders, as well as the reporting mechanism to the board of directors in the future.
Sadlemire should report to the board on the progress and risks of the Y2K project: 107 IS applications have been thoroughly checked, but there are still omissions at the departmental level, and 4,000 medical devices are awaiting assessment. The Peoplesoft conversion is proceeding as planned, but the Meditech project is time-critical. The technical team has postponed the Y2K hardware work due to the infrastructure upgrade. Risks include delayed payments from the payers, equipment replacement costs, and compliance loopholes. It is recommended to allocate resources from the infrastructure project, mandate departments to submit the inventory reports, include compliance clauses in the contract, apply for a $1 million budget and establish a supervision committee. Risks need to be quantified to prompt the board’s attention and prevent system failures in 2000 from endangering patient safety and hospital operations.
Key Messages for Bob to Share with the Board of Trustees in June:
1. Current Progress (June 1998)
Completed:
Inventory of 4,000 medical devices (via VHAseCURE.net).
Vendor compliance checks for critical systems (e.g., IDX, Peoplesoft).
in Progress:
Testing for life-critical equipment (planned late 1998).
Facilities inventory (ongoing, ~50% complete).
2. Major Risks & Challenges
Meditech Clinical Rollout: Scheduled for June 1999 (tight deadline).
Device Testing: 60% untested; nuclear medicine equipment non-compliant.
Resource Conflicts: Y2K work competes with telemedicine/infrastructure projects.
3. Urgent Needs
Approval to pause non-critical IT projects (free up staff for Y2K).
Additional budget for device upgrades (e.g., $400K nuclear medicine replacement).
Leadership mandate to enforce department-level compliance.
4. Bottom-Line Assurance
70% confidence in full compliance by 12/31/1999—if Meditech stays on track.
Contingency Plan: Manual workarounds ready for worst-case delays.
They should report project status—completed tasks and ongoing work—highlight urgent Y2K risks. Propose freezing non-critical projects (e.g., telemedicine), reallocating resources to Y2K, and seeking funding for HIS repairs/equipment upgrades to address immediate compliance threats and prioritize system stability.
When reporting to the board of directors, it is essential to emphasize that the initial inventory of core systems and medical equipment has been completed, and key projects are progressing as planned. However, significant risks are present, including tight schedules for clinical systems, 40% of medical equipment awaiting inspection, and unconfirmed third-party compliance. It is imperative that the board prioritize Y2K as the top priority, approve resource allocation and emergency funds, and establish a direct accountability mechanism. Otherwise, serious consequences such as equipment failures, financial disruptions, and legal risks will be faced. It is recommended to immediately suspend non-urgent projects and fully focus on ensuring compliance modifications are completed before the year 2000.
At the June meeting, Sadlemire should tell the Board: We’ve started forming teams and inventorying systems, but key upgrades like Meditech might miss deadlines. Critical equipment (like a $400K nuclear machine) needs replacing, and many departmental apps haven’t been checked. Tech upgrades face software compatibility issues, and old PCs are being reused, complicating testing. Vendors and payors could delay $40M in funds if they fail. This isn’t just an IT problem—we need urgent cross-team focus, or patient care and operations are at risk.
I think the followings can be included:
1.Current progress: What have done shows stakeholders the progress and also offer confidence for staff to complete the project. Besides, Showing what have not done can push employees and make better resources allocation in the whole busienss.
2.Solve the main problems and inform the current main risk: meeting is an excellent opportunity to concentrate everyone’s thought and deal with complex and collaboration-required items. Also, people who focus on his ow work may have no idea with other works and risks, thus meeting is here to notice them main risks.
3.Synchronous the priority: for the slow progress and difficulty to push, employees and critical individual’s working priority should be emphasized, through informing the consequences of inactions, like cashflow’s problem, lawsuits, patient safety,etc.
During the June meeting, Bob Sadlemire should concisely summarize the Y2K project’s progress since the last update, covering completed inventory preparation and analysis phase work. He should highlight identified critical systems and equipment while emphasizing key risks and mitigation gaps—such as resource conflicts, accountability lapses, and testing limitations imposed by the Board. The presentation should strategically request the Board’s support by balancing confidence in the plan with transparent communication about realistic management expectations.
What Bob Sadlemire Should Tell the Board of Trustees
1. Critical Risk Alert: Quantify Y2K Delay Impacts
Progress Gaps:
Only 50% assets inventoried (vs. industry 80%) → 40% critical devices (e.g., ventilators) unassessed.
0% systems tested (industry target: 30% by now).
Potential Losses (per BIA):
Financial: Day-1 outage loss ≥5M;annualexposure120M.
Legal: Medical malpractice suits ≈$20M/case (FDA precedents).
Reputational: 40% customer churn risk (peer incident data).
2. Root Cause: Priority Misalignment Starving Resources
Resource Diversion Evidence:
5 FTEs on Y2K vs. 50 on new outpatient building (Capex reports).
$2M Y2K budget reallocated to EMR customization (financial logs).
Governance Failures:
Y2K excluded from executive KPIs (compensation committee docs).
Zero clinical staff in Y2K decisions (12 committee meetings, no MDs).
3. 90-Day Rescue Plan
Immediate Actions:
Measure Resources Needed Outcome
Freeze non-critical projects (e.g., cafeteria) Free $1.5M funding Launch test lab next week
Outsource legacy COBOL fixes $500K contract Fix payroll system in 60 days
Form clinical risk team (MDs + engineers) 2 FTEs Assess ICU devices in 2 weeks
Board Decisions Required:
Approve: $3M emergency fund + pause EMR customization (free 15 engineers).
Mandate: Y2K priority overrides all projects (CEO arbitrates conflicts).
Accountability: Tie Y2K progress to executive bonuses (30% weighting).
4. Escalation Mechanism: Transparent Monitoring
Board Oversight Tools:
Weekly Y2K dashboard: Red/amber/green status for critical systems (e.g., ventilator patches).
Independent audits: Deloitte monthly verification.
Contingency Plan:
If progress <70% by September, activate patient diversion (transfer high-risk services to compliant hospitals).
Based on the case evidence, Bob Sadlemire’s briefing to the Board should balance transparency about critical risks with actionable recommendations, while leveraging the PCSI agenda (Exhibit 9) as a framework. Here’s what he should emphasize:
1.Start with a Reality Check: Progress vs. Peril
2.Flag Three “Make-or-Break” Risks
3.Direct Requests to the Board
4.Close with a Patient-Safety Ultimatum
They should indicate the current status and progress, including completed items and ongoing research. Reiterate the urgent and significant risks currently faced, as well as the matters that need to be addressed at present, such as freezing non-critical projects (such as telemedicine), reallocation resources to Y2K/ approval to provide additional funds for HIS repair and equipment upgrade.
In Bob’s report to the board, the key points include a summary of the overall project progress, such as the formulation of upgrade plans for core systems. Next, he should highlight the remaining risks in the project, such as delayed compliance verifications and incomplete emergency plans from suppliers, but emphasize that all risks are manageable and under control. Finally, he can request approval from the board for additional budget to replace equipment and ask for sufficient resource allocation to support the Y2K project.
Bob Sadlemire should provide a brief overview of the progress of the Y2K project since the last meeting, including the work that has been completed in the inventory preparation, analysis phase, and mention the key systems and equipment that have been identified. Identify the main challenges at hand and describe the serious impact on patient care, financial operations, and the reputation of the hospital if these challenges are not effectively addressed, and request the necessary support from the Board of Directors. This is followed by a concrete action plan, including speeding up the work of the unfinished parts, strengthening testing, and developing an emergency plan to deal with emergencies.
At the June meeting, Bob Sadlemire should define the Y2K problem and its impact on FAHC, display update on compliance progress across key domains, highlight critical risks and mitigation gaps, for example, resource conflicts, accountability gaps and testing limitations to the Board of Trustees. And request strategic support from the Board, convey confidence in the Plan while managing expectations.
At the June meeting with the Board of Trustees, Bob Sadlemire should present a clear and structured update on the Year 2000 (Y2K) compliance efforts while addressing both progress and challenges. In terms of progress, Sadlemire should highlight that: the scope of the Y2K project spans across IS-supported applications, technical infrastructure, clinical and non-clinical equipment, telecommunications, suppliers, and payors, all managed by the Year 2000 Task Force and Steering Committee. However, Sadlemire must candidly address challenges: limited top-down buy-in, delays in departmental inventory reporting, and resource competition from the $17 million Basic Infrastructure initiative. These factors threaten the project’s timeline. To conclude, Sadlemire should outline actionable next steps: accelerating inventory completion, prioritizing remediation of high-risk systems, and establishing contingency plans for critical failures. He should urge the Board to reinforce Y2K as the organization’s top priority, ensuring cross-departmental collaboration and dedicated funding to meet the December 31, 1999 deadline.
Bob Sadlemieux should report the progress of the Y2K project to the board, including the following:
Present the project scope: state what the project covers, which systems and clinical equipment are involved, and which third-party personnel are connected.
Highlight the importance of the Y2K project: explain the Y2K issue and its potential impact on hospital operations.
Progress description: list the current project achievements, which systems have been upgraded, which medical equipment has been handled, how much cost has been invested, and the time, manpower, money and resources required for the subsequent completion of the project.
He needs to report on the progress of the current project that has been completed, such as the evaluation of the application and the inventory of the physical equipment. Then needs to explain what are the challenges facing the project at this point. For example, incomplete program inventory, insufficient testing resources, and other things that are still outstanding. Finally, he should present his needs, i.e., the help he needs to accomplish his goals. For example, management needs to reallocate resources or assign more people to the Millennium Bug project. There is also a need to reprioritize the projects so that the Millennium Bug project is at the centre of attention.
1. Report on the current progress of the project;
2. Report current challenges, such as the project’s low priority and the complexity of the system making the project difficult to push;
3. Request for a higher priority and ask for more resource allocation;
4. Emphasize the importance and urgency of the project;
5. Express confidence in completing the project and achieving full-year 2000 compliance by December 31, 1999 with senior management’s support.
In Fletcher-Allen’s Y2K project, progress has been made in the inventory of IS and clinical equipment. However, there are difficulties in the inventory of departmental applications, high costs for remediating legacy systems, and resource-intensive external emergency measures. Currently, risks such as project delays, resource shortages, lack of departmental compliance, supplier instability, and priority confusion exist. Technical testing has been postponed, and the Meditech migration is uncertain. It is recommended that the Board reallocate resources to prioritize remediation, expand the team, establish an emergency fund, add compliance clauses to contracts, strengthen supervision, and issue a CEO-endorsed priority document. Although some achievements have been made, the unresolved departmental and external risks pose significant threats. Support from the Board is required; otherwise, costs will increase and patient safety will be endangered.
1. Current Status (Honest Assessment)：Report current status, project details.
2. Risks of Inaction: (explain the Y2K potential impact, current challenge, current existing problems. )
3. Ask for Support: (a higher priority or more resource allocation. )
Bob Sadlemieux should update the board on the Y2K project progress by first outlining its scope: detailing the systems and clinical equipment included (such as HIS, administrative applications, and ~6,000 medical devices), as well as any third-party vendors or personnel involved in compliance efforts. He must emphasize the project’s urgency by explaining the Y2K problem—specifically how date-related system failures could disrupt hospital operations, patient care, and incur legal/financial risks. For progress, he should itemize achievements like upgraded systems, remediated medical equipment, total costs incurred, and the remaining resources needed: specifying the timeline, staffing, budget, and infrastructure required to complete the project by the deadline. This comprehensive report will enable the board to understand the project’s scale, risks, and ongoing needs for informed decision-making.
At the June board meeting, Bob Sadlemire should report that 107 IS-supported applications have been inventoried and 4,000 clinical devices submitted for VHA compliance checks, with IDX and Peoplesoft projects progressing. However, departmental application remediation remains stalled, hardware checks are delayed, and a $400,000 device needs replacement. Risks include $26–40 million in potential payment delays from non-compliant payors, patient care disruptions, and legal liabilities. He should request 2 engineers from other projects and an extra $100,000 for HIS repairs, aiming to complete departmental app inventories by Q3 1998 and critical device fixes by Q1 1999. Citing a neighboring hospital’s Y2K failure as a warning, he should propose deferring non-essential infrastructure work. Additionally, he must present a New Year’s Eve manual date-switching plan with 10 nurses trained for emergencies, pledging to forfeit 5% of project bonuses if compliance isn’t certified by November 1999.
Tell them we’ve made some headway, but we’re still facing major hurdles. Mention the delays with critical projects like Meditech and the fact that hardware work is being pushed aside for other stuff.
Also, let them know that some managers aren’t taking Y2K seriously enough, and we’re running short on resources. But most importantly, stress how risky this is. If we don’t get our act together, the whole system could crash when the clock strikes 2000. We need their support to reprioritize and get the resources we need.
I believe Bob Sadlemire should clearly convey the following three core messages to the board:
1. Current progress: The key systems (such as HIS) have been thoroughly inspected, but there are still a large number of clinical equipment and department applications that have not completed the compliance verification, and some core projects (such as the Meditech system replacement) have a risk of delay;
2. Urgent threat: If not addressed promptly, the Y2K issue could lead to malfunctions of medical equipment, paralysis of the financial system, and even affect patient safety (referencing FDA warnings and cases of suppliers’ non-cooperation);
3. Action requirements:
Suspend non-urgent projects (such as network upgrades), and prioritize the allocation of manpower/funds for Y2K remediation.
At the June meeting, Bob Sadlemire should inform the Board of Trustees of the Y2K project’s progress, including the completion of inventories for critical systems and equipment and the launch of remediation plans, while highlighting challenges such as delays in replacing legacy systems, resource conflicts, and incomplete inventories of departmental applications. He must emphasize the systemic risks of Y2K issues to patient care, legal liability, and cash flow, recommending prioritization of compliance through strengthened risk assessment, integration of remediation into ongoing projects, implementation of cross-departmental accountability, and leveraging external resources to avoid operational disruptions and ensure completion of remediation by mid-1999. He should also report matters requiring the Board’s support, requesting a budget exceeding $100,000 for HIS system code remediation and coordinating resource prioritization to ensure the Y2K project is not sidelined by other initiatives.
At the June meeting, Sadlemire should first outline progress: inventory of IS-supported apps near-complete, clinical equipment assessment underway via VHA, and task forces formed. But he must stress critical risks: 4,000+ clinical devices need testing/upgrading, a $400K nuclear machine may require replacement, and departmental app inventories remain incomplete. He should highlight delays in technical upgrades due to competing infrastructure projects and warn that $26–$40M in payments could be delayed if payors aren’t compliant. Sadlemire must emphasize Y2K’s urgency, noting it’s treated as secondary to other projects, and request board support to prioritize resources, mandate cross-departmental accountability, and ensure timely remediation before 2000.
Bob Sadlemire should report at the June board meeting:
Progress: Indicates the status of the Y2K project’s initiation, progress, or completion, such as system evaluation, repair progress, and investment of human and financial resources.
Risk Challenge: Clarify compliance risks (systems, finance, reputation, etc.), as well as technical and coordination challenges encountered and response measures.
Future plan: List the remaining project timeline and key milestones, propose resource requirements (such as funding and manpower), and seek support from the board of directors.
Transparent communication: Clearly explain the communication situation and feedback impact of internal and external stakeholders, as well as the reporting mechanism to the board of directors in the future.
Sadlemire should report to the board on the progress and risks of the Y2K project: 107 IS applications have been thoroughly checked, but there are still omissions at the departmental level, and 4,000 medical devices are awaiting assessment. The Peoplesoft conversion is proceeding as planned, but the Meditech project is time-critical. The technical team has postponed the Y2K hardware work due to the infrastructure upgrade. Risks include delayed payments from the payers, equipment replacement costs, and compliance loopholes. It is recommended to allocate resources from the infrastructure project, mandate departments to submit the inventory reports, include compliance clauses in the contract, apply for a $1 million budget and establish a supervision committee. Risks need to be quantified to prompt the board’s attention and prevent system failures in 2000 from endangering patient safety and hospital operations.
Key Messages for Bob to Share with the Board of Trustees in June:
1. Current Progress (June 1998)
Completed:
Inventory of 4,000 medical devices (via VHAseCURE.net).
Vendor compliance checks for critical systems (e.g., IDX, Peoplesoft).
in Progress:
Testing for life-critical equipment (planned late 1998).
Facilities inventory (ongoing, ~50% complete).
2. Major Risks & Challenges
Meditech Clinical Rollout: Scheduled for June 1999 (tight deadline).
Device Testing: 60% untested; nuclear medicine equipment non-compliant.
Resource Conflicts: Y2K work competes with telemedicine/infrastructure projects.
3. Urgent Needs
Approval to pause non-critical IT projects (free up staff for Y2K).
Additional budget for device upgrades (e.g., $400K nuclear medicine replacement).
Leadership mandate to enforce department-level compliance.
4. Bottom-Line Assurance
70% confidence in full compliance by 12/31/1999—if Meditech stays on track.
Contingency Plan: Manual workarounds ready for worst-case delays.
They should report project status—completed tasks and ongoing work—highlight urgent Y2K risks. Propose freezing non-critical projects (e.g., telemedicine), reallocating resources to Y2K, and seeking funding for HIS repairs/equipment upgrades to address immediate compliance threats and prioritize system stability.
When reporting to the board of directors, it is essential to emphasize that the initial inventory of core systems and medical equipment has been completed, and key projects are progressing as planned. However, significant risks are present, including tight schedules for clinical systems, 40% of medical equipment awaiting inspection, and unconfirmed third-party compliance. It is imperative that the board prioritize Y2K as the top priority, approve resource allocation and emergency funds, and establish a direct accountability mechanism. Otherwise, serious consequences such as equipment failures, financial disruptions, and legal risks will be faced. It is recommended to immediately suspend non-urgent projects and fully focus on ensuring compliance modifications are completed before the year 2000.
At the June meeting, Sadlemire should tell the Board: We’ve started forming teams and inventorying systems, but key upgrades like Meditech might miss deadlines. Critical equipment (like a $400K nuclear machine) needs replacing, and many departmental apps haven’t been checked. Tech upgrades face software compatibility issues, and old PCs are being reused, complicating testing. Vendors and payors could delay $40M in funds if they fail. This isn’t just an IT problem—we need urgent cross-team focus, or patient care and operations are at risk.
I think the followings can be included:
1.Current progress: What have done shows stakeholders the progress and also offer confidence for staff to complete the project. Besides, Showing what have not done can push employees and make better resources allocation in the whole busienss.
2.Solve the main problems and inform the current main risk: meeting is an excellent opportunity to concentrate everyone’s thought and deal with complex and collaboration-required items. Also, people who focus on his ow work may have no idea with other works and risks, thus meeting is here to notice them main risks.
3.Synchronous the priority: for the slow progress and difficulty to push, employees and critical individual’s working priority should be emphasized, through informing the consequences of inactions, like cashflow’s problem, lawsuits, patient safety,etc.
During the June meeting, Bob Sadlemire should concisely summarize the Y2K project’s progress since the last update, covering completed inventory preparation and analysis phase work. He should highlight identified critical systems and equipment while emphasizing key risks and mitigation gaps—such as resource conflicts, accountability lapses, and testing limitations imposed by the Board. The presentation should strategically request the Board’s support by balancing confidence in the plan with transparent communication about realistic management expectations.
What Bob Sadlemire Should Tell the Board of Trustees
1. Critical Risk Alert: Quantify Y2K Delay Impacts
Progress Gaps:
Only 50% assets inventoried (vs. industry 80%) → 40% critical devices (e.g., ventilators) unassessed.
0% systems tested (industry target: 30% by now).
Potential Losses (per BIA):
Financial: Day-1 outage loss ≥5M;annualexposure120M.
Legal: Medical malpractice suits ≈$20M/case (FDA precedents).
Reputational: 40% customer churn risk (peer incident data).
2. Root Cause: Priority Misalignment Starving Resources
Resource Diversion Evidence:
5 FTEs on Y2K vs. 50 on new outpatient building (Capex reports).
$2M Y2K budget reallocated to EMR customization (financial logs).
Governance Failures:
Y2K excluded from executive KPIs (compensation committee docs).
Zero clinical staff in Y2K decisions (12 committee meetings, no MDs).
3. 90-Day Rescue Plan
Immediate Actions:
Measure Resources Needed Outcome
Freeze non-critical projects (e.g., cafeteria) Free $1.5M funding Launch test lab next week
Outsource legacy COBOL fixes $500K contract Fix payroll system in 60 days
Form clinical risk team (MDs + engineers) 2 FTEs Assess ICU devices in 2 weeks
Board Decisions Required:
Approve: $3M emergency fund + pause EMR customization (free 15 engineers).
Mandate: Y2K priority overrides all projects (CEO arbitrates conflicts).
Accountability: Tie Y2K progress to executive bonuses (30% weighting).
4. Escalation Mechanism: Transparent Monitoring
Board Oversight Tools:
Weekly Y2K dashboard: Red/amber/green status for critical systems (e.g., ventilator patches).
Independent audits: Deloitte monthly verification.
Contingency Plan:
If progress <70% by September, activate patient diversion (transfer high-risk services to compliant hospitals).
Based on the case evidence, Bob Sadlemire’s briefing to the Board should balance transparency about critical risks with actionable recommendations, while leveraging the PCSI agenda (Exhibit 9) as a framework. Here’s what he should emphasize:
1.Start with a Reality Check: Progress vs. Peril
2.Flag Three “Make-or-Break” Risks
3.Direct Requests to the Board
4.Close with a Patient-Safety Ultimatum