Lessons Learned and Records Retention at Hospital System Closure
A hospital completes a 22-month electronic health record rollout across three campuses. The project closure is in 10 working days. The lessons-learned register contains 180 items, mostly written as vague complaints; 35 have no owner, and several contradict each other. The PMO wants to archive everything in the project repository and hand a summary to the operations team. Legal has placed a hold on contract correspondence because of a dispute with a vendor over interface defects. The records schedule requires retention for seven years after go-live for validation, training, and audit records, but drafts and duplicates should be destroyed. The repository contains 12,000 files, including personal notes, duplicate scans, and final signed acceptance documents. The next similar rollout starts in four months, and the organization has no standard closure checklist.
1. Recommend what to retain, what to archive, and what to dispose of. How would you handle the legal hold and the seven-year retention requirement?
Read the worked answer
Separate records by value, legal status, and retention class. Retain and archive final signed acceptance documents, validation evidence, configuration baselines, training records, audit responses, interface defect records, and key governance decisions for the required seven years. Archive them read-only with metadata, an index, and a clear custodian. Dispose of transitory drafts, duplicate scans, personal notes, and superseded working files only after confirming they are not part of the legal hold or needed as evidence. The legal hold overrides the normal schedule for contract correspondence and interface-defect evidence: preserve those records in place or in a quarantined hold set, suspend deletion, and notify custodians. Do not archive the entire 12,000-file repository indiscriminately; that creates cost and discovery risk. Build a closure index that maps record classes to locations, retention periods, and disposal eligibility. Have legal and the records manager sign off before any deletion. The ten-day deadline is tight, so prioritize the hold and the high-risk record classes first, and document what remains for later cleanup.
2. The lessons-learned register is largely unusable. How would you salvage it into something the next rollout can act on before closure?
Read the worked answer
Treat the register as raw input, not a deliverable. Triage the 180 items into themes such as interface testing, vendor management, clinical validation, training, and governance. Merge duplicates and separate symptoms from causes. Validate the themes in a short facilitated session with representative leads from each campus and the operations team; ask what they would do differently and what must be repeated. Convert only a small number into reusable lessons: a lesson should state the context, what happened, why, the recommendation, and the conditions under which it applies. Assign owners for actions that can be completed before closure and route longer-term actions to the next program. Publish 10–15 lesson cards rather than 180 entries, each linked to supporting evidence where appropriate. Do not force consensus on contradictory items; record the disagreement and the decision. Capture the lessons in a searchable organizational repository and schedule a pre-start review for the next rollout. The test is whether the next team can use the lessons at planning time, not whether the register is complete.
3. Define the governance roles and closure controls needed to prevent this situation recurring. What should the next program do differently at start-up?
Read the worked answer
Assign clear roles: the project sponsor accountable for closure outcomes; a records or information manager responsible for the retention schedule and legal holds; legal responsible for hold scope and release; workstream leads responsible for record quality in their areas; and a lessons owner responsible for converting findings into reusable guidance. At closure, require a checklist with evidence: final accepted deliverables identified, hold confirmed, retention classes applied, duplicates and drafts disposed of only with approval, lessons reviewed and published, and repository permissions changed to read-only for archived records. The next program should start with a records plan and a lessons process, not add them at the end. That means defining record classes and owners at kickoff, requiring decision records and acceptance evidence as part of normal work, and scheduling lessons reviews at phase gates. Include a closure drill or audit before the final month. Also establish a light lessons review board with operations and a future-program representative so lessons are challenged for reuse value. Governance should make good recordkeeping the path of least resistance; otherwise closure becomes a rushed cleanup under legal risk.