Android & Medical systems

Transcription

1 Android & Medical systems November 15th, 2011 Stephane Strahm, Prog. Mgr Android Center of Excellence

2 Agenda Android in Medical too? Context Standards Use Cases It works! Wind River. All Rights Reserved.

3 3 The context

4 Standards compliance is key Standard /Organization Domain Actors Example Interface Example Standard IEEE / Continia Personal Telehealth PAN, AHD (Application Host Device), xhr PAN, xhrn BT, USB, IEEE PHD, HL7 CDA/CCD IHE-Integrating the Healthcare Enterprise MUST have regulated device Device Observation Reporter (DOR) and the Data Observation Customer (DOC). PCD-01 Profile DEC Device Enterprise Communications, Alarm Comm. Mng. IEEE 10101/10201, (Point-of-care medical device communication) HL7 2.6 ASTM-ICE. Derived interoperability toward safety Integrated Clinical Environmen t (ICE) Medical Device, Network Controller, Network Supervisor ICE Equipment Interface, ICE Manager ASTM F2671- mapping to IEEE PHD The Health Information Technology Standards Panel (HITSP). Compulsory on any players who are contributing to an EMR in the U.S. Identified for MU as having device interoperability Any player in the U.S. EMR specifically remote monitoring IS device intermediary (DI), remote monitoring management system (RMS), health information exchange (HIE) SDE (System Data Exchange) IEEE Data Requests (DR) xx Wind River. All Rights Reserved.

5 IEEE Personal Health Data (PHD) Standards HDP does not define the data format or content The Bluetooth SIG mandates the usage of IEEE Personal Health Device Communication Application Profile as the only allowed protocol for data exchange between HDP devices and the IEEE xx Device Specification First open standard in the medical care area, allowing free exchange of information between devices Focuses on personal use instead of hospital use and provide a simpler communications model 5

6 IEEE Personal Health Data (PHD) Standards Uses the concept of "Agents" and "Managers Agents are the Personal Health Devices and are generally small, inexpensive battery-powered devices that lack much in the way of displays and other user interfaces Managers are typically personal computers or smart phones with greater computing resources If the Agents transmit their data to more capable Managers then the data can be processed and displayed on the Managers, and then perhaps transferred through the Internet to people's carers and to health care professionals The standards assume that each Agent communicates with a single Manager. A Manager could communicate with more than one Agent. The Manager is able to maintain its own copy of the Agent's objects (data). 6

7 IEEE Personal Health Data (PHD) Standards IEEE defines the data exchange protocol IEEE xx defines the data format (size and coding of all data exchanged between HDP Devices) Devices establish a logical connection on level The communication happens between a HDP Source Node ( Agent) and a HDP Sink node ( Manager) Agent or Manager could start the data transmission. A Manager could ask for one data value or request data for a defined time (in seconds) or data is requested via start/stop from the agent Bluetooth link disconnection is not immediately reported to the layer; automatic reconnection is processed 7

8 Continua-compliant Device Interoperability Non-profit, open industry organization of healthcare and technology companies joining together in collaboration to improve the quality of personal healthcare Founded in June 2006 Aims to establish a system of personal connected healthcare solutions Focused on providing individuals the means to help in the treatment of their conditions in their own homes, helping themselves and easing the burden on health care professionals Currently, 240 active members The group is establishing a product certification program signifying that the product is interoperable with other Continua-certified products. Continua Alliance products make use of the ISO/IEEE Personal Health Data (PHD) Standards. Wind River is a member 8

9 Android Medical Profile Use Cases Scenario #1: A patient was sent home from the hospital and the doctor wants to monitor certain measurements remotely. The customer does the measurement and then sends them to the doctor via SMS/text messaging or . Scenario #2: Traveling nurse who visits several patients, does measurements for each one, and then at some point (end of the day), uploads all the data to a central system. Scenario #3: A patient does a measurement and wants additional data on that measurement such as data on high blood pressure or ways to lower weight. 9

10 New use cases for tablet based form factors Display Options Touch Screen Multi Screen Stationary, Wall Mount Portable, Mobile, Cradle, Etc Interfaces Options LAN Wireless/PAN NFC Barcode RFID Etc Medical Devic Connectivity Options Thermometer Oximeter Etc Wind River. All Rights Reserved.

11 Previously... Medical applications used Bluetooth Serial Port Profile (SPP) and proprietary implementations and data format Result = Poor interoperability 11

12 Today Health Device Profile (HDP) Provides control channel connection/disconnection, data link creation (reliable or streaming), data link deletion, data link abort, data link reconnection, data transmission (over one or more data links) clock synchronization 12

13 Health Device Profile Specifies two roles: Sink (receiver of the medical data) and Source (transmitter of the medical data) Application Data from a Source is transmitted over a reliable data channel or streaming data channel to a Sink Application (Source) Device Data Specializations IEEE Data Exchange Protocol (Agent) Application (Sink) Device Data Specializations IEEE Data Exchange Protocol (Manager) MCAP SDP SDP MCAP L2CAP L2CAP Source side Sink side 13

14 Today... Health Device Profile (HDP) that includes the MCAP (Multi-Channel Adaptation Protocol) and makes use of the Device ID Profile (DI). Medical Application IEEE Stack 14 Bluetooth profile designed to provide device specific information through use of the Service Discovery Protocol (SDP). Device Id (DI) Profile SDP Multi-Channel Adaptation Layer (MCAP) Logical Link and Adaptation Layer (L2CAP) Used by HDP. It facilitates the creation of a Communications Link (MCL) for exchanging generic commands, and the creation of one or more Data Links (MDL) to transfer actual Medical Device data. Health Device Profile (HDP) Host Control Interface (HCI) Bluetooth Transport Interface Generic Access Profile (GAP) The core Bluetooth profile designed to facilitate transmission and reception of Medical Device data. The APIs of this layer interact with the lower level MCAP layer, while performing SDP behaviour to connect to remote HDP devices.

15 Why Android in Medical Devices? Commoditize the Supply Chain Lower cost (HW, SW): regulatory agency pressures Faster TTM Greater Innovation App developer ecosystem Opportunity to gradually phase-in additional technology Standards-driven End-user UX recognition and acceptance Wind River. All Rights Reserved.

16 Key points to consider Android inside Medical Devices = First Mover Advantage Apps -> PHD -> Regulated Devices Wind River is Medical Platform solutions meet strategic OS options for device manufacturers VxWorks, WR Linux, Platform for Android Wind River. All Rights Reserved.

17 Android Medical & Wind River Wind River has enhanced Android with the following interoperability protocols Bluetooth Health Device Protocol (HDP) IEEE Health Informatics Protocol Continua-compliant device interoperability 17

18 Wind River current solution Wind River s PFA currently provides interoperability with the following Continua-compliant devices: Nonin Onyx II Pulse Oximeter, Model 9560 A&D Blood Pressure Monitor (UA-767PBT-C) A&D Weight scale (UC-321PBT-C) Demo tablet on Intel Green Ridge 18

19 Thank you 19