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

Difference between revisions of "Open mHealth to FHIR"

From HL7Wiki
Jump to navigation Jump to search
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[Category:201809_FHIR_Connectathon_Track_Proposals|Sept 2018 Proposals]]
+
 
 
__NOTOC__
 
__NOTOC__
  
Line 22: Line 22:
 
See [[Connectathon_Track_Lead_Responsibilities]]  -->
 
See [[Connectathon_Track_Lead_Responsibilities]]  -->
  
[mailto:ehaas@healthedatainc.com Eric Haas]
+
* [mailto:ehaas@healthedatainc.com Eric Haas]
 +
 
 +
Open mHealth Contacts:
 +
 
 +
* [mailto:simona.carini@ucsf.edu Simona Carina]
 +
* [mailto:Ida.Sim@ucsf.edu Ida Sim]
  
 
'''Dedicated [#.html Zulip chat stream] for this track ...tbd...'''
 
'''Dedicated [#.html Zulip chat stream] for this track ...tbd...'''
Line 31: Line 36:
 
==Expected participants==
 
==Expected participants==
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
GA Tech, UCSF <your name here!>
+
* GA Tech
 +
* UCSF
 +
<your name here!>
 +
 
 
==Roles==
 
==Roles==
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
 
See the [https://healthedata1.github.io/mFHIR/index.html mFHIR Implementation Guide] for the initial use cases and FHIR Mappings.
 
See the [https://healthedata1.github.io/mFHIR/index.html mFHIR Implementation Guide] for the initial use cases and FHIR Mappings.
  
===R24 Server===
 
  
===Smart App===
+
* '''FHIR-enabled EHR Sytem'''
 +
* A '''Open mHealth to FHIR Server''' with FHIR server running [http://docs.smarthealthit.org/ 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 [https://github.com/openmhealth/shimmer Shimmer]
 +
* '''Open mHealth to FHIR Client''' a SMART on FHIR app – has roles for PCP, onboarding staff, and patient
  
 
==Scenarios==
 
==Scenarios==
  
 
See the [https://healthedata1.github.io/mFHIR/index.html mFHIR Implementation Guide] for the initial use cases and FHIR Mappings.
 
See the [https://healthedata1.github.io/mFHIR/index.html mFHIR Implementation Guide] for the initial use cases and FHIR Mappings.
 +
 +
Base Use case
 +
 +
StoryBoard Description:
 +
 +
The patient determined by e.g., http://tools.acc.org/ASCVD-Risk-Estimator-Plus/#!/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 [https://healthedata1.github.io/mFHIR/#retrieving-omh-data-in-native-omh-schema-format mFHIR Implementation Guide] for this initial use case.
 +
 +
 +
[[image:Smartapp-binary.png|500px]]
 +
 +
==== Use Case 2: Retrieving OMH data as FHIR Observations ====
 +
 +
 +
See the [https://healthedata1.github.io/mFHIR/#retrieving-omh-data-as-fhir-observations mFHIR Implementation Guide] for this initial use case.
 +
 +
 +
[[image:Smartapp-observation.png|500px]]
  
 
==Test Implementations==
 
==Test Implementations==
 +
 +
#'''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 using the following URL: https://launch.smarthealthit.org/?auth_error=&fhir_version_1=r2&fhir_version_2=r3&iss=&launch_ehr=1&launch_url=https%3A%2F%2Fapps.hdap.gatech.edu%2Fomhonfhir%2Flaunch&patient=&prov_skip_auth=1&provider=&pt_skip_auth=1&public_key=&sb=&sde=&sim_ehr=0&token_lifetime=15&user_pt=
 +
#**The SMART Application Launcher simulates a SMART enabled EHR and launches an application. It allows us to test a SMART enabled application, using a simulated EHR and publically available FHIR servers maintained by SMART.
 +
#**Press the “Launch” button on the application to simulate the application launch, and then you will be able to select an EHR patient, and link that patient to an existing Google Fit account.
 +
#*The source code for the OMH on FHIR project is hosted on the [https://github.com/gt-health gt-health GitHub repository]
 +
#[https://app.getpostman.com/run-collection/0a54cd0197a5f2fc98d4 Run in Postman]

Latest revision as of 04:56, 8 September 2018


Submitting WG/Project/Implementer Group

Omh logo.png



Justification

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:

Dedicated [#.html Zulip chat stream] for this track ...tbd...

FHIR version

STU3

Expected participants

  • GA Tech
  • UCSF
<your name here!>

Roles

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

Scenarios

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

Base Use case

StoryBoard Description:

The patient determined by e.g., http://tools.acc.org/ASCVD-Risk-Estimator-Plus/#!/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.


Smartapp-binary.png

Use Case 2: Retrieving OMH data as FHIR Observations

See the mFHIR Implementation Guide for this initial use case.


Smartapp-observation.png

Test Implementations

  1. GAtech Reference Implementation Open mHealth to FHIR Server
  2. Run in Postman