PCD PC&TC 2009-05-04 to 08 F2F

From IHE Wiki
Revision as of 23:49, 12 May 2009 by Efurst (talk | contribs) (→‎Monday 2009.05.04: partial entry)
Jump to navigation Jump to search


Meeting Objectives

These face-to-face meetings have a number of objectives depending on the committees involved:
  • Planning Committe: Review overall PCD activities, identify strategic next steps and update the "roadmap"
  • Technical Committee: Review all materials slated for publication in May / June and resolve any issues so that final editing and publication may proceed.
  • SDOs: The last two days of the meetings will be joint with IEEE EMBS 11073 and HL7 Health Care Devices WG. This is in lieu of participation in the Kyoto meetings being held the following week.


Schedule & Agenda

Daily Schedule
08:00 - 08:30 Check in at NIST front gate, stop at Visitors Trailer for badge; proceed to Building 222 ("Chemistry Building"); Meetings in Room A314 (third floor). IDCO WG meetings in room B341.
Meeting will start promptly at 08:30 each day.
08:30 - 10:30 Session #1
11:00 - 12:30 Session #2
12:30 - 13:30 Lunch (location to be announced)
13:30 - 15:00 Session #3
15:30 - 17:00 Session #4
NOTE: Friday the meetings will end by 15:00.


Date Hours Committees Topics
Monday

2009.05.04

08:30 - 17:00 PCD Planning Committee
  • Greeting & Introductions (NIST [Jim St. Pierre, Dept. Director of ITL] & IHE)
  • Review & Approve Agenda
  • IHE IP Managment Process
  • Review Current PCD Program (incl. approved profiles)
  • Identify Key Interoperability Issues
  • Lunch
  • U.S. HHS / ARRA:
- IHE & NIST
- ARRA (Carnahan)
- Test Tooling Support (Snelick)
- Terminology Mapping Update
- Device Connectivity & HITSP/ARRA Message
- HHS Security & Privacy Disclosure Feedback
(Link 1 .. Link 2)
  • Review & Update PCD Roadmap
- ACM Roadmap
- WCM - Requirements Review
- Regulatory Considerations WP (a.k.a. MDDS/80001 & IHE)
Tuesday

2009.05.05

08:30 - 12:00 PCD Planning & Technical Committees
- Conceptual Approach
- Vendor Equipment / Systems Policy Review
Tuesday

2009.05.05

13:00 - 17:00 PCD Technical Committee
  • MEM Detailed Discussion
  • Profile Optionality Management
  • OBX, PID & ACK Discussion
Wednesday

2009.05.06

08:30 - 17:00 PCD Technical Committee
  • Cycle 4 Test Tooling Strategy (NIST)
  • PCD Message Profile Registration (e.g., w/ HL7 repository)
  • IHE International Update
  • HITSP Engagement
  • MoU Updates / SDO IP Management
- IEEE
- HL7
- ASTM/CIMIT
  • ICE-PAC Review/Update
  • Tour of NIST's Radiation Physics Lab (1:15 - 2:45 PM)
- Limited to 24 visitors
  • Detailed Cycle 4 Work Items Review
- Technical Framework Update (DEC, v2.6,...)
- Review pending updates
- EUI-64 Usage
- PIB - Incoming ID binding status notification
- SPD - Proposed predicate enhancements
- ACM Update
- PIV Update
  • PCD TF Architecture Discussion
  • Patient-Device Association
  • Continua Coordination
  • Cycle 4 Development Activities Review
Thursday

2009.05.07

08:30 - 17:00 PCD Technical Committee & HL7 DEV WG & IEEE 11073 Terminology & Semantic Architecture
  • IEEE 11073 & HL7 DEV WG Open Leadership Positions - Call for Nominations
  • NIST Terminology Management Tooling Update
  • 11073-10202 DIM Schema Update & Work Plan
  • Rosetta:
- Update & Harmonization w/ aECG & IDC nomenclatures
- Inclusion of 11073 Personal Health Terms
- Term Review ("vote off the island")
  • IHTSDO Collaboration Update
  • IDCO Profile Review
  • Technical Framework Vol. 3 & Device Semantic Architecture
  • Detailed Clinical Models (DCM) Update from TC215 Edinburgh Meetings
  • Ventilator Terminology Update
- Status Review
- Respiratory Therapy "Booklet" Content / Template Discussion
- WCM
- HL7 v2.6 Proposal
- ACM Integration
- DPI WP (main discussion Friday)
  • 2009 Survey Questions Review
Friday

2009.05.08

08:30 - 15:00 PCD Technical Committee & HL7 DEV WG & IEEE 11073 Device Point-of-care Integration (DPI)
  • White Paper Draft Review
  • NIST Tooling (ICSGenerator & ValidatePDU)
  • Action Item Review (from this week)
  • Supplements Roadmap & Review (defered to the 2009.05.13 Wednesday meeting)

Adjourn Meetings by 15:00

Note: Additional evening working sessions may be scheduled as needed.

Location Information

National Institutes of Standards and Technology (NIST)
Building 222, Room A314 (Conference Room)
100 Bureau Drive
Gaithersburg, MD 20899


  • IMPORTANT REGISTRATION INFORMATION: Though there are no fees for this meeting, all participants must indicate their intention to attend by sending an advanced notification e-mail to John Garguilo (NIST) and Manny Furst (IHE PCD). Since these meetings are located at a U.S. government facility, international participants must provide additional information for security checks.
  • General location information: NIST is about 30 miles north of Washington D.C. and located nearly equi-distant from three airports: Dulles (Northern Virginia - IAD), Washington National (Reagan), and Baltimore-Washington International (closer to Baltimore - BWI). If you are comfortable with taking the metro, Washington National may be the best solution, the other two require a rather lengthy/expensive taxi ride…(~25 - 40 miles). Dulles likely has the most international flights, but that may depend on which carrier you use.
  • Shuttle service: (Super Shuttle) is also available from Dulles, National and Baltimore airports. From Dulles to the Hilton costs $33, and from National to the Hilton costs $31 and from BWI it is $47. No reservations are required for the trip from the airport. To return to the airport requires a reservation, which we can try to coordinate during the F2F (which also reduces costs). Super Shuttle site

Attachments / Materials

Reference materials can be downloaded from ftp://ftp.ihe.net/Patient_Care_Devices/Minutes-and-Meeting-Summaries-Yr4-2009-10/F2F-2009May4-8/ Please note: some of the materials are in the recent Microsoft .docx, pptx formats. These have been converted to the earlier .doc and .ppt formats and may have lost some details in the conversion.

Decisions Summary

NOTE: These decisions are in addition to the action items listed above.

No. Decision Date Description
1 xyz 2009.05.04
  • ...
2 xyz ...
  • ...
3 xyz ...
  • ...
4 xyz ...
  • ...
5 xyz ...
  • ...

Action Items Summary

Action Items listed below were developed during the meetings. Action Items from the PC and TC are found in Discussion Summaries of those committees. PCD PC 2009-04-29 Webex and PCD TC 2009-04-22 Webex

No. Action Item Owner Participants Due Open/Closed Description/Update
1 ... ... 2009.05.04 Open ...
2 ... ... 2009.05.04 Open ...
3 ... ... 2009.05.04 Open ...
4 ... ... 2009.05.04 Open ...
5 ... ... 2009.05.04 Open ...
6 ... ... 2009.05.04 Open ...
7 ... ... 2009.05.04 Open ...
8 ... ... 2009.05.04 Open ...
9 ... ... 2009.05.04 Open ...
10 ... ... 2009.05.04 Open ...
11 ... ... 2009.05.04 Open ...
12 ... ... 2009.05.04 Open ...
13 ... ... 2009.05.04 Open ...


Meeting Minutes

Monday 2009.05.04

Participants:

Sam Carello – Welch Allyn, Maria Cherkaoui - NIST, Anupriyo Chakravarti – Surgical Information Systems, Malcolm Clarke – Brunel University (TC215 participant), Bikram Day - Capsule, Fred Ehrhardt – Capsule, Al Engelbert - B Braun, Ken Fuchs - Draeger, John Garguilo - NIST, John Hotchkiss - LiveData, Barbara Majchrowski - ECRI, Sandra Martinez - NIST, Steve Merritt - Baystate, Gary Meyer - Cardinal, Monroe Pattillo - Philips, John Rhoads - Philips, Jeff Rinda - Hospira, Paul Schluter - GE, Tom Schultz - Medtronic, Erin Sparnon – ECRI Institute, Iaona Singureanu - VA, Greg Staudenmaier - VA, Nick Steblay – Boston Scientific, Sandy Weininger - FDA, Jan Wittenber – Philips, Scott Zaffrin – B Braun, Vaughan Zakian - Nuvon, Khalid Zubaidi - Cardinal,

Chairs: Ken Fuchs, Steve Merritt

Technical Project Manager: Manny Furst – Improvement Technologies/HIMSS


Item Topic Discussion
1 Welcome
- John Garguilo 		Status/Discussion:
  • Welcome from NIST – Jim St. Pierre, ITL Department Director provided a description of NIST structure and an introduction to NIST’s participation in ARRA funding. The funds include
- $220M grants formal bidding on technology
- $20 M from HHS for interoperability, security, other EMR related grants

Decisions/Issues: Action(s):

2 Introductions, Review of Agenda
- Cochairs 		Status/Discussion:
  • Participants introduced themselves.
  • Agenda was a approved with a few additions, notably OBX 4 and acknowledgement other than original ACK. Paul indicated that Ruth Berge asks that PCD address issues related to linking devices and data to the patient.
  • Erin indicated that HIMSS has a patient safety group and that she will act as liaison. One of their interest in an implementation guide for EMRs and that has potential links to PCD’s implementation guide.
  • Ken described the IP requirements for those participating. Todd referred to the IHE wiki page with the patent disclosure requirements.

Decisions/Issues: Action(s):


3 Review of Profile Status and Cycle 4 Plans
- Ken Fuchs and working group (WG) champions 		Status/Discussion:
  • ACM: Monroe indicated the direction will be to determine how to provide the output message and WCM. Paul asked if alarms can be added to RTM, and possibly a data model and priority. Monroe indicated a need for RTM to set a threshold for minimum data set that will tie the alarm to the patient. ACM should add one or more use cases that illustrate this extension. Discussion continued about the broad scope of potential alarm/alert notifications, the scope that includes messages from other domains (e.g., radiology, lab), the levels of significance (up to life threatening). Anupriyo indicated the variety of alarm subjects is too large to list. Vaughan indicated that the number of alarm possibilities and the number of recipients can reach a level that users will ignore them. Monroe summarized the difference between PCD’s interests (from devices to people) while other domains are most interested in data from the patient. The consensus was to first address those that are common. Ken suggested that a subscribe model be added to the existing push model. Manny suggested a webinar focused on the AM to AC communication. Todd observed that a new standard may be required and an early step will be to identify the standards group responsible. Iaona suggested that it may be other than HL7.

Action Item: Manny will contact companies identified by ECRI Institute and Monroe, and include a list of user needs and priorities.

  • DEC: CPs will be addressed, including a move to HL7 2.6.
  • PIV: As above. Paul asked if drug id has been standardized. There are standards, none of which are used. Jeff indicated this will develop over time.
- Jan proposed that key characteristics may also be desirable, such as pharmokinetics and the approach should permit future extension. Erin suggested these might include how to safely store the drug, where it is kept and other items. Anupriyo added reconciliation because there are multiple ways of identifying the drug. Erin indicated that when suppliers are changed both are acceptable. Todd observed that standardizing ID is not limited to drugs. Discussion indicated that drug nomenclature varies among countries, hospitals, companies.

Action Item: Monitor HITSP’s work – Jan is on the relevant tiger team.

  • RTM: Paul provided a status report which indicated that it is substantially complete except for ventilator terms. The RTM-vent WG had a breakthrough recently that should lead to the ability to map vendor representation and machine representation. In addition, IDCO terminology is well along.
- Anupriyo requested a way to indicate the basic measurement when there are multiple sources (e.g., heart rate developed from ecg, bp, etc.). Paul suggested adding synonyms to RTM. Iaona indicated this is available in HL7 v3.
- Paul noted that the IDCO terminology mapping is consistent with the existing RTM table and with XML representation.
  • DPI: Jan provided a status report. He noted that DPI depends upon other profiles. Following tghat identification, they will be able to write the white paper. This is scheduled for Friday morning. He suggested taking an hour in the PC to introduce the first white paper.
  • Semantic White Paper: Will kick off in August.
  • MEM: Steve asked if the high level approach used is adequate or if technical detail is required. He asked if RTM should include more device data as well as physiologic data. Todd indicated that the white paper should recommend priorities. Steve ;ater provided these links with additional information:
http://wiki.ihe.net/index.php?title=PCD_MEM_2009-05-05

Action Items:

- New Brief Profile Proposals for Cycle 5
- Battery management (leverage existing PCD-01)
- Location boundary alarms
- Other work items for Cycle 5: Nomenclature requirements (Data types, names, value sets); Examine status of location services within HL7
  • Key Interoperability Issues: Priorities for PCD (roadmap). Harmonization with Continua, which will require an intermediary. Ioana indicated that the VA’s home care experiment is addressing the question of integrating this with inpatient applications using a “device manager”. Issues arose, including consistent time.
  • TF: Todd asked that a date be set to move the TF to final text version.

Action Item: Set the date for TF final text version public comment release.

Decisions/Issues:

  • Action Items as noted.

Action(s):


4 ARRA and NIST Test Tooling
- Rob Snellick, Lisa Carnahan 		Status/Discussion:
  • Rob Snellick and Lisa Carnahan introduced NIST’s support of testing and ARRA funding. Two of the three are of interest: testing and grants related to health IT. Grants funding is largely to non-profits and universities. $15 M will be contracted. Standards/subject matter expertise and testing will be the largest portions, mostly testing. The idea is that the tools would become services. NIST will build and fund the core, while SOA access will be tailored to the organization needing access. NIST will seek collaborators for development and evaluating the tools. IHE domains, CCHIT, ONC are among those expected to collaborate. No current work will be dropped (including PCD).
  • In the short term, PIX PDQ v2, v3, lab results, and PCD pre-connectathon testing are at top of list being considered. These will be used to validate NIST’s approach. In the Fall NIST will have a workshop to evaluate its direction before addressing other test tools.
  • Rob then provided a high level overview. REFER TO SLIDES The tests will be conducted in Pre-Connectathon timing and provide more rigorous evaluation. Subject matter experts will be required to define the requirements. Access to the receiving system’s behavior may require a query function since the ACK does not provide detail and may not be sufficient to detect the receiving system’s proper performance with defective messages.

Decisions/Issues:

Action(s):

5 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

6 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

7 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

8 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

Tuesday 2009.05.05

Participants:


Item Topic Discussion
1 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

2 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):


3 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):


4 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

5 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

6 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

7 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

8 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

|}

Wednesday 2009.05.06

Participants:


Item Topic Discussion
1 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

2 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):


3 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):


4 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

5 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

6 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

7 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

8 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

Thursday 2009.05.07

Participants:


Item Topic Discussion
1 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

2 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):


3 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):


4 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

5 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

6 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

7 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

8 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

Friday 2009.05.08

Participants:


Item Topic Discussion
1 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

2 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):


3 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):


4 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

5 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

6 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

7 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

8 xyz
- <lead> 		Status/Discussion:

Decisions/Issues:

Action(s):

Next Meeting

The next meetings are:

A joint TC and PC webinar May 13, 2009: PCD PC&TC 2009-05-13 Webex.

The Technical Committee will hold a webinar meeting May 20 PCD TC 2009-05-20 Webex

The Planning Committee will hold a webinar meeting May 27 PCD PC 2009-05-27 Webex


Back to Roadmap > Schedule

PCD Home

Retrieved from "http://wiki.ihe.net/index.php?title=PCD_PC%26TC_2009-05-04_to_08_F2F&oldid=32888"