openevidence-deploy-integration
Provides a Docker-based deployment pattern for secure, production-ready OpenEvidence clinical service integrations.
Install
mkdir -p .claude/skills/openevidence-deploy-integration && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/4685" && unzip -o skill.zip -d .claude/skills/openevidence-deploy-integration && rm skill.zipInstalls to .claude/skills/openevidence-deploy-integration
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Deploy Integration for OpenEvidence.Key capabilities
- →Deploy containerized clinical evidence integration services
- →Configure HIPAA-conscious audit logging and data-at-rest encryption
- →Implement health checks for API connectivity
- →Execute rolling update strategies for service availability
How it works
The service uses a multi-stage Docker build to create a production-ready Node.js environment. It includes a health check endpoint that verifies API connectivity while ensuring no PHI is exposed.
Inputs & outputs
When to use openevidence-deploy-integration
- →Deploying to production environments
- →Setting up staging environments
- →Configuring audit logging for AI
- →Creating Docker containers for clinical tools
About this skill
OpenEvidence Deploy Integration
Overview
Deploy a containerized OpenEvidence clinical evidence integration service with Docker. This skill covers building a HIPAA-conscious production image that connects to the OpenEvidence API for querying clinical evidence, retrieving medical literature summaries, and validating treatment recommendations. Includes environment configuration with audit logging and data-at-rest encryption flags, health checks that verify API connectivity without exposing PHI, and rolling update strategies that maintain service availability during critical clinical query periods.
Docker Configuration
FROM node:20-slim AS builder
WORKDIR /app
COPY package*.json ./
RUN npm ci
COPY tsconfig.json ./
COPY src/ ./src/
RUN npm run build
FROM node:20-slim
RUN addgroup --system app && adduser --system --ingroup app app
WORKDIR /app
COPY --from=builder /app/dist ./dist
COPY --from=builder /app/node_modules ./node_modules
COPY package*.json ./
RUN mkdir -p /app/audit-logs && chown app:app /app/audit-logs
USER app
EXPOSE 3000
HEALTHCHECK --interval=30s --timeout=5s --retries=3 \
CMD curl -f http://localhost:3000/health || exit 1
CMD ["node", "dist/index.js"]
Environment Variables
export OPENEVIDENCE_API_KEY="oe_live_xxxxxxxxxxxx"
export OPENEVIDENCE_BASE_URL="https://api.openevidence.com/v1"
export OPENEVIDENCE_ORG_ID="org_xxxxxxxxxxxx"
export HIPAA_AUDIT_LOG="true"
export HIPAA_ENCRYPT_AT_REST="true"
export LOG_LEVEL="info"
export PORT="3000"
export NODE_ENV="production"
Health Check Endpoint
import express from 'express';
const app = express();
app.get('/health', async (req, res) => {
try {
const response = await fetch(`${process.env.OPENEVIDENCE_BASE_URL}/status`, {
headers: { 'Authorization': `Bearer ${process.env.OPENEVIDENCE_API_KEY}` },
});
if (!response.ok) throw new Error(`OpenEvidence API returned ${response.status}`);
// Health response must not contain PHI or query content
res.json({ status: 'healthy', service: 'openevidence-integration', audit: process.env.HIPAA_AUDIT_LOG === 'true', timestamp: new Date().toISOString() });
} catch (error) {
res.status(503).json({ status: 'unhealthy', error: (error as Error).message });
}
});
Deployment Steps
Step 1: Build
docker build -t openevidence-integration:latest .
Step 2: Run
docker run -d --name openevidence-integration \
-p 3000:3000 \
-v /var/log/openevidence:/app/audit-logs \
-e OPENEVIDENCE_API_KEY -e OPENEVIDENCE_BASE_URL -e OPENEVIDENCE_ORG_ID \
-e HIPAA_AUDIT_LOG=true -e HIPAA_ENCRYPT_AT_REST=true \
openevidence-integration:latest
Step 3: Verify
curl -s http://localhost:3000/health | jq .
Step 4: Rolling Update
docker build -t openevidence-integration:v2 . && \
docker stop openevidence-integration && \
docker rm openevidence-integration && \
docker run -d --name openevidence-integration -p 3000:3000 \
-v /var/log/openevidence:/app/audit-logs \
-e OPENEVIDENCE_API_KEY -e OPENEVIDENCE_BASE_URL -e OPENEVIDENCE_ORG_ID \
-e HIPAA_AUDIT_LOG=true -e HIPAA_ENCRYPT_AT_REST=true \
openevidence-integration:v2
Error Handling
| Issue | Cause | Fix |
|---|---|---|
401 Unauthorized | Invalid or expired API key | Regenerate key in OpenEvidence admin portal |
403 Forbidden | Organization access denied | Verify OPENEVIDENCE_ORG_ID matches API key scope |
404 Not Found | Evidence query endpoint unavailable | Check API version and endpoint path |
429 Rate Limited | Exceeding clinical query rate limits | Implement backoff; cache evidence responses |
| Audit log not writing | Volume mount missing or permissions | Verify /var/log/openevidence exists and is writable |
Resources
Next Steps
See openevidence-webhooks-events.
When not to use it
- →Exposing PHI in health check responses
- →Running without audit log volume mounts
Prerequisites
Limitations
- →Rate limiting requires backoff implementation
- →Audit logs require writable volume mounts
How it compares
This workflow provides a pre-configured Docker environment specifically hardened for HIPAA-compliant clinical AI deployments.
Compared to similar skills
openevidence-deploy-integration side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| openevidence-deploy-integration (this skill) | 1 | 24d | Caution | Intermediate |
| groq-deploy-integration | 1 | 24d | Review | Intermediate |
| agent-sandbox | 1 | 6mo | No flags | Intermediate |
| docker-node-version-compat-modules | 0 | 6mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
groq-deploy-integration
jeremylongshore
Deploy Groq integrations to Vercel, Fly.io, and Cloud Run platforms. Use when deploying Groq-powered applications to production, configuring platform-specific secrets, or setting up deployment pipelines. Trigger with phrases like "deploy groq", "groq Vercel", "groq production deploy", "groq Cloud Run", "groq Fly.io".
agent-sandbox
ruvnet
Agent skill for sandbox - invoke with $agent-sandbox
docker-node-version-compat-modules
Disentinel
|
DevOps Engineer Skills
lanmata
Consolidated skill set for the DevOps Engineer agent — Maven build, Docker, GitHub Actions, CI/CD orchestration, and release management
deployment-engineer
sickn33
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization. Use PROACTIVELY for CI/CD design, GitOps implementation, or deployment automation.
devops
mrgoonie
Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm). Use for serverless, containers, CI/CD, GitOps, security audit.