Exchange of analytics data using FHIR resources
summary
Uses FHIR's Measure and MeasureReport (clinical reasoning) plus the $evaluate-measure operation to export precomputed analytics from an aggregated layer back to FHIR clients. Transactional data flow: OLTP → ETL/enrichment/rollup → aggregated storage, then the server applies requested filters (period, stratifiers like month and approval status) and returns a MeasureReport with group-level measureScore (example: 255 claims) and per-stratum scores. Drilldowns are possible via evaluatedResources or by fetching claim bundles from the source.
AI-written summary · about
chapters (11)
- 0:00Introduction and speaker intro
- 1:13Need for analytical data exchange
- 3:40Limitations of FHIR for analytics
- 5:47Measure and MeasureReport resources
- 7:55Solution architecture approach
- 9:18Resource structure deep dive
- 13:55Step-by-step implementation
- 14:59Q&A session start
- 15:43Q&A: Drill-down to original data
- 17:31Q&A: Generic analytics use cases
- 19:19Closing and thanks
related talks
19mAnalyzing FHIR Data Using ML and Analytical Tools
48mAnalytics and AI on FHIR
39mHow to integrate FHIR with your analytics pipeline
44mTransforming FHIR Data for horizontally scalable analytics
21mClinical and Claims Data Transformation utilizing FHIR Bulk Data
27mStorage and analytics
17mHealth Care Analytics: The Key Is Integration
46mHEDIS on FHIR: NCQA’s digital transformation