PCD ADQ 2011-04-14 Webex: Difference between revisions
Created page with " {{TOCright}} ''Patient Care Device Domain'' == Meeting Purpose == 4th ADQ meeting (Asynchronous Data Query) == WebEx Information == Topic: '''Asynchronous Data Query''' D..." |
mNo edit summary |
||
| (9 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:PCD Meeting Archive 2011]] | |||
{{TOCright}} | {{TOCright}} | ||
| Line 6: | Line 7: | ||
== Meeting Purpose == | == Meeting Purpose == | ||
4th ADQ meeting (Asynchronous Data Query) | 4th ADQ meeting (Asynchronous Data Query) | ||
Refer to [[:Category:PCD ADQ]] | |||
== WebEx Information == | == WebEx Information == | ||
| Line 18: | Line 21: | ||
== Proposed Agenda == | == Proposed Agenda == | ||
''- ADQ Transaction Requirements'' | |||
|''- Accurate Time'' | |||
|''- John R. Diagram'' | |||
|''- QPD use for Queries'' | |||
== Action Items from Previous Meetings == | == Action Items from Previous Meetings == | ||
| Line 27: | Line 33: | ||
== Participants == | == Participants == | ||
:'''Chair:''' Khalil Maalouf (Nuvon) | :'''Chair:''' Khalil Maalouf (Nuvon) | ||
Ken Fuchs (Mindray), John Rhoads (Philips), Paul Schluter (GE Healthcare), Nishan Wijesinghe (Parigan) | |||
== Discussion == | == Discussion == | ||
| Line 40: | Line 46: | ||
| align="center" | 1 | | align="center" | 1 | ||
| '''Introductions & Agenda Review''' <br>- Chair | | '''Introductions & Agenda Review''' <br>- Chair | ||
| | | Time 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. | ||
| Line 47: | Line 54: | ||
| '''Item''' <br>- chair | | '''Item''' <br>- chair | ||
| '''Status/Discussion:''' | | '''Status/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''' | '''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 available | |||
'''Actions''' | '''Actions''' | ||
| Line 59: | Line 67: | ||
| '''Status/Discussion:''' | | '''Status/Discussion:''' | ||
John R. went over his flow diagrams representing the ADQ requirements. They need to be included in the ADQ formulation document. | |||
'''Decisions''' | '''Decisions''' | ||
| Line 68: | Line 76: | ||
=== Next Meeting === | === Next Meeting === | ||
''[[PCD ADQ 2011-04- Webex]]'' | ''[[PCD ADQ 2011-04-21 Webex]]'' | ||
<!--''<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]] | ||
Latest revision as of 17:17, 20 July 2012
Patient Care Device Domain
Meeting Purpose
4th ADQ meeting (Asynchronous Data Query)
Refer to Category:PCD ADQ
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