PCD ADQ 2011-06-02 Webex: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
← Older edit
Khalil M (talk | contribs)
46 edits
Efurst (talk | contribs)
editor
8,826 edits
mNo edit summary
 
(8 intermediate revisions by 3 users not shown)
Line 1: Line 1:
[[Category:PCD Meeting Archive 2011]]
{{TOCright}}
{{TOCright}}


Line 25: Line 27:
== Participants ==
== Participants ==
:'''Chair:''' Khalil Maalouf (Nuvon)
:'''Chair:''' Khalil Maalouf (Nuvon)
Al Engleburt (Protolink)
Al Engleburt(Protolink), John Rhoads(Philips), Ken Fuchs(Mindray), Nishan Wijesinghe(Parigan), John Zaleski(Nuvon), Khalil Maalouf(Nuvon)(Host)


== Discussion ==
== Discussion ==
Line 38: Line 40:
| align="center" | 1
| align="center" | 1
| '''Introductions & Agenda Review''' <br>- Chair  
| '''Introductions & Agenda Review''' <br>- Chair  
| - The name ADQ was discussed along with Ken’s suggested name MDDQ. A name change is a good idea .. we can also consider something that reflects a Patient Centric framework.
| - Reviewed last meeting topics and Discusion
- Al provided an explanation for the OBX.3 in Class Device / Containment Tree under PCD02. So the Open question will be removed and Device Class will refer to OBX.3 (containment tree) throughout the document.
- We are still leaning towards a new messaging system, (PCD-xx TBD) different than PCD02 to satisfy the requirements of ADQ.




|-
| align="center" | 2
| '''Item''' <br>- Chair
| '''Status/Discussion:'''
- Discussed Patient Identification in QPD with multiple parameters.
'''Decisions'''
- Agreed that according to the HL7 CH-05 queries, the default interpretation of multiple QPD parameters is that they are “anded” and therefore all patient identification parameters will be interpreted by the receiving system as belonging to the same patient.
'''Actions'''
|




|-
|-
| align="center" | 3
| align="center" | 3
| '''Item''' <br>- chair
| '''Item''' <br>- Chair


| '''Status/Discussion:'''
| '''Status/Discussion:'''
- Discussed a scheme for Requester and Responder registration and parameter notification.
'''Decisions'''
- An address table of potential Responders configured into the ADQ Requester application, so the requester has apriori information of where to send its queries.
- The Requester can send any allowed query under the profile to any Responder in its table. 
- The Responder will reply with a message containing all the requested parameters along with a flag for each parameter indicating if:
a.  The parameter is supported by the Responder
b. If supported, then if it is available for the patient and time frame specified by the query
c. If supported and available, then report on the value




'''Decisions'''


'''Actions'''
'''Actions'''
Line 60: Line 81:
=== Next Meeting ===
=== Next Meeting ===


 
[[PCD ADQ 2011-07-14 Webex]]




Line 67: Line 88:


[[Patient Care Device | PCD Home]]
[[Patient Care Device | PCD Home]]
[[Category:PCD Meeting]]

Latest revision as of 17:20, 20 July 2012


Patient Care Device Domain

Meeting Purpose

8th ADQ meeting (Asynchronous Data Query)

WebEx Information

Topic: Asynchronous Data Query

Date: Thursday, 02 June 2011

Time: 2:00 pm Eastern

Duration: 60 Minutes

Proposed Agenda

- Resolution to questions raised during the F2F meeting in Boca Raton

Action Items from Previous Meetings

See ADQ Action Items


Participants

Chair: Khalil Maalouf (Nuvon)

Al Engleburt(Protolink), John Rhoads(Philips), Ken Fuchs(Mindray), Nishan Wijesinghe(Parigan), John Zaleski(Nuvon), Khalil Maalouf(Nuvon)(Host)

Discussion

Item Topic Discussion
1 Introductions & Agenda Review
- Chair 		- Reviewed last meeting topics and Discusion


2 Item
- Chair 		Status/Discussion:

- Discussed Patient Identification in QPD with multiple parameters.

Decisions - Agreed that according to the HL7 CH-05 queries, the default interpretation of multiple QPD parameters is that they are “anded” and therefore all patient identification parameters will be interpreted by the receiving system as belonging to the same patient.


Actions


3 Item
- Chair 		Status/Discussion:

- Discussed a scheme for Requester and Responder registration and parameter notification.

Decisions - An address table of potential Responders configured into the ADQ Requester application, so the requester has apriori information of where to send its queries. - The Requester can send any allowed query under the profile to any Responder in its table. - The Responder will reply with a message containing all the requested parameters along with a flag for each parameter indicating if: a. The parameter is supported by the Responder b. If supported, then if it is available for the patient and time frame specified by the query c. If supported and available, then report on the value


Actions


Next Meeting

PCD ADQ 2011-07-14 Webex



PCD Home

Retrieved from "http://wiki.ihe.net/index.php?title=PCD_ADQ_2011-06-02_Webex&oldid=61769"