I.Executive Summary

II.Conceptual Description

Conceptual

FHIRframe

III.Critical Data Elements (Matthew)

IV.Existing Frameworks for Interfacing with Devices(Chris Doss)

Overview, Critical data elements supported, messaging type (how data is transferred – interoperability), supported standards,

A.Continua/CESL (Thom)

The Personal Connected Health Alliance (PCHA) is a first-of-its-kind collaboration designed to engage consumers with their health via personalized connected health solutions, and to promote individualized care as a critical way of relieving the burden on our healthcare system. PCHA, a global, non-profit organization, brings together Continua’s plug-and-play interoperability Design Guidelines and product certification program, the mHealth Summit's international ecosystem of networking events, industry education and thought leadership, and HIMSS' worldwide presence supporting locally-based advocacy and market development. Continua is the only international initiative to establish end-to-end ICT framework for personal connected health and care with open standards.

To enable this interoperable framework, Continua publishes and maintains a set of interoperability Design Guidelines that clearly defines the interfaces that enable the secure flow of medical data among sensors, gateways, and end services, removing ambiguity in underlying healthcare standards and ensuring consistent implementation through product certification. These design guidelines become an international standard via the United Nations ITU Telecommunications Sector (ITU-T).

High Level Architecture

The Personal Health Devices Interface standardizes around the IEEE 11073 Personal Health Device family of standards for data format and exchange between the sensor and the gateway. Continua works within the healthcare community to agree on a subset of IEEE 11073 device specialization attributes that are sufficient for consumer-friendly healthcare monitoring solutions. Continua also works closely with the Bluetooth SIG to ensure that Bluetooth Smart healthcare profiles include these attributes and that they are compatible with the IEEE 11073 data format.

The Services Interface standardizes around the IHE PCD-01 Transaction to move data between a Personal Health Gateway and Health & Fitness Services (e.g. tele-health service). It provides for uploading device observations, exchange of questionnaires and responses, consent management, capabilities exchange, and authenticated persistent sessions over a wide area network. Interoperability is assured by constraining IHE specifications and HL7 standards and providing implementation guidance and interface certification.

The Health Information Service Interface standardizes around the HL7-based PHMR and the IHE XDS specifications to move information between a Health & Fitness Service and Healthcare Information Service provider (e.g. EHR). The PHMR is used by Continua to communicate patient information based on a collection of one or more PCD-01 messages.

Continua addresses end-to-end security and privacy through a combination of identity management, consent management and enforcement, entity authentication, confidentiality, integrity and authentication, non-repudiation of origin, and auditing.

Continua's Test and Certification program ensures interoperability by verifying that products conform to the Continua Design Guidelines and its underlying standards. Certification of sensor devices ensures that IEEE 11073 conformant data is securely received at the gateway. Certification of the WAN interface ensures that each field of every segment in the PCD-01 message contains a valid value. Certification of the HRN interface ensures the syntax and semantics of the XML message.

Continua provides a Continua Enabling Software Library (CESL) to give developers a head start on implementing the design guidelines, greatly reducing development time and cost, and helping to assure interoperability. CESL includes a set of executable agents (device simulators) and a GUI based manager (manager/gateway simulator), an SDK for software development, and a full source code distribution.

B.Google Fit (Janine)

Comments: / Critical data elements supported, secure messaging type (interoperability-how is data transferred; proprietary standards vs supported standards?)
Platform Overview
Google Fit is an open ecosystem that allows developers to upload fitness data to a central repository where users can access their data from different devices and apps in one location:
◦Fitness apps can store data from any wearable or sensor.
◦Fitness apps can access data created by any app.
User's fitness data is persisted when they upgrade their fitness devices.
Google Fit
fit.google.com/
Described as “An open platform that lets users control their fitness data, developers build smarter apps, and manufacturers focus on creating amazing devices.”
CRITICAL ELEMENTS: Appears to support gathering of a variety of data elements typically collected by fitness apps.
SECURE MESSAGING: Does not appear to have this feature.
INTEROPERABILITY: Appears to have proprietary standards.
------

-----

------
Google Fit Android Mobile App
Google Fit Wear App
Google Fit on the Web
------
With Google Fit, you can measure, track, and store your fitness information. It's available on your computer, mobile devices, and Android Wear devices, so you can access it just about anywhere. Here are some things you can do:
◦Set goals around personal fitness
◦Automatically measure how close you are to reaching those goals
◦See what kinds of activities you perform daily and how long you do them
◦Compare your activity over time to see how you’ve improved
◦Keep and view data from other fitness apps you’ve connected to Google Fit
You’ll need a Google account to get started with Fit. To access Fit on your computer, visit
Google APIs for Android

Use Google Fit
◦Get started with Google Fit
◦Enter your profile & fitness goals
◦Track your fitness activity
◦Add & edit fitness activities
◦See daily progress and get notifications
◦Use Fit on Android Wear devices
◦Accessibility for Fit on Android
Manage Google Fit settings

Partnering with:

From:

Data Attribution

Every data point in Google Fit has an associated data source. Data sources contain information to identify the app or the device that collects or transforms the data. The package name of the app is available for data sources that don't represent a physical sensor.

Google Fit enables you to:

◦Determine which app inserted fitness data.

◦Fire an intent to view fitness data with a specific app.

◦Receive intents to show fitness data using your app.

For example, an app that analyzes a variety of data from the user's fitness history may want to present users with the list of fitness sessions included in the analysis, along with information about which app inserted each session. When users tap on each session, the app can fire an intent to show a detailed view of the session using a different app.

C.Apple HealthKit and ResearchKit (Chris Doss)

HealthKit allows apps that provide health and fitness services to share their data with the new Health app and with each other. A user’s health information is stored in a centralized and secure location and the user decides which data should be shared with your app.

D.ONC Open API Initiative (Chris/Thom)

E.Philips(Asim Muhammad)

F.GE – General Electric (Hans Anderson)

G.OMA - Open Mobile Alliance(Harry Rhodes)

The OMA was created in June 2002 as an answer to the proliferation of industry forums each dealing with a few application protocols: WAP Forum (focused on browsing and device provisioning protocols), the Wireless Village (focused on instant messaging and presence), The SyncML Initiative (focused on data synchronization), the Location Interoperability Forum, the Mobile Games Interoperability Forum and the Mobile Wireless Internet Forum. Each of these forums had its bylaws, its decision-taking procedures, its release schedules, and in some instances there was some overlap in the specifications, causing duplication of work. The OMA was created to gather these initiatives under a single umbrella.

Members include traditional wireless industry players such as equipment and mobile systems manufacturers (Ericsson, Thomson, Huawei, ZTE, RetiRadiotelevisiveDigitali, Nokia, Openwave, Sony, Philips, Motorola, Samsung, LG Electronics, Texas Instruments, Qualcomm) and mobile operators (Vodafone, Orange, T-Mobile, LG Telecom), and also software vendors (Microsoft, Sun Microsystems, IBM, Oracle Corporation, Symbian, Celltick, Expway, Mformation, InnoPath, Motive).

H.SMART on FHIR (Grad student)

V.Existing Frameworks for Interfacing with EHR/PHR

A.Smart on FHIR

B.Custom

C.Microsoft Health Vault?

D.

VI.Methods of Health Data Exchangebetween Applications

VII.Security and Privacy Issues (Paul Petronelli)

mobile security document