abridge-upgrade-migration

# Abridge Upgrade & Migration ## Overview Procedures for upgrading Abridge API integrations and migrating between EHR systems. Healthcare migrations are high-risk — clinical documentation cannot have gaps. ## Common Migration Scenarios | Scenario | Complexity | Downtime | Risk | |----------|-----------|----------|------| | API version bump (v1 → v2) | Medium | Zero (dual-version) | Low | | EHR migration (Epic → Athena) | High | Planned window | High | | New specialty onboarding | Low | Zero | Low | | Note template changes | Medium | Zero | Medium | | Multi-site rollout | High | Per-site windows | Medium | ## Instructions ### Step 1: API Version Migration ```typescript // src/migration/api-version-adapter.ts // Dual-version adapter for zero-downtime API upgrades interface ApiVersionConfig { v1BaseUrl: string; // Current production v2BaseUrl: string; // New version (canary) canaryPercent: number; // Percentage of traffic to v2 } class AbridgeVersionAdapter { constructor(private config: ApiVersionConfig) {} getBaseUrl(): string { // Gradual canary rollout const useV2 = Math.random() * 100 < this.config.canaryPercent; return useV2 ? this.config.v2BaseUrl : this.config.v1BaseUrl; } // Map v1 response to v2 format (or vice versa) normalizeNoteResponse(response: any, version: 'v1' | 'v2'): any { if (version === 'v1') { return { ...response, // v2 adds quality_metrics — provide defaults for v1 quality_metrics...