A public-health chatbot lacks decommissioning criteria when the vaccine campaign ends. What should the auditor emphasize?
Select an answer to reveal the explanation.
Short Explanation
When the campaign ends, the chatbot should not become a zombie giving last season's advice. Write decommissioning criteria up front. Forever-online is not a retirement plan.
Full Explanation
Defining end-of-life and decommissioning criteria for the civic public-health chatbot when the vaccine campaign purpose ends works because AI solutions inherit the lifespan of the business need they serve. Campaign-specific guidance on eligibility, sites, and timing becomes stale or harmful if the bot remains online after the campaign closes. Planned decommissioning covers content freeze or archive, model and prompt retirement, data disposition, redirect messaging for residents, and owner accountability. The correct emphasis is lifecycle completeness: birth and death of the solution are both control points.
Extending chatbot performance monitoring to track residual vaccine uptake trends for planning the next campaign cycle fails because continued monitoring does not retire the live, resident-facing answers; the bot keeps serving stale campaign guidance to the public even while metrics are gathered for future planning. Migrating the approved chatbot content to the central public health department portal under scheduled clinical review fails conceptually: the AI channel is often the higher-trust, more interactive surface and must be retired with—or before—content migration, not merely relocated to a portal where it may still surface outdated guidance. Documenting detailed model version history and training data sources to support campaign audit traceability reviews fails because documentation alone is not a retirement trigger; the bot can keep serving stale guidance while records are compiled.
Exam caveat: some campaign knowledge may need archival access for historians or auditors without remaining a live advisory channel—decommissioning should distinguish offline archive from resident-facing inference. Operational check: write decommission triggers (campaign end date, superseding guidance, owner sign-off), execute a shutdown runbook with content takedown verification, and confirm the bot returns a clear retirement message instead of outdated advice.