This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Open mHealth to FHIR"

From HL7Wiki
Jump to navigation Jump to search
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]
  
other contacts regarding OMH
+
Open mHealth Contacts:
[mailto:simona.carini@ucsf.edu Simona Carina]
+
 
[mailto:Ida.Sim@ucsf.edu Ida Sim]
+
* [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...'''

Revision as of 03:22, 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.

R24 Server

Smart App

Scenarios

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

Test Implementations