fhir-developer-skill

FHIR R4 resource validation requires checking field cardinality and enums, then returning an OperationOutcome structure with appropriate HTTP status codes like 422, 412, or 404 to ensure standards-compliant API behavior.

You can scaffold a new FHIR API project by running the provided setup_fhir_project.py script, which generates a working FastAPI environment using Pydantic v2 models for testing and prototyping Patient or Observation endpoints.

Yes, SMART on FHIR authorization is supported through scope syntax guidance, discovery endpoints, token exchange examples, and middleware patterns for enforcing scopes within your FHIR R4 REST API server.

FHIR bundle transaction processing applies changes atomically, while batch processing executes entries independently, both requiring specific search pagination and search result Bundle patterns for correct endpoint semantics.

You handle coding system references by applying Pydantic v2 model patterns to validate codes against LOINC, SNOMED, RxNorm, and ICD-10 systems, ensuring standards-compliant server behavior for FHIR resources.

Incorrect HTTP status codes often occur when missing FHIR resources do not trigger a 404 with an OperationOutcome structure, requiring strict endpoint validation and error handling patterns to achieve standards-compliant behavior.