openevidence-incident-runbook
Execute OpenEvidence incident response procedures with triage, mitigation, and postmortem. Use when responding to OpenEvidence-related outages, investigating errors, or running post-incident reviews for clinical AI integration failures. Trigger with phrases like "openevidence incident", "openevidence outage", "openevidence down", "openevidence emergency", "clinical ai broken".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- openevidence-incident-runbook
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Execute OpenEvidence incident response procedures with triage, mitigation, and postmortem. Use when responding to OpenEvidence-related outages, investigating errors, or running post-incident reviews for clinical AI integration failures. Trigger with phrases like "openevidence incident", "openevidence outage", "openevidence down", "openevidence emergency", "clinical ai broken".
- allowed-tools
- Read, Grep, Bash(kubectl:*), Bash(curl:*)
- compatible-with
- claude-code, codex, openclaw
02 资源文件 1
- 参考文档references/implementation.md2.1 KB
03 SKILL.md 正文
OpenEvidence Incident Runbook
Table of Contents
Overview
Rapid incident response procedures for OpenEvidence clinical AI integration outages in healthcare environments. Includes severity classification, triage steps, error-specific remediation, fallback procedures, and postmortem templates.
Prerequisites
- Access to OpenEvidence status page
- kubectl access to production cluster
- Prometheus/Grafana access
- PagerDuty or on-call system access
Severity Levels
| Level | Definition | Response Time | Examples |
|---|---|---|---|
| P1 | Complete outage | < 15 min | API unreachable, all queries failing |
| P2 | Degraded service | < 1 hour | High latency, partial failures |
| P3 | Minor impact | < 4 hours | DeepConsult delays, webhook issues |
| P4 | No user impact | Next business day | Alert noise, logging issues |
Critical Note
OpenEvidence outages may affect clinical decision-making. Always communicate clearly with clinical staff, ensure fallback procedures are known, and document any clinical impact.
Instructions
Step 1: Initial Assessment (2 minutes)
Check OpenEvidence status page, your integration health endpoint, error rate metrics, and recent error logs.
Step 2: Follow Decision Tree
- API errors + OpenEvidence status incident -> Enable fallback, wait for resolution
- API errors + no status incident -> Check credentials, config, network
- No API errors + unhealthy service -> Infrastructure issue (pods, memory, network)
Step 3: Apply Error-Specific Remediation
- 401/403: Verify API key, rotate if needed, restart pods
- 429: Enable request queuing, contact OpenEvidence for limit increase
- 500/503: Enable graceful degradation, notify clinical staff
- Timeout: Increase timeout temporarily, check network latency
Step 4: Enable Fallback
Return helpful message directing to UpToDate, DynaMed, or clinical guidelines directly.
Step 5: Communicate
Notify clinical staff via Slack/Teams and email. Update status page.
Step 6: Post-Incident
Collect evidence (logs, metrics, alerts), run postmortem with clinical impact assessment, create action items.
Output
- Quick triage procedure completed
- Issue identified and categorized
- Remediation applied
- Clinical staff notified
- Evidence collected for postmortem
Error Handling
| Error Type | Quick Fix |
|---|---|
| 401/403 Auth | kubectl create secret with new key, kubectl rollout restart |
| 429 Rate Limit | kubectl set env RATE_LIMIT_MODE=queue |
| 500/503 Server | kubectl set env OPENEVIDENCE_FALLBACK=true |
| Timeout | kubectl set env OPENEVIDENCE_TIMEOUT=60000 |
Examples
One-Line Health Check
set -euo pipefail
curl -sf https://api.yourhealthcare.com/health/openevidence | jq '.status' || echo "UNHEALTHY"
Enable/Disable Fallback
set -euo pipefail
kubectl set env deployment/clinical-evidence-api OPENEVIDENCE_FALLBACK=true # Enable
kubectl set env deployment/clinical-evidence-api OPENEVIDENCE_FALLBACK=false # Disable
See detailed implementation for advanced patterns.
Resources
04 同仓库更多 Skills
zustand-store-ts
Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state/action separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.
zustand-store-creator
Zustand Store Creator - Auto-activating skill for Frontend Development. Triggers on: zustand store creator, zustand store creator Part of the Frontend Development skill category.
zero-trust-config-helper
Zero Trust Config Helper - Auto-activating skill for Security Advanced. Triggers on: zero trust config helper, zero trust config helper Part of the Security Advanced skill category.
zapier-integration-helper
Zapier Integration Helper - Auto-activating skill for Business Automation. Triggers on: zapier integration helper, zapier integration helper Part of the Business Automation skill category.
zai-cli
Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP. Use when user needs image/video analysis, OCR, UI-to-code conversion, error diagnosis, real-time web search, web page to markdown extraction, or GitHub code exploration. Trigger with phrases like "analyze this image", "search the web for", "read this page", "explore this repo", or "use zai". Requires Z_AI_API_KEY.
yt-research
Research competitor YouTube channels, niches, and trending topics for your content strategy. Use this skill whenever the user says "research channels", "analyze competitors", "find trending topics", "niche analysis", "competitive research", "what are other creators doing", "scrape YouTube channels", or wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.