ISO/IEEE 11073 Personal Health

Devices

Malcolm Clarke on behalf of the

ISO/IEEE 11073 Personal Health Device Work GroupBrunel University

May 26, 2008

MIE 2008

ISO/IEEE 11073 Personal Health Devices

Overview

The Base Standard (ISO/IEEE P11073-20601™)

The Domain Information Model

Nomenclature

Service Model

Device Specializations (ISO/IEEE P11073-104zz)

Questions (feel free to ask while we go too)

-00103 Technical Report - Overview

Serial IrDA Bluetooth USB ZigBee

Layers

1-4

Layer

5-7

OSI

-20601 Optimized Exchange Protocol

-10400 Common Framework

-10404Pulse

Oximeter

-10407Blood

Pressure

-10417Glucose

-10406Pulse

-10415Weighing

Scale

-10408Thermo-meter

Phase II

…

Device Specializations

Personal Health Devices Framework

Background: Terminology

Agent

Other terms:

Service Component

PAN Device

Device

Source

Sensor

Manager

Other terms:

Client Component

Application Host Device

Host

Sink

Compute Engine

Transport

Other terms:

PAN Interface

USB

Bluetooth

Background: Supported Domains

Three domains

Disease Management

Agent Examples: Pulse oximeter, Heart rate monitor,

Blood pressure monitor, Thermometer, Weighing scale,

Glucose meter

Health and Fitness

Agent Examples: Heart rate monitor, Weighing scale,

Thermometer, Cardiovascular fitness and activity

monitor, Strength fitness equipment

Independent Living (Aging Independently)

Agent Examples: Disease management devices plus

Independent living activity hub, Medication monitor

Background: Example – Weight

A person steps on a scale

Measurement is taken

Weight is sent to a Manager for tracking

and trend analysis

If connection fails, weight is queued

until a future time

Same example applies to many other

measurement types: Blood pressure,

glucose, temperature

Background: Guiding Principles

Exchange protocol: Places more burden on Managers than Agents

Supports multiple data types (episodic, streaming, store and forward)

Designed to be transport portable (Bluetooth, USB, etc.)

Optimizes data exchange

Enables efficient reconnections

Targets personal health in home and mobile environments

ISO/IEEE 11073 Personal Health Devices

Overview

The Base Standard (ISO/IEEE P11073-20601™)

The Domain Information Model

Nomenclature

Service Model

Device Specializations (ISO/IEEE P11073-104zz)

Questions (feel free to ask while we go too)

IEEE P11073-20601 Modeling

Domain Information Model (DIM) – describes the device and physiological data

ASN.1 – language used in the abstract modeling of data and interactions

Nomenclature – provides binary codes for terminology

Service Model – defines interactions with the device and data

Communication Model – manages the connection state machine and communication characteristics

ASN.1

Service Model

DomainInformation Model

Communication Model

Nomenclature

Domain Information

Model

Object oriented model

No requirement to implement in object

oriented language

Generic set of classes created

Classes define attributes and methods

Attribute type defined in ASN.1

Objects are tailored using the attributes

Attributes may be:

Mandatory, optional, or conditional

Static or dynamically changing

ASN.1

Service Model

DomainInformation Model

Communication Model

Nomenclature

DIM Classes

Medical Device System (MDS) – represents the device

Metric – models different forms of measurements

Persistent Metric Store (PM) – provides mechanism to store data for a period of time

Scanner – groups and optimizes data transmission

Class PHD-DIMScanner

MDS

Metric

Numeric

PM-Segment

EnumerationRealTime-SA

PM-Store

Activity Data

CfgScanner

EpiCfgScanner PeriCfgScannerNumeric Ave

Object Class Attribute Definitions

Each set of object class attributes are defined in tabular form

Attribute name used when talking about the attribute

Nomenclature for attribute identification

ASN.1 attribute type definition (see -20601 Annex B or Annex C for full details)

Description of attribute usage and requirements

Qualifier: Mandatory, Conditional, Optional

Nomenclature

Description Nomenclature defines 32-bit identifiers

Aids in semantic interoperability

Increases portability to different locales

Fully defined in ISO/IEEE Std 11073-10101™

-20601 and -104zz standards repeat relevant parts

Each MDC_* identifier has two parts Code block in high 16-bits

Term code in low 16-bits (with sub partitions)

Code blocks group similar term codes together Physiological measurements, dimensions, events, body sites

To reduce packet size, term code can be used alone Code block must be already known (e.g. standardized)

For example, unit codes are always in dimension code block

ASN.1

Service Model

DomainInformation Model

Communication Model

Nomenclature

Example

Numeric class is instantiated to

create a weight object

All mandatory attributes are included

Meets the conditions in the remarks

column for 3 conditional attributes

Includes an optional Unit-Code

No other attributes are included

+Handle

+Type

-Metric-Spec-Small

-Attribute-Value-Map

-...

Metric

Handle = 1

Type = MDC_MASS_BODY_ACTUAL

Metric-Spec-Small = 0xD040

Attribute-Value-Map

...

Simple-Nu-Observed-Value = 175.0

Unit-Code = MDC_DIM_LB

...

Weight : Numeric

+Simple-Nu-Observed-Value

+Unit-Code

-...

Numeric

Service Model

Message format described in ASN.1

Available services

Event Reporting Service Config, Data Update

Object Access Service Get, Set, Actions (Methods)

Association Service Assoc request/response, release

request/response, abort

Conversion Service Fixed format binary, packed binary, XML

ASN.1

Service Model

DomainInformation Model

Communication Model

Nomenclature

Event Reporting Service (1 of 2)

Configuration Event Report Describes a particular configuration

Describes all Agent objects

Transmits infrequently changing attributes

Optionally describes fixed and grouped message formats

Manager accepts / rejects based on ability to support

Optimization: Device specializations can define Standard

configurations

Agent sends a well known Dev-Configuration-Id

If Manager knows the configuration, no need to transmit the configuration

Event Reporting Service (2 of 2)

Data Update Event Reports Formats

Variable –sends type, length, data

Fixed – send the type and length at configuration time

Scanner (Grouped) – further optimization to remove transmission of handles

Support for Single person reporting

Multi-person reporting

Transmission types Confirmed

Unconfirmed

PM-Segment Data Event Report

Object Access Service (1 of 2)

Currently defined Gets and Sets

Get

Types

Get all attributes (Mandatory)

Get list of attributes

Objects

MDS Object

PM-Store

Set

Scanner – Operational State

Object Access Service (2 of 2)

Currently defined Actions (Methods): MDS Object:

MDS-Data-Request (optional):

Poll for data

Enable data transmission – timed

Enable data transmission – untimed

Query for all attributes, list of attributes, or by class

Set-Time (optional)

Set time and date on Agent

PM-Store: Clear-Segments

Get-Segment-Info

Trig-Segment-Data-Xfer

ISO/IEEE 11073 Personal Health Devices

Overview

The Base Standard (ISO/IEEE P11073-20601™)

The Domain Information Model

Nomenclature

Service Model

Device Specializations (ISO/IEEE P11073-104zz)

Questions (feel free to ask while we go too)

ISO/IEEE 11073 Personal Health Devices

IEEE P11073-20601™ Optimized exchange protocol IEEE P11073-10400™ Dev specialization - Common framework

IEEE P11073-10404™ Dev specialization – Pulse oximeter

IEEE P11073-10406™ Dev specialization – Heart rate monitor

IEEE P11073-10407™ Dev specialization – Blood pressure monitor

IEEE P11073-10408™ Dev specialization – Thermometer

IEEE P11073-10415™ Dev specialization – Weighing scale

IEEE P11073-10417™ Dev specialization – Glucose meter

IEEE P11073-10441™ Dev specialization – Cardiovascular

IEEE P11073-10442™ Dev specialization – Strength

IEEE P11073-10471™ Dev specialization – Activity hub

IEEE P11073-10472™ Dev specialization – Medication monitor

ISO/IEEE P11073-10415 Weighing Scale

Support for episodic mode

Standard Config defined

Uses nomenclature from -10101 and

adds a new term for BMI

Weighing Scale : MDS

Body Weight : Numeric

Body Height : Numeric

1

0..*

1

1..*

Body Mass Index : Numeric

10..*

ISO/IEEE P11073-10417 Glucose Meter

Support for episodic mode

Standard Config defined

Uses nomenclature from -10101 and

adds new terms for Glucose

Glucose Meter : MDS

Glucose : Numeric

Flags : Numeric

1

0..*

1

0..*

Events : Numeric

10..*

Summary

Optimized exchange protocol: Places more burden on Managers than Agents. Agent is “in

charge”, Manager adapts

Supports multiple data types (episodic, streaming, store and forward)

Designed to be transport portable (Bluetooth, USB, etc.)

Optimizes data exchange (data transmission sizes, run-time construction, and parsing overhead)

Enables efficient reconnections (Agent not always connected, configuration transferred a single time)

Targets personal health in home and mobile environments

Leverages traditional Domain Information Model to enable leveraging other IEEE 11073 specifications

Device specializations: Narrows a broad framework to a specific application

Enable interoperability for each device type

Questions and Answers

Join Information:

No cost to join the work group and participate in development activities

To participate in final ballot, the costs are < $250 USD per individual per year for an IEEE and IEEE Standards Association membership

To join the work group, contact:phd-chair@ieee.org