ITI Tech 2006 2007 Meetings

Meeting December 5-6, 2006

Agenda

1. Review New Proposals from Planning Committee
   • Cross Community location service (Karen W.) (Profile)
   • XUA (John M.) (Profile)
   • MTOM (Vassil/Roberto) (Profile)
   • Non-Patient Document Sharing (???) (Profile)
   • Web Services specialized bindings (Vassil) (Appendix(s))
     • PIX/PDQ V3
     • EMR Query
   • Configuration Management (Rob) (White Paper)
   • Aggregate Data (Charles, Floyd) (White Paper/Profile???)
2. Carry-over from last season
   • RFD (George) - PCC work dependent on new ITI Profile Proposal 'Investigator Identity and Authentication' which did not get forwarded to tech from planning
   • PIX/PDQ V3 (???)
     • Web service bindings (see above)
     • Other????
3. Cardiology/Patient Care Devices Presentation
   • Tue 1-2
   • IHE Cardiology and IHE PCD Profiles presentation - requesting ITI vendor implementations
   • Feedback on the IDCO Profile (use HLv2 or XML payload?)
4. Discuss use of new IHE wiki
5. Discuss CPs

Schedule

Tues 930 Organize/Breakfast/wiki discussion 1000 XUA (John M) 1100 Non-Patient Doc Sharing (??) 1200 Lunch 100 Cardiology/Patient Care Devices (?) 200 Aggregate Data (Charles) 300 XC Location Service (Karen) 400 Web Services Bindings (Vassil) 430 CP Discussion 530 Adjourn

Wed 830 Breakfast 900 RFD (George) 930 PIX/PDQ V3 (????) 1000 MTOM (Vassil/Roberto) 1100 Config Mgmt White Paper (Rob) 1200 Lunch 100 Overflow 200 Review Plans/Assignments 230 Adjourn

Change Proposal TCON November 15, 2006

Minutes

Attendees Rob Horn - AGFA Karen Witting - IBM Bill Majurski – NIST Glen Deen – IBM Yongjian Bao – GE Josh – Misys Mark Sinke – ForeCare Vassil Peytchev - Epic John Moerke – GE Laurie Williams – IBM George Cole - Allscripts

pixpdq_170_09

item #4 became new CP 204

1. 5 no change - added example
2. 6 fixed

ask for response from Isabelle

xds_164_05- atna and xds - rob, mark

Emmanuel offered the following:

1) We effectively decided not to create an "import" event on a consumer side for a retrieve document, because the nature of the protocol (HTTP Get) making probable that the retrieve itself is directly performed by the Web browser. When we evolve this protocol (WS...) it must be reconsidered. 2) The name of the Studies / DICOM Studies is not consistent for Import/Export events. We have definitly to tell to people what is the corresponding "study" for the XDS/XDR/XDM profiles. I would recommend that it is the XDSSubmissionSet (referenced by its uniqueId) for XDS Register, XDS/XDR Provide&Register and XDM Distribute, and the XDSDocumentEntry for the XDS Retrieve. 3) Similarly, we have to precise the ParticipantObjectID in the Query event to be set to the UUID of the type of XDS object queried (document, submission set or folder) 4) There are some typos in the CP. For example you did not end the Query section, or errors in parentheses.

Long discussion – Mark and Rob to merge their independent writings.

xds_136_02 - John M - No need to discuss

xds_144 - long URI - need status on ballot #3 from LaVerne - not present on call

Action items

CP 164 includes codes that need to be registered. Who does this?

Mark and Rob submitted updated at the same time. They are working to reconcile. Schedule next review.

Many questions have floated about this season regarding audit. Suggest creating an Implementers Guide on generating audit messages.

Ask for review and comments from Isabelle on CP 170

Long URI CP in Ballot #3 - Get in touch with LaVerne

Next call noon (central) on Dec 19