I SO TC2 1 5 / HL7 Dev SI G / 1 1 0 7 3 Mtg Low er Layer- 3 yyzz - - PowerPoint PPT Presentation

I SO TC2 1 5 / HL7 Dev SI G / 1 1 0 7 3 Mtg Low er Layer- 3 yyzz Transport Status Phoenix May 9 , 2 0 0 8

Mark Schnell ( Cisco) Rick Cnossen ( I ntel)

1 1 0 7 3 .3 yyzz Series Standards ( Transport)

Proposed Active Released W ithdraw n 1 1 0 7 3-3 0 0 0 0 Transport F&O [ PAR in draft] 1 1 0 7 3-3 0 2 0 0 Cable connected [ needs reballot] 1 1 0 7 3-3 0 3 0 0 I nfrared w ireless 1 1 0 7 3-3 0 4 0 0 Cabled Ethernet ( 8 0 2 .3 ) [ ballot underw ay] 1 1 0 7 3-3 0 5 0 0 RF W ireless- Fram ew ork & Overview 1 1 0 7 3-3 0 5 0 1 Bluetooth 1 1 0 7 3-3 0 5 0 2 PAN High Rate ( 8 0 2 .1 5 .3 UW B) 1 1 0 7 3-3 0 5 0 3 W LAN ( 8 0 2 .1 1 x) [ on hold] 1 1 0 7 3-3 0 5 0 4 MAN ( Broadband) 1 1 0 7 3-3 0 5 0 5 W AN ( m obile; CDMA) [ stalled] 1 1 0 7 3-3 0 5 06 I ntegrated Transports ( xAN data profile) 1 1 0 7 3-3 0 5 0 7 Mesh Netw orks 1 1 0 7 3-3 0 5 0 8 W ireless Medical Telem etry Service

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 3

IEEE 11073 Inter-LAN Work Group Status

in association with HL7 DEV SIG & ISO TC 215 @ HL7 Working Group Meeting, Phoenix, AZ, USA, 2008May09

Mark Schnell, mschnell@cisco.com

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 4

11073 Inter-LAN Agenda

• History / Goals from San Antonio, TX, USA, 2008Jan18
• Various activities on…
• -30200 Cable connected
• -30400 Cabled Ethernet
• -20401 Common Network Infrastructure
• -30000 Transport Framework & Overview
• Status
• Today’s decisions
• Next Steps
• Back up

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 5

History / Goals from San Antonio, TX, USA, 2008Jan18

• 1. -30400 Cabled Ethernet
• Finish ballot process
• 2. -30200 Cable connected
• Finish ‘delta’ document
• Start and finish ballot process
• 3. -20401 Common Network Infrastructure
• Develop transport architecture
• Overlay supporting network services
• 4. -30000 Transport Framework & Overview
• ??work as back ground to -20401 activities??

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 6

11073 Inter-LAN Agenda

• History / Goals from San Antonio, TX, USA, 2008Jan18
• Status
• -30400

Cabled Ethernet

• -30200

Cable connected

• -20401

Common Network Infrastructure

• -30000

Transport Framework & Overview

• Today’s decisions
• Next Steps
• Back up

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 7

Status - overall

• Unfortunately, not much progress
• The many of the most active Inter-LAN team

members were also active in the -20601/PHD effort.

• Thus, most of the Inter-LAN team members’ available

bandwidth was absorbed in the -20601/PHD activities.

• (However, we thought that it was the right thing to do

and we think that -20601/PHD is the better for it. :-)

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 8

• 1. -30400 Cabled Ethernet
• Finish ballot process
• 2. -30200 Cable connected
• Finish ‘delta’ document
• Start and finish ballot process
• 3. -20401 Common Network Infrastructure
• Develop transport architecture
• Overlay supporting network services
• 4. -30000 Transport Framework & Overview
• ??work as back ground to -20401 activities??

Status – 30400 specifics: goals & status

• Balloting logistics
• Ballot closed with appropriate voting mix
• 114 comments received
• Comments yet to be dispositioned

132 133 134 135 136 137 138 139 140 141 142 143 144 145 S T U V Category View Subtotal Closed Closed % mac/phy 15 0% connector 2 0% cabling 9 0% network 2 0% wording 40 0% clarification 20 0% style 14 0% query na fyi 2 0%

• ther

10 0% <blank line> Total 114 0%

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 9

• 1. -30400 Cabled Ethernet
• Finish ballot process
• 2. -30200 Cable connected
• Finish ‘delta’ document
• Start and finish ballot process
• 3. -20401 Common Network Infrastructure
• Develop transport architecture
• Overlay supporting network services
• 4. -30000 Transport Framework & Overview
• ??work as back ground to -20401 activities??

Status – 30200 specifics: goals & status

• “Delta” changes document complete
• Change existing -30200 Annex F (optional)
• From: 10 Mbps Ethernet signaling
• To: 10/100 Mbps Ethernet signaling
• Add new -30200 Annex O (informative)
• MIB power vs. Ethernet PoE “cross connect”

analysis

• Balloting process issue
• ISO/IEEE ballot process only allows for…
• Reaffirm – no changes.

Monolithic thumbs up/down.

• Amendment – Separate doc. from main spec.

Only changes open to ballot comment Need new PAR.

• Revision – Merged spec.

Whole document open to comment. Need new PAR.

• Can’t get “delta” changes into doc with Reaffirm

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 10

• 1. -30400 Cabled Ethernet
• Finish ballot process
• 2. -30200 Cable connected
• Finish ‘delta’ document
• Start and finish ballot process
• 3. -20401 Common Network Infrastructure
• Develop transport architecture
• Overlay supporting network services
• 4. -30000 Transport Framework & Overview
• ??work as back ground to -20401 activities??

Status – 20401 specifics: goals & status

• No progress. Sorry.

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 11

• 1. -30400 Cabled Ethernet
• Finish ballot process
• 2. -30200 Cable connected
• Finish ‘delta’ document
• Start and finish ballot process
• 3. -20401 Common Network Infrastructure
• Develop transport architecture
• Overlay supporting network services
• 4. -30000 Transport Framework & Overview
• ??work as back ground to -20401 activities??

Status – 30000 specifics: goals & status

• Draft PAR
• Updated with CG feedback
• Ready to submit to IEEE

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 12

11073 Inter-LAN Agenda

• History / Goals from San Antonio, TX, USA, 2008Jan18
• Status
• Today’s decisions
• Next Steps
• Back up

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 13

Decisions for today

• 1. Update of -30200 Cable connected

1. Proposed updates

• Change existing -30200 Annex F (optional)
• From: 10 Mbps Ethernet signaling
• To: 10/100 Mbps Ethernet signaling
• Add new -30200 Annex O (informative)
• MIB power vs. Ethernet PoE “cross connect”

analysis 2. Decision 1. Don’t bother. Just reaffirm current doc. 2. Generate Amendment. Need new PAR. 3. Generate Revision. Need new PAR.

• 2. -30000 Transport Framework & Overview
• Submit drafted PAR to IEEE. Yes/No.
• Suggest amendment
• Minimal work load on

work group to generate desired information.

• Suggest submit
• (Even with the lack of specific

people to work this just now.)

30000.PAR.draft.v04.ppt SLIDE 14 2008 March 18

Proposed 30000 PAR language

2.1 Title of Standard: Standard for Health informatics - Healthcare device communication - Transport profile - Framework and overview 5.2 Scope of Proposed Standard: This document focuses on the enumeration and definition of the transport services and characteristics required by the upper layers of the ISO/IEEE 11073 family of standards that are to be provided by the lower layers of the ISO/IEEE 11073 family of standards. The transport services and characteristics may cover such areas as, but are not limited to, reliability, latency, bandwidth, flow control, security, media type/category, forward and reverse channel set-up/tear-down times, power consumption, device/service discovery and virtual channel usage. 5.4 Purpose of Proposed Standard: The purpose of this document is to define the overall framework for communication between the upper and lower layers of the ISO/IEEE 11073 family of standards. This document identifies logical transport services and characteristics, and as such, no particular implementation is implied by this document. To provide consistency and continuity across the different ISO/IEEE 11073-3xxyy family of standards and to assist in the understanding of these logical transport services and characteristics, representative examples of upper and lower layers from the ISO/IEEE 11073 family of standards are included. The document also summarizes the underlying transport profile specifications.

30000.PAR.draft.v04.ppt SLIDE 15 2008 March 18

Proposed 30000 PAR language

5.5 Need for the Project: Healthcare devices use communications technologies in a wide range of environments including: enterprises, departments, care units, embedded point of care topologies, home and personal situations. However, efficient integration is limited by insufficient standardization at the transport layer in time-critical data communication contexts. 5.6 Stakeholders for the Standard: Key stakeholders include healthcare device and system developers who are incorporating communications technologies, those who sell, deploy and/or manage these systems and those organizations that regulate this environment.

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 16

11073 Inter-LAN Agenda

• History / Goals from San Antonio, TX, USA, 2008Jan18
• Status
• Today’s decisions
• Next Steps
• Back up

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 17

Next steps

• 1. -30400 Cabled Ethernet
• Disposition comments
• Finish ballot process
• 2. -30200 Cable connected
• As decided in “Today’s decisions”
• 3. -20401 Common Network Infrastructure
• Develop transport architecture
• Overlay supporting network services
• 4. -30000 Transport Framework & Overview
• As decided in “Today’s decisions”

11073.Inter-LAN.2008.05.09.v01.ppt SLIDE 18

Logistics/contacts

Emails: list: x73-30400@ieee.org chair: x73-30400-chair@ieee.org Weekly calls:

• Date: Weekly on Tuesday
• Time: 12:00 PM (noon) USA/Eastern Time

Continua Transport Update

Continua Health Alliance

First Plugfest- April, 2008 Luxembourg

Cardio Glucose Meter Pulse Oximeter Medication Monitor Blood Pressure Monitor Weighing Scale Thermometer

7 Devices 2 PAN Interface Transports 2 Managers 10 Companies

V1 PAN Interface using ISO/ IEEE PHD Standards

Continua Health Alliance

Status on V1 Transports

• USB Personal Health Device Class

– Version 1.0 released by USB IF in Q407 – Automated Test Suite under development (slated for Q308)

• Bluetooth Health Device Profile

– Release tied to L2CAP core changes – InterOps underway – Release slated for June – Automated Test Suite slated for June

Continua Health Alliance

Candidate V2 Low Power Radio Technologies

• ANT: Dynastream
• Bluetooth ULP: CSR
• BodyLAN: Fitsense
• Sensium: Toumaz
• ZigBee: Philips
• Z-Wave: Zensys
• Low Power WiFi???

V2 BAN Interface- Can ISO/IEEE 20601 run over these?

Backup slides

1 1 0 7 3 .2 0 4 yy Series Standards ( N/ W Related Application Profiles)

• 1 1 0 7 3-2 0 4 0 0 Netw ork service F&O: Role and types of network

services- Compatibility with transport profiles for xAN, 802.11e QoS; Transport Independent Sub Layer (TISL)

• 1 1 0 7 3-2 0 4 0 1 I nternet Protocol ( I P) : Define transport-agnostic

IP implementation [ underw ay]

• 1 1 0 7 3-2 0 4 0 2 QoS: Provides a transport-neutral model for

application level management of QoS capabilities

• 1 1 0 7 3-2 0 4 0 3 Location: Patient location, asset tracking, staff

location and tracking; RTLS

• 1 1 0 7 3-2 0 4 0 4 I dentification: Patient ID, pharmacy ID, supply

chain, RFID Proposed Active

Data & I nform ation Application Profiles

Specification Topology

Transport Philosophy

The following slides are from the draft ISO / IEEE 11073-30000 Framework & Overview document and provide an approach or philosophy for Transports. The intent is to establish a consistent approach for items such as establishing requirements and referencing outside specifications. The general approach is to define requirements and then utilize application-driven profiling to accomplish, leveraging commercial technologies as much as possible.

Transport Philosophy

1 .5 .1 .3 Tailoring a Standard In some cases an existing standard must be tailored in order to meet ISO/ IEEE 11073 requirements. For example, there may be a unique QoS requirement that is necessary in an acute care setting. In this case, the required additive deltas should be documented in a new ISO/ IEEE specification that references the specification that is being leveraged. In addition, profiling should be used to tighten optional items that may exist in the referenced specification and to provide clarification of ambiguous specification language. 1 .5 .2 Separate Transport from Data It is a goal to separate out Transport issues and associated specifications from Data issues and associated specifications. As much as possible, these should be independent and Transport series specifications should not create requirements that have implications for the payload data. 1 .5 .3 Spectrum of I m plem entations There is a spectrum of target environments for products that are implemented in accordance with the ISO/ IEEE 11073 specifications. As such, a range of requirements should be accommodated. For example, some of the stringent error reporting requirements that are necessary in the clinical acute-care environment may not be germane to all environments.

Transport Philosophy

1 .5 .1 Leveraging Existing Com m ercial Standards It is a goal to avoid having redundant and possibly contradictory specifications that exist in conjunction with the ISO/ IEEE 11073 series of Transport

• specifications. There are many commercial Transport standards available

that are widely implemented and that should be leveraged to the fullest extent. To facilitate this, actions below should be considered. 1 .5 .1 .1 Selection of Standards The standards selection process should include canvassing the industry for existing standards. Evaluation criteria should consider commonality with other medical consortiums where there may be overlap. When considering a standard to reference, preference should be given to an open industry standard that is released and sponsored by an international SDO. 1 .5 .1 .2 Establish a Liaison For active standards, a liaison or point-of-contact should be established between ISO/ IEEE 11073 and the host SDO that controls the standard to be

• leveraged. The liaison will be responsible for providing periodic updates to the

ISO/ IEEE 11073 team on the state of the specification and the plans to evolve

• it. The liaison will also be responsible for providing the host SDO with

collective inputs from the ISO/ IEEE 11073 team.