openevidence-multi-env-setup

# OpenEvidence Multi-Environment Setup ## Overview OpenEvidence clinical AI requires strict environment separation to maintain HIPAA compliance across the data lifecycle. Development uses only synthetic patient data with no PHI access, staging operates on de-identified datasets for clinical validation, and production handles full PHI under BAA-covered infrastructure. Each environment enforces its own audit logging, encryption, and access control policies. Misconfigured environments risk PHI exposure and regulatory violations, making environment validation a hard requirement at startup. ## Environment Configuration ```typescript const openEvidenceConfig = (env: string) => ({ development: { apiKey: process.env.OPENEVIDENCE_API_KEY_DEV!, baseUrl: "https://api.dev.openevidence.com/v1", dataClassification: "synthetic", phiEnabled: false, auditLevel: "basic", encryptionRequired: false, }, staging: { apiKey: process.env.OPENEVIDENCE_API_KEY_STG!, baseUrl: "https://api.staging.openevidence.com/v1", dataClassification: "de-identified", phiEnabled: false, auditLevel: "full", encryptionRequired: true, }, production: { apiKey: process.env.OPENEVIDENCE_API_KEY_PROD!, baseUrl: "https://api.openevidence.com/v1", dataClassification: "phi", phiEnabled: true, auditLevel: "full", encryptionRequired: true, }, }[env]); ``` ## Environment Files ```bash # Per-env files: .env.development, .env.staging, .env.production OPENEVIDENCE_API_KEY_{DEV|STG|PROD}=<api...