1. Project: IEEE P802.19 Coexistence TAG
January, 2005
Project: IEEE P Coexistence TAG
Submission Title: [Overview of IEEE 1073 Medical Device Communications]
Date Submitted: [17 January, 2005]
Source: [David Cypher] Company [NIST]
Address [100 Bureau Drive, Stop 8920, Gaithersburg, MD, 20899, USA]
Voice:[ ], FAX: [ ],
Re: []
Abstract: [Provides an overview of the IEEE 1073 and the desire for a liaison relationship]
Purpose: [To give members of the IEEE TAG information on what IEEE 1073 is doing.]
Notice: This document has been prepared to assist the IEEE P It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.
Release: The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P
This is a contribution of the National Institute of Standards and Technology (NIST) and is not subject to copyright in the United States of America. Contributor(s) do not have the authority to transfer ownership of this contribution to the IEEE.
This contribution was not officially approved by IEEE 1073.
David Cypher; NIST

2. Medical Device Communications
January, 2005
IEEE 1073
Medical Device Communications
David Cypher; NIST

3. Current work item needing IEEE 802.19 liaison
<month year>
doc.: IEEE <doc#>
January, 2005
Current work item needing IEEE liaison
Creating a guideline for RF usage in medical devices for point of care (PoC).
Looking at using existing wireless technologies, not creating new one, unless necessary.
Currently investigating , , , and
Engineering medical applications to use these technologies.
Heterogeneous wireless environments require coexistence evaluations.
David Cypher; NIST
<author>, <company>

4. What does a liaison relationship mean?
January, 2005
What does a liaison relationship mean?
Exchange of information (e.g., meeting minutes and notices, drafts, questions and hopefully answers) for mutual benefit of the groups involved.
Report given to each group about the other.
“Official” letters between groups may be sent.
Possible attendance at other’s meetings.
David Cypher; NIST

5. January, 2005
LMSC POLICIES AND PROCEDURES REVISED NOVEMBER 19, 2004 PAGE 32 OF 41 FILE: LMSC_P&P_NOVEMBER_2004_R0.DOC
Working Group or TAG communications
- Working Group communications with external standards bodies that are not "Information Only" shall be copied to the EC.
- Working Group communications with external standards bodies shall not imply that they represent the position of IEEE or IEEE 802. They shall be issued by the Working Group or TAG Chair(s) and the LMSC Chair shall be included in the distribution list.
EC members receiving incoming liaison letters from external standards bodies shall forward a copy to the LMSC Chair, and, as applicable, the relevant Working Group or TAG Chair.
Informal communications shall not imply that they are a formal position of IEEE 802 or of the Working Group or TAG.
David Cypher; NIST

6. Liaison IEEE 1073 (www.ieee1073.org)
January, 2005
Liaison
IEEE (
Next meeting January 28th , 2005 in Orlando, FL. (A joint meeting with HL7 and ISO TC215 WG2)
Most work is done via and weekly teleconferences (Wednesday and Thursday)
David Cypher; NIST

7. Questions? What other information does 802.19 TAG want?
January, 2005
Questions?
What other information does TAG want?
What will TAG provide IEEE 1073? - meeting minutes - official report (reviewed or approved)
David Cypher; NIST