Graohql & GraphDefinition
summary
GraphQL sits as a lightweight facade over the FHIR REST API, letting clients request exactly the JSON fields they need which reduces bandwidth and latency and avoids client-side caching work; servers can parse GraphQL quickly but may incur extra load and caching becomes harder. Mutations add no clear benefit over PUT/POST. GraphDefinition defines traversals and cardinality across resources so a server can validate cross-resource rules (for example encounter and observation subjects must match) and return a bundled document. Implementations exist in HAPI and public test servers.
AI-written summary · about
chapters (7)
- 0:00Start
- 1:52Problem Statement
- 5:26Simple GraphQL example
- 7:42Polymorphic Fields
- 12:08References
- 19:54Flattening
- 37:49Graph Definition Example
related talks
37mGraphQL — A New Look at the API
23mAn Introduction to GraphQL
32mTradeoffs between leveraging FHIR REST APIs vs. GraphQL APIs
27mWhat the hell is graphQL and why should I care
33mGraphQL - the What, how and why
58mGraphQL -- Flexible APIs for Adaptive Clients
48mGraphQL Is the New Sexy
01h 00mGraphQL - A query language to empower your API consumers