7 Medical Android

Android & Medical systemFebruary 15th, 2012

Diego Buffa, System Engineer

Agenda

Android in Medical too ?

Context

Standards

Use Cases

It works !

| © 2011 Wind River. All Rights Reserved.2

3

Android devices are entering a complex environment


Previously...

Medical applications used Bluetooth Serial Port Profile (SPP) and proprietary implementations and data format

Result = Poor interoperability

Standard /Organization Domain Actors Example

Interface

Example

Standard

IEEE / Continia Personal

Telehealth

PAN, AHD

(Application Host

Device), xHR

PAN BT, USB,

IEEE 11073-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

Environme

nt (ICE)

Medical Device,

Network Controller,

Network Supervisor

ICE Equipment

Interface,

ICE Manager

ASTM F2671-

mapping to IEEE

11073-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 11073

Data Requests (DR)

xx

© 2009 Wind River. All Rights Reserved.5

Standards compliance is key


Connectivity

Wind River provides a solution Accelerator for Android which enables the following interoperability protocols

– Bluetooth Health Device Profile (HDP)

– IEEE 11073 Health Informatics Protocol

– Continua-compliant device interoperability

These enhanced interoperability enable devices running Wind River Solution Accelerators for Android (Medical) to be ready to work with almost 20 different Continua-compliant sensors in use today


Today... Health Device Profile (HDP) that includes the MCAP (Multi-Channel

Adaptation Protocol) and makes use of the Device ID Profile (DI).

Bluetooth Transport Interface

Host Control Interface (HCI)

Logical Link and Adaptation Layer (L2CAP)

SDPMulti-Channel Adaptation

Layer (MCAP)

Device Id (DI)

Profile

Generic

Access

Profile (GAP)

Health Device Profile (HDP)

IEEE 11073-20601 Stack

Medical Application

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.

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.

Bluetooth profile

designed to provide

device specific

information through use

of the Service Discovery

Protocol (SDP).


Health Device Profile

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


IEEE 11073 Personal Health Data (PHD) Standards

HDP does not define the data format or content

The Bluetooth SIG mandates the usage of IEEE 11073-20601 Personal Health Device Communication Application Profile as the only allowed protocol for data exchange between HDP devices and the IEEE 11073-104xx Device Specification


HDP + PHD

Application

(Source)

IEEE 11073 Data Exchange

Protocol (Agent)

Application

(Sink)

SDPMCAP

L2CAP

IEEE 11073 Data Exchange

Protocol (Manager)

L2CAP

SDP MCAP

Source side Sink side

Device Data Specializations Device Data Specializations

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

HDP HDP


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 Device Connectivity Options

•Thermometer

•Oximeter

•Etc…


Why Android in Medical Devices

Commoditize the Supply Chain

– Lower cost (HW, SW)

– Faster TTM

– Greater Innovation

– App developer ecosystem

Opportunity to gradually phase-in additional technology

Standards-driven

End-user UX recognition and acceptance


Medical Use-Cases

Scenario #1 A patient who was sent home from the hospital and the doctor wants to monitor certain measurements remotely. The patient does the measurement and then sends them to the doctor via SMS/text messaging or email.

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 want more data on that measurement such as data on high blood pressure or ways to lower weight.


Proposed Solution

7 Medical Android

Documents

Transcript of 7 Medical Android