fhir-api

Solid

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".

API & Backend 127 stars 23 forks Updated 3 days ago Apache-2.0

Install

View on GitHub

Quality Score: 79/100

Stars 20%
70
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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...

Details

Author
aehrc
Repository
aehrc/pathling
Created
6 years ago
Last Updated
3 days ago
Language
Java
License
Apache-2.0

Integrates with

REST API · API

Similar Skills

Semantically similar based on skill content — not just same category

Web & Frontend Featured

common-api-design

Apply REST API conventions — HTTP semantics, status codes, versioning, pagination, and OpenAPI standards for any framework. Use when designing endpoints, choosing HTTP methods, implementing pagination, or writing OpenAPI specs. (triggers: **/*.controller.ts, **/*.router.ts, **/*.routes.ts, **/routes/**, **/controllers/**, **/handlers/**, rest api, endpoint, http method, status code, versioning, pagination, openapi, api design, api contract)

498 Updated today
HoangNguyen0403
API & Backend Featured

oma-backend

Backend specialist for APIs, databases, authentication with clean architecture (Repository/Service/Router pattern). Use for API, endpoint, REST, database, server, migration, and auth work.

1,017 Updated today
first-fluke
API & Backend Featured

api-fuzzing-for-bug-bounty

This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.

4,168 Updated yesterday
zebbern
API & Backend Featured

api-doc-generator

Generate API documentation from source code, supporting REST APIs, GraphQL, and various documentation formats.

528 Updated today
JackyST0