fhir-developer-skill

Builds a RESTful FHIR API scaffold with SMART on FHIR authorization and OperationOutcome error reporting.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/zengsihang/EHR-QA-Skill --skill fhir-developer-skill-zengsihang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fhir-developer-skill
Source: https://github.com/zengsihang/EHR-QA-Skill/tree/main/vendor/fhir-developer-skill
Command: npx skills add https://github.com/zengsihang/EHR-QA-Skill --skill fhir-developer-skill-zengsihang

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured blueprint for building compliant and interoperable RESTful FHIR APIs, including SMART on FHIR authorization, standardized error handling with OperationOutcome, and guidance for resource validation, versioning, and bundle operations.

Core Features & Use Cases

  • Templates for common FHIR resources (Patient, Observation, Encounter, Condition, MedicationRequest) with guidance on required fields, coding, and search parameters.
  • A scaffolded project structure (models, routes, helpers) and reference material to accelerate development and ensure interoperability.
  • Use cases include rapid prototyping of FHIR endpoints, validation and secure access control, and generation of auditable, provenance-aware responses.

Quick Start

Install the scaffold, set up a virtual environment, install dependencies, and run the FastAPI server to explore the FHIR API templates.

Frequently Asked Questions about fhir-developer-skill

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

FAQPage Schema
How do I build a FHIR API with SMART on FHIR authorization?

Build a FHIR API with SMART on FHIR authorization by using a scaffolded project structure with FastAPI that includes pre-built RESTful endpoints, OAuth security practices, and starter code to enforce standard access control.

What FHIR R4 resources are covered for RESTful endpoint development?

FHIR R4 endpoint development covers Patient, Observation, Encounter, Condition, and MedicationRequest resources, providing templates with required fields, coding guidance, search parameters, and pagination to ensure interoperability.

How does OperationOutcome error reporting work in FHIR APIs?

OperationOutcome error reporting in FHIR APIs uses standardized FHIR R4 structures to return validation errors and robust exception details, ensuring clients receive consistent, interoperable diagnostic responses across all endpoints.

Can I use FastAPI for healthcare API development with FHIR standards?

FastAPI supports healthcare API development with FHIR standards by running the scaffolded server to explore generated templates, enabling rapid prototyping of secure, compliant endpoints without starting from scratch.

What's the best way to implement pagination and Bundle semantics in FHIR?

Implement pagination and Bundle semantics in FHIR by leveraging the scaffolded project templates that enforce FHIR R4 structures, ensuring search results are correctly packaged and navigable across resource queries.

Why does my FHIR API need SMART on FHIR for secure access control?

FHIR APIs need SMART on FHIR for secure access control because it enforces OAuth standard security practices, providing the authorization framework required for healthcare applications to safely access protected patient data.