fhir-developer-skill

This skill acts as an authoritative reference for engineers and developers tasked with building healthcare data exchange solutions compliant with the HL7 FHIR R4 standard. It provides immediate access to critical architectural patterns required for backend development, including schema validation, RESTful endpoint design, and mandatory status code management. Designed to bridge the gap between abstract health data standards and concrete code implementation, this tool is essential for teams working on EHR integration, patient portals, or clinical data interoperability projects.

• Full FHIR R4 resource structure guide including Patient, Observation, Encounter, Condition, and MedicationRequest configurations.

• Strict validation logic for required vs. optional fields, ensuring cardinality compliance to prevent common integration errors.

• Comprehensive lookup tables for value sets, including gender codes, encounter classes, and clinical status enums.

• Standardized implementation patterns for OperationOutcome error responses and HTTP status codes (200, 201, 401, 403, 422, etc.).

• Reference for international coding systems and terminology standards including LOINC, SNOMED CT, RxNorm, and ICD-10.

• Pre-defined coding templates for vital signs, including blood pressure and heart rate measurement definitions.

• Guidance on SMART on FHIR authorization flows and OAuth scope requirements for secure health data access.

• Helper patterns for handling Bundles, transactions, batch operations, and search pagination.

• Use this skill to validate JSON payloads against the FHIR R4 specification during the development of REST APIs.

• Consult the provided HTTP status code reference to ensure your API conforms to RESTful healthcare practices and properly communicates validation failures.

• Utilize the Pydantic v2 and TypeScript/Express code snippets to quickly scaffold secure, standard-compliant services.

• When implementing resource creation, strictly follow the cardinality rules provided to identify mandatory fields vs. optional attributes.

• Integrate the suggested OperationOutcome structure to provide meaningful, actionable error logs that developers and automated systems can interpret correctly.

• Always refer to the canonical URLs for coding systems to maintain interoperability across different healthcare software platforms.