FHIR REST API
summary
Live demos show FHIR REST behavior: POST returns server-assigned GUIDs and Location/ETag headers, PUT lets clients upsert with chosen IDs, DELETE returns 204 and only removes the latest version, and PATCH is rarely used. Bundles support temporary IDs and two modes—transaction bundles are processed in order (atomic on compliant servers) and batch (non-atomic). Validation layers, history/version endpoints, search by GET or POST with include chains, and concurrency via If-Match with ETag and optional pessimistic locks are all demonstrated.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 4:26Creating and updating
- 7:22Resource management
- 10:10Deleting resources
- 13:15Bundles and transactions
- 17:53Validation and errors
- 20:00Responses and formatting
- 21:58Concurrency control
- 24:44Search parameters
- 29:57Capability statements
- 32:32Q&A session
