Skill UI

This deep dive guide provides comprehensive strategies and detailed checklists for migrating to the OpenEvidence platform. It covers various migration methods, such as parallel run, Strangler fig, and Big bang approaches. The guide assists technical teams in planning the transition by addressing key areas including API mapping, data migration plans, rollback procedures, and performance baselines, ensuring a secure and smooth transition for healthcare IT systems.

This guide outlines the strict multi-environment setup for the OpenEvidence clinical AI system, crucial for maintaining HIPAA compliance. It details how to configure and validate separate environments (Development, Staging, Production) to manage different data classifications—synthetic, de-identified, and full PHI. The process emphasizes environment validation checks, BAA adherence, and robust audit logging to prevent regulatory violations and PHI exposure.

Provides comprehensive observability for OpenEvidence, a system delivering critical clinical evidence queries. It monitors key metrics such as query response latency (p95), evidence freshness, citation accuracy, and compliance audit logs (HIPAA). Essential for ensuring timely, accurate, and regulatory-compliant patient care information retrieval.

This guide provides comprehensive strategies for optimizing API interactions with OpenEvidence. It covers implementing robust caching mechanisms (TTL management), efficient batch retrieval of citations, connection pooling, and handling rate limits. By applying these techniques, users can significantly reduce query latency, ensuring smooth system performance even when handling complex multi-condition queries or large citation batches.

This comprehensive checklist guides the secure and compliant deployment of OpenEvidence, a clinical decision support system. It covers critical requirements for handling Protected Health Information (PHI), including HIPAA-grade security, robust API integration best practices, mandatory monitoring setup, and resilience testing. Use this guide to ensure your healthcare-adjacent system meets the highest standards of compliance and reliability.

This guide demonstrates how to implement robust rate limiting and retry logic for critical healthcare APIs using a token bucket pattern. It covers managing specific service limits (e.g., clinical queries, evidence synthesis) and implementing strategies like exponential backoff and batch processing to ensure graceful degradation and reliable data retrieval in clinical decision support systems.

This comprehensive reference architecture guides the integration of OpenEvidence into clinical decision support systems (CDS). It is designed for healthcare platforms needing evidence-based query processing, deterministic citation tracking, and full audit logging. Key considerations include HIPAA compliance, optimizing for sub-second response times in point-of-care workflows, and establishing robust data models and event pipelines.

This guide provides comprehensive documentation and code examples for integrating OpenEvidence webhooks. Learn how to subscribe to real-time events (e.g., query completion, evidence updates, new citations) to keep clinical decision support systems fresh. Use these webhooks to trigger downstream audit workflows and ensure immediate data synchronization.

This skill provides comprehensive, structured audit logging for OpenRouter API interactions. It automatically captures essential metadata like total cost, token usage, model details, latency, and status, while also performing PII redaction. The resulting audit trail is stored in an append-only SQLite database, making it ideal for building compliance-ready systems, detailed cost monitoring, and deep debugging of production environments.

This skill provides comprehensive strategies for implementing robust caching mechanisms for OpenRouter API calls. It covers in-memory caching using Python, persistent caching with Redis for scalability, and utilizing provider-specific features like Anthropic prompt caching. By implementing deterministic key generation and managing Time-To-Live (TTL), developers can significantly reduce API costs and improve application latency when handling repetitive or similar LLM queries, making it ideal for RAG systems and high-volume applications.

A comprehensive guide on implementing failover and fallback mechanisms for Large Language Models (LLMs) when using OpenRouter. This skill covers native model fallbacks, provider routing strategies, and advanced client-side fallback chains. Use this pattern when building mission-critical or highly resilient systems that must maintain service availability even if a primary model or an entire provider goes offline. It ensures robust API integration and graceful degradation.

Implements standardized function/tool calling across various large language models (LLMs) via OpenRouter. This unified approach allows developers to build sophisticated, multi-step agents and complex workflows, regardless of the underlying provider (e.g., GPT-4o, Claude 3.5). It simplifies the process of achieving structured output and tool-augmented reasoning in production systems.