PCD ADQ 2011-04-14 Webex: Difference between revisions
m cat |
|||
| Line 1: | Line 1: | ||
[[Category:PCD Meeting]] | |||
[[Category:PCD ADQ]] | |||
{{TOCright}} | {{TOCright}} | ||
| Line 78: | Line 80: | ||
<!--''<Add review line here when minutes are approved; e.g., "(Reviewed & approved by PCD RTM Vent TG 2008-04-16)">''--> | <!--''<Add review line here when minutes are approved; e.g., "(Reviewed & approved by PCD RTM Vent TG 2008-04-16)">''--> | ||
[[Patient Care Device | PCD Home]] | [[Patient Care Device | PCD Home]] | ||
Revision as of 13:41, 14 July 2011
Patient Care Device Domain
Meeting Purpose
4th ADQ meeting (Asynchronous Data Query)
WebEx Information
Topic: Asynchronous Data Query
Date: Thursday, 14 April 2011
Time: 2:00 pm Eastern
Duration: 60 Minutes
Proposed Agenda
- ADQ Transaction Requirements |- Accurate Time |- John R. Diagram |- QPD use for Queries
Action Items from Previous Meetings
See ADQ Action Items
Participants
- Chair: Khalil Maalouf (Nuvon)
Ken Fuchs (Mindray), John Rhoads (Philips), Paul Schluter (GE Healthcare), Nishan Wijesinghe (Parigan)
Discussion
Item Topic Discussion 1 Introductions & Agenda Review
- ChairTime Accuracy: Paul suggested to always report out with PCD01 (or equivalent) message – OBX, OBR. Need to move the corresponding requirements down to the Responder notification section. Need to construct a table of the different time reporting cases depending on Gateway/Medical device connection.
2 Item
- chairStatus/Discussion: Parameter set notifications: Do we need active notification of changes in parameter set, or do we keep sending the same fields in the HL7 message with a flag indicating that the parameter is no longer available.
Decisions: It was agreed that it would be easier to keep sending the same data set, but with a flag indicating that a particular obervation became available/not availableActions
3 Item
- chairStatus/Discussion: John R. went over his flow diagrams representing the ADQ requirements. They need to be included in the ADQ formulation document.
Decisions
Actions
Next Meeting