PCD ADQ 2011-03-24 Webex: Difference between revisions
Jump to navigation
Jump to search
initial |
m remove PCD Meeting category |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Patient Care Device | PCD Home]] | |||
[[Category:PCD ADQ]] | |||
{{TOCright}} | {{TOCright}} | ||
| Line 5: | Line 7: | ||
== Meeting Purpose == | == Meeting Purpose == | ||
Intial meeting for development of Asynchronous Data Query profile | Intial meeting for development of Asynchronous Data Query profile. | ||
Refer to [[:Category:PCD ADQ]] | |||
== WebEx Information == | == WebEx Information == | ||
| Line 80: | Line 84: | ||
''[[PCD ADQ 2011-03-31 Webex]]'' | ''[[PCD ADQ 2011-03-31 Webex]]'' | ||
[[Category:PCD Meeting Archive 2011]] | |||
[[Category:PCD Meeting]] | |||
Latest revision as of 17:07, 20 July 2012
Patient Care Device Domain
Meeting Purpose
Intial meeting for development of Asynchronous Data Query profile.
Refer to Category:PCD ADQ
WebEx Information
Topic: Asynchronous Data Query
Date: Thursday, 24 March 2011
Time: 2:00 pm Eastern
Duration: 60 Minutes
Proposed Agenda
- Initial Plan of Work for ADG Group
Action Items from Previous Meetings
See ADQ Action Items
Participants
- Chair: Kahlil Maloof (Nuvon)
- John Zaleski (Nuvon), Ken Fuchs (Mindray), John Rhoads (Philips Healthcare).
Discussion
Item Topic Discussion 1 Introductions & Agenda Review
- Chair1 Review of Detailed Profile Proposal
- ZaleskiStatus/Discussion: Discussed example CABG use case: Implications for scope, kinds of queries needed
1 Discussion of general scope of profile
- chairStatus/Discussion: - Profile actors are systems acting on behalf of clinical actors. What kinds of systems will use the ADQ interfaces?
- We can't dictate storage capabilities of systems, so "discovery" queries of what data are available will be needed
- Will we reuse / extend PCD-02 Subscribe to Patient Data?
1 Outlining of Tasks
- chairAction(s): - Investigate strengths and weaknesses of approach used in PCD-01 (and other HL7 query mechanisms)
- Consider additional use cases and use contexts to determine what technical capabilities will be required