Don't Forget About the List Resource!
summary
Argues that the FHIR List resource doubles as a lightweight metadata and state store: used in production to cache EMR patient lists (fetched via legacy non‑FHIR APIs), hold user settings and ordered list for UI config with FHIRPath expressions, and drive UI behavior without code changes. Implementation uses patch operations, occasional list.search, and Google Healthcare FHIR Server; designs keep lists small (largest ≈100 items) while maintaining thousands of lists overall. Claims this approach speeds delivery despite being a non‑traditional pattern.
AI-written summary · about
chapters (7)
- 0:00Intro
- 0:49Agenda
- 1:35What is the List Resource
- 3:19Object Properties
- 4:09Using the List Resource
- 5:48Example
- 12:26Questions
related talks
42mFHIR for clinicians
50mIntroduction to FHIR
16mThe Future of Healthcare and Clinical Research Under FHIR
46mUsing clinFHIR to learn and develop FHIR solutions
41mBuilding a clinical scenario
49mReferrals and orders: How to ask for stuff in FHIR
34mFHIR Projects
40mDistributing Decision Support with FHIR