PCD DPI 2008-10-17 WebEx
IHE PCD Device Point-of-care Integration (DPI) profile development discussions.
Topic: IHE PCD DPI Profile TG
Date: Friday, October 17, 2008
Time: 10:00, 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.
- 1 Approve Minutes from previous session
- 2 Review Action Items
- 3 Application vs. Deployment Archicture
- 4 Review Transport Issues & Architectures for PnP
- 5 Topological Models Review
- x Open discussion
Attachments / Materials
Minutes for approval: <add minutes links here>
- Chair/Host: Todd Cooper (BSF)
- Steve Borchers (Spacelabs), John Garguilo (NIST), Colin FX (Epic), Jeff Rinda (Hospira), John Rhoads (Philips), Ken Fuchs (Draeger), Phil Raymond (Philips), Steve Merritt (Baystate Health), Jan Wittenber (Philips)
Item Topic Discussion 1 Introductions & Agenda Review
- Agenda reviewed & approved
2 Approval of Minutes
Reviewed minutes from 2008.10.15
Ken - Avoid usage of PnP? e.g., MDPnP folks, over used - more confusing than helpful Jan - also there is ALWAYS some level of configuration / pre-coordination to make it ... PnP IOW - may never be achievable e.g., -30300 A/P had pre-coordination IP addresses Ken - Break it into the "self ID" part of the protocol ... reporting ... configuration ... OR Discovery & Association OR Data Reporting (or Data Reporting Polled & Data Reporting Asynchronous) OR Bi-directional Information Exchange OR External Control
WP - include description of PnP (clear definition) + need for pre-coordination
"CLC" (closed loop control) may be similarly overloaded & misunderstood (a la real-time)
3 Wireless & Device/Patient Pairing
may have two radios (short & long range) may be manually entered Need to look at different layers of the problem ... technology dependent / independent ICE spec "nasty" is ... adding into an environment w/o disrupting other devices Must be secure, include contextual awareness, etc. ...
WP - Including section in white paper ... but may need to be addressed in subsequent phases
Thursday - Include wireless u/c & archicture discussion w/ Phil Raymond
Action(s): Enterprise Application vs. Deployment architectures
<used Ken's latest diagram to beg the question...>
BCMA can be Enterprise functions or VeriScan is a stand-alone system What does "enterprise" mean? What does DPI mean? DPI "PoC" Must be patient connected DPI is focused on FIRST communication hop... Enterprise "full blown hospital information system" vs. Speciality systems (e.g., infusion pump management systems / gateways) May have a single function BUT do so across all the enterprise
Multiple concurrent connections must be supported Device communication systems are not disconnected with each other Portal vs. local "persistent" connections
- Need to address multiple paths to the "enterprise" for the same device info (specialized servers vs. general gateway)
Where would a lab system go?
In the F2F, need to see if we can come up with a model that will clearly communicate the differences between these perspectives and the PCD TF (as well as other IHE TFs).
Action(s): DPI-PnP =>
DPI-Discovery & Association Device connecting into a "PnP" network Discovery of other patient connected devices (incl. Schluter's nurse PDA discovering & commuicating with connected devices) DPI-Data Reporting DRPolled DRAsynchronous DPI-Bi-directional Information Exchange Device Pairing / discovery of devices & information with same patient DPI-PIB Wired - port oriented / pairing operation Wireless pairing DPI-External Control Open Loop Closed Loop Device reporting local settings for display on a monitor or central station for clinician review (a la PIV "closing the loop") vs. Changes to controls w/o clinician intervention (algorithmic)
Fully automated control communication vs. Semi-automated control communication (human in the loop to complete the process) Safety Interlocks ??? Never involves clinician activation??? Alarm silence Open loop control
U/C Arith. algo on Central ... linked to bed ... comm is broken ... Must be "closed loop"
TO DO: Flesh out attributes associated with external control ... drudge out of use cases ...
DPI - Real-time Archival [and retrieval] Management "flight recorder"
DPI - Application Server Platform ??? Ability of a device to request / receive / be notification re. download of an algo / code to be run on device *** Drudge out use cases for this
DPI- Put device in "standby" mode for communication purposes (e.g., to save battery) Poll for device asset management functions (a la MEM) RTLS
n Next Meeting
- Next meeting will be the Boston face-to-face scheduled for 2008.10.23 & 24
<Add review line here when minutes are approved; e.g., "(Reviewed & approved by PCD RTM Vent TG 2008-04-16)">