[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M754TJTHWP1C9S62CBC52YZF":3,"skill-same:01M754TJTHWP1C9S62CBC52YZF":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M754TJTHWP1C9S62CBC52YZF","openevidence-migration-deep-dive",null,"Execute complex OpenEvidence migrations including EHR integration, data migration, and system transitions.\nUse when migrating from legacy clinical decision support systems, integrating with new EHRs,\nor performing major platform transitions.\nTrigger with phrases like \"openevidence migration\", \"ehr integration\",\n\"migrate to openevidence\", \"clinical ai migration\", \"legacy cds migration\".","SamuelChien\u002Fmega-skills-collection","SamuelChien","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F4652114?v=4","01M74KK34WVHA0P5ZYSJRDDFMG","Samuel Chien","01M74KK35FQN1N9VZ9EPTH3P2S",0,"MIT","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fopenevidence-migration-deep-dive\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: openevidence-migration-deep-dive\ndescription: |\n  Execute complex OpenEvidence migrations including EHR integration, data migration, and system transitions.\n  Use when migrating from legacy clinical decision support systems, integrating with new EHRs,\n  or performing major platform transitions.\n  Trigger with phrases like \"openevidence migration\", \"ehr integration\",\n  \"migrate to openevidence\", \"clinical ai migration\", \"legacy cds migration\".\nallowed-tools: Read, Write, Edit, Bash(npm:*), Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# OpenEvidence Migration Deep Dive\n\n## Table of Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nExecute complex migrations including legacy CDS system transitions, EHR integrations (Epic\u002FCerner), and multi-site deployments for OpenEvidence clinical AI.\n\n## Prerequisites\n- Access to both source and target systems\n- Downtime window approved (if required)\n- Rollback plan documented\n- Clinical staff communication plan\n\n## Migration Scenarios\n\n| Scenario | Complexity | Downtime | Duration |\n|----------|------------|----------|----------|\n| Legacy CDS to OpenEvidence | High | 4-8 hours | 2-4 weeks |\n| Add EHR Integration | Medium | None | 1-2 weeks |\n| Multi-site Expansion | Medium | None | 1-2 weeks |\n| API Version Upgrade | Low | None | 1-3 days |\n\n## Instructions\n\n### Step 1: Assess Legacy System\nAudit current usage (daily queries, peak rate, unique users), map features, identify integrations (EHR, SSO, audit), and determine data migration scope (saved searches, preferences, audit logs -- required for HIPAA).\n\n### Step 2: Implement Parallel Running\nCreate `ParallelRunner` that queries OpenEvidence as primary, optionally queries legacy for comparison (configurable ratio). Log comparison metrics (response time, confidence, citation count) without PHI. Auto-fallback to legacy on OpenEvidence failure.\n\n### Step 3: Migrate Data\nRun migration jobs for users (with role mapping), user preferences, and audit logs (HIPAA required). Use upsert for idempotency, batch processing for audit logs (10k per batch), and progress tracking.\n\n### Step 4: Integrate with EHR (Epic\u002FCerner)\nConfigure SMART on FHIR with appropriate scopes. Implement CDS Hooks endpoints for `patient-view` and `medication-prescribe`. Extract conditions and medications from FHIR prefetch data for OpenEvidence queries.\n\n### Step 5: Configure Multi-Site\nDefine per-site configuration: siteId, region, OpenEvidence orgId, EHR system, feature flags, and quotas. Support different tiers per site.\n\n### Step 6: Execute Cutover\nFollow migration checklist: pre-migration (approvals, backups, test env), during (parallel run, data migration, EHR testing), post (decommission legacy, train staff, document lessons).\n\n## Output\n- Legacy system assessment and feature mapping\n- Parallel running with comparison metrics\n- Data migration scripts (users, preferences, audit logs)\n- EHR integration (SMART on FHIR, CDS Hooks)\n- Multi-site configuration\n- Migration checklist\n\n## Error Handling\n| Migration Issue | Detection | Resolution |\n|-----------------|-----------|------------|\n| Data corruption | Validation checks | Restore from backup |\n| SSO failure | Auth errors | Verify IdP configuration |\n| EHR integration fails | CDS Hook errors | Check FHIR endpoints |\n| Performance regression | Metrics comparison | Optimize or rollback |\n\n## Examples\n\n### CDS Hook Discovery\n```json\n{\n  \"services\": [\n    { \"id\": \"openevidence-clinical-decision-support\", \"hook\": \"patient-view\" },\n    { \"id\": \"openevidence-drug-interaction\", \"hook\": \"medication-prescribe\" }\n  ]\n}\n```\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for advanced patterns.\n\n## Resources\n- [SMART on FHIR](https:\u002F\u002Fsmarthealthit.org\u002F)\n- [CDS Hooks](https:\u002F\u002Fcds-hooks.hl7.org\u002F)\n- [Epic App Orchard](https:\u002F\u002Fappmarket.epic.com\u002F)","# OpenEvidence Migration Deep Dive\n\n## Table of Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nExecute complex migrations including legacy CDS system transitions, EHR integrations (Epic\u002FCerner), and multi-site deployments for OpenEvidence clinical AI.\n\n## Prerequisites\n- Access to both source and target systems\n- Downtime window approved (if required)\n- Rollback plan documented\n- Clinical staff communication plan\n\n## Migration Scenarios\n\n| Scenario | Complexity | Downtime | Duration |\n|----------|------------|----------|----------|\n| Legacy CDS to OpenEvidence | High | 4-8 hours | 2-4 weeks |\n| Add EHR Integration | Medium | None | 1-2 weeks |\n| Multi-site Expansion | Medium | None | 1-2 weeks |\n| API Version Upgrade | Low | None | 1-3 days |\n\n## Instructions\n\n### Step 1: Assess Legacy System\nAudit current usage (daily queries, peak rate, unique users), map features, identify integrations (EHR, SSO, audit), and determine data migration scope (saved searches, preferences, audit logs -- required for HIPAA).\n\n### Step 2: Implement Parallel Running\nCreate `ParallelRunner` that queries OpenEvidence as primary, optionally queries legacy for comparison (configurable ratio). Log comparison metrics (response time, confidence, citation count) without PHI. Auto-fallback to legacy on OpenEvidence failure.\n\n### Step 3: Migrate Data\nRun migration jobs for users (with role mapping), user preferences, and audit logs (HIPAA required). Use upsert for idempotency, batch processing for audit logs (10k per batch), and progress tracking.\n\n### Step 4: Integrate with EHR (Epic\u002FCerner)\nConfigure SMART on FHIR with appropriate scopes. Implement CDS Hooks endpoints for `patient-view` and `medication-prescribe`. Extract conditions and medications from FHIR prefetch data for OpenEvidence queries.\n\n### Step 5: Configure Multi-Site\nDefine per-site configuration: siteId, region, OpenEvidence orgId, EHR system, feature flags, and quotas. Support different tiers per site.\n\n### Step 6: Execute Cutover\nFollow migration checklist: pre-migration (approvals, backups, test env), during (parallel run, data migration, EHR testing), post (decommission legacy, train staff, document lessons).\n\n## Output\n- Legacy system assessment and feature mapping\n- Parallel running with comparison metrics\n- Data migration scripts (users, preferences, audit logs)\n- EHR integration (SMART on FHIR, CDS Hooks)\n- Multi-site configuration\n- Migration checklist\n\n## Error Handling\n| Migration Issue | Detection | Resolution |\n|-----------------|-----------|------------|\n| Data corruption | Validation checks | Restore from backup |\n| SSO failure | Auth errors | Verify IdP configuration |\n| EHR integration fails | CDS Hook errors | Check FHIR endpoints |\n| Performance regression | Metrics comparison | Optimize or rollback |\n\n## Examples\n\n### CDS Hook Discovery\n```json\n{\n  \"services\": [\n    { \"id\": \"openevidence-clinical-decision-support\", \"hook\": \"patient-view\" },\n    { \"id\": \"openevidence-drug-interaction\", \"hook\": \"medication-prescribe\" }\n  ]\n}\n```\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for advanced patterns.\n\n## Resources\n- [SMART on FHIR](https:\u002F\u002Fsmarthealthit.org\u002F)\n- [CDS Hooks](https:\u002F\u002Fcds-hooks.hl7.org\u002F)\n- [Epic App Orchard](https:\u002F\u002Fappmarket.epic.com\u002F)",{"name":5,"author":24,"license":15,"version":25,"description":26,"allowed-tools":27,"compatible-with":28},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Execute complex OpenEvidence migrations including EHR integration, data migration, and system transitions.\nUse when migrating from legacy clinical decision support systems, integrating with new EHRs,\nor performing major platform transitions.\nTrigger with phrases like \"openevidence migration\", \"ehr integration\",\n\"migrate to openevidence\", \"clinical ai migration\", \"legacy cds migration\".\n","Read, Write, Edit, Bash(npm:*), Grep","claude-code, codex, openclaw","main","c2b1fdccc779e99ac814e55fb69ca8d71215dd0f","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection","https:\u002F\u002Fgithub.com\u002FSamuelChien","http:\u002F\u002Fsamuelchien.com\u002F","2026-05-26 08:27:14",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add SamuelChien\u002Fmega-skills-collection --skill openevidence-migration-deep-dive",{"tool":41,"command":42},"bunx","bunx skills add SamuelChien\u002Fmega-skills-collection --skill openevidence-migration-deep-dive",{"tool":44,"command":45},"pnpm","pnpm dlx skills add SamuelChien\u002Fmega-skills-collection --skill openevidence-migration-deep-dive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fopenevidence-migration-deep-dive\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fimplementation.md","REFERENCE","参考文档",1759,"https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fopenevidence-migration-deep-dive\u002Freferences\u002Fimplementation.md",[56,63,70,77,84,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M76R4WZQZAXGGXMQCA0FZ716","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M76R4T9KENDH7FENGZQHBW4G","zustand-store-creator","Zustand Store Creator - Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M76R3YWN84B7SANJ52X799ZE","zero-trust-config-helper","Zero Trust Config Helper - Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M76R3HNSV2AEYSKHM915GJ58","zapier-integration-helper","Zapier Integration Helper - Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":88,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M76R3DJSKAT4FA7DV4BF3GCE","zai-cli","Execute z.AI CLI providing vision, search, reader, and GitHub exploration via CLI and MCP.\nUse when user needs image\u002Fvideo analysis, OCR, UI-to-code conversion, error diagnosis,\nreal-time web search, web page to markdown extraction, or GitHub code exploration.\nTrigger with phrases like \"analyze this image\", \"search the web for\", \"read this page\",\n\"explore this repo\", or \"use zai\". Requires Z_AI_API_KEY.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fzai-cli\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M76R2KAM699XE9AJVAWE4H2E","yt-research","Research competitor YouTube channels, niches, and trending topics for your content strategy.\nUse this skill whenever the user says \"research channels\", \"analyze competitors\", \"find trending topics\",\n\"niche analysis\", \"competitive research\", \"what are other creators doing\", \"scrape YouTube channels\",\nor wants to understand the competitive landscape for a specific tool or topic area. Use when working with yt research. Trigger with 'yt', 'research'.","https:\u002F\u002Fgithub.com\u002FSamuelChien\u002Fmega-skills-collection\u002Fblob\u002Fmain\u002Fyt-research\u002FSKILL.md",[],[]]