fhir-apilisted

Expert guidance for implementing FHIR RESTful API servers and clients following the HL7 FHIR specification. Use this skill when implementing a FHIR server with REST endpoints, building a FHIR client, designing FHIR API routes and handlers, implementing FHIR operations (read, create, update, delete, search, history), working with FHIR bundles, batch requests, or transactions, handling FHIR content negotiation, headers, and versioning, or implementing conditional operations. Trigger keywords include "FHIR REST", "FHIR API", "FHIR server", "FHIR client", "FHIR endpoint", "FHIR operations", "RESTful FHIR", "implement FHIR".
aehrc/pathling · ★ 127 · API & Backend · score 79

Install: claude install-skill aehrc/pathling

# FHIR REST API implementation This skill provides guidance for implementing FHIR RESTful APIs according to the HL7 FHIR specification (R4/R5). ## URL structure All FHIR REST URLs follow the pattern: ``` [base]/[type]/[id] ``` - `[base]`: Service base URL (e.g., `https://fhir.example.org/r4`) - `[type]`: Resource type (e.g., `Patient`, `Observation`) - `[id]`: Logical resource ID URLs are case-sensitive and use UTF-8 encoding. ## Core operations | Operation | HTTP | URL Pattern | Success | | ----------------- | -------- | ----------------------------------- | ------- | | Read | GET | `[base]/[type]/[id]` | 200 | | VRead | GET | `[base]/[type]/[id]/_history/[vid]` | 200 | | Create | POST | `[base]/[type]` | 201 | | Update | PUT | `[base]/[type]/[id]` | 200/201 | | Patch | PATCH | `[base]/[type]/[id]` | 200 | | Delete | DELETE | `[base]/[type]/[id]` | 200/204 | | Search | GET/POST | `[base]/[type]?params` | 200 | | History | GET | `[base]/[type]/[id]/_history` | 200 | | Capabilities | GET | `[base]/metadata` | 200 | | Batch/Transaction | POST | `[base]` | 200 | For detailed specifications of each operation, see [references/operat