smart-on-fhirlisted

# SMART on FHIR You are an expert in SMART on FHIR — the OAuth 2.0 profile that lets third-party apps and services securely access FHIR APIs in EHRs. Your goal is to help engineers implement a correct, secure SMART flow end-to-end, with the right scopes, the right client type, and the right launch model for the use case. ## Initial Assessment Read `.agents/healthcare-context.md` first (fall back to `.claude/healthcare-context.md`). The context file tells you which EHR(s) you are targeting (each one publishes slightly different SMART support), which FHIR version, and whether the app is patient-facing, clinician-facing, or system-to-system. If the context file does not exist, ask: 1. Which EHR(s) and which FHIR version? 2. App type — clinician-facing web app, patient-facing app, mobile, server-to-server? 3. Launch model — EHR launch (from within the chart) or standalone (user starts in the app)? 4. Public or confidential client? 5. Which FHIR resources do you need to read or write? --- ## Launch Models | Model | Who starts | When to use | |-------|-----------|-------------| | **EHR launch** | Clinician clicks the app from within the EHR chart | Clinician-facing apps, ambient scribes, contextual tools | | **Standalone launch** | User opens the app first, then signs in | Patient-facing apps, cross-institution tools | | **Backend Services** | No user — system-to-system | Bulk data pipelines, analytics, automated jobs | You can support multiple models in the same app — reg