FHIR Developer Skill

• You are building FHIR REST endpoints (Patient, Observation, Encounter, Condition, MedicationRequest) and need spec-correct field requirements and value sets.
• You need to implement proper HTTP status codes and OperationOutcome error responses for a FHIR server.
• You are integrating SMART on FHIR OAuth authorization and need correct scope syntax and enforcement patterns.
• You are working with FHIR Bundles (transaction, batch, searchset) or implementing search pagination.

• You are working with FHIR DSTU2 or STU3 — this skill targets R4 specifically.
• You need a live FHIR server or data storage solution; this skill provides development guidance only, not infrastructure.
• Your project has no healthcare data or FHIR API requirements.

Provides authoritative required-field cardinality tables for Patient, Observation, Encounter, Condition, MedicationRequest, Medication, and Bundle — preventing common mistakes like treating optional fields as required.

Covers all key value sets (Observation.status, Encounter.status/class, Condition.clinicalStatus, MedicationRequest.status/intent, Bundle.type, Patient.gender) with the correct 422 response for invalid enum values.

Precise guidance on when to use 200, 201, 204, 400, 401, 403, 404, 412, and 422 — including the critical distinction between 412 Precondition Failed for ETag mismatches and 422 for validation errors.

Ready-to-use OperationOutcome JSON structures and code snippets for Python/FastAPI and TypeScript/Express, ensuring all error responses are FHIR-compliant.

Canonical system URLs for LOINC, SNOMED CT, RxNorm, ICD-10, and HL7 terminology systems, plus common vital-sign LOINC codes for quick reference.

References for OAuth scope enforcement, conditional create/update operations, transaction vs. batch Bundle semantics, and search result pagination patterns.

Ask the assistant to scaffold a POST /Observation endpoint with correct status validation, 422 error responses, and OperationOutcome formatting in FastAPI or Express.

Paste your existing FHIR endpoint code and ask the assistant to identify violations — such as wrong status codes, missing Location headers, or incorrect Encounter.class data types.

Get guidance on OAuth scope syntax (v1/v2), backend service flows, and scope enforcement logic for securing FHIR endpoints.

Use the built-in quick-start script reference to generate a FastAPI project with correct Pydantic v2 models, OperationOutcome helpers, and Patient CRUD endpoints.