Difference between revisions of "PCD PC&TC 2015 October 20-23 F2F Webex"

From IHE Wiki
Jump to navigation Jump to search
 
(127 intermediate revisions by 4 users not shown)
Line 1: Line 1:
  
 
[[Patient Care Device | PCD Home]]
 
[[Patient Care Device | PCD Home]]
[[Category:PCD Meeting]]
 
  
 
{{TOCright}}
 
{{TOCright}}
Line 16: Line 15:
  
 
: '''Location''':
 
: '''Location''':
:: Philips Healthcare,  
+
:- Philips Healthcare,  
 
::  951 Yamato Rd, Boca Raton, FL 33431
 
::  951 Yamato Rd, Boca Raton, FL 33431
 
::  Suite 175W
 
::  Suite 175W
::- NoteThis is a new location
+
::- Meeting room
   
+
 
::: Meeting room
+
Hotel
 +
:- Springhill Suites
 +
:: 130 NW 8th Avenue Boca Raton FL  33487
 +
:: Book at group room rate at [[http://www.marriott.com/meeting-event-hotels/group-corporate-travel/groupCorp.mi?resLinkData=PCD%20ASSOCIATION%20^PBISH%60PCDPCDA%6095.00%60USD%60false%603%6010/18/15%6010/23/15%6010/9/15&app=resvlink&stop_mobi=yes Hotel link]]
  
  
 
: '''Dates'''  
 
: '''Dates'''  
::: Monday October 19 Pump Working Group
 
::: Tuesday October 20  Joint PCD Planning and Technical Committees
 
::: Wednesday October 21 morning: PCD Planning Committee
 
::: Wednesday October 21 afternoon through Friday: PCD Technical Committee
 
  
: '''Daily Schedule''' - '''Placeholder'''
+
::: Tuesday October 20  PCD Planning Committee
 +
::: Wednesday October 21 morning: Joint PCD Planning and Technical Committees
 +
::: Wednesday October 21 afternoon through Thursday: PCD Technical Committee
 +
::: Friday October 23 Pump Working Group
 +
 
 +
: '''Daily Schedule''' -  
  
 
::: 08:00 - 08:30    Meet at Philips, Boca Raton, FL  
 
::: 08:00 - 08:30    Meet at Philips, Boca Raton, FL  
Line 36: Line 39:
 
::::: '''''Meeting will start promptly at 08:30 Eastern Time each day.'''''
 
::::: '''''Meeting will start promptly at 08:30 Eastern Time each day.'''''
  
::: 08:30 - 10:30     Session #1
+
::: 08:30 - 10:15     Session #1
  
::: 11:00 - 12:30    Session #2
+
::: 10:30 - 12:30    Session #2
  
 
::: 12:30 - 13:30    Lunch (location to be announced)
 
::: 12:30 - 13:30    Lunch (location to be announced)
  
::: 13:30 - 15:00     Session #3
+
::: 13:30 - 15:15     Session #3
  
 
::: 15:30 - 17:00    Session #4
 
::: 15:30 - 17:00    Session #4
  
::::: '''''If needed, the Friday session will end by 12:00'''''
+
::::: '''''The Friday Pump workgroup session will end by 12:30'''''
  
 
== Agenda Suggestions ==
 
== Agenda Suggestions ==
Line 78: Line 81:
 
== Webex ==
 
== Webex ==
  
Webex meetings have been set up in anticipation of interest. They will be provided when requested in advance; i.e., the log in information is provided here, and the Webex will be initiated for those portions of the agenda that are of interest. Please let the co-chairs and Manny know of your interest and when you are available. The co-chairs will try to arrange the agenda to permit your remote participation.
+
Webex meetings have been set up in anticipation of interest. They will be provided when requested in advance; i.e., the log in information is provided here, and the Webex will be initiated for those portions of the agenda that are of interest. Please let the co-chairs and Paul know of your interest and when you are available. The co-chairs will try to arrange the agenda to permit your remote participation.
  
 
Reminders: the IP agreement is in force, and participation counts toward voting rights.
 
Reminders: the IP agreement is in force, and participation counts toward voting rights.
Line 84: Line 87:
 
Please note: the log in and phone number for each meeting is the same as for our WG meetings. The password is different, and has been included in the email sent to participants.  These are not provided here for security reasons (this is a public Wiki page).
 
Please note: the log in and phone number for each meeting is the same as for our WG meetings. The password is different, and has been included in the email sent to participants.  These are not provided here for security reasons (this is a public Wiki page).
  
Monday morning: Pump WG: Meeting Number:  
+
The HIMSS Webex page is [[https://himss.webex.com/mw0401lsp13/mywebex/default.do?siteurl=himss here]]
  
Monday afternoon: Pump WG: Meeting Number:  
+
Tuesday morning, October 20: PC: Meeting Number: 922 345 610
  
Tuesday morning, October 20: Joint PC, TC: Meeting Number:   
+
Tuesday afternoon, October 20: PC: Meeting Number:  927 328 705
  
Tuesday afternoon, October 20: Joint PC, TC: Meeting Number:   
+
Wednesday morning, October 21: Joint PC, TC: Meeting Number:  927 905 271
  
Wednesday morning, October 21: PC: Meeting Number:
+
Wednesday afternoon, October 21: TC: Meeting Number: 921 745 176
  
Wednesday afternoon, October 21: TC: Meeting Number:  
+
Thursday morning October 22: TC: Meeting Number: 921 791 087
  
Thursday morning October 22: TC: Meeting Number:   
+
Thursday afternoon October 22: TC: Meeting Number:  922 601 518
  
Thursday afternoon October 22: TC: Meeting Number: 
+
Friday morning October 23: Pump WG: Meeting Number: 924 383 028
 
 
Friday morning October 23: TC: Meeting Number:
 
  
 
== Attachments / Materials ==
 
== Attachments / Materials ==
  
Documents related to the meeting '''when established '''will be found at ftp://ftp.ihe.net/Patient_Care_Devices/FaceToFaceMeetings/2014-October-Boca Raton/ unless otherwise noted. Documents are available without a password.
+
Documents related to the meeting '''when available '''will be found at the [[ftp://ftp.ihe.net/Patient_Care_Devices/Meetings/Face%20to%20Face%20Meetings/2015-Oct-Boca-F2F/ F2F ftp site]] unless otherwise noted. Documents are available without a password.
  
'''PCD Schedule/Deadline Information:''' http://tinyurl.com/PCD-Publication-Deadlines, Schedule/Deadlines: [[Patient Care Device]] and [[Domain Milestones]]
+
Schedule/Deadlines: [[Patient Care Device]] and [[Domain Milestones]]
  
 
PCD PC Action Items [[PCD Planning Committee Action Items]]. Significant changes, other than dates, will be in bold.
 
PCD PC Action Items [[PCD Planning Committee Action Items]]. Significant changes, other than dates, will be in bold.
Line 113: Line 114:
  
 
== Detailed Schedule & Agenda ==
 
== Detailed Schedule & Agenda ==
 
=== '''Monday - Pump Workgroup''' ===
 
 
  
  
 
+
=== Tuesday October 20, 2015 ===
:{|border="2"
 
|-
 
! width="10%"  align="center" |Date
 
! width="10%"  align="center" |Hours
 
! width="20%"  align="center" |Committees
 
!              align="center" |Topics
 
 
 
|-
 
| align="center" | '''Monday Morning'''
 
2014-03-31
 
| align="center" | 08:30 - 12:30
 
| Pump workgroup
 
|
 
::
 
:* Introductions
 
:* Agenda review and prioritization
 
:* [[Patent_Disclosure_Process | IHE IP Management Process]]
 
::
 
:* AGENDA TOPICS
 
::* Pump model - discuss and determine best option for channels and containment
 
::* IPEC - determine changes needed based on revised pump model
 
 
 
:* 12:30 > Lunch
 
 
 
|-
 
| align="center" | '''Monday Afternoon'''
 
2014-03-31
 
| align="center" | 13:30 - 17:00
 
| Pump workgroup
 
|
 
::
 
:* Continue discussions
 
:* Review of action items
 
::* Publish document with all pump terms and codes
 
::* Summarize changes made to pump profiles since last year
 
:* Wrap-up
 
::
 
 
 
|}
 
 
 
 
 
 
 
=== Tuesday October 20, 2014 ===
 
  
 
:{|border="2"  
 
:{|border="2"  
Line 173: Line 128:
 
|-
 
|-
 
| align="center" | '''Tuesday Q1'''
 
| align="center" | '''Tuesday Q1'''
| align="center" | 08:30 - 12:30
+
| align="center" | 08:30 - 10:15
| PCD Technical Committee (TC)
+
| PCD Planning Committee (PC)
 
|
 
|
 
:* 08:30 > [[Patent_Disclosure_Process | IHE IP Management Process]]
 
:* 08:30 > [[Patent_Disclosure_Process | IHE IP Management Process]]
 
:* 08:35 > Introductions and Agenda Review
 
:* 08:35 > Introductions and Agenda Review
:* 0900 >  TC Co-Chair Recruiting
+
:* 0900 >  Review current PCD programs (statuses, plans only, details during TC sessions):
:* 09:15 > Update from C4MI (Todd)
+
::- ACM (Monroe P)
::
+
::- DEC (updated PCD TF) (John R)
 +
::- IDCO (Paul Schluter)
 +
::- PIV (Al E, Paul E)
 +
::- IPEC (Al E)
 +
::- EC (John R)
 +
::- WCM (Chris C)
 +
::- OMS (Ken F)
 +
::- RTM (Paul Schluter)
 +
 
  
 
|-
 
|-
Line 190: Line 153:
 
| align="center" | '''Tuesday Q2'''  
 
| align="center" | '''Tuesday Q2'''  
 
| align="center" | 10:30 AM - 12:30 PM
 
| align="center" | 10:30 AM - 12:30 PM
| PCD Technical Committee (TC)(Cont)
+
| PCD Planning Committee (PC)(Cont)
 
|  
 
|  
:*  10:30 > Continue Update from C4MI
+
:*  10:30 > Continue program review
 +
::- RDQ (John R)
 +
::- DPI  (John R)
 +
::- PCIM (John R)
 +
::- MEM DMC (Monroe P)
 +
::- MEM LS (Monroe P)
 +
::- DCM Pulse Oximetry Integration Supplement(Completed)
 +
::- Pump (Al E, Paul E, Jeff R.)
 +
::- Physio monitor (John R)
 +
::- Vent (Paul Schluter)
 +
:* 11:30 > Action item Discussion
 +
:: 78. Stakeholder Survey
 +
:: 140. AAMI Alarm Safety Committee
 +
:: 157 Update cookbook to include ACM implementation
  
 
|-
 
|-
Line 203: Line 179:
 
| align="center" | '''Tuesday Q3'''
 
| align="center" | '''Tuesday Q3'''
 
| align="center" | 1:30 - 3:00 PM
 
| align="center" | 1:30 - 3:00 PM
| | PCD Technical Committee (TC)(Cont)
+
| | PCD Planning Committee (PC)(Cont)
 
|
 
|
  
:* 1:30 > Location, Dates of the PCD 2015 Spring F2F
+
:* 1:30 > Location, Dates of the PCD 2016 Spring F2F
 
:* 1:45 > Review IHE Milestones from now until Pre-Connectathon
 
:* 1:45 > Review IHE Milestones from now until Pre-Connectathon
::* [[Patient_Care_Devices | PCD Key Dates (Cycle 9)]]
+
:: IHE 2016 Publication Schedule [http://wiki.ihe.net/index.php?title=Domain_Milestone_Dates]
::* IHE 2015 Publication Schedule [http://wiki.ihe.net/index.php?title=Domain_Milestone_Dates]
 
  
  
Line 220: Line 195:
 
| align="center" | '''Tuesday Q4'''  
 
| align="center" | '''Tuesday Q4'''  
 
| align="center" | 3:15 - 5:00 PM
 
| align="center" | 3:15 - 5:00 PM
| PCD Technical Committee (TC)(Cont)
+
| PCD Planning Committee (PC)(Cont)
 
|  
 
|  
 
:* 3:15 >  
 
:* 3:15 >  
  
Adjourn PCD Technical Committee (TC) Meeting
+
:* Adjourn PCD Planning Committee (PC) Meeting
 
|}
 
|}
  
=== Wednesday October 21, 2014 ===
+
=== Wednesday October 21, 2015 ===
  
  
Line 241: Line 216:
 
| align="center" | '''Wed Q1'''
 
| align="center" | '''Wed Q1'''
 
| align="center" | 08:30 - 10:15 AM
 
| align="center" | 08:30 - 10:15 AM
| PCD Joint Planning & Technical Committee (PC & TC)  
+
| PCD Joint Planning & Technical Committee (PC & TC) and Technical Committee (TC)
 
|  
 
|  
 
:* 08:30 > Introduction
 
:* 08:30 > Introduction
Line 248: Line 223:
 
::- Review & Approve Joint PC & TC Agenda (10 minutes)
 
::- Review & Approve Joint PC & TC Agenda (10 minutes)
 
::- Review Discussion Summary Last PC & TC Meeting ''PC & TC October 14, 2015 [[PCD PC&TC 2015-10-14 Webex]] ''
 
::- Review Discussion Summary Last PC & TC Meeting ''PC & TC October 14, 2015 [[PCD PC&TC 2015-10-14 Webex]] ''
:* 09:00 > Review PCD Calendar and Update
+
:* 09:00 > HIMSS Showcase
 
+
::  MEMLS emphasis at HIMSS
:* 09:15 > :* Review Current PCD Program:
+
:* 09:30 > AAMI Showcase
 +
:* Nomenclature update (Paul Schluter
 +
:* 09:45 > Adjourn PCD Joint Planning & Technical Committee (PC & TC)
 +
:  Open PCD Technical Committee (TC)
 +
:- [[Patent_Disclosure_Process | IHE IP Management Process]]
 +
::  Announcement – Decision Making meeting (TC Co-Chairs)
 +
:* 09:50 > TC Welcome and Agenda Review (Tom Kowalczyk)
 +
::- Intellectual Property Requirements
 +
:* 09:55 > TC Cochair election
 +
:* 10:00 > Review Current PCD Program:
 
::- ACM (Monroe P)
 
::- ACM (Monroe P)
::- DEC (updated PCD TF) (John R)
 
::- IDCO (Paul Schluter)
 
::- PIV (Al E, Paul E)
 
::- IPEC (Al E)
 
::- EC (John R)
 
::- WCM (Ken F)
 
::- OMS (Ken F)
 
::- RTM (Paul Schluter)
 
::- RDQ (John R)
 
::- DPI  (John R)
 
::- PCIM (John R)
 
::- MEM DMC (Monroe P)
 
::- MEM LS (Monroe P)Specializations (statuses, plans only, details during TC sessions):
 
::- DCM Pulse Oximetry Integration Supplement(Completed)
 
::- Pump (Al E, Paul E, Jeff R.)
 
::- Physio monitor (John R)
 
::- Vent (Paul Schluter)
 
 
 
|-
 
|-
 
| align="center" | '''Break'''  
 
| align="center" | '''Break'''  
| align="center" | 10:15 - 10:30
+
| align="center" | 10:45 - 11:00
 
|
 
|
 
|  
 
|  
 
|-
 
|-
 
| align="center" | '''Wed Q2'''  
 
| align="center" | '''Wed Q2'''  
| align="center" | 10:30 - 12:30
+
| align="center" | 11:00 - 12:30
| PCD Joint Planning & Technical Committee (PC & TC)   
+
| PCD Technical Committee (TC)   
 
|  
 
|  
:* 10:30 >  
+
:* 11:00 > Test Tool update (John G)
:* 12:30 > Adjourn PCD Joint Planning & Technical Committee (PC & TC)  
+
 
 
|-
 
|-
 
| align="center" | '''Lunch'''  
 
| align="center" | '''Lunch'''  
Line 290: Line 256:
 
|-
 
|-
 
| align="center" | '''Wed Q3'''
 
| align="center" | '''Wed Q3'''
| align="center" | 1:30 - 3:00 PM
+
| align="center" | 1:30 - 3:15 PM
 
| PCD Technical Committee (TC)
 
| PCD Technical Committee (TC)
 
|
 
|
:* 1:30 > [[Patent_Disclosure_Process | IHE IP Management Process]]
+
:* 1:30 > Review Current PCD Program (continued):
::  Announcement – Decision Making meeting (TC Co-Chairs)
+
::- RTM (Paul Schluter)
:* 1:40 > TC Welcome and Agenda Review (Jeff McGeath)
 
::- Intellectual Property Requirements
 
:* 1:45 >
 
  
 
|-
 
|-
Line 306: Line 269:
 
|-
 
|-
 
| align="center" | '''Wed Q4'''  
 
| align="center" | '''Wed Q4'''  
| align="center" | 3:15 - 5:00 PM
+
| align="center" | 3:30 - 5:00 PM
 
| PCD Technical Committee (TC)
 
| PCD Technical Committee (TC)
 
|  
 
|  
  
:* 3:30 >  
+
:* 3:30 > IPEC (Al E, Jeff R)
 +
:* 4:30 > Whitepaper - MEMDMC communication from systems to devices (EPIC/Matt Rush)
 +
:: [[ftp://ftp.ihe.net/Patient_Care_Devices/Meetings/Face%20to%20Face%20Meetings/2015-Oct-Boca-F2F/ FTP link]]
 +
 
 +
 
 
|}
 
|}
  
=== Thursday October 22, 2014===
+
=== Thursday October 22, 2015===
  
  
Line 329: Line 296:
 
|
 
|
 
:* 08:30 > [[Patent_Disclosure_Process | IHE IP Management Process]]  
 
:* 08:30 > [[Patent_Disclosure_Process | IHE IP Management Process]]  
:* 8:35 > Review of On-going work
+
:* 8:35 > Point-of-Care Identity Management (PCIM) white paper (John R)
::* ACM (Monroe)
+
 
::* RDQ
 
::* WCM (Ken F)
 
::* OMS (Ken F)
 
::* RTM / RTMMS (Paul Schluter)
 
::* MEM DMC (Monroe P)
 
::* MEM LS (Monroe P)
 
 
|-
 
|-
 
| align="center" | '''Break'''  
 
| align="center" | '''Break'''  
Line 347: Line 308:
 
| PCD Technical Committee (TC)
 
| PCD Technical Committee (TC)
 
|  
 
|  
:* 10:00 >  
+
 
 +
:- Private Terms (Paul Schluter)
 +
 
 +
:- Continue Profile Review:
 +
:: IDCO (Paul Schluter)
 +
:: DEC (updated PCD TF) (John R)
 +
:: PIV (Al E, Paul E)
 +
:: EC (John R)
 +
:: WCM (Ken F)
 +
:: OMS (Ken F)
 +
:: DPI  (John R)
 +
:: MEM DMC (Monroe P)
 +
:: MEM LS (Monroe P)
 +
:: Pump (Al E, Paul E, Jeff R.)
 +
:: Physio monitor (John R)
 +
:: Vent (Paul Schluter)
 +
 
 +
:* [[http://wiki.ihe.net/index.php?title=PCD_Technical_Committee_Action_Items TC Action item]] review
 +
:: 118. Implementation Guide
 +
:: 140. Assemble the Baseline Set of Standards for Easy Reference
 +
:: 143. Describe HL7 Version Implications
 +
:: 150. Seek null flavors in HL7 2.9
 +
:: 167. Versioning and Archiving
 +
:: 170. Convert IPEC to EC
 +
:: 178  MSH-5 and Connectathon
 +
:: 179. IPEC and EC documentation
 +
 
 +
 
 +
:* 10:00 > Continue TC Action item review
 +
:: 183  CP for WCM and implementation
 +
:: 186  Review and reformat ftp site
 +
:: 189  Identify unique identifiers before the Connectathon
 +
:: 190  PRT Segment Use
 +
:: 191  Liaise with IDCO on Waveform communication
 +
:: 192  FHIR
 +
 
 +
:*  11:00 > ACM change to containment MDC codes and MSH-21 OID change (Monroe)
 +
 
 +
:*  11:30 > Proposal Review
 +
:: Communication Between Devices - DPI Working Group  (Angela Merzweiler)
 +
:: Workflow Profile  (Angela Merzweiler, Björn Bergh)
 +
:: [[ftp://ftp.ihe.net/Patient_Care_Devices/Meetings/Face%20to%20Face%20Meetings/2015-Oct-Boca-F2F/ FTP link]]
 
|-
 
|-
 
| align="center" | '''Lunch'''  
 
| align="center" | '''Lunch'''  
Line 359: Line 361:
 
| PCD Technical Committee (TC)
 
| PCD Technical Committee (TC)
 
|
 
|
:* 1:30 >  
+
:* 1:30 > Security Discussion (Axel)
 +
:* 2:30 > Proposal Review (cont.)
 +
 
 
|-
 
|-
 
| align="center" | '''Break'''  
 
| align="center" | '''Break'''  
 
| align="center" | 3:00 - 3:15 PM
 
| align="center" | 3:00 - 3:15 PM
 
|
 
|
|  
+
|
 
|-
 
|-
 
| align="center" | '''Thursday Q4'''  
 
| align="center" | '''Thursday Q4'''  
Line 370: Line 374:
 
| PCD Technical Committee (TC)
 
| PCD Technical Committee (TC)
 
|  
 
|  
:* 3:15 >  
+
:* 3:15 > IEEE to LOINC mapping (Paul Schluter)
::* Wiki page Maintenance
+
:* 4:00 > F2F Action Review (from this week)
 +
:* 4:45 > TC Meeting Wrap up and Adjournment (Kowalczyk)
  
  
 
|}
 
|}
  
=== Friday October 24, 2014 ===
+
=== Friday October 24, 2015 (Pump Workgroup) ===
  
  
Line 388: Line 393:
 
|-
 
|-
 
| align="center" | '''Friday Q1'''
 
| align="center" | '''Friday Q1'''
| align="center" | 08:30 - 10:15 AM
+
| align="center" | 08:30 - 12:00
| PCD Technical Committee (TC)
+
| Pump workgroup
 
|
 
|
:* 08:30 > [[Patent_Disclosure_Process | IHE IP Management Process]]  
+
::
:* 8:35 > TC Action items not yet addressed  [[PCD Technical Committee Action Items]]
+
:* Introductions
 +
:* Agenda review and prioritization
 +
:* [[Patent_Disclosure_Process | IHE IP Management Process]]
 +
::
 +
:* AGENDA TOPICS
 +
::* Pump model - discuss and determine best option for channels and containment
 +
::* IPEC - determine changes needed based on revised pump model
 +
 
 +
:* 12:00 > Meeting Adjournment
 
|-
 
|-
| align="center" | '''Break'''
 
| align="center" | 10:15 - 10:30 AM
 
|
 
|
 
 
|-
 
|-
| align="center" | '''Friday Q2'''
 
| align="center" | 10:30 - 12:00 PM
 
| PCD Technical Committee (TC)
 
|
 
:* 10:30 > F2F Action Item Review (from this week)
 
:* 12:00 > TC + Meeting Adjournment (McGeath)
 
|-
 
|-
 
| align="center" | '''Lunch'''
 
| align="center" | 12:00 - 1:00
 
| Paul Sherman
 
|
 
:* Box Lunch (if sufficient number of participants on site)
 
|-
 
|-
 
| align="center" | '''Friday Q3'''
 
| align="center" | 1:00 - 3:00 PM
 
| Working Groups
 
 
:Separate WG Meetings if needed
 
 
  
  
Line 433: Line 421:
 
== Participants ==
 
== Participants ==
  
'''Tuesday, October 21'''
+
'''Tuesday, October 20'''
  
 
On Site:  
 
On Site:  
  
Todd Cooper, Bikram Day, Paul Elletson, Kurt Elliason, Al Engelbert, John Garguilo, Bob Gold, Joe Good, Jeff McGeath, Monroe Pattillo, Doug Pratt, John Rhoads, Paul Schluter, Paul Sherman
+
 
  
 
Remote:  
 
Remote:  
  
Casey Chester (Iatric), Manny Furst, Brian Reinhold, Tom Kowalczyk, Stan Wiley
 
  
'''Wednesday, October 22'''
+
 
 +
'''Wednesday, October 21'''
  
 
On Site:  
 
On Site:  
  
Bikram Day, Paul Elletson, Kurt Elliason, Al Engelbert, John Garguilo, Bob Gold, Joe Good, Jeff McGeath, Monroe Pattillo, Doug Pratt, John Rhoads, Jeff Rinda, Paul Schluter, Paul Sherman
+
 
  
 
Remote:  
 
Remote:  
  
Chris Courville, Manny Furst, Tom Kowalczyk, Alex Lippitt, Stan Wiley
 
  
  
'''Thursday, October 23'''
+
 
 +
'''Thursday, October 22'''
  
 
On Site:  
 
On Site:  
  
Bikram Day, Paul Elletson, Kurt Elliason, Al Engelbert, John Garguilo, Bob Gold, Joe Good, Jeff McGeath, Monroe Pattillo, Doug Pratt, John Rhoads, Paul Schluter, Paul Sherman
 
  
Remote:
 
  
Manny Furst, Tom Kowalczyk, Alex Lippitt, Brian Reinhold, Ioana Singureanu, Greg Staudenmaier, Sandy Vance, Stan Wiley,
+
Remote:
  
 
== Discussion ==
 
== Discussion ==
Line 468: Line 454:
 
Discussion Summaries do not require formal approval, while minutes of meetings where votes are taken do. Participants are encouraged to review and bring up significant issues with discussion summaries of previous meetings. Votes will be taken to approve meetings where votes took place; these may be email ballots.
 
Discussion Summaries do not require formal approval, while minutes of meetings where votes are taken do. Participants are encouraged to review and bring up significant issues with discussion summaries of previous meetings. Votes will be taken to approve meetings where votes took place; these may be email ballots.
  
=== Monday ===
+
=== Tuesday ===
Pump Working Group
 
  
 
:{|border="2"  
 
:{|border="2"  
Line 480: Line 465:
 
| '''Introductions & Agenda Review''' <br>- Chair
 
| '''Introductions & Agenda Review''' <br>- Chair
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
 +
:  Monroe reviewed the IHE IP Management Process
 +
:  Introductions and Agenda Review
 +
:
 
'''Decisions/Issues:'''
 
'''Decisions/Issues:'''
: Agenda approved  '''Placeholder'''
+
: Agenda approved   
 
'''Action(s):'''
 
'''Action(s):'''
  
Line 488: Line 476:
 
| '''Discussion Summary or Approval of Minutes''' <br>- Chair
 
| '''Discussion Summary or Approval of Minutes''' <br>- Chair
 
| '''Status/Discussion:'''  
 
| '''Status/Discussion:'''  
:- Accepted: Planning Committee November 14 '''Placeholder'''
 
  
 +
: Minutes approved
  
 
'''Decisions/Issues:'''
 
'''Decisions/Issues:'''
: : 1. Agenda Review
+
:  
:2. IP Patent Disclosure Notification (https://docs.google.com/presentation/d/1w4rDh1jxBLV2w1RL0nGtmCPvKcYAxWqmIO_H5UqS9g4/edit#slide=id.g10b420c04_3_27)
 
 
 
: 3. General Status Update
 
 
 
: - Recap PCD Infusion Pump informatics activities
 
:: @ C4MI, engineer has completed comparison / harmonization efforts between the draft -10101a amendment document, the RTMMS definitions and the last Excel file; is now able to re-create the Excel file ... though it is tedious
 
:: RTMMS Tagging now provided - thank you Nicolas!!!
 
:: MyDevice ready for use in approx. 3 weeks - C4MI will update with pump model (See 2014 Chicago update files)
 
 
 
:- IEEE 11073-10417 (?) Insulin Pump Update
 
::  ACTION(Todd) Provide draft doc to IP group (Doug, Jeff)
 
::  ACTION(Todd) Provide pump model to IEEE PHD group
 
:: Todd described activity to the PCD group; no vendors currently involved have these kinds of devices or consume information from these devices (though "home device" divisions may)
 
 
: - HL7 FHIR Update
 
:: See slides from Chicago 2014-09 update
 
:: C4MI continues to drive FHIR for Devices standardization & prototyping; also engaged are Epic and Draeger
 
:: FHIR DSTU #1 includes 2 Resources for devices (Device, DeviceObservationReport); subsequent prototyping work, though, has resulted in the deprecation of the DeviceObservationReport, which is now being replaced by additional resources and resource profiles that more closely represent the 11073-based information; this includes support for alert communication
 
:: Due to this continued evolution, completion of the IHE PCD FHIR White Paper remains on a back burner
 
:: NOTE:  HL7 FHIR was a major topic at the ONC 10/15 joint PC/SC meetings in D.C. last week, where there are calls to establish open API standards that many identify HL7 FHIR as providing;  with device informatics included, this would be an easy way to get device information into the mix
 
:: Question:  How to get PCD companies to recognize importance?
 
 
 
: -  AAMI PCA ICS + AAMI/UL 2800
 
:: No current engagement in either of these efforts w.r.t. advancing pump informatics from IHE PCD or IEEE 11073
 
 
 
: -  C4MI Update @ Infusion Pumps
 
:: Supporting supporting PCD pump informatics development & IEEE 10101a update
 
:: PIM modules @ PCD transactions
 
:: FHIR prototyping @ pump informatics
 
::  Will leverage all the pump modeling / terminology components in its medical device interoperability (MDI) campaigns.
 
 
 
: 1.  Finalize Channel / Mode Nomenclature
 
:-  ACTION (Todd)  Replace RTMMS "Vendor VMD" content with containment using updated "labels"
 
:- Channel Discussion:
 
:: What does a consuming system need to see from a pump?
 
::- Medication administration information
 
::: Focus is the medication
 
::- Device (infusion pump) information
 
::: Device type & configuration
 
::: Battery status
 
:::  Alert status
 
::: On / Off Line
 
 
 
::- Applications (Use cases) to consider
 
 
 
::: EMR Charting / Flow Sheet
 
:::- Infusate / Medication Delivered  to Patient
 
:::: Infusate / Drug / Amount / Timestamp
 
:::: Patient / Clinician Initiated Dosing
 
:::: Order ID
 
::: Communication Status (staleness of information)
 
:::- NOT: 
 
:::: Device type
 
:::: Fluid Path (e.g., A or B)
 
:::: General operational mode programming
 
 
 
::: Billing
 
:::- Start of Container delivery (bag is spiked)
 
:::- Order ID
 
:::- Future: End of Container (easy @ syringe, not available @ bag)
 
 
 
::: Rx / Manufacturing
 
:::- NOTE: pharmacy monitoring when new container medication is needed
 
:::- Order ID
 
:::- Remaining VTBI
 
:::- Remaining Time
 
:::- Communication Status (would need to recognize probability that medication is being delivered, though status reporting is not available)
 
 
 
::: Infusion Administration / Programming
 
:::- NOTE:  Nurse @ bedside, includes BCMA system usage
 
:::- Order ID
 
:::- Programmed Settings
 
:::- Infusate source (A or B)
 
:::-Mode?
 
:::: Piggyback
 
:::: Future:  multi-step, ...
 
:::- Audit Log (Programming changes @ bedside)
 
 
 
::: Nurse Workflow / Dashboard
 
:::- Charting + ...
 
:::- Remaining VTBI / Time
 
:::- Current Status (infusing / not infusing)
 
 
 
::: Alarm Communication
 
:::- Charting + ...
 
:::- Pump alert condition (e.g., occlusion, Air-in-Line, door open, ...)
 
 
 
:- Pump Containment Labeling
 
:: NOTE:  MDC_DEV_PUMP_
 
:: Primary Channel => Primary Infusate Source  [MDC_DEV_PUMP_INFUSATE_SOURCE_PRIMARY]
 
:: Secondary Chanel =>  Secondary Infusate Source [ MDC_DEV_PUMP_INFUSATE_SOURCE_SECONDARY]
 
:: Clinician Dose Channel => Clinician Dose Info [MDC_DEV_PUMP_CLINICIAN_DOSE_INFO]
 
:: Patient Dose ("PCA") Channel => Patient Dose Info [  MDC_DEV_PUMP_PATIENT_DOSE_INFO]
 
:: Loading Dose Channel =>  Loading Dose Info [ MDC_DEV_PUMP_LOADING_DOSE_INFO]
 
:: Syringe Channel => Syringe Info    [MDC_DEV_PUMP_SYRINGE_INFO]
 
:: Delivery Channel => Pump Delivery Info  [MDC_DEV_PUMP_DELIVERY_INFO]
 
:: New:  Intermittent Dose Info  [MDC_DEV_PUMP_INTERMITTENT_DOSE_INFO]
 
:: - This is defined when it can run concurrently with a Primary or Secondary drug source
 
::-  Default programmed delivery mode = multi-dosing
 
::-  Need to flesh out more complete parameter set as a separate exercise
 
 
 
:- Parameters
 
:: @ "Source" Info:
 
::- Programmed Delivery Mode:  continuous, ramp-taper, multi-step, multi-dosing
 
::: Present in ...
 
:::- @ Primary / Secondary = all of the above
 
::: Not present in "dose info" constructs
 
::- Program Completion Mode:  Stop, KVO, Continue
 
::-  Flush Enabled:  Yes / No
 
::-  Current Delivery Status:  inter-dose-stop, Priming, flush, KVO, delivering, delaying, not delivering
 
::: KVO is optional after completion of the programmed delivery mode
 
::: Priming - All other mode / delivery parameters are out-of-scope
 
::- Program Status:  Not Started, Active, Complete
 
:::  ACTION:  Remove from Not Infusing Reason "pump-stopped-ready-no-started", "pump-stopped-delayed-start", "pump-stopped-delivery-complete", "pump-stopped-between-doses" ... review entire list for pump-wide vs. programmatic states
 
::- Source Label => "Primary" "Secondary"
 
::- NOTES:
 
::: Can have separate KVO optionality settings + different KVO rates on infusate sources  [KVO rate may be same as continuous rate]
 
::: On PCA, can go into KVO while delivery limited (by dosing parameters) then pick up basal rate, etc.
 
::: "Standby" should be handled by using Not Infusing Reason in Delivery Info
 
:: @ Delivery Info
 
:: - Active Sources:  <see list above, except Syringe & Delivery>
 
::- Multi-Source Mode:  Single, Piggyback, Concurrent
 
::- Enabled Sources:  <see list above, except Syringe & Delivery>
 
 
 
:- Question:  Where to locate the Drug Library parameters?
 
:: MDC_PUMP_DRUG_LIBRARY_CARE_AREA @ Primary & Secondary Sources + Dose Info
 
:: MDC_PUMP_DRUG_LIBRARY_VERSION    @ Delivery Info
 
 
 
:- Question:  Infusion Pumps w/ multiple Channels => VMDs:  Separate into different PCD-01?
 
:: ACTION:  In PCD TF-1 binding to Infusion Pump Specialization, limit one TF-3 / VMD  (Delivery + sources) per TF-2/ PCD-01 & PCD-10
 
:: NOTE:  This limitation cannot be generally applied to device data reporting, and thus is not a constraint for TF-2
 
:: For infusion pumps, a future TF-1 infusion pump specialization, will bind a constrained value set (TF-3 Infusion Pump) to transactions (TF-2 / PCD-01 or PCD-10), and constrain for an infusion pump that a transaction should only include pump VMD info for a single device.
 
:- Question:  Parameters in PCA dose info
 
::  ACTION:  Harmonize PCA w/ Primary parameters (duplicate Primary & add in PCA specific); review resulting set with group
 
 
 
: 2.  IPEC - determine changes needed based on revised pump model
 
:- NOTE:  No changes to IPEC for NA CAT'15
 
 
 
: 3. Action Plan
 
:- Summarize changes made to pump profiles since last year
 
::  ACTION(C4MI) identify differences between RTMMS IP 1.0 & Excel 1.2 & -10101a Draft; review with team
 
:: - Compare Excel 1.2 (latest published) vs. current export vs. NA CAT'14 version (1.1 2014.01.15)
 
::  ACTION(IP WG) Use the above to finalize the NA CAT'15 infusion pump data set
 
::-Determine CAT'14 version differences and current RTMMS IHE_PCD_IP_REL_1.0
 
::-Decide what will be used for NA CAT'15 ... targeting Excel spreadsheet ver 1.3
 
:-  NA CAT'15 ramifications
 
:: Question:  Given timing (2014.10) ... should all these modifications be held until after NA CAT'15?
 
::- DECISION:  Yes.  Given the lateness of these changes, it would be too disruptive for the January changes
 
::- NOTE:  These changes only impact testing of IPEC (e.g., calls out Pump Mode Set), not DEC (since there are currently no pump specializations)
 
:: IF a pump vendor updates their reporting per the above model, it will still be able to pass the NA CAT'15 tests, but this would be an individual basis
 
::  ACTION:  Discuss with Garguilo (a) profile versioning support; (b) NA CAT'15 ... will there be an impact related to the above changes (esp. updates to RTMMS)
 
:- Finalizing 11073-10101a Amendment
 
:: Finalize definitions & document
 
::- ACTION:  Update draft -10101a document per the above changes
 
:- Updating Collateral / Publish document with all pump terms and codes
 
:: Migrate to RTMMS
 
:: Update Vendor VMD with containment
 
:: "Tag" pump parameters / UoM / Enumerations in RTMMS for export as a constrained value set
 
::  Create updated Excel spreadsheet
 
:- Updating TF (TBD timing)
 
:: TF-3 with new pump section
 
:: TF-1 with Infusion Pump Specialization(s) (LVP, PCA, Syringe)
 
:: Working Plan
 
::- Next steps (near term) ...
 
:::  Review & Finalize -10101a content
 
:::  Review & Finalize NA CAT'15 data set
 
::- Update IPEC per new model
 
 
 
  
 
'''Action(s):'''
 
'''Action(s):'''
Line 666: Line 486:
 
|-
 
|-
 
| align="center" | 3
 
| align="center" | 3
| '''Agenda Items''' <br>- Standards Coordination
+
| '''Agenda Items''' <br>-
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
  
 +
:* Review current PCD programs (statuses, plans only, details during TC sessions):
 +
:- ACM (Monroe P)
 +
:: Updates in PP file on ftp site
 +
:: (Monroe has slides for all 3)
 +
:- MEMDMC
 +
:: Updates in PP file on ftp site
 +
:- MEMLS
 +
:: Updates in PP file on ftp site
 +
:: Discussion on encouraging further vendor participation.  How to encourage them to join MEMLS?  Approach hospitals to pressure them, medical device vendors when deploying, Examined DARPA work as well (Inertial guidance if  GPS not available) – useful for home care. 
 +
:- DEC (updated PCD TF) (John R)
 +
::  Very slight evolution, no substantial change.  A couple of explanatory pieces in the TF update. 
 +
:- IDCO (Paul Schluter)
 +
:: Extension for 10103a submitted, should be approved.  Extensions on items not already addressed.  Making progress.  Plan on January 2017 Connectathon participation.  Concern over costs in attending the Connectathon. 
 +
:- PIV (Al E, Paul E)
 +
:: Not much new.  Some TF updates. 
 +
:- IPEC (Al E)
 +
:: Worked on pump model, finalizing with proposed CP.  Mostly it's a TI implementation, just need TC review, then send to Mary so she can publish for public review.
 +
:- EC (John R)
 +
:: IPEC working well.  Other possible is MEMDMC.  Unsure if this needs a general profile or keep it within specific profiles.  Monroe – there is some commonality, may be good to have design goals and guidance for all to use.  Jeff R - Question on how all profiles combine.  Could use a guide for new participants.
 +
:- WCM (paul Sc)
 +
::  Know what the updates are, need to write them up.  Right now it's adhoc strings. Some Cps are out, just need to write them up.  Would be good to have MDC/REFID to outline them.  How granular?  Stream or Static.  Two formats currently.  Continuous wasn't originally indicated; hadn't looked at it yet.  Discussion of transition between static and dynamic (snippet and continuous). 
 +
:- OMS (Ken F)
 +
::  published a white paper a while back, not much activity.  In China – most devices are RS-232 serial.  If they start implementing HL7, this will be useful.
 +
:- RTM (Paul Schluter)
 +
:: Several related items.  Standards – ACM code hiccup, delayed approval.  Should be approved Dec 5, published Dec 9, to NIST Dec 10.  Different Word fonts make it interesting; formatting to make the document clean and open in HTML.  Should be ready for downloading.  Hope to have ready for Pre-CN for trial work and fully ready for CN.(gone 9:57 – 10:10). 
 +
:- Polysomnography
 +
:: Monroe discussed Polysomnography in IHE Brazil.  Challenge – need a mechanism to 'package' individual equipment info into a single report.  If we can get a sample report to build from, that would help.
 +
:- RDQ (John R)
 +
:: Quiescent.  Asks for past data dump.  Well documented and available, but few want to use it.  Not sure when it will be implememted.  ACM used to have their own, extracted it and recommend using RDQ.  Paul Sh – one company registered for RDQ at Connectathon, CardioPulmonary Corp.  This may be superseded by something based on FIHR.
 +
:- DPI  (John R)
 +
::  Work sporadic, sharing with automating device info model.  Proposal sent touches on several areas, including DPI.
 +
:- PCIM (John R)
 +
::  Creating a WP to aid implementation.  Any vendors creating material?  Yes, Epic, Philips and others are working on that.
 +
:- Pulse Ox
 +
::  Need resources to take this further
 +
:- Pump (Al E, Paul E, Jeff R.)
 +
:: Discuss profile enhancements later this week.  Work group meets Friday morning
 +
:- Physio monitor (John R)
 +
::  Basic Vol 3 content specification available.  Todd is considering adding to it, but doesn't have resources to do it now. 
 +
:- Vent (Paul Schluter)
 +
::  10101a has 50 pages in it, will expand in 10101b.  Message content good, will add additional terms as vendors request.  Will include events in 10101c. 
 +
:- Certification (John G)
 +
:: Just had CASC meeting.  They've ID'd some PCD profiles to work on.  They're trying to ID what other tasks are needed to comply ISO standard.  Charles asked if there are scenarios we would test to around Connectathon time.  Quickly developing, a big effort under IHE Intl.  The focus is on the end user side.  Monroe provided some certification background.  Testing rigor is there.  This group wants to  focus on mature profiles.  Discussed certification process.  Can we improve Connectathon testing to provide this info to customers?  Yes, but it will take a lot of work.  Key is to define specializations in Vol 3.  Can develop test plans to define scenarios, then add specializations. 
  
 +
:* 11:30 > Action item Discussion
 +
:- 78. Stakeholder Survey
 +
::  Associated with AAMI representation.  Not active yet.  Will close and open a new one for ECRI.  Juuso will check with ECRI staff to see if they're willing to do a survey with their customers.
 +
:- 140. AAMI Alarm Safety Committee
 +
::  Close until it resurrects with Joint Commision analysis of Alarm fatigue.  Start a new Action Action for this. 
 +
:- 157 Update cookbook to include ACM implementation
 +
:: Resource availability limited ability to update so far.  Jeff R willing to look at the pump part and Rob will look into the ACM part.  Change date to Nov 11.
  
 +
:* 12:00 > Use of 11073 terms in HL7.  (Epic) – 
 +
::  Discussed at IEEE/HL7 meetings.  Most of our terms will be used in Rosetta without formal acceptance.  Not as solid as we would like it, but it's usable.  Numeric codes and REFIDs are freely available.  Yes, but it's better too include IEEE terms as well.
  
'''Decisions/Issues:'''
+
:* 1:30 > Location, Dates of the PCD 2016 Spring F2F
 +
:: West Health Institute, in San Diego (AFC)
 +
:: Likely 2nd week of  April, paul will confirm and provide to the Committees
  
 +
:-  Review Connectathon milestone dates
 +
:-  Review IHE Milestones from now until Pre-Connectathon
 +
:- IHE 2016 Publication Schedule [http://wiki.ihe.net/index.php?title=Domain_Milestone_Dates] 
  
'''Action(s):'''
+
:: Long term Roadmap [[ftp://ftp.ihe.net/Patient_Care_Devices/Roadmap_and_Calendar/  Roadmap ftp link]]
  
 +
:-  Cycle 11
 +
:: Architecture:  We use 2.6, moving to 2.8 and 2.8.2  (UDI, PCM uses it)
 +
:: DEC: 
 +
::- RDQ not at FT, moved out to 2016
 +
:: PCD02:  In TF
 +
:: MEMDMC profile options, WCM option for DEC,
 +
:: Smart Alarms:  Move to Cycle 12
 +
:: RDQ profile specific work:  move to Cycle 12
 +
:: IPEC
 +
::-  Device order Management
 +
::: Multi componnent admixtures:  Pump roup will discuss this week, may go away
 +
:: MEM:  Final text – not enough vendors yet, moved to 2017
 +
::  Cybersecurity/Patching Wps – underway
 +
::  Point of Care:
 +
::-  DPI no change.  Overlatp with a proposal?  Yes, likely
 +
::-  Symmetric Comms: 
 +
::-  UML model – fairly complete, add to calendar for 2016.
 +
::-  DIM editor – V1  mostly done, should be ready in 2016
 +
:: Content Management
 +
::- 10101b for new terms Q4 2016
 +
::- 10101c Q2 2017
 +
::- Map IEEE to LOINC
 +
:: WCM – updated TI
 +
:: IPEC:  Jeff R will submit updated CPs for IPEC TI.  Will be several updated CPs.
 +
::- PCA Content in IPEC TI – change to pump specialization and move to 2016. 
 +
:: Vent Specialization in RTMMS and PCD TF Vol 3 - 2016
 +
:: Coordination Efforts
 +
::- Sending PCHA records (PCC) – Can use LOINC mapping, but says SNOMED now (unlikely).
 +
::- HIMSS ONC MU standards – 11073 distant 2nd to other standards. 
 +
:: Quality
 +
::- IEC 60601 - 60601.1.? specific Alarm info not released yet
  
|-
+
Adjourn PCD Planning Committee (PC)
| align="center" | 4
 
| ''' ___ '''
 
| '''Status/Discussion:'''
 
http://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_8#Cycle_8_WorkItem_Candidates
 
  
  
 +
'''Decisions/Issues:'''
  
'''Decisions/Issues:'''
 
  
 
'''Action(s):'''
 
'''Action(s):'''
 
 
  
 
|}
 
|}
  
=== Tuesday ===
+
=== Wednesday Morning ===
  
 
:{|border="2"  
 
:{|border="2"  
Line 705: Line 607:
 
| '''Introductions & Agenda Review''' <br>- Chair
 
| '''Introductions & Agenda Review''' <br>- Chair
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
:  Monroe reviewed the IHE IP Management Process
 
:  Introductions and Agenda Review
 
: - Monroe – Agenda modified to reflect scheduling with presenters and other groups.
 
 
'''Decisions/Issues:'''
 
'''Decisions/Issues:'''
: Agenda approved   
+
: Introductions
 +
: Reviewed the IHE IP Management Process
 +
: Reviewed & approved Agenda (10 minutes)
 +
: Reviewed and approved Oct 14 PC/TC Meeting discussion summary
 +
: Reviewed PCD Calendar and Update "PCD ftp site [[ftp://ftp.ihe.net/Patient_Care_Devices/]]"
 +
 
 
'''Action(s):'''
 
'''Action(s):'''
  
Line 716: Line 620:
 
| '''Discussion Summary or Approval of Minutes''' <br>- Chair
 
| '''Discussion Summary or Approval of Minutes''' <br>- Chair
 
| '''Status/Discussion:'''  
 
| '''Status/Discussion:'''  
 
+
 
+
'''Decisions/Issues:'''  
'''Decisions/Issues:'''
 
:
 
  
 
'''Action(s):'''
 
'''Action(s):'''
 +
: Oct 14 PC/TC summary approved
  
 
|-
 
|-
 
| align="center" | 3
 
| align="center" | 3
| '''Agenda Items''' <br>-
+
| '''Agenda Items''' <br>-  
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
  
 +
:- AAMI Showcase
 +
:: In Tampa this time.  No HIMSS showcase.  Likely back to 10x20 display, should reduce costs a bit.  Will piece together a demo.  There will be more info coming.
  
 +
:-  AP/Lab domain merger.
 +
::  How active is lab?  Fairly active, not sure what their current specifics are.  Paul Sc – what standards are they using?  Any MU used?  Monroe – good questions, send them to him to ask at next week's DCC call. 
  
: PC and TC Co-Chair Recruiting
+
:- HIMSS Showcase
: - If interested contact Jeff, Monroe or Paul Sh
+
::  Family of four didn't quite work, will have 15 patients independent of each otherWill minimize overlap in vignettesFewer devices per vignette allows more time for each vendorDocents will work with vendors to discuss devices with visitorsWill help between tours as wellReduced use cases by two, allowing more frequent tours.  
: - Todd - Modified term limit requirement to recommendation
+
:: Proposed having badge scanners for each vignetteHelps ID walk-ups and tours of specific vignetteShould help with lead creation.  
 
+
::  Started discussing use cases with vendorsVendors now can select vignettes, rather than have them assignedThey are listed on the page as well.  
Update from C4MI (Todd)
+
:: Prospectus on Showcase web page with levels of participationPhilip provided an overview of what vendors get for different levelsDiscussed 'Leadership' level benefits.
: - 1.      IHE International Update -
+
::  MEMLS emphasis at HIMSS No one has signed up yetOne vendor participated last year as location services providorHe hasn't signed up yetWe will ping him to sign upIs the Showcase in the same place as last time? Unofficially yes.  Will provide signs to connect vendor booths with the ShowcaseHope to provide more directions, etc. to drive traffic to the ShowcaseThere are event spots availableRob - Is this being communicated to our marketing people?  Yes.
::450-500 organizational members
+
::  Why the issue of location in VegasThey don't want to give up prime floor space for the Showcase. Much like Chicago Connectathon spaceThere are space constraints.   
:-    Financial Sustainability
+
:: Monroe's relationship with the ShowcaseWanted someone to manage PCD interfaces with the vignettesWill start PCD calls in November.   
::  Clear message from HIMSS and RSNA – not funding in perpetuity.  Needs to be self supporting
 
:: PCD was asked why not meet with other domains at RSNA, etc. Most PCD members don't attend those meetings, no real financial benefit.   
 
::  IHE sent out a survey early this year – what activities would the members be able to support? 
 
:: - Set up membership dues and activity fees.
 
:: - Service offerings? Like continuous virtual CN.  Not put forth as a revenue model yet.
 
:: - Other sustainability models?  Not sure check the poll.
 
:- Members discussed the company looking for certificates - is this a possible revenue stream?
 
 
 
::  International /New countries
 
:: - John G – Questions regarding Colombia CN  Is ther any formal process, guidelines, etc?  Would like to discuss with Todd.
 
::: Discussion - Sponsors must be non-commercialUsually someone on board helps mentor – not requiredVladimir participates quite a bit.  Provide deployment committee reports.  Board may have someone work with that country.
 
::-    Strategic Coordination
 
::: Internally – Board retereat early July.  Prioritize what needed done.  IHE wide integration strategy, nothing currently exists for multi domain profilesTooling and reference designs high priority. 
 
::: Monroe – concern of repeated work; LS and ACM as examplesSome discussion at DCC about this.
 
::: TC - can go back before next reteat and bring this up
 
 
 
: - 2    FDA @ IHE PCD Update
 
:: Got past ANSI process/standard requirement.
 
:: FDA asked for a briefing. Slides provided, will be posted to the ftp siteIHE PCD compliant list impacted FDA.
 
 
 
: - 3  PIM (Protocol interoperability Manager) - Supports various protocols (HL7, IHE PCD, IEEE 11073, etc.)  Package includes source code, risk analysis, support documentation, etc.  Hope to have some deliverables mid 2015Outlined architecture.  Submitted standardization projects to IEEE. 
 
 
 
: - 4 Conformity Assessment – In final stages of progress for IHE Int'l.  Will have a CA by CN2015. 
 
:: Overview of program.  (I gone from recorder 1:19 – 1:22).  Companies inconsistent.  Described deployment process IHE >certification.  Plan to get to the actor level. Trying to get a virtual lab at the Innovation center. 
 
 
 
: - 5  ONC update
 
:: Created JASON task force – recommended open source API, HL7 FIHR, not too positive on IHE.  Testimony last week – using IHE, well baked.  IHE has filed formal response.  Not strong device activity.  Met with IPSIDOO – interested in device semantics, IEEE 11073, LOINC, etcNot main focusYesterday's pump meeting talked about My Device.
 
 
 
: - 6 Monday Pump meeting Summary
 
:: Long list of open issues, dealing with modes and status.  Made it through the listFlushing, priming, intermittent delivery.  Have a model most agree on, should scale well.  Looked at all receiving mechanisms and addressed them.  C4MI engineer comparing with RTMMS should be able to map and exportWill make sure RTMMS is consistent.  
 
:: For CN: Will compare 1.3 with 1.1 then decide what to use.  How it will affect CN – John G: Shouldn't be a problem, as long as all are aware of itWho is responsible for drafting text?  Todd will.  Paul Sc has the codes.  
 
 
 
: - 7 Olympics Demo Effort to use IHE thereLarge healthcare section there. Use EU-US MOU to work on this.  A lot of interest and support.  GE is the the healthcare provider for the OlympicsBrazil may be too early, but Korea wants to do this for 2019 Olympics(Gone until 2:30 on recorder)
 
 
 
: - 8 FHIR Update – Todd will provide presentation.
 
:: Best opportunity to put device informatics into HL7 V.3 – almost for free.
 
 
 
: - 9 FDA UDI @ HL7 V2.8.2 & FHIR
 
:: John R and Todd worked hard on it. How can you consistently represent UDI in HL7Drafted an implementation guidance document.  John and Todd created a CP for 2.8.2; could be out next yearUse PRT segment to capture UDI, asked them to include devicesPRT10 updated for UDI and other data (bar code, EUI-64). Could this be used for user defined identifiersYes.  Suggest providing user guidance on how to implement.  Concerns about not requiring information placed in PRT segments.  That may be in a UDI implementation guide; some profile specific requirements can be placed in the specific domain guidanceISO will state who 'owns' a segment; will be more specific as it drills down.  Can ask a party which one they own.  Can we take this 2.8.2 work and specify it in 2.6?  Yes, it's quite common.   
 
  
: - 10 HL7 - IHE Coordination   
+
:- Nomenclature update (Paul Schluter)
:: Working on a financial model that worksNeed to coordinate between two groups
+
:: Likely 10101a approved by IEEE Dec 6.  Should be available for use.  Most topics for TC callWill work with Nicholas to upload into RTMMS.  Have four groups competing for the same numeric set, need to manage that processMany codes start with 0, active ones will have non-0 to show they're active.  This helps the receiver know it's an active codeFocussing on getting it approved, don't want to add anything, it could delay approval.  Won't include pump info yet.   
:: Now working on this – Todd is HL7 rep to IHESlides will be availableBoth recognize need, but execution struggling.   
 
  
: -11  Update CP097 and submit for balloting – OBX-4 (TCAI 184)
+
: 10:30 Adjourn PCD Joint Planning & Technical Committee (PC & TC)  
:: Dealing with intermediaries.  Much is in TF, but not tested yet.  The Tiger Team may address this (not started yet).  How do device capabilities get advertised?  Paul Sc: prepare a list of needs.  Can move OBX-4 topic forward to after Brian Reinhold discussion today. 
+
:: Start PCD Technical Committee (TC)
  
:  Location, Dates of the PCD 2015 Spring F2F
 
: - Location - Cleveland doesn't meet our participant's cost model.  ECRI is available and willing.  Paul and Bikram can check on Portland.  C4MI San Diego or DC.
 
: - Dates – Week of April 27. 
 
 
:  Review IHE Milestones from now until Pre-Connectathon
 
: - * [[Patient_Care_Devices | PCD Key Dates (Cycle 9)]]
 
:: Unable to determine at this time – will depend upon proposals and resources available.
 
: - * IHE 2015 Publication Schedule [http://wiki.ihe.net/index.php?title=Domain_Milestone_Dates]
 
:: Monroe will draft and circulate to Paul Sh and Jeff M, then submit to the committees.  Will discuss on co-chair call Oct 28
 
 
:  CP to Convert IPEC to EC (Todd) (TC Action Item 170)
 
: -  No current progress.  Input from pump group.  About to do a major rework of the pump profile.  Why go to final text now?  Most changes are in content, not structure.  Some IPEC items may end up device specializations, eventually obsoleting IPEC.  Suggest finalizing IPEC within 1-2 years, then create EC with device specializations.  Pump group will work on this and come back with a proposal.
 
 
:  MSH-5  and Connectathon (TC AI 178)  (Started recording)
 
: - Receiving application – if MSH 5 blank, receiver can do different things, somewhat randomly.  (Back at 14 mins).  Should know who it's sending to when one to one.  Whatever we decide needs to be in sync with NIST.  Conclusion:  Test to what's registered in Gazelle.  If MSH-5, then receiver can send acknowledgement.  Add text to
 
 
:  New remote patient monitoring profile (Brian Reinhold, via Webex)
 
: - Done unofficially at CN, not a recognized profile.  Want to make this a ratified profile.  Brings info from outside the enterprise to within.  Meant to be done in stages.  This is basic – patient device measurements into an EHR.  Low cost home devices interface with hosting device, which would create message to facility.  Use case:  Ability to monitor patient outside the hospital. 
 
: - Discussion
 
:: John R – What would be PCD's initial steps?  Not exactly sure.  JR - Perhaps a workgroup and some use cases?  Outline the sequence for a profile.  BR - PHMR not in the standard, he's working on that.  Introduce necessary text into TF to outline profile and steps needed.    Trying to get it alive as an HL7 document.  First stage document – Trial implementation documents the flow and this profile.  The implementation exists, but isn't official.  DSTU is HL7's Trial Implementation, but if standards work isn't done, it's sunsetted.  This happened to this process.  Paul Sc - Will need to test CDAR2 document.  BR – it may exist.  PSc – Use existing parts?  Good, but not quite complete.  MP – Seems like all the pieces are in place, just need official recognition.  Get Personal Health folks to recognize PHMR.  PSc – Many of the device pieces are in place, many of the challenges are in PCC and ITI domains.  Can start with WAN interface and PCD messages.  PCD happy with device to hosting/accumulating system then out to WAN.  From there on it would be a different domain.  PSc – Use new status as part of HIMSS to discuss with big her vendors.  Break into two pieces:  Med equip to EHR/WAN then EHR/ to HL7 clinical messages and PHMR.  Brian will break this into two parts for thursday call with PCC;  PCD and PCC.  He'll show the original and separated briefs, and send the PCD one to us.  For PCD, it could be the DEC profile with the WAN Option added.  Would need a CP to the DEC Profile to enable this.  Section 4.2 Vol 1 of PCD TF has the actors and options assume MLLP transport.  Just add lines using WSI.  Vol 3 talks about remote monitoring use case.  Can back translate definitions to match up; then PCC can cross reference to their profile. 
 
 
: -  MSH-5  and Connectathon (cont from above) 
 
:: Reviewed proposed additions to tests.  Monroe drafted documents.  Epic may have concerns with this.  MSH-3 on ACK may be an issue.  Need to write the rules in the TF to address this.  Can we can go from Conditional to RE?  Will need to discuss this with EPIC.  Suggest rephrasing as Conditional.  Reason:  Some were blindly posting MSH-5 messages into MSH-3 as ACKs; if blank, then it would trigger an error.  Will put 1st sentence in tests and Gazelle. 
 
::Do we need anything in MSH-05 if we do MSH-03 correctly?  No.  2nd sentence adds clarity.  Send to Showcase and Connectathon Google group.  Group outlined new structure
 
 
 
Adjourn Joint PCD Planning and Technical Committees (PC/TC)
 
  
  
Line 819: Line 660:
  
  
|-
 
| align="center" | 4
 
| ''' ___ '''
 
| '''Status/Discussion:'''
 
http://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_8#Cycle_8_WorkItem_Candidates
 
 
 
 
'''Decisions/Issues:'''
 
 
'''Action(s):'''
 
  
  
Line 835: Line 665:
 
|}
 
|}
  
=== Wednesday Morning ===
+
=== Wednesday 10:00 AM ===
  
'''Placeholder'''
 
  
 
:{|border="2"  
 
:{|border="2"  
Line 846: Line 675:
 
|-
 
|-
 
| align="center" | 1
 
| align="center" | 1
| '''Introductions & Agenda Review''' <br>- Chair
+
| '''TC Welcome and Agenda Review (Tom Kowalczyk)''' <br>- Chair
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
 
'''Decisions/Issues:'''
 
'''Decisions/Issues:'''
: Introductions
+
 
: Monroe  reviewed the IHE IP Management Process
+
: Agenda approved 
: Reviewed & approved PC Agenda (10 minutes)
+
 
: Reviewed and approved Oct 8 PC Meeting discussion summary
+
: [[Patent_Disclosure_Process | IHE IP Management Process]]
: Reviewed PCD Calendar and Update  "PCD ftp site [[ftp://ftp.ihe.net/Patient_Care_Devices/]]"
+
: Announcements –
: - Added 2016, discussion of FHIR/HL7 V3
+
:- Decision Making meeting (TC Co-Chairs)
 +
:- TC Cochair election
 +
:: Ballot currently open for John Rhoads as new cochair.  
 +
 
 
'''Action(s):'''
 
'''Action(s):'''
  
 
|-
 
|-
 
| align="center" | 2
 
| align="center" | 2
| '''____________''' <br>- Chair
+
| '''Discussion Summary ''' <br>- Chair
 
| '''Status/Discussion:'''  
 
| '''Status/Discussion:'''  
 
:-  
 
:-  
 
  
 
'''Decisions/Issues:'''
 
'''Decisions/Issues:'''
Line 874: Line 705:
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
  
: - Cycle 9 -
+
: Review Current PCD Program:
:: MDISS security – a white paper drafted, in review (John R)
+
:- ACM (Monroe P)
:: DPI, CNS – much work focus on tooling support, device support.  Could use updating. CNS on hold (John R). 
+
:: Presentation available on F2F ftp site
:: DEC – PCD01 in final text.   
+
:: Passed a number of CPs.   
:: PCD-16 and 15 added this cycle
+
::- Resurrected some functions redacted to acheive Final Text.   
:: - No new transactions currentlyDMIO
+
:::  Discussion over PCD-05 resurrectionIt is an option at the ConnectathonCan do ad-hoc if neededTests are updated for 2016Rob they will likely participate in 2017.
:: ACM – added Alert Inventory; resend with present indication
+
::- Aligned Containment MDCs with IEEE 11073-10101a
:: RDQ – No activity, many senders don't have ability to store historical data. Those that do haven't dedicated resources to send that dataThey have about 72 hours of data, more than that would probably be in the realm of research, not enough interest to supportMore harmonized interfaces and a 'past' time stamp could helpSPD query type is archaic re HL7.
+
::- Some in process, not balloted yet.
:: Question on calendar – the year is effective the Showcase of that year.
+
:- Discussion of upcoming CPs and potential impact.
:: PCIM – progress, preliminary WP draft circulated last weekDiscussion this afternoon.
+
::  Question of PRT and HL7 versionsDiscussion of OBX.
:: Multi component add mixtures Can move into general PIV enhancements
 
:: PCA/Syringe – Done
 
:: Med Admin Management white paper – extended.
 
:: RTLS/MEMDMC – Available as TI
 
:: DPI – Continues
 
:: Device Data Reporting – Continues
 
:: Content Management -  
 
:: - 10101A – Balloting starting Nov 2014  Paul Sc ready to take comments from anyone for ballot group to consider.  Coordinating Efforts
 
:: - UL2800 – Work in process.  Not handled that well, going slowly.
 
:: Quality - Smart Alarm TIR coming along – meeting in december (Stan W)
 
:: - Add row to Coordination to cover Julian's efforts? No – UL2800 and 11073 efforts cover thatNot a lot of IHE meetings with them lately.
 
  
Review Current PCD Program:
+
: -Test tool updates (John G)
:- ACM (Monroe P) – In TF, some CPs backlog and a CP for alert list, integrated in TFResurrection of PCD-05 as a workflow notification; closing loop on notificationsLooking to be used for lab results notificationDiscussionsIn acm wg calls.   Looking at sample messages not enough, effort stalledContinued next cycle.
+
:: Presentation on ftp site
 +
:: Scope 'creeps' and become defacto e-version of the standards.
 +
:: HL7 V2 tooling -
 +
::- Working with IHE int'l to help with their certification. IGAMT and TCAMT – guides constrain the standards to usable levels, reduces ambiguity.  Drives user consistency, especially useful for Meaningful Use.  Want to get PCD-01 into them.  Once done, can work on specializations and other profiles.  Hope to have it ready to demo by spring F2F. 
 +
:- DIM Editor and tools
 +
::  Showed updates at IEEE-HL7 meeting earlier this month.  Challenge; seperating 11073 terms from others.  Model robust and stable, being tested.  Once model done, can build containment.  Need to know the DIM a bit, but it's very powerful and useful for generating standards. 
 +
:: Meetings and activities coming up
 +
:: Addressing Cps as they happen and TF 2, V5.
 +
:- IHE-Japan Connectathon – Asked them how the tools worked, worked well
 +
:- As they evolve, will be able to use different tool versions
 +
:- RTMMS
 +
:: Updated tools.  How well is IE working with the tools?  It's a bit erratic, they recommend Firefox and Chrome.  Working through those challenges.  Dr. Swapna provided a great cross reference sheet.
 +
:: 11073 will include LOINC and SNOMED mappings soon.  Paul Sc – concerned it may be a bit premature, suggest starting with a lighter touchIt will take a while to implement.  Needs more review.
 +
:- NIST tool framework work
 +
:- Royalty free agreement with IEEE
 +
:-  Tool updates
 +
:: WCTP in the futureMonroe and John G to discuss.
 +
:- Discussion
 +
::  CP122 update underway
 +
::  IPEC Have a lot of 0 MDC codes, How to resolve?  Todd working on it.  Current mechanism doesn't work, paul Sc will discuss at his session.
 +
:: John demonstrated TCAMT .  A process to automate test generationExample - Paul Sherman can use the test spreadsheets and create the tests.
 +
::  When will Pre-Connectathon start?
  
:- DEC (updated PCD TF) (John R) – Updated PCD TF should be published soon
+
:* 1:30 > Review Current PCD Program (continued):
 +
:- RTM (Paul Schluter) Presentation is on ftp site.
 +
:: 10101a, and lessons learned -
 +
::  Either method can be supported.  Paul is looking for feedback and suggestions.
 +
::  Dealing with 'junk' terms.
 +
::  Q – Without ability to see what's submitted to 10101a, how to see what's submitted so we can provide input?  A - IEEE instituted public review period; working group must review comments.
 +
::  Q - How to get new pump term numbers?  A – On RTMMS now, Todd can approve them.  Likely have few junk terms.
 +
:: Q  MEMLS has 20+ terms, some from other areas.  A – should be no problem, there's space for them.
  
:- IDCO (Paul Schluter) – Active defining new terms.  Craig Reister and Alexander Krauss running group wellSeeing use in research and production environments
+
:- IPEC (Jeff R)
 +
::  Not a lot going on right now.  Found pumps and use cases it didn't accommodate.  IPEC is driving the IEEE model.  Redefining the model.  Will be a CP to approve a new version.  The events haven't changed much.  The changes reflect pump models and content of those events.  Some will end up in Vol 3.  Clinical Scenario section; many changes in the Parameters.  Eliminated use of 'channel', will use 'info' instead.  Come too far to go back, need to know how to get them into RTMMS and the NIST tools.  John G Todd entered some new terms, is committed to get other codes assigned by EOW.  Reviewed RTMMS.  92 terms, 22 without codes.  This will change the DEC profile as well.  Struggles with adding dose units as well.  What needs to happen?  Al updated Todd about the terms, need them  loadedHow long to validate the terms?  It depends on the field and requirementsExtensive discussion and review of terms in RTMMS. 
  
:- PIV (Al E, Paul E) – PCA and syringe integrated into TFConfident it's pretty mature.
+
:- Whitepaper proposal - MEMDMC communication from systems to devices (EPIC/Matt Rush)
 +
:: [[ftp://ftp.ihe.net/Patient_Care_Devices/Meetings/Face%20to%20Face%20Meetings/2015-Oct-Boca-F2F/ FTP link]]
 +
:: Alert Management Silence Alerts and setting alert limits.   
 +
:: 11073 meeting a couple of years ago – seems there's been work there.  Look at 11073 – 10201.  prepare for feedback from Jan Wittenber.  Some things to be done first.  There's a lot of interest in 11073; personal health devices has done some work.  Issuing commands in FIHR will create a lot of new terms. Seems a very good time to discuss it. 
  
:- IPEC (Al E) – Spent last year discussing how best to define models.  Profile will need dissected and rebuilt for new models.  Events won't change substantially, but reporting modes will.
 
  
:- WCM  – Two areas discussion getting terms into 10101a.  Units of measure for EHRs; can supply in various units to be compatible.  Not seeing overwhelming demand for waveform attributes and signal filters.  Should we define in general 11073 or have defined attributes?  Not a pressing issue – defer and manage in 10101b.  Discuss with Epic, Capsule.  Continua at about the same stage.  Sampling rate question – integers/second; looks to be manageable.
+
'''Decisions/Issues:'''
  
:- OMS  – None known, seems dormant
 
 
:- RTM (Paul Schluter) – Almost all work on vents, working with ISO 19223 for cardiopulmonary devices.  About the worst for vendors inventing own terms, FDA is watching closely.  RTM group aligning work, causing some delay in 10101A work.  In about 3 weeks should have a draft ready.  Could be used in 2016 CN.  Some discussion of LOINC/SNOMED mapping and proposal. 
 
 
 
'''Decisions/Issues:'''
 
  
 +
|-
  
 
'''Action(s):'''
 
'''Action(s):'''
Line 924: Line 770:
 
| ''' ___ '''
 
| ''' ___ '''
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
http://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_8#Cycle_8_WorkItem_Candidates
+
 
 +
 
  
  
Line 936: Line 783:
 
|}
 
|}
  
=== Wednesday Afternoon ===
+
=== Thursday ===
  
'''Placeholder'''
 
  
 
:{|border="2"  
 
:{|border="2"  
Line 950: Line 796:
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
 
'''Decisions/Issues:'''
 
'''Decisions/Issues:'''
: Agenda approved
+
: Agenda approved
 
'''Action(s):'''
 
'''Action(s):'''
  
 
|-
 
|-
 
| align="center" | 2
 
| align="center" | 2
| '''Discussion Summary ''' <br>- Chair
+
| '''____________''' <br>- Chair
 
| '''Status/Discussion:'''  
 
| '''Status/Discussion:'''  
 
:-  
 
:-  
Line 969: Line 815:
 
| '''Agenda Items''' <br>-  
 
| '''Agenda Items''' <br>-  
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
'''Decisions/Issues:'''
 
  
(gone at 1:26)  (back at 1:40)
+
: ** reviewed IHE IP Management Process
 +
: Review of On-going work
 +
 
 +
: - ACM update (Monroe)- 
 +
 
 +
:-  Point-of-Care Identity Management (PCIM) white paper (John R)
 +
::  No major change in OBX-4, but could be EMR challenges.
 +
::  John provided OBX4 overview.  Discussion of official definitions versus implementation.  As soon as we define the models, it will be useful for implementers, particularly on the receiver end.  Epic explained how they implement OBX-4.  In general, XML is like a tree, you can parse a message to find the info needed.  In TF as a 'should, not a 'shall'.  Epic had to code to the current framework.Enforcing document order won't eliminate OBX-4.  This ensures consistency within channels.  Risk of mixing semantics, but not sure it's a practical concern.  Brian will discuss this with Chris (Epic).  Pump model has a couple of attributes for events and alarms.  Also a companion attribute that defines hierarchy position.  Example – will use different OBX's for primary and secondary pump channels.  
 +
 
 +
:- Private Terms (Paul Schluter)
 +
 
 +
:- Continue Profile Review:
 +
:: DEC (updated PCD TF) (John R)
 +
:: IDCO (Paul Schluter)
 +
:: PIV (Al E, Paul E)
 +
:: DPI  (John R)
 +
::-  Semi-quiescent
 +
:: MEM DMC (Monroe P)
 +
::-  Moving more into the mainstream.  Some 11073 attributes not in RTMMS yet, but can be added when needed by MEMDMC.  May be in the X73 tab; will need to be harmonized.  May be able to use Personal Health Devices as well.  Two Cps, proposals for communication to devices, this may be the best group
 +
:: MEM LS (Monroe P)
 +
::- Will need to change the document to resolve an editing error.  Al will submit a public comment to correct.
 +
:: PCIM (John R)
 +
::- Core of the WG (Stan, Chris and Doug) did a lot.  Have a good draft, hope to submit by EOY, then send for balloting.  Pretty specific on format and content.  John and Chris will prototype, then TI in 2017
 +
:: Pump (Al E, Paul E, Jeff R.)
 +
:: Physio monitor (John R)
 +
:: Vent (Paul Schluter)
 +
::-  Done a lot of work, a lot of mappings wih positive feedback. Covered basics, breathe by breath annotation, additional parameters.  Will need to take care of private terms.  Advanced topics may be in 10101c. 
 +
 
 +
:* [[http://wiki.ihe.net/index.php?title=PCD_Technical_Committee_Action_Items TC Action item]] review
 +
 
 +
:: 118. Implementation Guide
 +
::- Ties to Igamt and tcamt work.  Trying to implement PCD-01.  Will mirror TF Vol 2, provide more focused device speciliazation guides.
  
 +
:: 136 WCM Attribute List
 +
::- Can use numeric Ids or annotated ECG.  Not a compelling need to include them.Have a good way to show filters.  Change to Nov 18.
  
:- RDQ (John R)
+
:: 143. Describe HL7 Version Implications::- :: 143. Describe HL7 Version Implications
 +
::- CLOSE
  
:- DPI (John R)
+
:: 150. Seek null flavors in HL7 2.9
 +
::- HL7 V3 item to explain why a field is empty. In TF Vol 2, line 3380.  Tweaked it to make a tutorial.  CLOSE
  
:- PCIM (John R)
+
:*  11:30 > Proposal Review
 +
:: Communication Between Devices - DPI Working Group  (Angela Merzweiler)
 +
::- Don't have ability to communicate between devices, described five use cases. 
 +
::- Discussion – John R; DPI goals for some time, looks like a good project.  Monroe; some profiles and TIs started on it, may need to spraed out over multiple Wgs.  Some experience and expertise to help achieve.  What does a device need to support?  Use this approach to configure devicxes and record alerts and observations.  There are a lot of pieces that exist.  DPI can build on that work.  Need to prioritize the tasks, then fill in the rest as time allows.  Need to find resources to implement it.  Part of 11073, but not main part, part of Open SDC.  Stephan:  Described transport specs, web services derived from HL7 specs.  Glues together how the sections work.  Needs implemented by devices (not HL7).  Are there libraries available?  Yes, two.  Open SDC and OC-lib. 
  
:- MEM DMC (Monroe P)
+
:: Workflow Profile for ordering Device Monitoring  (Angela Merzweiler, Björn Bergh)
 +
::- Closes loop from order to results.  (I want this device to do this thing)
 +
:-  Discussion – Similar to original DEC profile, takes existing HL7 V2 infrastructure.  Tailors this to a specific use case.  Similar to RGB in PIV.  Want to order, then take results and update the order.  RAD has done similar work, can use this to build this profile. 
  
:- MEM LS (Monroe P)Specializations (statuses, plans only, details during TC sessions):
+
: Next steps – Evaluate proposals.  Determine work needed and resources available.  PC will review and determine if we'll take I forward.  Will need to submit to HIMSS to determine if this is appropriate for PCD or another domain.
  
:- Pulse Oximetry (Ioana S)
+
:: [[ftp://ftp.ihe.net/Patient_Care_Devices/Meetings/Face%20to%20Face%20Meetings/2015-Oct-Boca-F2F/ FTP link]]
  
:- Pump (Al E, Paul E, Jeff R.) - Updates to terminology, new intermittent dose parameter set. 
+
:*  Continue TC Action item review.
  
:- Physio monitor (John R)
+
:: 167. Versioning and Archiving
 +
::- ::- ACM used OID to perform this.  Can add a how-to to TF next iteration  CLOSE
  
:- Vent (Paul Schluter) – terms to be submitted to IEEEWant to build a vent containment model, how to validate for next steps.   
+
:: 170. Convert IPEC to EC
 +
::- Do we take it down a notch and put info in framework, and let device specific groups define as needed (IPEC becomes an example of EC)?  IPEC principles can provide a base for others to build on.  Close this and open another to create common EC material to go into TFOwner of new AI – IPEC team and John R.  What is the need for this material?  Would be a template for other equipment types to build on.   
  
Cycle 10 Work Items (Monroe P) – If you have some get them to Jeff, Monroe or Paul Sh.
+
::- CP-122:  ACM change to containment MDC codes and MSH-21 OID change (Monroe)
: Parking Lot Item Review (Monroe) – ExplainedDon't see any that are likely to be activated.   
+
::: Monroe reviewed CP, found a few edits needed.  Any other profiles have changed their content.  Questions on why this needs a CP.  Because this is in Final Text, most others are in Trial Implementation. Epic is concerned over keeping track of the changes and versioningDoesn't see this as a big enough change to warrant versioning.  This one is, this won't be a habitMonroe will retract the CP, edit as needed and resubmit for balloting.
  
: Standards coordination/Continua - overview (Paul Schluter)
+
:*  Medical Device Cybersecurity Discussion (Axel)
:- HIMSS/Continua  -
+
::  All this work needs to happen quickly, but in a highly regulated environmentThis is a system of systems issueOverview of prior work and current activitiesGetting good feedback from Symantec customers. Limitation – only best practices for current tech, nothing for new technologies; had to update chapters while writingSeptember asked 'What's Next?'Users provided a list of what they needThe workgroup needs provider membersNeed a way to make this work at the hospital levelExamplesEquipment returned from repair, loaners, demo equipment – how to confirm they aren't a security issue without overloading the hospital? This typically would go to ITI, but they don't really look at device functionLife critical vs. mission critical, the variety, number of devices and device age are all more complex than IT systems.
:: Most through WAN interface, uses PCD-01. Some work with cell phone vendors, recent work focused on MQTT, a more useful transport mechanismPCD-01 remains intact, just carried in MQTTStarting work on remote control and command, including remote turn-onMQTT will help with that. Proposal going through ITU ballot processA lot of alignment between the two standardsUnsure of their FHIR interestWork started on Alerts, events and remote controlNot much resistance to PCD-01May want to explore xml in the future.
 
: - UL 2800 -  
 
:: General goal is a set of standards for testing systems of systems, similar to Julian goldman's ICE model. One model is PCA morphine use and patient vital signs feedback.  Drafting general, clinical and ICE standard implementationsMultiple sub groups dependent on others. Pressure from AAMI to have standards in place soon, may not be doable on their schedule. Would they use containment models?  Yes 
 
  
: - Restoring PCD-05 to ACM (Monroe)
+
:*  Continue TC Action item review.
:: Intended as closed loop delivery confirmation for escalation if needed.  It was extracted to get ACM to FT.  Don't need brief proposal, go to detailed proposal. Monroe will put one together and send it around.  Meaningful and well intended.  Vendors testing?  Epic wants to receive but there were no senders. 
+
:: 175  Develop a PCD UDI Witepaper for IHE
 +
::- John R – Unless someone has material changes, close this.
  
: - White paper on PCIM-DEC series to address unknown/no patient challenges (John R)
+
:: 178  MSH-5 and Connectathon
:: There is progressWP draft sent to PC & TC, looking for feedback and improvementsSome items need to be discussed and identified. Need user point of view.  Please have clinicians review if possible.  Will walk through it this afternoon at TC session.  Good candidate for 2016 New Directions?  Yes, maybe even 2015John will send bullet points to Greg S, he will review and discuss with clinicians in his informatics group.
+
::- Retitle to MSH 3 and ACKsLook for Jeff's email and use that an update to the TFWhat to do as a gateway? The gateway is responsible for the ACKChange date to Nov 4 and put on the TC agenda.
  
: - ftp site review (Jeff M)
+
:: 179. IPEC and EC documentation - CLOSE
:: Discussed at spring f2f. John R demo'd some flat files.  Great data, but a bit tough to read.  Could use a different architecture – but need a good view of what we have.  Jeff used FreeMind to show the structure.  Suggest moving to an archive structure.  Archive most and keep some high use areas at the top.  Jeff showed several examples.  Could organize by cycle – then by activity.  Any changes will affect related wiki pages, would need to update those links as well.  Not the only domain dealing with this and someone else will not look at it the same way we do.  Wiki does support searches and Google does a good job of finding items (today's search for the parking lot items worked well.). 
 
  
: - Meet with Alex to discuss Remote Patient Monitoring and DSB
+
:: 183 CP for WCM and implementation
:: (Paul Sc)  Concerns about PCD message going directly to LOINC and SNOMED.  Need high level of abstraction to ensure vendor independence.  This effort, as is, will require substantial resources from PCD and would take away from existing efforts.  No EPIC interest in LOINCNeed a clear boundary for this to work.
+
::- Will update WCM TI rather than create a CPChange date to Nov 18.
  
Adjourn Planning Committee
+
:: 186  Review and reformat ftp site
 +
::-  Make Cochairs owners.  Change date to Dec 31
  
Begin Technical Committee Meeting
+
:: 189  Identify unique identifiers before the Connectathon
: - > [[Patent_Disclosure_Process | IHE IP Management Process]]
+
::- Discussion on how to proceed.  Could have the vendors provide, NIST loads the info, then it can tie back during Connectathon registration.  John G will assemble a spreadsheet to go to CN and PC members asking them to load their info.  Will try to have ready for Pre-Connectathon.  Paul Sc suggests including a private company identifier. Set up for warning if not in the table, error if different than in table.  Stay with OBX-18 for now.  Need extra data and analysis.  John will send a notice on what's needed for this Connectathon.
::  Announcement – Decision Making meeting (TC Co-Chairs)
 
: TC Welcome and Agenda Review (Jeff McGeath)
 
:- Incoming TC CoChair (Garguilo term completed 1 Sept 2014)
 
  
: OBX-4  (John Rhoads) – Relates to CP 097. 
+
:: 190 PRT Segment Use -  CLOSE
:- Concern by EPIC that the channel segment could change. Want assurance that it won't, so they don't need to parse the segment for each message.  This CP was clarifying existing OBX-4 behavior.  Other parameters will assure unique/stable channel segments.  Would be good to have limits for complex commands and control. CLOSE AI 184
 
  
: Identify unique Identifiers (John G) (TC Action Item 189)
+
:: 191 Liaise with IDCO on Waveform communication
:- Do people want EUI-64s validated in Connectathon and Pre-connectathon?  If so, NIST needs a table with those values for all participants.  TF allows for different options – DNS is acceptable.  It would remain static for testing.  Would need to write into the test case.  Not always used outside of PCD or Connectathon.  Makes testing more rigorous.  Action needed – NIST maintain a table and add that to the test case (preamble).  NIST only checks for A value, not a SPECIFIC value.  Participants will need to provide that information to NISTThis will provide traceability for healthcare users.  Send a message before the Pre-Connectathon.  Similar to patient demographics.   It will be a test requirement to provide the fields (to be specified) to NIST.  NIST will add the value they have to the fields first. 
+
::- Liaised, unsure what IDCO will doChange to Dec 31.
  
: Describe HL7 Version Implications (John R, John G)(TC Action Item 143)
+
:: 192 FHIR Change date to Dec 31  
:- Do we continue to take out the parts we need, or move our baseline to 2.8.  Many consider 2.3 state of the art.  The versions are pretty compatible.  If this has been working, then we may not want to change yet, stay with consensus version.  Doug P will look for when V2.6 will be obsoleted.  Resource:  For understanding versions  - http://www.ringholm.com/    Action:  Continue current practice. Will pull in later feaures when needed, update TF to include reference in data segment and data type. Add to TF vol. 2.  Make this a CP (Jeff McG). ACTION ITEM
 
  
: >  FDA UDI and how to integrate into PCD messages (John R/Monroe)
+
: IEEE to LOINC mapping (Paul Schluter)
: - Took evolved version of UPC to make global trade identifier with 14 more symbols.  Called GS1. Medical equipment is a small part of the whole device world.  Displayed sample image.  FDA has 'Good ID' which lets them look up manufacturer.  Some fields don't have fixed digit lenths, though some do.  Since century isn't provided, is 2000's implied – yes).  Took out OBX18.  Group reviewed fields that may have medical device impact.  There are other health care barcode standards.  Interested in providing more fields in human readable form – Lot numbers, donor source, etc.  Sender can provide all the code or portions, the receiver must be ready to take either.  Does HL7 make the scope clear?  Not really. 
+
:-   IEEE 11073 to LOINC Mapping
  
: > PCIM white paper  (John R/Doug P.)
+
: Very reasonable first draft of mapping exists, due to the work of Dr. Swapna Abhyankar.   
: - John - Quick intro.  Trying to deal with right patient/right device issue.  White paper out, need feedback.  Provide for someone to report an association; a patient with device(s).  Patient registration not new, will use ITI patient mechanisms.  John explained how the process would work. Association Manager could have UIYou need to know the current association and keep eye on beginning and end.
+
: 600+ ‘harmonized’ Rosetta terms, incorporate dimensionality, maps (almost reversibly) to LOINC.
: -  Doug – Reviewed use cases.  DOR-DOC isn't a use case fulfilled by this, but this is the result of this activity.  Messaging review – Device reporting observation.  OBX-9, 11.  Very important to have the fields correct, can affect who is accepts changes.
+
: Recommend that mapping information be captured as a single, authenticatable file.
: - Stan – Glossary.  First approach, datamined to use what was available and worked.  Can't confirm all are accurate, need feedback. Each member of the group sponsored a definition, the group challenged. 
+
: IEEE P11073-10104 as possible future standard, provides ANSI recognized open-consensus review and voting.
: - Chris – Effects on the system section:  Association Manager or other entititiy evaluates association integrity. No details associated yet.  Recommend – Embed capability for a small JPEG photo for identification. 
+
: MoU between IEEE and Regenstrief ‘almost’ signed (should have been two weeks ago).
: - Discussion – How does this integrate with IHE PCD ecosystem?  How to mitigate chances of things going wrong.    Discussed where PRT segment goes; can go many places, depending upon content.  A collaboration with other groups.  If you find an error, you can fix it, but need to fix it with the enterprise system – they do this quite well.
+
: IEEE-SA is considering similar relationship with SNOMED-CT, but many things are needed to be done to make this happen.
  
 +
'''Decisions/Issues:'''
  
|-
 
  
 
'''Action(s):'''
 
'''Action(s):'''
Line 1,050: Line 930:
 
| ''' ___ '''
 
| ''' ___ '''
 
| '''Status/Discussion:'''
 
| '''Status/Discussion:'''
http://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_8#Cycle_8_WorkItem_Candidates
+
http://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_10#Cycle_10_WorkItem_Candidates
  
  
Line 1,057: Line 937:
  
 
'''Action(s):'''
 
'''Action(s):'''
 
 
  
 
|}
 
|}
  
=== Thursday ===
+
=== Friday Pump WG Meeting ===
  
  
Line 1,077: Line 955:
 
: Agenda approved
 
: Agenda approved
 
'''Action(s):'''
 
'''Action(s):'''
 +
 +
|-
 +
  
 
|-
 
|-
 
| align="center" | 2
 
| align="center" | 2
| '''____________''' <br>- Chair
+
| '''General Discussion''' <br>  
| '''Status/Discussion:'''
+
| '''Status/Discussion:''
:-
+
: reviewed IHE IP Management Process
 +
: Attendees: Al Englebert, Paul Elletson, Brian Witkowski, Tom Kowalczyk, Megan Tetlow, Olivier Coeffic, Jeff Rinda
  
  
'''Decisions/Issues:'''
 
:
 
  
'''Action(s):'''
+
:-Pump specialization will be major focus of pump group in 2016
 +
:• LVP, PCA, Syringe
  
|-
 
| align="center" | 3
 
| '''Agenda Items''' <br>-
 
| '''Status/Discussion:'''
 
  
: Jeff reviewed IHE IP Management Process
+
:-IPEC - messages should contain information for all channels
: Review of On-going work
+
:• most important for the "start" message after infusion programmed using PIV
 +
:• consider updating IPEC profile to explicitly state this
  
: - ACM update (Monroe)- 
 
:: Alerts and Alerms inventory;  Specific inventories challenging, will likely go into next cycle.  First time a nurse call will be ACM participant at CN.  Which field will be hosting information – In ACM for at least 5 years, just not used. 
 
  
: - CP107 –
+
:-Extending PIV to other use cases
:: Adding web services to Vol 1, section 4.2.  Web service not listed, so not a valid CN option.  Adding this will enable it.  Same actors, option name WS*Reporter, WS*Consumer.  Vol 2 Appendix J.  Paul Sh will prepare and send for ballot.  Similar to WTCP. 
+
:Multistep and Loading Dose programs
 +
:PIV can support when all program parameters are ordered and known by EMR "up front"
 +
:Paul E - determine whether there is an MDC term for "continuous" that can be used
  
:  - Possible CP to add language to Vol 2 regarding pulling future HL7 version items into PCD work.  Profiling section may be a better fit.  Some disussion regarding where to best fit this statement.  Add superscript number with the referred statement outside the table.  2.2 (Profiling Conventions) seems to be the best place for this.  So far, applies to ACM, MEMLS, IPEC; jeff Mc will search for usage.
 
  
: - WCM – progress on integer/second issue.  Chris and Paul Sc will update documentation
+
:-Proposed PIV message structure for multi-segment orders:  
: - OMS – dormant
+
::• loading dose or bolus followed by continuous infusion
: -  RTMMS –
+
::• multi-step infusion
:: Goal – Get new terms out to ballot in 3 weeks. 
 
:: Working on vent terminology.  Include Infusion pump terms, should be ready in 3 weeks, infusion technology should drop in without changes.  Need to review background/introductory text. 
 
  
: - IEEE 11073 -10101a update Almost there (Paul  Sc -slides)
+
::MSH
:: Updated VMD list.  Next big item camera ready pump terms.  Waveform attributes most defined.  Sent earlier draft to RTM group, let him know of any changes.  If we take a device specialization process, the work goes faster.  Discussion of vent progress and terms. 
+
::PID
 +
::(PV1)
 +
::ORC
 +
::{
 +
::RXG
 +
::(TQ1)
 +
::RXR (consider placing this segment before RXG so that it only appears once if HL7 supports)
 +
::OBX indicates dose type (use existing MDC terms for loading dose, clinician dose, may need new term for “continuous or continuous rate”)
 +
::OBX – pump ID
 +
::OBX patient height/weight/BSA
 +
::}
  
: - MEM DMC (Monroe P) and  MEM LS (Monroe P)
 
::  New profiles for new actors.  Discussion of how LS info is conveyed.  MEMLS profile also provides ability to send to LS concentrator.  Example – Awarepoint is sender and consumer.  Listed a number of MEMDMC items they can send, but vendors using a limited number of them.  Will likely end up in 10101b.  MDCx – not sanctioned in RTM, MDC0 – awaiting approval.  One nurse call vendor interested in tying LS into response to patient calls.
 
 
 
:* 10:00 > Joint PCD PCC meeting (via Webex)
 
: - Remote Patient Monitoring Profile
 
:: Intro by Paul Schluter highlighting end to end connectivity plan.  This proposal creates the implementation of this plan.  Just need a profile to tie this together.  New platforms can implement as well.  Could migrate some of Continua's work as this moves forward.  Many options for getting the message in. 
 
:: PCC – not entirely clear on technical detail.  Don't need high detail to go forward.  Home health to EHR. 
 
  
: - Device Observation Semantic Bridge Proposal (Alex Lippitt and PCC via Webex)
+
:-Ramp/Taper
:: Alex – overview with slides.  While home care devices has clear mapping, there's no such path for info into LOINC. One struggle is what this falls under.  It's broken into 3 sections. 
+
:In order to support we need to know the specific parameters required by the pump.
NOTE – ask Alex for slides
+
:Need to define terms for these parameters (some examples might be "target dose rate", ramp time, taper time, enumerations for "ramp" and "taper". Do we :have status elements defined?)
:: - Has IEEE11073 codes been mapped to LOINC? No
+
:Vendors may handle programming differently or not support at all.
:: - No one to one term mapping.  What will be lost in mapping?  Different 11073 code depending upon device providing the measurement.  LOINC has measurement and device codes.  Potential safety issues exist – vent example.  Working on submitting 11073-10101a to ISO.
 
NOTE:  USE RECORDING TO FILL IN THE BLANKS (MANY OF THEM)
 
  
: - Connectathon and Showcase Update (Sandy via Webex)
 
:: Showcase – using vignettes again, averaging six vendors per vignette.  Sign up ASAP for biggest discount.  Reviewed levels of participation.  Vignettes worked well – more visibility, easier for attendees.  Enhancements – storyboards will have more info.  Have graphics match storyline; will need help ahead of time.  Looking for a way to have presenters face the audience and still see displays.  Good positioning in McCormick Place.  Dates April 12-16, planning start in Jan, and work on Feb – March. 
 
:: Next demo at mHealth Summit in DC.  About 8000 attendees.  Brings in Continua and home health.  In December.  Work with Manny and Sandy to participate.
 
:: AAMI – AAMI approached IHE to make this an anchor, more like HIMSS demo. 
 
:: Questions?
 
:: - Pricing:  Blanket % off for level of participation (International/domestic).  She will send prospectus.
 
Showcase registration deadline extended until Oct 31.
 
  
: Remote Command Control/Continua (Barry Reinhold)
+
:-Bolus
: - Overview of process and capabilities (with slides)
+
:There are many use cases where the word bolus is commonly used
: - To be standardized: AHD models, config and interrogation operations, Comms protocol with WAN, security to restrict to authorized users
+
::• Initial bolus (= loading dose)
: - Options
+
::• Bolus administered from bag
:: 1. Use 11073 Object model and protocol.
+
::• Bolus administered from secondary
:: 2. Use 1. and mapping it to lwm2m model – focused on cell environment, can use sms, mapping may be difficult.
+
::• Bolus according to protocol order (as needed according to patient parameter or condition)
:: 3. Use 1 and OMA DM 2x or 1x  objects and protocol.
+
::• Bolus administered from syringe (heparin, insulin, narcotics often given this way)
: - Questions
+
:Jeff will solicit comments on bolus practice, consistency within an institution, etc
:: PCD doesn't have all those challenges what do we want to move between 'here and there'. 
+
:Brian will solicit comments on bolus ordering (if separate order how to “link” to an infusion in progress, how to know whether given by syringe or as :secondary/piggyback)
:: Challenge will be ensuring accurate delivery/fallback if it fails.  Use other protocols. 
 
  
: Tooling update (John G)
 
:- Tools updated for Cycle 9, Pre-Conn starts Nov 4
 
:-  IEEE agreement for royalty free use
 
:- Implementation Guide Authoring Tool
 
:- Domain Information Model Editor (DIM) – Automatically producing containment tree, IEEE formatted standard document.  Enables building device specilization documents/profiles. 
 
:- IHE Japan used Connectathon static tool for CN
 
:-  Overview of Pre-Conn tools.  MEM tools added.
 
  
: Medical device cybersecurity project (Axel, via Webex)
+
:-Use of 5th containment level
: - Started with Steve Merrit's white paper.  Talked about how to generally mitigate risks.  Two years ago started on technical white paper.  Ongoing, but closing in, some challenges with day job activities. Now; the team has a deadline of Oct 24.  Complex topic, 50 pages, comprehensive; descriptions and solutions.  Team core about  6-7 people, new people joined and contributed. 
+
:Jeff will schedule pump group call pending Todd’s availability to review Al's email on use of the 5th containment level
: - Axel proposed NDIS and IHE to work together on a consistent message.  NDIS wrote patching white paper.  Would be good for IHE to supply editing/formatting guidelines ASAP (they are editing tomorrow).  John R can provide some info. 
 
: - Nat'l Academy of Sciences workshop.  FDA released cybersecurity document Oct 1.  Workshop last week – very hands on.  Many gov't agencies working together, hospitals and vendors sitting at table discussing the issue and solving it.  He will publish info soon, will send us a copy. 
 
: - Use cases
 
:: (Missed 1st)
 
:: Infusion pump use case; medical device security problems.  Most providers – clinician and user authentication a big problem.  Too tight – unable to treat.  Too loose – anyone can adjust.  John G will forward document to pump members for review/comment.  Intent – Guideline documents  Groups; local/state government drive this (CRADA), are looking for members.  So far a paper exercise. 
 
:: Encryption of devices at rest and at motion, how to manage and still make devices manageable.
 
  
: Review of a couple of articles sent by Manny, will send to group
 
  
:  Wiki page Maintenance
+
:-Use of reference range (OBX-7)
: - What is most used page in our wiki? 
+
:Al will develop a CP to optionally use the reference range (OBX-7) to contain drug library limits.
: - Priorities for wiki pages?
 
: - Archive all but last 4 meeting pages on meeting wiki.  (Paul Sh)
 
: - Profile wikis are not up to date – IHE seems more interested in format than content.
 
: - Moving some items to Google Docs from wikis (Google is phasing it out), existing items may not migrate.  Also doesn't work well from in some companies' firewalls. 
 
: - Need to have WG leads update Profile pages.  (Cochairs)
 
: - OIDs and Transaction numbers page needs updated
 
: - PCD main page needs updated 
 
: - Add Wiki page review to cochair agenda items. (Paul Sh)
 
: - CP grid – add a column for current status
 
  
: TC action items and F2F action items covered next Wednesday
 
: - 3 CPs – Alert list, HL7 v2.6, Brian's remote monitoring
 
  
: Assemble DCC calendar
+
:-Target-controlled infusions (TCI)
: Enforce system identifiers.
+
:Require specialized pumps that deliver a drug to maintain a target blood concentration
 +
:More common in Europe
 +
:Issue: How to program using PIV
 +
:Vendor(s) of those pumps are not currently participating in IHE pump group, and current group members are not familiar with the programming and :operational parameters for the devices.
 +
:“Diprifusor” is a TCI device developed specifically for the administration of a single drug - propofol (Diprivan)
  
Technical Committee Adjourned
 
  
  
 
'''Decisions/Issues:'''
 
'''Decisions/Issues:'''
 
+
See above
  
 
'''Action(s):'''
 
'''Action(s):'''
 
+
See above
  
 
|-
 
|-
| align="center" | 4
 
| ''' ___ '''
 
| '''Status/Discussion:'''
 
http://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_8#Cycle_8_WorkItem_Candidates
 
 
 
 
'''Decisions/Issues:'''
 
  
'''Action(s):'''
 
  
  
Line 1,219: Line 1,056:
 
== Action Items - TC and WGs ==
 
== Action Items - TC and WGs ==
 
The Action Items that follow and approved in subsequent committee meetings will be added to the committee Action Item page.
 
The Action Items that follow and approved in subsequent committee meetings will be added to the committee Action Item page.
 
: CP 107 - Update TF-1 to include Web Services delivery
 
: Provide instructions reconciling MSH-3 and MSH-5 messages.
 
  
 
== Next Meetings ==
 
== Next Meetings ==
Joint Planning and Technical Committee: ''PC and TC __ [[PCD PC&TC 2014-10-29 Webex]] ''
+
Joint Planning and Technical Committee: ''PC and TC __ [[PCD PC&TC 2015-10-28 Webex]] ''
  
''TC [[PCD TC 2014-11-05 Webex]]''
+
''TC [[PCD TC 2015-11-04 Webex]]''
  
''PC [[PCD PC 2014-11-12 Webex]]''
+
''PC [[PCD PC 2015-11-11 Webex]]''
  
 
<!--
 
<!--
 
[[Patient Care Device | PCD Home]]
 
[[Patient Care Device | PCD Home]]
  
[[Category:PCD Meeting]]
+
[[Category:PCD Meeting Archive 2015]]

Latest revision as of 10:18, 2 January 2017

PCD Home


Meeting Objectives

These face-to-face meetings have a number of objectives depending on the committees involved:
  • Planning Committee: Review, plan and initiate PCD activities; contribute to planning of the HIMSS Interoperability Showcase and other Showcases and events; recruit vendors and users.
  • Technical Committee: Review and adopt brief profile proposals; contribute to Connectathon test tools, tests, and procedures.


Location & General Schedule

Location:
- Philips Healthcare,
951 Yamato Rd, Boca Raton, FL 33431
Suite 175W
- Meeting room
Hotel
- Springhill Suites
130 NW 8th Avenue Boca Raton FL 33487
Book at group room rate at [Hotel link]


Dates
Tuesday October 20 PCD Planning Committee
Wednesday October 21 morning: Joint PCD Planning and Technical Committees
Wednesday October 21 afternoon through Thursday: PCD Technical Committee
Friday October 23 Pump Working Group
Daily Schedule -
08:00 - 08:30 Meet at Philips, Boca Raton, FL
Meeting will start promptly at 08:30 Eastern Time each day.
08:30 - 10:15 Session #1
10:30 - 12:30 Session #2
12:30 - 13:30 Lunch (location to be announced)
13:30 - 15:15 Session #3
15:30 - 17:00 Session #4
The Friday Pump workgroup session will end by 12:30

Agenda Suggestions

Please submit suggestions for agenda topics here or through emails to the committee co-chairs.

From the PC Action Items PCD Planning Committee Action Items:

78. Stakeholder Survey
140. AAMI Alarm Safety Committee
157 Update cookbook to include ACM implementation

From the TC Action Items: PCD Technical Committee Action Items:

118. Implementation Guide
136. WCM Parameter List
140. Assemble the Baseline Set of Standards for Easy Reference
143. Describe HL7 Version Implications
150. Seek null flavors in HL7 2.9
167. Versioning and Archiving
170. Convert IPEC to EC
175. Develop a PCD UDI whitepaper for IHE
178 MSH-5 and Connectathon
179. IPEC and EC documentation
183 CP for WCM and implementation
186 Review and reformat ftp site
189 Identify unique identifiers before the Connectathon
190 PRT Segment Use
191 Liaise with IDCO on Waveform communication
192 FHIR

Webex

Webex meetings have been set up in anticipation of interest. They will be provided when requested in advance; i.e., the log in information is provided here, and the Webex will be initiated for those portions of the agenda that are of interest. Please let the co-chairs and Paul know of your interest and when you are available. The co-chairs will try to arrange the agenda to permit your remote participation.

Reminders: the IP agreement is in force, and participation counts toward voting rights.

Please note: the log in and phone number for each meeting is the same as for our WG meetings. The password is different, and has been included in the email sent to participants. These are not provided here for security reasons (this is a public Wiki page).

The HIMSS Webex page is [here]

Tuesday morning, October 20: PC: Meeting Number: 922 345 610

Tuesday afternoon, October 20: PC: Meeting Number: 927 328 705

Wednesday morning, October 21: Joint PC, TC: Meeting Number: 927 905 271

Wednesday afternoon, October 21: TC: Meeting Number: 921 745 176

Thursday morning October 22: TC: Meeting Number: 921 791 087

Thursday afternoon October 22: TC: Meeting Number: 922 601 518

Friday morning October 23: Pump WG: Meeting Number: 924 383 028

Attachments / Materials

Documents related to the meeting when available will be found at the [F2F ftp site] unless otherwise noted. Documents are available without a password.

Schedule/Deadlines: Patient Care Device and Domain Milestones

PCD PC Action Items PCD Planning Committee Action Items. Significant changes, other than dates, will be in bold.

PCD TC Action Items PCD Technical Committee Action Items. Significant changes, other than dates, will be in bold.

Detailed Schedule & Agenda

Tuesday October 20, 2015

Date Hours Committees Topics


Tuesday Q1 08:30 - 10:15 PCD Planning Committee (PC)
  • 08:30 > IHE IP Management Process
  • 08:35 > Introductions and Agenda Review
  • 0900 > Review current PCD programs (statuses, plans only, details during TC sessions):
- ACM (Monroe P)
- DEC (updated PCD TF) (John R)
- IDCO (Paul Schluter)
- PIV (Al E, Paul E)
- IPEC (Al E)
- EC (John R)
- WCM (Chris C)
- OMS (Ken F)
- RTM (Paul Schluter)


Break 10:15 - 10:30 AM
Tuesday Q2 10:30 AM - 12:30 PM PCD Planning Committee (PC)(Cont)
  • 10:30 > Continue program review
- RDQ (John R)
- DPI (John R)
- PCIM (John R)
- MEM DMC (Monroe P)
- MEM LS (Monroe P)
- DCM Pulse Oximetry Integration Supplement(Completed)
- Pump (Al E, Paul E, Jeff R.)
- Physio monitor (John R)
- Vent (Paul Schluter)
  • 11:30 > Action item Discussion
78. Stakeholder Survey
140. AAMI Alarm Safety Committee
157 Update cookbook to include ACM implementation
Lunch 12:30 PM - 1:30 PM
Tuesday Q3 1:30 - 3:00 PM PCD Planning Committee (PC)(Cont)
  • 1:30 > Location, Dates of the PCD 2016 Spring F2F
  • 1:45 > Review IHE Milestones from now until Pre-Connectathon
IHE 2016 Publication Schedule [1]


Break 3:00 - 3:15 PM
Tuesday Q4 3:15 - 5:00 PM PCD Planning Committee (PC)(Cont)
  • 3:15 >
  • Adjourn PCD Planning Committee (PC) Meeting

Wednesday October 21, 2015

Quarter Time Lead Agenda Items


Wed Q1 08:30 - 10:15 AM PCD Joint Planning & Technical Committee (PC & TC) and Technical Committee (TC)
  • 08:30 > Introduction
- IHE IP Management Process (5 minutes)
  • 08:45 >
- Review & Approve Joint PC & TC Agenda (10 minutes)
- Review Discussion Summary Last PC & TC Meeting PC & TC October 14, 2015 PCD PC&TC 2015-10-14 Webex
  • 09:00 > HIMSS Showcase
MEMLS emphasis at HIMSS
  • 09:30 > AAMI Showcase
  • Nomenclature update (Paul Schluter
  • 09:45 > Adjourn PCD Joint Planning & Technical Committee (PC & TC)
Open PCD Technical Committee (TC)
- IHE IP Management Process
Announcement – Decision Making meeting (TC Co-Chairs)
  • 09:50 > TC Welcome and Agenda Review (Tom Kowalczyk)
- Intellectual Property Requirements
  • 09:55 > TC Cochair election
  • 10:00 > Review Current PCD Program:
- ACM (Monroe P)
Break 10:45 - 11:00
Wed Q2 11:00 - 12:30 PCD Technical Committee (TC)
  • 11:00 > Test Tool update (John G)
Lunch 12:30 - 1:30
Wed Q3 1:30 - 3:15 PM PCD Technical Committee (TC)
  • 1:30 > Review Current PCD Program (continued):
- RTM (Paul Schluter)
Break 3:15 - 3:30 PM
Wed Q4 3:30 - 5:00 PM PCD Technical Committee (TC)
  • 3:30 > IPEC (Al E, Jeff R)
  • 4:30 > Whitepaper - MEMDMC communication from systems to devices (EPIC/Matt Rush)
[FTP link]


Thursday October 22, 2015

Quarter Time Lead Agenda Items
Thursday Q1 08:30 - 9:45 AM PCD Technical Committee (TC)
Break 09:45 - 10:00 AM
Thursday Q2 10:00 AM - 12:30 PM PCD Technical Committee (TC)
- Private Terms (Paul Schluter)
- Continue Profile Review:
IDCO (Paul Schluter)
DEC (updated PCD TF) (John R)
PIV (Al E, Paul E)
EC (John R)
WCM (Ken F)
OMS (Ken F)
DPI (John R)
MEM DMC (Monroe P)
MEM LS (Monroe P)
Pump (Al E, Paul E, Jeff R.)
Physio monitor (John R)
Vent (Paul Schluter)
118. Implementation Guide
140. Assemble the Baseline Set of Standards for Easy Reference
143. Describe HL7 Version Implications
150. Seek null flavors in HL7 2.9
167. Versioning and Archiving
170. Convert IPEC to EC
178 MSH-5 and Connectathon
179. IPEC and EC documentation


  • 10:00 > Continue TC Action item review
183 CP for WCM and implementation
186 Review and reformat ftp site
189 Identify unique identifiers before the Connectathon
190 PRT Segment Use
191 Liaise with IDCO on Waveform communication
192 FHIR
  • 11:00 > ACM change to containment MDC codes and MSH-21 OID change (Monroe)
  • 11:30 > Proposal Review
Communication Between Devices - DPI Working Group (Angela Merzweiler)
Workflow Profile (Angela Merzweiler, Björn Bergh)
[FTP link]
Lunch 12:30 - 1:30 PM
Thursday Q3 1:30 - 3:00 PM PCD Technical Committee (TC)
  • 1:30 > Security Discussion (Axel)
  • 2:30 > Proposal Review (cont.)
Break 3:00 - 3:15 PM
Thursday Q4 3:15 - 5:00 PM PCD Technical Committee (TC)
  • 3:15 > IEEE to LOINC mapping (Paul Schluter)
  • 4:00 > F2F Action Review (from this week)
  • 4:45 > TC Meeting Wrap up and Adjournment (Kowalczyk)


Friday October 24, 2015 (Pump Workgroup)

Quarter Time Lead Agenda Items
Friday Q1 08:30 - 12:00 Pump workgroup
  • AGENDA TOPICS
  • Pump model - discuss and determine best option for channels and containment
  • IPEC - determine changes needed based on revised pump model
  • 12:00 > Meeting Adjournment
Note: Additional evening working sessions may be scheduled as needed.
Note: Time slot TBD: IDCO

Webex Support

Webex will likely be available for those who could not attend in person. The links will be provided below. Reminder: the IP agreement is in force, and participation counts toward voting rights.

Participants

Tuesday, October 20

On Site:


Remote:


Wednesday, October 21

On Site:


Remote:



Thursday, October 22

On Site:


Remote:

Discussion

Discussion Summaries do not require formal approval, while minutes of meetings where votes are taken do. Participants are encouraged to review and bring up significant issues with discussion summaries of previous meetings. Votes will be taken to approve meetings where votes took place; these may be email ballots.

Tuesday

Item Topic Discussion
1 Introductions & Agenda Review
- Chair
Status/Discussion:
Monroe reviewed the IHE IP Management Process
Introductions and Agenda Review

Decisions/Issues:

Agenda approved

Action(s):

2 Discussion Summary or Approval of Minutes
- Chair
Status/Discussion:
Minutes approved

Decisions/Issues:

Action(s):

3 Agenda Items
-
Status/Discussion:
  • Review current PCD programs (statuses, plans only, details during TC sessions):
- ACM (Monroe P)
Updates in PP file on ftp site
(Monroe has slides for all 3)
- MEMDMC
Updates in PP file on ftp site
- MEMLS
Updates in PP file on ftp site
Discussion on encouraging further vendor participation. How to encourage them to join MEMLS? Approach hospitals to pressure them, medical device vendors when deploying, Examined DARPA work as well (Inertial guidance if GPS not available) – useful for home care.
- DEC (updated PCD TF) (John R)
Very slight evolution, no substantial change. A couple of explanatory pieces in the TF update.
- IDCO (Paul Schluter)
Extension for 10103a submitted, should be approved. Extensions on items not already addressed. Making progress. Plan on January 2017 Connectathon participation. Concern over costs in attending the Connectathon.
- PIV (Al E, Paul E)
Not much new. Some TF updates.
- IPEC (Al E)
Worked on pump model, finalizing with proposed CP. Mostly it's a TI implementation, just need TC review, then send to Mary so she can publish for public review.
- EC (John R)
IPEC working well. Other possible is MEMDMC. Unsure if this needs a general profile or keep it within specific profiles. Monroe – there is some commonality, may be good to have design goals and guidance for all to use. Jeff R - Question on how all profiles combine. Could use a guide for new participants.
- WCM (paul Sc)
Know what the updates are, need to write them up. Right now it's adhoc strings. Some Cps are out, just need to write them up. Would be good to have MDC/REFID to outline them. How granular? Stream or Static. Two formats currently. Continuous wasn't originally indicated; hadn't looked at it yet. Discussion of transition between static and dynamic (snippet and continuous).
- OMS (Ken F)
published a white paper a while back, not much activity. In China – most devices are RS-232 serial. If they start implementing HL7, this will be useful.
- RTM (Paul Schluter)
Several related items. Standards – ACM code hiccup, delayed approval. Should be approved Dec 5, published Dec 9, to NIST Dec 10. Different Word fonts make it interesting; formatting to make the document clean and open in HTML. Should be ready for downloading. Hope to have ready for Pre-CN for trial work and fully ready for CN.(gone 9:57 – 10:10).
- Polysomnography
Monroe discussed Polysomnography in IHE Brazil. Challenge – need a mechanism to 'package' individual equipment info into a single report. If we can get a sample report to build from, that would help.
- RDQ (John R)
Quiescent. Asks for past data dump. Well documented and available, but few want to use it. Not sure when it will be implememted. ACM used to have their own, extracted it and recommend using RDQ. Paul Sh – one company registered for RDQ at Connectathon, CardioPulmonary Corp. This may be superseded by something based on FIHR.
- DPI (John R)
Work sporadic, sharing with automating device info model. Proposal sent touches on several areas, including DPI.
- PCIM (John R)
Creating a WP to aid implementation. Any vendors creating material? Yes, Epic, Philips and others are working on that.
- Pulse Ox
Need resources to take this further
- Pump (Al E, Paul E, Jeff R.)
Discuss profile enhancements later this week. Work group meets Friday morning
- Physio monitor (John R)
Basic Vol 3 content specification available. Todd is considering adding to it, but doesn't have resources to do it now.
- Vent (Paul Schluter)
10101a has 50 pages in it, will expand in 10101b. Message content good, will add additional terms as vendors request. Will include events in 10101c.
- Certification (John G)
Just had CASC meeting. They've ID'd some PCD profiles to work on. They're trying to ID what other tasks are needed to comply ISO standard. Charles asked if there are scenarios we would test to around Connectathon time. Quickly developing, a big effort under IHE Intl. The focus is on the end user side. Monroe provided some certification background. Testing rigor is there. This group wants to focus on mature profiles. Discussed certification process. Can we improve Connectathon testing to provide this info to customers? Yes, but it will take a lot of work. Key is to define specializations in Vol 3. Can develop test plans to define scenarios, then add specializations.
  • 11:30 > Action item Discussion
- 78. Stakeholder Survey
Associated with AAMI representation. Not active yet. Will close and open a new one for ECRI. Juuso will check with ECRI staff to see if they're willing to do a survey with their customers.
- 140. AAMI Alarm Safety Committee
Close until it resurrects with Joint Commision analysis of Alarm fatigue. Start a new Action Action for this.
- 157 Update cookbook to include ACM implementation
Resource availability limited ability to update so far. Jeff R willing to look at the pump part and Rob will look into the ACM part. Change date to Nov 11.
  • 12:00 > Use of 11073 terms in HL7. (Epic) –
Discussed at IEEE/HL7 meetings. Most of our terms will be used in Rosetta without formal acceptance. Not as solid as we would like it, but it's usable. Numeric codes and REFIDs are freely available. Yes, but it's better too include IEEE terms as well.
  • 1:30 > Location, Dates of the PCD 2016 Spring F2F
West Health Institute, in San Diego (AFC)
Likely 2nd week of April, paul will confirm and provide to the Committees
- Review Connectathon milestone dates
- Review IHE Milestones from now until Pre-Connectathon
- IHE 2016 Publication Schedule [2]
Long term Roadmap [Roadmap ftp link]
- Cycle 11
Architecture: We use 2.6, moving to 2.8 and 2.8.2 (UDI, PCM uses it)
DEC:
- RDQ not at FT, moved out to 2016
PCD02: In TF
MEMDMC profile options, WCM option for DEC,
Smart Alarms: Move to Cycle 12
RDQ profile specific work: move to Cycle 12
IPEC
- Device order Management
Multi componnent admixtures: Pump roup will discuss this week, may go away
MEM: Final text – not enough vendors yet, moved to 2017
Cybersecurity/Patching Wps – underway
Point of Care:
- DPI no change. Overlatp with a proposal? Yes, likely
- Symmetric Comms:
- UML model – fairly complete, add to calendar for 2016.
- DIM editor – V1 mostly done, should be ready in 2016
Content Management
- 10101b for new terms Q4 2016
- 10101c Q2 2017
- Map IEEE to LOINC
WCM – updated TI
IPEC: Jeff R will submit updated CPs for IPEC TI. Will be several updated CPs.
- PCA Content in IPEC TI – change to pump specialization and move to 2016.
Vent Specialization in RTMMS and PCD TF Vol 3 - 2016
Coordination Efforts
- Sending PCHA records (PCC) – Can use LOINC mapping, but says SNOMED now (unlikely).
- HIMSS ONC MU standards – 11073 distant 2nd to other standards.
Quality
- IEC 60601 - 60601.1.? specific Alarm info not released yet

Adjourn PCD Planning Committee (PC)


Decisions/Issues:


Action(s):

Wednesday Morning

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

Decisions/Issues:

Introductions
Reviewed the IHE IP Management Process
Reviewed & approved Agenda (10 minutes)
Reviewed and approved Oct 14 PC/TC Meeting discussion summary
Reviewed PCD Calendar and Update "PCD ftp site [[3]]"

Action(s):

2 Discussion Summary or Approval of Minutes
- Chair
Status/Discussion:

Decisions/Issues:

Action(s):

Oct 14 PC/TC summary approved
3 Agenda Items
-
Status/Discussion:
- AAMI Showcase
In Tampa this time. No HIMSS showcase. Likely back to 10x20 display, should reduce costs a bit. Will piece together a demo. There will be more info coming.
- AP/Lab domain merger.
How active is lab? Fairly active, not sure what their current specifics are. Paul Sc – what standards are they using? Any MU used? Monroe – good questions, send them to him to ask at next week's DCC call.
- HIMSS Showcase
Family of four didn't quite work, will have 15 patients independent of each other. Will minimize overlap in vignettes. Fewer devices per vignette – allows more time for each vendor. Docents will work with vendors to discuss devices with visitors. Will help between tours as well. Reduced use cases by two, allowing more frequent tours.
Proposed having badge scanners for each vignette. Helps ID walk-ups and tours of specific vignette. Should help with lead creation.
Started discussing use cases with vendors. Vendors now can select vignettes, rather than have them assigned. They are listed on the page as well.
Prospectus on Showcase web page with levels of participation. Philip provided an overview of what vendors get for different levels. Discussed 'Leadership' level benefits.
MEMLS emphasis at HIMSS – No one has signed up yet. One vendor participated last year as location services providor. He hasn't signed up yet. We will ping him to sign up. Is the Showcase in the same place as last time? Unofficially – yes. Will provide signs to connect vendor booths with the Showcase. Hope to provide more directions, etc. to drive traffic to the Showcase. There are event spots available. Rob - Is this being communicated to our marketing people? Yes.
Why the issue of location in Vegas? They don't want to give up prime floor space for the Showcase. Much like Chicago Connectathon space. There are space constraints.
Monroe's relationship with the Showcase? Wanted someone to manage PCD interfaces with the vignettes. Will start PCD calls in November.
- Nomenclature update (Paul Schluter)
Likely 10101a approved by IEEE Dec 6. Should be available for use. Most topics for TC call. Will work with Nicholas to upload into RTMMS. Have four groups competing for the same numeric set, need to manage that process. Many codes start with 0, active ones will have non-0 to show they're active. This helps the receiver know it's an active code. Focussing on getting it approved, don't want to add anything, it could delay approval. Won't include pump info yet.
10:30 Adjourn PCD Joint Planning & Technical Committee (PC & TC)
Start PCD Technical Committee (TC)


Decisions/Issues:


Action(s):



Wednesday 10:00 AM

Action(s):
Item Topic Discussion
1 TC Welcome and Agenda Review (Tom Kowalczyk)
- Chair
Status/Discussion:

Decisions/Issues:

Agenda approved
IHE IP Management Process
Announcements –
- Decision Making meeting (TC Co-Chairs)
- TC Cochair election
Ballot currently open for John Rhoads as new cochair.

Action(s):

2 Discussion Summary
- Chair
Status/Discussion:
-

Decisions/Issues:

Action(s):

3 Agenda Items
-
Status/Discussion:
Review Current PCD Program:
- ACM (Monroe P)
Presentation available on F2F ftp site
Passed a number of CPs.
- Resurrected some functions redacted to acheive Final Text.
Discussion over PCD-05 resurrection. It is an option at the Connectathon. Can do ad-hoc if needed. Tests are updated for 2016. Rob – they will likely participate in 2017.
- Aligned Containment MDCs with IEEE 11073-10101a
- Some in process, not balloted yet.
- Discussion of upcoming CPs and potential impact.
Question of PRT and HL7 versions. Discussion of OBX.
-Test tool updates (John G)
Presentation on ftp site
Scope 'creeps' and become defacto e-version of the standards.
HL7 V2 tooling -
- Working with IHE int'l to help with their certification. IGAMT and TCAMT – guides constrain the standards to usable levels, reduces ambiguity. Drives user consistency, especially useful for Meaningful Use. Want to get PCD-01 into them. Once done, can work on specializations and other profiles. Hope to have it ready to demo by spring F2F.
- DIM Editor and tools
Showed updates at IEEE-HL7 meeting earlier this month. Challenge; seperating 11073 terms from others. Model robust and stable, being tested. Once model done, can build containment. Need to know the DIM a bit, but it's very powerful and useful for generating standards.
Meetings and activities coming up
Addressing Cps as they happen and TF 2, V5.
- IHE-Japan Connectathon – Asked them how the tools worked, worked well
- As they evolve, will be able to use different tool versions
- RTMMS
Updated tools. How well is IE working with the tools? It's a bit erratic, they recommend Firefox and Chrome. Working through those challenges. Dr. Swapna provided a great cross reference sheet.
11073 will include LOINC and SNOMED mappings soon. Paul Sc – concerned it may be a bit premature, suggest starting with a lighter touch. It will take a while to implement. Needs more review.
- NIST tool framework work
- Royalty free agreement with IEEE
- Tool updates
WCTP in the future? Monroe and John G to discuss.
- Discussion
CP122 update underway
IPEC – Have a lot of 0 MDC codes, How to resolve? Todd working on it. Current mechanism doesn't work, paul Sc will discuss at his session.
John demonstrated TCAMT . A process to automate test generation. Example - Paul Sherman can use the test spreadsheets and create the tests.
When will Pre-Connectathon start?
  • 1:30 > Review Current PCD Program (continued):
- RTM (Paul Schluter) Presentation is on ftp site.
10101a, and lessons learned -
Either method can be supported. Paul is looking for feedback and suggestions.
Dealing with 'junk' terms.
Q – Without ability to see what's submitted to 10101a, how to see what's submitted so we can provide input? A - IEEE instituted public review period; working group must review comments.
Q - How to get new pump term numbers? A – On RTMMS now, Todd can approve them. Likely have few junk terms.
Q MEMLS has 20+ terms, some from other areas. A – should be no problem, there's space for them.
- IPEC (Jeff R)
Not a lot going on right now. Found pumps and use cases it didn't accommodate. IPEC is driving the IEEE model. Redefining the model. Will be a CP to approve a new version. The events haven't changed much. The changes reflect pump models and content of those events. Some will end up in Vol 3. Clinical Scenario section; many changes in the Parameters. Eliminated use of 'channel', will use 'info' instead. Come too far to go back, need to know how to get them into RTMMS and the NIST tools. John G – Todd entered some new terms, is committed to get other codes assigned by EOW. Reviewed RTMMS. 92 terms, 22 without codes. This will change the DEC profile as well. Struggles with adding dose units as well. What needs to happen? Al updated Todd about the terms, need them loaded. How long to validate the terms? It depends on the field and requirements. Extensive discussion and review of terms in RTMMS.
- Whitepaper proposal - MEMDMC communication from systems to devices (EPIC/Matt Rush)
[FTP link]
Alert Management – Silence Alerts and setting alert limits.
11073 meeting a couple of years ago – seems there's been work there. Look at 11073 – 10201. prepare for feedback from Jan Wittenber. Some things to be done first. There's a lot of interest in 11073; personal health devices has done some work. Issuing commands in FIHR will create a lot of new terms. Seems a very good time to discuss it.


Decisions/Issues:


4 ___ Status/Discussion:



Decisions/Issues:

Action(s):


Thursday

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

Decisions/Issues:

Agenda approved

Action(s):

2 ____________
- Chair
Status/Discussion:
-


Decisions/Issues:

Action(s):

3 Agenda Items
-
Status/Discussion:
** reviewed IHE IP Management Process
Review of On-going work
- ACM update (Monroe)-
- Point-of-Care Identity Management (PCIM) white paper (John R)
No major change in OBX-4, but could be EMR challenges.
John provided OBX4 overview. Discussion of official definitions versus implementation. As soon as we define the models, it will be useful for implementers, particularly on the receiver end. Epic explained how they implement OBX-4. In general, XML is like a tree, you can parse a message to find the info needed. In TF as a 'should, not a 'shall'. Epic had to code to the current framework.Enforcing document order won't eliminate OBX-4. This ensures consistency within channels. Risk of mixing semantics, but not sure it's a practical concern. Brian will discuss this with Chris (Epic). Pump model has a couple of attributes for events and alarms. Also a companion attribute that defines hierarchy position. Example – will use different OBX's for primary and secondary pump channels.
- Private Terms (Paul Schluter)
- Continue Profile Review:
DEC (updated PCD TF) (John R)
IDCO (Paul Schluter)
PIV (Al E, Paul E)
DPI (John R)
- Semi-quiescent
MEM DMC (Monroe P)
- Moving more into the mainstream. Some 11073 attributes not in RTMMS yet, but can be added when needed by MEMDMC. May be in the X73 tab; will need to be harmonized. May be able to use Personal Health Devices as well. Two Cps, proposals for communication to devices, this may be the best group
MEM LS (Monroe P)
- Will need to change the document to resolve an editing error. Al will submit a public comment to correct.
PCIM (John R)
- Core of the WG (Stan, Chris and Doug) did a lot. Have a good draft, hope to submit by EOY, then send for balloting. Pretty specific on format and content. John and Chris will prototype, then TI in 2017
Pump (Al E, Paul E, Jeff R.)
Physio monitor (John R)
Vent (Paul Schluter)
- Done a lot of work, a lot of mappings wih positive feedback. Covered basics, breathe by breath annotation, additional parameters. Will need to take care of private terms. Advanced topics may be in 10101c.
118. Implementation Guide
- Ties to Igamt and tcamt work. Trying to implement PCD-01. Will mirror TF Vol 2, provide more focused device speciliazation guides.
136 WCM Attribute List
- Can use numeric Ids or annotated ECG. Not a compelling need to include them.Have a good way to show filters. Change to Nov 18.
143. Describe HL7 Version Implications::- :: 143. Describe HL7 Version Implications
- CLOSE
150. Seek null flavors in HL7 2.9
- HL7 V3 item to explain why a field is empty. In TF Vol 2, line 3380. Tweaked it to make a tutorial. CLOSE
  • 11:30 > Proposal Review
Communication Between Devices - DPI Working Group (Angela Merzweiler)
- Don't have ability to communicate between devices, described five use cases.
- Discussion – John R; DPI goals for some time, looks like a good project. Monroe; some profiles and TIs started on it, may need to spraed out over multiple Wgs. Some experience and expertise to help achieve. What does a device need to support? Use this approach to configure devicxes and record alerts and observations. There are a lot of pieces that exist. DPI can build on that work. Need to prioritize the tasks, then fill in the rest as time allows. Need to find resources to implement it. Part of 11073, but not main part, part of Open SDC. Stephan: Described transport specs, web services derived from HL7 specs. Glues together how the sections work. Needs implemented by devices (not HL7). Are there libraries available? Yes, two. Open SDC and OC-lib.
Workflow Profile for ordering Device Monitoring (Angela Merzweiler, Björn Bergh)
- Closes loop from order to results. (I want this device to do this thing)
- Discussion – Similar to original DEC profile, takes existing HL7 V2 infrastructure. Tailors this to a specific use case. Similar to RGB in PIV. Want to order, then take results and update the order. RAD has done similar work, can use this to build this profile.
Next steps – Evaluate proposals. Determine work needed and resources available. PC will review and determine if we'll take I forward. Will need to submit to HIMSS to determine if this is appropriate for PCD or another domain.
[FTP link]
  • Continue TC Action item review.
167. Versioning and Archiving
- ::- ACM used OID to perform this. Can add a how-to to TF next iteration CLOSE
170. Convert IPEC to EC
- Do we take it down a notch and put info in framework, and let device specific groups define as needed (IPEC becomes an example of EC)? IPEC principles can provide a base for others to build on. Close this and open another to create common EC material to go into TF. Owner of new AI – IPEC team and John R. What is the need for this material? Would be a template for other equipment types to build on.
- CP-122: ACM change to containment MDC codes and MSH-21 OID change (Monroe)
Monroe reviewed CP, found a few edits needed. Any other profiles have changed their content. Questions on why this needs a CP. Because this is in Final Text, most others are in Trial Implementation. Epic is concerned over keeping track of the changes and versioning. Doesn't see this as a big enough change to warrant versioning. This one is, this won't be a habit. Monroe will retract the CP, edit as needed and resubmit for balloting.
  • Medical Device Cybersecurity Discussion (Axel)
All this work needs to happen quickly, but in a highly regulated environment. This is a system of systems issue. Overview of prior work and current activities. Getting good feedback from Symantec customers. Limitation – only best practices for current tech, nothing for new technologies; had to update chapters while writing. September asked 'What's Next?'. Users provided a list of what they need. The workgroup needs provider members. Need a way to make this work at the hospital level. Examples: Equipment returned from repair, loaners, demo equipment – how to confirm they aren't a security issue without overloading the hospital? This typically would go to ITI, but they don't really look at device function. Life critical vs. mission critical, the variety, number of devices and device age are all more complex than IT systems.
  • Continue TC Action item review.
175 Develop a PCD UDI Witepaper for IHE
- John R – Unless someone has material changes, close this.
178 MSH-5 and Connectathon
- Retitle to MSH 3 and ACKs. Look for Jeff's email and use that an update to the TF. What to do as a gateway? The gateway is responsible for the ACK. Change date to Nov 4 and put on the TC agenda.
179. IPEC and EC documentation - CLOSE
183 CP for WCM and implementation
- Will update WCM TI rather than create a CP. Change date to Nov 18.
186 Review and reformat ftp site
- Make Cochairs owners. Change date to Dec 31
189 Identify unique identifiers before the Connectathon
- Discussion on how to proceed. Could have the vendors provide, NIST loads the info, then it can tie back during Connectathon registration. John G will assemble a spreadsheet to go to CN and PC members asking them to load their info. Will try to have ready for Pre-Connectathon. Paul Sc suggests including a private company identifier. Set up for warning if not in the table, error if different than in table. Stay with OBX-18 for now. Need extra data and analysis. John will send a notice on what's needed for this Connectathon.
190 PRT Segment Use - CLOSE
191 Liaise with IDCO on Waveform communication
- Liaised, unsure what IDCO will do. Change to Dec 31.
192 FHIR Change date to Dec 31
IEEE to LOINC mapping (Paul Schluter)
- IEEE 11073 to LOINC Mapping
Very reasonable first draft of mapping exists, due to the work of Dr. Swapna Abhyankar.
600+ ‘harmonized’ Rosetta terms, incorporate dimensionality, maps (almost reversibly) to LOINC.
Recommend that mapping information be captured as a single, authenticatable file.
IEEE P11073-10104 as possible future standard, provides ANSI recognized open-consensus review and voting.
MoU between IEEE and Regenstrief ‘almost’ signed (should have been two weeks ago).
IEEE-SA is considering similar relationship with SNOMED-CT, but many things are needed to be done to make this happen.

Decisions/Issues:


Action(s):


4 ___ Status/Discussion:

http://wiki.ihe.net/index.php?title=PCD_Proposals_Cycle_10#Cycle_10_WorkItem_Candidates


Decisions/Issues:

Action(s):

Friday Pump WG Meeting

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

Decisions/Issues:

Agenda approved

Action(s):

2 General Discussion
'Status/Discussion:
reviewed IHE IP Management Process
Attendees: Al Englebert, Paul Elletson, Brian Witkowski, Tom Kowalczyk, Megan Tetlow, Olivier Coeffic, Jeff Rinda


-Pump specialization will be major focus of pump group in 2016
• LVP, PCA, Syringe


-IPEC - messages should contain information for all channels
• most important for the "start" message after infusion programmed using PIV
• consider updating IPEC profile to explicitly state this


-Extending PIV to other use cases
Multistep and Loading Dose programs
PIV can support when all program parameters are ordered and known by EMR "up front"
Paul E - determine whether there is an MDC term for "continuous" that can be used


-Proposed PIV message structure for multi-segment orders:
• loading dose or bolus followed by continuous infusion
• multi-step infusion
MSH
PID
(PV1)
ORC
{
RXG
(TQ1)
RXR (consider placing this segment before RXG so that it only appears once if HL7 supports)
OBX – indicates dose type (use existing MDC terms for loading dose, clinician dose, may need new term for “continuous or continuous rate”)
OBX – pump ID
OBX – patient height/weight/BSA
}


-Ramp/Taper
In order to support we need to know the specific parameters required by the pump.
Need to define terms for these parameters (some examples might be "target dose rate", ramp time, taper time, enumerations for "ramp" and "taper". Do we :have status elements defined?)
Vendors may handle programming differently or not support at all.


-Bolus
There are many use cases where the word bolus is commonly used
• Initial bolus (= loading dose)
• Bolus administered from bag
• Bolus administered from secondary
• Bolus according to protocol order (as needed according to patient parameter or condition)
• Bolus administered from syringe (heparin, insulin, narcotics often given this way)
Jeff will solicit comments on bolus practice, consistency within an institution, etc
Brian will solicit comments on bolus ordering (if separate order – how to “link” to an infusion in progress, how to know whether given by syringe or as :secondary/piggyback)


-Use of 5th containment level
Jeff will schedule pump group call pending Todd’s availability to review Al's email on use of the 5th containment level


-Use of reference range (OBX-7)
Al will develop a CP to optionally use the reference range (OBX-7) to contain drug library limits.


-Target-controlled infusions (TCI)
Require specialized pumps that deliver a drug to maintain a target blood concentration
More common in Europe
Issue: How to program using PIV
Vendor(s) of those pumps are not currently participating in IHE pump group, and current group members are not familiar with the programming and :operational parameters for the devices.
“Diprifusor” is a TCI device developed specifically for the administration of a single drug - propofol (Diprivan)


Decisions/Issues: See above

Action(s): See above

Action Items - PC

The Action Items that follow and approved in subsequent committee meetings will be added to the committee Action Item page.

Submit updated Milestones to IHE (Mary Junger)
Update PCD's long term visionary roadmap calendar

Action Items - TC and WGs

The Action Items that follow and approved in subsequent committee meetings will be added to the committee Action Item page.

Next Meetings

Joint Planning and Technical Committee: PC and TC __ PCD PC&TC 2015-10-28 Webex

TC PCD TC 2015-11-04 Webex

PC PCD PC 2015-11-11 Webex