PCD TC 2015-11-04 Webex

From IHE Wiki
Jump to: navigation, search

Patient Care Device Domain

Meeting Purpose

PC At the Regularly Scheduled Meeting Time

WebEx Information

Topic: PCD Technical Committee

Regularly Scheduled Meeting Time

Time: 11:00 am, Eastern Time (New York)

Duration: 60 Minutes


Proposed Agenda

1. Agenda Approval
2. Review Discussion Summary: PCD TC 2015-10-07 Webex
3. Standards Coordination
4. Marketing and Recruiting PCD, IHE
- John Rhoads for TC cochair - [Ballot] open until Nov 19. We have achieved quorum.
5. Calendar http://wiki.ihe.net/index.php?title=Domain_Milestone_Dates
- Status of Adopted Workitem Proposals
6. TC Action Item Review
- Action Item TC178: Jeff McGeath's notes - The final outcome was that systems would be graded on what they are sending in MSH:3. This is the sending application, and therefore should be known in advance. We ran into an issue at last year's (Jan 2014) connectathon where systems were receiving a message, then when building their ACK they would create a MSH:3 that just copied the original message’s MSH:5 value. Those systems should know who they are and would never send out an ACK with an empty MSH:3
- My memory on the action item was that either Gazelle or the NIST tools would have a table to track the vendor names and map that to the Connectathon IP address assignments. If that were in place, the validation engine could then cross reference the sending IP with the known vendor and fail any transactions that have incorrect or empty MSH:3 values.
7. Other Business
- CP 123 open until Friday, Nov 6
- Proposal Review
- Polysomnography profile.
- ONC, LOINC and 11073
8. Next and Recent Meetings
- PC Nov 11
- PC & TC Nov 18
- TC Dec 2

Action Items from Previous Meetings

See PCD Technical Committee Action Items

Significant changes, other than dates, will be in bold.

References

  • Published and Draft Versions of the TF, Supplements, Other Documents:
- The PCD ftp site has draft versions.
- Published (and possibly in the process of being replaced with new versions):
o http://ihe.net/Technical_Framework/index.cfm#pcd
  • Not Yet Published:
o ftp://ftp.ihe.net/Patient_Care_Devices/Profiles/

Participants

Al Engelbert, John Garguilo, Tom Kowalczyk, Monroe Pattillo, Dalibor Pokrajac,Paul Schluter, Paul Sherman, Megan Tetlow
Chair: Tom Kowalczyk

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.

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

Decisions/Issues:

Agenda approved

Action(s):

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


Decisions/Issues:

Action(s):

3 Agenda Items
- Standards Coordination
Status/Discussion:
3. Standards Coordination
- Waiting for December final meeting for 10101a, moving along well.
4. Marketing and Recruiting PCD, IHE
- John Rhoads for TC cochair - [Ballot] open until Nov 19. We have achieved quorum.
- Still interest in a BI&T article (Monroe)
5. Calendar http://wiki.ihe.net/index.php?title=Domain_Milestone_Dates
- Status of Adopted Workitem Proposals
6. TC Action Item Review
- 170: Suggest moving this past Connectathon and Showcase. It's a cure with no known disease. Move to April Face to Face. Paul Schluter - May be tied to containment work.
- Action Item TC178: Jeff McGeath's notes - The final outcome was that systems would be graded on what they are sending in MSH:3. This is the sending application, and therefore should be known in advance. We ran into an issue at last year's (Jan 2014) connectathon where systems were receiving a message, then when building their ACK they would create a MSH:3 that just copied the original message’s MSH:5 value. Those systems should know who they are and would never send out an ACK with an empty MSH:3. Jeff: My memory on the action item was that either Gazelle or the NIST tools would have a table to track the vendor names and map that to the Connectathon IP address assignments. If that were in place, the validation engine could then cross reference the sending IP with the known vendor and fail any transactions that have incorrect or empty MSH:3 values.
What's next? This will need to be tested and NIST will need info in advance. Gazelle and NIST tools are separate. John G: If info is available, they can validate it. If NIST tools are consumer, they can parse the info. As a reporter they need it up front to send the message. This info should be entered before Connectathon, but often isn't. Need agreement by all to submit IP addresses before CN. This is mostly a Pre-connectathon participant issue. Already performes in Pre-Connectathon. Close this and open a new one for Connectathon. CLOSE.
- 189 Start sending EUIs to NIST so they can pre-populate. For companies with multiples, NIST will allow them to enter all of those and select during testing. For those without an EUI-64, enter your DNS number. Set date to Nov 18
7. Other Business
- CP 123 open until Friday, Nov 6
- Proposal Review
- Polysomnography profile.
will be a device specialization. May need some new MDCs. Will meet with them on Friday.
- ONC, LOINC and 11073 - meeting next to provide ONC with input recommending using 11073 for vital signs monitoring.
8. Next and Recent Meetings
- PC Nov 11
- PC & TC Nov 18
- TC Dec 2

Action(s):


Next Meetings

The next meetings are:

PC Nov 11, 2015 PCD PC 2015-11-11 Webex

PC & TC Nov 18, 2015, PCD PC&TC 2015-11-18 Webex

TC Dec 2, 2015 PCD TC 2015-12-02 Webex

PCD Home