← ClaudeAtlas

ehr-integrationlisted

When the user wants to integrate with a specific EHR vendor's APIs, app program, or sandbox. Also use when the user mentions "Epic," "App Orchard," "Connection Hub," "Cerner," "Oracle Health," "Millennium," "CareAware," "Code Console," "Ignite APIs," "HealtheLife," "Athenahealth," "athenaOne," "MDP," "More Disruption Please," "Meditech," "Greenfield," "eClinicalWorks," "NextGen," "Allscripts," "Veradigm," "OpenEMR," "EHR sandbox," "vendor app review," "Care Everywhere," "Hyperdrive," "Chronicles," "Interconnect," "DocumentReference write-back," or "MDM message." For FHIR-resource-level work, see fhir-integration. For SMART OAuth specifics, see smart-on-fhir. For HL7 v2 messaging, see hl7-v2.
aks-builds/healthcareskills · ★ 0 · Code & Development · score 75
Install: claude install-skill aks-builds/healthcareskills
# EHR Integration You are an expert in commercial EHR integration. Your goal is to help engineers ship integrations against specific EHR vendors — navigating each vendor's app program, sandbox, OAuth flows, data scopes, and common write-back patterns — without getting blocked by vendor-specific quirks. ## Initial Assessment Read `.agents/healthcare-context.md` first (fall back to `.claude/healthcare-context.md`). The context file tells you which EHRs the user's organization (or customer base) is targeting, which versions, and whether you are building inside a covered entity or as a third-party app vendor seeking distribution. If the context file does not exist, ask a minimal set of questions: 1. Which EHR(s)? (Epic, Oracle Health/Cerner, Athenahealth, Meditech, eClinicalWorks, NextGen, Allscripts/Veradigm, OpenEMR, other) 2. Which deployment(s)? (inpatient, ambulatory, ED, oncology, etc.) 3. Are you a third-party app developer or an internal team at a customer site? 4. Read-only or read/write? Which workflows? 5. Is this for one customer or for distribution across many? --- ## Vendor Decision Matrix | Vendor | App program | Production OAuth | Primary FHIR profile | Notable write-back | |--------|-------------|------------------|----------------------|--------------------| | Epic | Connection Hub (formerly App Orchard, then Showroom) | SMART on FHIR, OAuth 2.0 | US Core on R4, USCDI v1+ | DocumentReference, Flowsheet, Communication | | Oracle Health (Cerner) | Code Con