smart-on-fhir

Configure SMART on FHIR app OAuth flows with EHR launch and Backend Services.

1|1|Updated May 16, 2026
One-click install
npx skills add https://github.com/aks-builds/healthcareskills --skill smart-on-fhir
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smart-on-fhir
Source: https://github.com/aks-builds/healthcareskills/tree/main/skills/smart-on-fhir
Command: npx skills add https://github.com/aks-builds/healthcareskills --skill smart-on-fhir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the complexities of building and configuring SMART on FHIR apps, ensuring secure and compliant OAuth flows and access to FHIR APIs in EHRs.

Core Features & Use Cases

  • OAuth Flow Configuration: Guides through the OAuth 2.0 flow for SMART on FHIR apps, including PKCE and state management.
  • Launch Models: Supports EHR launch, standalone launch, and Backend Services for system-to-system interactions.
  • SMART Scopes: Provides guidance on choosing the right scopes for different use cases, including v1 and v2 scope syntax.
  • Security Best Practices: Offers a comprehensive security checklist to mitigate risks in SMART app development.

Quick Start

Use the smart-on-fhir skill to configure OAuth for a SMART on FHIR app launching from an EHR chart.

Frequently Asked Questions about smart-on-fhir

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure OAuth 2.0 for a SMART on FHIR app launching from an EHR?

Configuring OAuth 2.0 for a SMART on FHIR EHR launch involves setting up PKCE and state management. This Skill guides you through securing the OAuth flow and selecting correct SMART scopes for EHR and standalone launches.

What is the difference between EHR launch and standalone launch in SMART on FHIR?

EHR launch starts your app from within the EHR user interface, while standalone launch starts independently from a portal. This Skill helps configure both models, plus Backend Services for system-to-system interactions.

Do I need OAuth 2.0 knowledge to implement SMART on FHIR security best practices?

Yes, implementing SMART on FHIR security requires knowledge of OAuth 2.0, SMART on FHIR, and FHIR APIs. This Skill provides a comprehensive security checklist to mitigate risks in SMART app development.

How do I set up Backend Services for system-to-system SMART on FHIR interactions?

Backend Services enable secure system-to-system SMART on FHIR interactions. This Skill supports configuring backend OAuth flows alongside EHR and standalone launch models for automated FHIR API access.

What are the security best practices for SMART on FHIR app development?

Security best practices for SMART on FHIR include implementing PKCE, managing state, and choosing correct scopes. This Skill offers a comprehensive security checklist to mitigate risks in SMART app development.