Transcript N0254_LL-Status_WG7_meeting_2009-01

ISO TC215 / HL7 Dev SIG /11073 Mtg
Lower Layer Transport Status
Orlando
January, 2009
Rick Cnossen (Intel)
Mark Schnell (Cisco)
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 1
 11073-30000
Proposed
Active
Released
Withdrawn
Transport F&O [PAR ready for submission]
 11073-30200
Cable connected [Reaffirmation ballot out]
 11073-30300
Infrared wireless
 11073-30400
Cabled Ethernet (802.3) [ballot disposition]
 11073-30500
RF Wireless- Framework & Overview
 11073-30501
Bluetooth
 11073-30502
PAN High Rate (802.15.3 UWB)
 11073-30503
WLAN (802.11x) [on hold]
 11073-30504
MAN (Broadband)
 11073-30505
WAN (mobile; CDMA) [stalled]
 11073-30506
Integrated Transports (xAN data profile)
 11073-30507
Mesh Networks
 11073-30508
Wireless Medical Telemetry Service
11073.3yyzz Series Standards (Transport)
Summary Overview
11073.204yy Series Standards (N/W Related)
Summary Overview
Proposed
Active

11073-20400 Network service F&O: Role and types of network
services- Compatibility with transport profiles for xAN, 802.11e
QoS; Transport Independent Sub Layer (TISL)

11073-20401 Internet Protocol (IP): Define transport-agnostic
IP implementation [underway]

11073-20402 QoS: Provides a transport-neutral model for
application level management of QoS capabilities

11073-20403 Location: Patient location, asset tracking, staff
location and tracking; RTLS

11073-20404 Identification: Patient ID, pharmacy ID, supply
chain, RFID
30400 (Cabled Ethernet) Specifics
• Balloting logistics
•
•
•
•
Current Status
•
•
Disposition comments
Finish ballot process
Rick’s recommend next step:
• Identify someone to team
with Mark on remaining
handful of comments and
drive it through the ballot
process.
30000.PAR.draft.v04.ppt
2008 March 18
132
133
134
135
136
137
138
139
140
141
142
143
144
148
149
150
151
152
153
154
155
156
157
Ballot closed with appropriate voting mix
114 comments received
100 comments dispositioned
Of the remaining 14 comments
• 5 in various states of drafting or analysis
• 6 "document logistics" type comments to be
worked with IEEE staff
• 3 dups from the 11 comments above
S
Category View
conn/cabling
mac/phy
other
network
wording
clarification
style
query
fyi
<blank line>
Total
T
Subtotal
U
Closed
12
16
11
0
40
20
13
0
2
0
12
13
6
0
36
20
11
0
2
114
100
S
T
Resolution view Subtotal
76
Agree
0
Principle
24
Disagree
0
Out of Scope
0
Unresolvable
In process
14
<blank line>
0
Total
114
U
V
W
Closed % Still open
100%
0
81%
3
55%
5
na
0
90%
4
100%
0
85%
2
na
0
100%
0
88%
14
V
% of total
67%
0%
21%
0%
0%
12%
0%
SLIDE 4
30200 (Cabled Connected) Specifics
Current Status
•
•
Submit for “reaffirmation” ballot (underway)
Generate Amendment. Need new PAR.
• Change existing -30200 Annex F (optional) (From 10 to 10/100
Ethernet)
• Add new -30200 Annex O (informative) (MIB power vs. Ethernet
PoE “cross connect” analysis)
Rick’s recommend next steps:
• Allow reaffirmation ballot to complete
• Identify new owner to drive the 2 changes noted above
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 5
20401 Common Network Infrastructure
Current Status
• Develop transport architecture
• Overlay supporting network services
Rick’s recommend next step:
• Identify new owner or place on hold
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 6
30000 Transport Framework & Overview
Current Status
• Draft PAR language reviewed with GC (see next 2 slides)
• Submit to IEEE
• Develop Specification
Rick’s recommend next step:
• Identify new owner or place on hold
11073.Inter-LAN.2008.09.19.v02.ppt
SLIDE 7
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 identification and characterization of the transport services
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
2008 March 18
SLIDE 8
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 medical 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.
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 9
Backup slides
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 10
Specification Topology
Data & Information
Application Profiles
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 11
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.
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 12
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 Implementations
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.
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 13
Transport Philosophy
1.5.1 Leveraging Existing Commercial 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.
30000.PAR.draft.v04.ppt
2008 March 18
SLIDE 14