Difference between revisions of "PCD DPI 2008-10-02 WebEx"

From IHE Wiki
Jump to navigation Jump to search
m (→‎Discussion: Converted "raw" text to formatted text)
m (→‎Discussion: Converted Raw minutes to formatted & complete version)
Line 82: Line 82:
 
:* Use Cases - a substantive section describing representative scnearios and providing an analysis that indicates what components fall within the DPI scope and which are addressed by other profiles and constructs.
 
:* Use Cases - a substantive section describing representative scnearios and providing an analysis that indicates what components fall within the DPI scope and which are addressed by other profiles and constructs.
 
:* 11073-00000 Framework & Overview document:  This DPI should be organized to directly inform the revised top-level 11073 Framework & Overview document.
 
:* 11073-00000 Framework & Overview document:  This DPI should be organized to directly inform the revised top-level 11073 Framework & Overview document.
−
:* "ICE" Use Cases & conceptual architecture & requirements:  The DPI should also directly address the use cases, requirements and architetures identified in the ASTM F29 "ICE" standard.  The PCD DPI profiles should include support for ICE-compliant systems.
+
:* "ICE" Use Cases & conceptual architecture & requirements:  The DPI should also directly address the use cases, requirements and architetures identified in the ASTM F29 "ICE" standard.  The PCD DPI profiles should include support for ICE-compliant systems.  
−
 
+
:* DPI WP Front Matter...
−
'''''NOTE - THESE ARE TODD'S RAW NOTES ... TO BE FORMATTED AFTER THE 2008.10.09 WEBEX'''''
+
:::- Scope:  Differentiate DPI vs. DEC
−
DPI White Paper Outline
+
:::- Audience:  IHE TF developers
−
        - Contents
+
:::- IHE PCD TF:  Should describe the relationship of DPI to the other PCD & IHE TF's
−
                Front matter...
+
:::- Regulatory Considerations:  Should point out that though DPI profiles support development of devices & systems that may fall under national regulatory oversight.
−
                          scope:  DPI vs. DEC
+
:* Use Cases:  There should be a section that presents the use cases that define the DPI scope & the logical relationship between them
−
                          audience:       IHE TF Developers
+
:* Topological Model (leading from the use cases)
−
                          IHE TF's:  Relationship of DPI with other PCD & IHE frameworks
+
:* PnP: The WP should describe the notion of PoC plug-and-play (e.g., across all 7 OSI Layers)
−
                          Regulatory considerations - cross reference white paper
+
:* Technological Archittecture...
−
                use cases & logical relationships between them  
+
:::- Transports / Service model / Abstract Device Sematic & Service model
−
                Topological model (leading from use cases)
+
:::- Peer-to-peer communication
−
                Plug-and-Play - across all 7 layers
+
:::- Network Manager / Agent
−
                Technological architecture: transports / service model / device abstract model
+
:* DPI Profile Framework (anticipated development items)
−
                          Peer to peer
+
:* Anticipated IHE documents...
−
                          Network Manager / Agent
+
:::- White Papers
−
                Anticipated framework of profiles
+
:::- Users Handbook
−
                Anticipated IHE documents
+
:* Service Components
−
                          DPI User's Handbook  
+
:::- Device Reporting
−
                Service Components
+
:::- Device configuration (simple control)
−
                          Device Reporting
+
:::- "Symmetric" communciation (device as client)
−
                          Device Configuration (simple control)
+
:::- External Control...
−
                          "Symmetric" Communication (device as client)
+
:::: Basic PnP control
−
                          External Control
+
:::: Safety Interlocks
−
                                  Basic PnP Control
+
:::: "Simple" non-therapeutic Control
−
                                  Safety Interlocks
+
:::: Therapeutic controls
−
                                    "Simple" non-therapeutic Control
+
:::: Closed-loop control (incl. QoS requirements / "contract")
−
                                  Therapeutic controls
+
:* ?ICE Supervisor function?
−
                                  Closed-loop control (incl. QoS requirements / "contract")
+
:* ?Flight Recorder / Back Box (a la "real-time storage & retrieval")
−
 
+
:* Relationship to ISO/IEEE 11073 Framework & Overview
−
                Supervisor
 
−
 
 
−
                <Flight Recorder Black Box>
 
−
 
 
−
        - <Compare to current 11073 F&O>
 
−
 
 
−
'''''=========== END RAW NOTES ====================='''''
 
  
 
'''Decisions/Issues:'''
 
'''Decisions/Issues:'''

Revision as of 18:14, 11 October 2008

(DPI Profile Main Page)

Meeting Purpose

IHE PCD Device Point-of-care Integration (DPI) profile development discussions.

WebEx Information

Topic: IHE PCD DPI Profile TG

Date: Monday, October 2, 2008

Time: 10:30, Eastern Daylight Time (GMT -04:00, New York)

Duration: 90 Minutes


Note: Specific web & phone informaiton will be provided via e-mail to group members.

Contact Manny Furst for more information.

Proposed Agenda

1 DPI Status Review
2 WebEx Planning
3 F2F Planning
4 White Paper Outline
5 Open discussion

Attachments / Materials

(no minutes were reviewed in this meeting)

Minutes

Participants

Chair/Host: Todd Cooper (BSF)
Steve Borchers (Spacelabs), Ken Fuchs (Draeger), Steve Merritt (Baystate Health), John Rhoads (Philips)

Discussion

Item Topic Discussion
1 Introductions & Agenda Review
- Chair 		Status/Discussion:

No agenda was published. The group decided on the agenda listed above.

Decisions/Issues:

Action(s):

2 Approval of Minutes
- Chair 		Status/Discussion: No minutes were reviewed

Decisions/Issues:

Action(s):

3 Discussion & F2F Planning
- Chair 		Status/Discussion:
  • The group should schedule 3-4 WebEx sessions for the next two weeks (leading up to the Boston F2F).

Decisions/Issues:

  • The Friday 2008.10.24 F2F meeting should be held at CIMIT.

Action(s):

  • (Todd) Publish Doodle poll for 3-4 WebEx sessions over the next two weeks.
  • (Todd) Contact Susan Whitehead (CIMIT/MDPnP) to arrange for Friday's room.
4 DPI White Paper Outline
- Todd 		Status/Discussion:

The group discussed the general purpose & content of the proposed DPI White paper. The following content was suggested:

  • Use Cases - a substantive section describing representative scnearios and providing an analysis that indicates what components fall within the DPI scope and which are addressed by other profiles and constructs.
  • 11073-00000 Framework & Overview document: This DPI should be organized to directly inform the revised top-level 11073 Framework & Overview document.
  • "ICE" Use Cases & conceptual architecture & requirements: The DPI should also directly address the use cases, requirements and architetures identified in the ASTM F29 "ICE" standard. The PCD DPI profiles should include support for ICE-compliant systems.
  • DPI WP Front Matter...
- Scope: Differentiate DPI vs. DEC
- Audience: IHE TF developers
- IHE PCD TF: Should describe the relationship of DPI to the other PCD & IHE TF's
- Regulatory Considerations: Should point out that though DPI profiles support development of devices & systems that may fall under national regulatory oversight.
  • Use Cases: There should be a section that presents the use cases that define the DPI scope & the logical relationship between them
  • Topological Model (leading from the use cases)
  • PnP: The WP should describe the notion of PoC plug-and-play (e.g., across all 7 OSI Layers)
  • Technological Archittecture...
- Transports / Service model / Abstract Device Sematic & Service model
- Peer-to-peer communication
- Network Manager / Agent
  • DPI Profile Framework (anticipated development items)
  • Anticipated IHE documents...
- White Papers
- Users Handbook
  • Service Components
- Device Reporting
- Device configuration (simple control)
- "Symmetric" communciation (device as client)
- External Control...
Basic PnP control
Safety Interlocks
"Simple" non-therapeutic Control
Therapeutic controls
Closed-loop control (incl. QoS requirements / "contract")
  • ?ICE Supervisor function?
  • ?Flight Recorder / Back Box (a la "real-time storage & retrieval")
  • Relationship to ISO/IEEE 11073 Framework & Overview

Decisions/Issues:

  • The DPI WP should be drafted so as to directly inform the revision of the ISO/IEEE 11073-00000 Framework & Overview standard.
  • The PCD DPI profiles should include support for ICE-compliant systems.

Action(s):

  • (Todd) Publish DPI White Paper outline & process by 2008.10.05
  • (Todd) Coordinate with Dr. Julian Goldman re. the Boston F2F schedule & agenda, and regarding IHE PCD sync with ICE & MDPnP work.
5 Next Meeting
- Chair 		Status/Discussion:

Discusion topics for upcoming meetings should include:

  • DPI Wireless Architecture
  • White Paper Outline / Content Review (probably 2 sessions, one each week)
  • 4th session topic TBD

Decisions/Issues:

Action(s):

6 Next Meeting
- Chair 		Status/Discussion:

Decisions/Issues:

  • Next meeting will be scheduled for Thursday 2008.10.09

Action(s):

Next Meeting

Next meeting scheduled for Thursday, 2008-10-09 @ 10:00 - 11:30 Eastern


<Add review line here when minutes are approved; e.g., "(Reviewed & approved by PCD RTM Vent TG 2008-04-16)">


PCD Home

Retrieved from "http://wiki.ihe.net/index.php?title=PCD_DPI_2008-10-02_WebEx&oldid=25024"