PCD ADQ 2011-04-14 Webex: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Jrhoads (talk | contribs)
m cat
Efurst (talk | contribs)
mNo edit summary
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:PCD Meeting]]
[[Category:PCD ADQ]]


[[Category:PCD Meeting Archive 2011]]
{{TOCright}}
{{TOCright}}


Line 8: 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 ==  

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
- 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.


2 Item
- chair
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: 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

3 Item
- chair
Status/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

PCD ADQ 2011-04-21 Webex



PCD Home