This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Open mHealth to FHIR"
Jump to navigation
Jump to search
| Line 36: | 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 | + | * 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 --> | ||
Revision as of 03:23, 8 September 2018
Submitting WG/Project/Implementer Group
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:
- A patient preventing or managing one or more diseases
- 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.
