This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201809 Open mHealth to FHIR"

From HL7Wiki
Jump to navigation Jump to search
Line 3: Line 3:
==Submitting WG/Project/Implementer Group==
==Submitting WG/Project/Implementer Group==
Review the [ track orientation slides] now.

Revision as of 19:29, 13 September 2018

Submitting WG/Project/Implementer Group

Omh logo.png


Open mHealth to FHIR Connectathon Track OrientationPreview Slides

To pilot the Open mHealth to FHIR Implementation Guide which describes how to use FHIR and OMH to pull health data from popular third-party APIs like Runkeeper and Fitbit. Using the OMH SHIMMER adn an "Open mHealth to FHIR" server, this data is made accessible to a FHIR SMART client either in the native OMH schema format or as FHIR resources (typically FHIR Observations).

Use Cases to include:

  1. A patient preventing or managing one or more diseases
  2. Accessing to mHealth data for enterprise level-needs, e.g., to support population health and research purposes

Proposed Track Lead

Open mHealth Contacts:

GA Tech (Test Server) Contacts:

FHIR version


Expected participants

  • GA Tech
  • UCSF
<your name here!>


See the mFHIR Implementation Guide for the initial use cases and FHIR Mappings.

  • FHIR-enabled EHR Sytem
  • A Open mHealth to FHIR Server with FHIR server running SMART-on-FHIR protocols for authentication/authorization, etc.
  • Patient’s step counter sensor (called ** StepSensor** in this use case) – specific product, may be the patient’s phone
  • Data store for the Step-Counter Device output (e.g., cloud and/or phone (e.g., GoogleFit, HealthKit)) that either offers data directly in Open mHealth format using an Open mHealth endpoint, or is supported by Shimmer
  • Open mHealth to FHIR Client a SMART on FHIR app – has roles for PCP, onboarding staff, and patient


See the mFHIR Implementation Guide for the initial use cases and FHIR Mappings.

Base Use case

StoryBoard Description:

The patient determined by e.g.,!/calculate/estimate/ to be 
at moderate CV risk based on blood pressure, BMI, diet and exercise, blood glucose. Patient has a primary 
care physician (PCP). PCP and the patient jointly decide on improving exercise to meet AHA/WHO/CDC 
guidelines of150 minutes of moderate exercise (3-6 METS) every week, which they have refined into a 
mutually agreed upon step goal of 4000 steps daily. PCP prescribes the collection of steps using an mHealth 
device, to track daily steps and average daily and weekly steps. The patient is given an Open mHealth- 
compliant/supported consumer device (e.g., FitBit, GoogleFit, Misfit) by the clinic, or the patient already 
has an Open mHealth-compliant/supported device.

At the next scheduled visit (e.g., in 90 days), the PCP and patient will jointly review during a clinic 
visit the daily step count and daily and weekly averages in the past 90 days vs the goal of 4000 daily 
steps. They will do this using a FHIR app that presents the data graphically within the EHR session.

Use Case 1: Retrieving OMH data in native OMH Schema format

See the mFHIR Implementation Guide for this initial use case.


Use Case 2: Retrieving OMH data as FHIR Observations

See the mFHIR Implementation Guide for this initial use case.


Test Implementations

  1. GAtech Reference Implementation Open mHealth to FHIR Server
    • The latest version of the OMH on FHIR application can be launched with the SMART Application Launcher - INSTRUCTIONS
  2. Run in Postman