Implement SMART App Launch OAuth 2.0 authorization flows for FHIR applications.
npx skills add https://github.com/aehrc/pathling --skill smart-app-launch
Please help me install this Agent Skill. Skill: smart-app-launch Source: https://github.com/aehrc/pathling/tree/main/.claude/skills/smart-app-launch Command: npx skills add https://github.com/aehrc/pathling --skill smart-app-launch
This Skill provides expert guidance for securely authorizing applications to access sensitive health data within FHIR systems, ensuring compliance and user privacy.
Use the smart-app-launch skill to understand the EHR launch authorization request parameters.
High-intent search queries and answers about installing and using this skill.
SMART App Launch standardizes OAuth 2.0 authorization for FHIR applications to securely access health data. It covers EHR launch, standalone launch, and backend service flows, ensuring applications receive properly scoped tokens to read patient records from EHR systems.
EHR launch embeds the application within the provider's EHR interface, while standalone launch initiates from outside the EHR. Both utilize OAuth 2.0 authorization flows, but standalone launch requires explicit patient selection and identity provider interaction.
Handling OAuth 2.0 scopes and PKCE for FHIR applications involves defining clinical data access boundaries and using Proof Key for Code Exchange to secure public client authorization. This framework details token handling, scope management, and PKCE implementation for FHIR servers.
SMART App Launch supports backend services for FHIR server access through specialized client authentication and OAuth 2.0 flows. It provides guidance on backend service authorization, ensuring secure system-level access to health data without direct user interaction.
Discovering FHIR server capabilities for SMART App Launch authorization involves querying the server's metadata endpoint. This framework outlines capability discovery according to HL7 FHIR specifications to determine supported OAuth 2.0 endpoints and authorization scopes.
Security best practices for SMART on FHIR token handling include implementing PKCE, validating client authentication, and strictly managing OAuth 2.0 scopes. This framework addresses these security measures to ensure secure access to sensitive health data.
aks-buildsConfigure SMART on FHIR app OAuth flows with EHR launch and Backend Services.
maziyarpanahiScaffold SMART-on-FHIR apps using OAuth2 PKCE and retrieve patient clinical notes.
ISAQQSAIDevelop FHIR R4 REST endpoints with SMART on FHIR authorization and pagination.
2nth-aiIntegrate healthcare systems using FHIR, HL7, and SMART on FHIR standards.
