Open mHealth OmH and FHIR
summary
Open mHealth supplies JSON schemas for ~20–30 mobile health data types and a shim library called Shimmer shims that pulls from Google Fit, Fitbit and Apple Health and converts to OMH format; a draft OMH→FHIR implementation guide maps those schemas to FHIR Observations using OMH→FHIR mapping tables (codes, categories, quantity units) and a Python converter/Jupyter demo; architecture uses an OMH/FHIR server and SMART-on-FHIR front end so the SMART-on-FHIR app visualizes step counts and observations and the conversion validates.
AI-written summary · about
chapters (12)
- 0:00Start
- 1:29Outline
- 2:07Use Case: Increase Physical Activity to Reduce CV Risk
- 3:39Example Instances of Step Count
- 4:36To answer use case
- 7:55Difference Between Mobile Health Data and EHR Data
- 9:00Open mHealth to FHIR Implementation Guide Open mHealth
- 9:27Mapping Overview
- 11:34Approach to Mapping
- 12:45Mapping Spreadsheet
- 30:12OmH-on-FHIR High Level Design
- 31:05SMART App Workflow
related talks
42mBuilding on Cerner with SMART on FHIR
22mAPI’s in public healthcare – case Health Village
49mFHIR Bulk Data API and what's new in v2
42mAll of Us / Sync for Science
33mHealthcare Interoperability : From Buzzword to APIs
44mFHIR Mapping Language
26mUsing APIs to Transform the way CMS Shares Medicare Claims Data
45mFHIR REST API