openevidence-deploy-integration
Deploy OpenEvidence integrations to healthcare production environments. Use when deploying to production, setting up staging environments, or configuring cloud deployments for clinical AI applications. Trigger with phrases like "deploy openevidence", "openevidence staging", "openevidence production deploy", "release openevidence".
- License 许可
- MIT
- 最近更新
- 2026-05-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- openevidence-deploy-integration
- author
- Jeremy Longshore <jeremy@intentsolutions.io>
- license
- MIT
- version
- 1.0.0
- description
- Deploy OpenEvidence integrations to healthcare production environments. Use when deploying to production, setting up staging environments, or configuring cloud deployments for clinical AI applications. Trigger with phrases like "deploy openevidence", "openevidence staging", "openevidence production deploy", "release openevidence".
- allowed-tools
- Read, Write, Edit, Bash(npm:*), Grep
- compatible-with
- claude-code, codex, openclaw
02 资源文件 1
- 参考文档references/implementation.md2.2 KB
03 SKILL.md 正文
OpenEvidence Deploy Integration
Table of Contents
Overview
Deploy OpenEvidence clinical AI integrations to production healthcare environments with canary releases, Kubernetes manifests, health checks, and rollback procedures.
Prerequisites
- CI pipeline configured (see
openevidence-ci-integration) - Production credentials from OpenEvidence
- Cloud platform configured (GCP, AWS, Azure)
- Signed BAA for production environment
Instructions
Step 1: Multi-Environment Configuration
Define environment configs (dev/staging/prod) with baseUrl, timeout, retries, secret paths, and feature flags.
Step 2: Create Deployment Workflow
Build GitHub Actions workflow with test -> build -> deploy-staging -> deploy-production stages. Use canary releases for production (no-traffic deploy, 10% canary, monitor, full rollout).
Step 3: Configure Kubernetes
Create Deployment (3 replicas), Service, Ingress, and HPA manifests. Use K8s secrets for API credentials, liveness/readiness probes against /health.
Step 4: Implement Health Checks
Create /health (basic) and /health/openevidence (deep) endpoints that verify API connectivity and report latency.
Step 5: Prepare Rollback
Create rollback script that lists recent revisions, identifies previous, and shifts traffic back with health verification.
Output
- Multi-environment deployment configuration
- CI/CD pipeline with canary releases
- Kubernetes deployment manifests (Deployment, Service, Ingress, HPA)
- Health check endpoints (basic + deep)
- Rollback procedures and scripts
Error Handling
| Deployment Issue | Detection | Resolution |
|---|---|---|
| Health check fails | Readiness probe | Rollback to previous revision |
| High error rate | Monitoring alert | Rollback, investigate logs |
| Secret missing | Container fails to start | Check secret manager |
| Rate limit hit | 429 errors spike | Scale down, check quotas |
Examples
Deploy to Staging
gcloud run deploy clinical-evidence-api-staging \
--image $IMAGE --region us-central1 \
--set-env-vars NODE_ENV=staging \
--set-secrets OPENEVIDENCE_API_KEY=openevidence-staging-api-key:latest
Rollback Production
gcloud run services update-traffic clinical-evidence-api \
--region us-central1 --to-revisions PREVIOUS_REVISION=100
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'.