FHIR for clinicians
summary
FHIR claims to make clinical data exchange simpler by using minimalist, linkable resources and references (about 20 properties each) that get adapted with profiling and value sets to enforce required fields and code bindings. Implementations move from mostly read‑only to read‑write APIs, vendors and providers widely adopt FHIR, and a large community answers questions quickly. Tooling such as ClinFire and ConMan builds resource graphs and generates instances; SMART and CDS Hooks enable app marketplaces and workflow decision support.
AI-written summary · about
chapters (19)
- 0:00Intro
- 0:44Outcomes of this talk...
- 2:13A bit of history
- 6:49Benefits of FHIR
- 9:20What is FHIR
- 15:17FHIR: the important bits
- 15:44Resources: What are they?
- 18:03Some examples
- 21:55References between resources
- 23:38Recording a consultation
- 27:36Structured / coded data
- 28:27Datatypes
- 30:27ValueSet
- 32:23Binding
- 33:35For example...
- 34:13Implementation Guide
- 34:50Exchange
- 36:30CDS-Hooks
- 37:50Reality check
