1. Cross Community (XC) Profiles November 2006 ITI Planning committee meeting Karen Witting

2. Next step of Cross Community White Paper White Paper recommends two profiles be developed in 2007: –Cross Community Location Service –Cross Community Access

3. Cross Community (XC) Location Service Service to save, update, remove, query patient record references –Record references might me: To documents (internal and external) To XDS registry (internal and external) To XC Bridge definition TBD To Fine grained data repository definition TBD i.e. MUST BE EXTENSIBLE –Record references indexed by patient demographics Patient ids could be one element of demographics but service must talk using demographics as a common patient id cannot be assumed.

4. Draft Transaction Diagram XC Location Consumer XC Location Service (PIX+/RLS/RLUS) Add Update Merge Remove Query XC Location Feed

5. Cross Community Access Two purposes: –Encapsulate cross community interactions in one actor – Cross Community Bridge (XC Bridge) –Define a query which returns data from external communities – Cross Community Query (XC Query) The XC query is the first instance of an interaction that the XC Bridge mediates

6. Meta-community XDS community C XDS community A XDS community B XDS Registry XC Bridge XC Locator Service or Any other service or configuration XDS Registry XC Bridge XDS Repository XC Consumer XC Bridge Use of the Cross Community Access profile in a Meta-community (1) XC Query (3) XC Query (2) internal (4) XC Query Response XDS Repository (5) XC Retrieve XDS Registry XDS Repository (6) XC Retrieve (3) XC Query (3) (5) Retrieve (6) XC Retrieve

7. Draft Transaction Diagram XC Bridge XC Consumer XC Query XC Query (between XC Bridge actors) XC Retrieve (between XC Bridge actors) XC Retrieve