September, 2005What IHE Delivers 1 Karen Witting IBM Cross-Community: Peer- to-Peer sharing of healthcare information

2 Outline Defining the Cross-Community vision XCPD XCA XDR

3 Timeline of ITI vision for Cross-Community 2006 – initial Cross-Community Vision  Why is XDS not enough?  2006 Whitepaper published  Community defined  Models of communication  Future IHE profiles 2007 – Cross-Community Access Profile (XCA)  Defines query & retrieve peer-to-peer model 2008 – updated Cross-Community Vision  Whitepaper refining and expanding vision from – Cross-Community Patient Discovery Profile (XCPD)  Defines transactions for discovery of patient locations and identification 2010 – Cross-Community use of XDR  Anecdotal use of XDR in peer-to-peer environments

4 Why extend XDS? XDS only addresses document sharing within an XDS Affinity Domain Cross-Community addresses the questions:  How to share documents between XDS Affinity Domains?  How to share documents with non-XDS Affinity Domains?

5 Cross Community Information Exchange White Paper Developed concept of “community” and exchange of health information across communities Released in August 2006 and revised October 2008 Available on under “Resources – Technical Frameworks” then select IT Infrastructurewww.ihe.net Defines two types of cross community information exchange: Hierarchical Lateral Defines a set of profiles which are useful in both types of community information exchanges. The first step in realizing the vision of this whitepaper is the Cross Community Access profile

6 What is Cross Community Community  Definition: A community is defined as a coupling of facilities/enterprises that have agreed to work together using a common set of policies for the purpose of sharing clinical information via an established mechanism.  XDS Affinity Domain is an example of a community. Community expands the scope to include sharing of clinical information by a mechanism OTHER than XDS. Cross Community  Transactions that support sharing of clinical information across Community boundaries.  Cross Community is a peer-to-peer environment where information is exchanged between gateways which each represent a community.  Typically a national or regional organizing body defines policies for the exchange.

Community Network B Document Registry Practice Clinic Hospitals Hospital Diag Test Other Practice Hospital Community Network C Document Registry Practice Clinic Hospitals Hierarchical Exchange From Cross Community Information Exchange White Paper IHE transactions (XCA and future)   Gateways query and retrieve records   National or Regional Networks not required to be IHE-based – could do the mapping to & from IHE Transactions in the Gateway Gateway National Network A Non-IHE National EHR Which community holds records for a patient ?

Community Network B Document Registry Practice Clinic Hospitals Hospital Diag Test Other Practice Hospital Community Network C Document Registry Practice Clinic Hospitals Lateral Exchange From Cross Community Information Exchange White Paper IHE transactions (XCA and future)   No shared resource to map patients to communities   Identification of communities done through attributes, or other configuration.   Identification of patient id through lateral transactions rather than hierarchical management Gateway National Network A Non-IHE National EHR Which communities have specific attributes CommunitySearchService

9 Common features of Lateral and Hierarchical models Require method for finding communities  Lateral – based on community attributes  Hierarchical – based on matching to patient Require transactions between Gateways  To resolve patient identifiers  To query by patient identifier  To retrieve documents  Etc.

10 Existing IHE profiles used in XC environments Cross Community Patient Discovery (XCPD)  Profiled in 2009  the means to locate communities which hold patient relevant health data and  the translation of patient identifiers across communities holding the same patient’s data. Cross Community Access (XCA)  Profiled in 2007  Query and retrieve of patient related clinical information Cross-Enterprise Document Reliable Interchange (XDR)  Existing profile applied to Cross-Community environment  Push of information Cross-Enterprise Media Interchange  Existing profile applied to Cross-Community environment  Push of information

11 XCPD Overview The Cross-Community Patient Discovery (XCPD) profile supports:  the means to locate communities which hold patient relevant health data and  the translation of patient identifiers across communities holding the same patient’s data. Use Cases  Same as XCA  Compliments XCA by supporting needed function

12 XCPD Actors and Transactions

13 XCPD Actors and Transactions Defined Initiating Gateway - initiates the new XCPD transactions, does not need to be grouped with XCA Initiating Gateway Responding Gateway – responds to the new XCPD transactions, does not need to be grouped with XCA Responding Gateway Cross Gateway Patient Discovery – discover mutually known patients. Patient Location Query – query for a list of communities which may have relevant health data about a particular patient.

14 XCPD Illustration of Use (Informative) Steps

15 XCPD Illustration of Use (Informative) Steps 11-13

16 Cross Gateway Patient Discovery Transaction Mutual discovery of patients - dual purposes:  Query requesting demographic match  Feed announcing known patient Result is patient identifier correlations, potentially in both initiating and responding side Different modes used in different environments:  Demographic Query only  Demographic Query and Feed  Shared/National Patient Identifier Query and Feed Includes a revoke message for remove correlations found through this transaction Supports both asynchronous and synchronous transport

17 Cross Gateway Patient Discovery Transaction Standards Based on HL7 V3 Patient Administration DSTU, Patient Topic  Patient Registry Query by Demographics  Patient Registry Find Candidates Response  Patient Nullify Design started with PDQ V3 Query (incomplete list of differences with PDQ V3):  asynchronous web services exchange  mutual discovery of patient identifier correlations  special error codes  requiring name and gender  supports MothersMaidenName and PrincipalCareProviderId  specification of homeCommunityId and Community patient id assigning authority.  Etc.

18 Patient Location Query Request for list of communities that may have healthcare data for a specified patient Request includes a single patient identifier Response includes a list of triples  homeCommunityId – identifies community which may have data for the patient  CorrespondingPatientId – identifies the patients identifier within homeCommunityId  RequestPatientId – same as request parameter Standards  Based on Appendix V IHE Web Services  Content defined by IHE schemas Chose not to use HL7 or ebXML because the simplicity of the request/response content did not warrant complex content

19 Cross Community Access (XCA) Scope Sharing of documents across communities Re-use of XDS.b transactions. Document Consumer consistency  Requirements of Document Consumer are the same as for local document query and retrieval Out of scope:  How to identify which communities to interact with  How to identify the patient id to use when interacting  XCPD supplies solutions to both of the above

20 XCA Transaction Diagram minimum required

21 XCA Transaction Diagram

22 XCA Transaction Diagram

23 XCA Transaction Diagram

24 Cross Community Access Actors and Transactions Initiating Gateway  On behalf of internal actors, initiates all transactions leaving the community  Receives Registry Stored Query and Retrieve Document Set from Document Consumer  Propagates transaction to local Document Registry and Repository, if appropriate  Propagates transaction to other communities by contacting their Responding Gateway and sending: Cross Gateway Query and Cross Gateway Retrieve Responding Gateway  Single contact point for all transactions coming in to the community.  Propagates incoming transactions to local actors New Transactions:  Cross Gateway Query: from Initiating Gateway to Receiving Gateway, mimics Registry Stored Query  Cross Gateway Retrieve: from Initiating Gateway to Receiving Gateway, mimics Retrieve Document Set Document Consumer  Supports Registry Stored query and Retrieve Document Set  New requirement: propagation of the homeCommunityId requirement Applies to XDS.a, XDS.b and XCA profiles

XDS Registry Initiating Gateway Document Consumer XCA Process Flow XDS Registry XDS Repository RSQ XDS Registry RSQ XGQ XDS Repository Community A Community B Community C Responding Gateway Responding Gateway XGQ RSQ RDS RSQ – Registry Stored Query XGQ – Cross Gateway Query RDS – Retrieve Document Set XGR – Cross Gateway Query RDS XGR RDS

26 homeCommunityId NEW: requirement for all Document Consumer implementers (XDS.a, XDS.b, XCA) SHALL propagate homeCommunityId value to subsequent Registry Stored Query (XDS.a & XDS.b) or Retrieve Document Set (XDS.b only) transactions. homeCommunityId corresponds to the ‘home’ attribute defined on the relevant ebRIM 3.0 elements. Example: homeCommunityId value is unique and opaque Used by Initiating Gateway to map to the originator of the data New optional parameter to stored queries which do not include a patient id. Optional parameter on the new Retrieve Document Set transaction

Processing of “home” (homeCommunityId) Initiating GW Responding GW Home ‘a’ Home ‘b’ Doc Consumer Home ‘a’ GW Address Home ‘a’ GW Address Home ‘b’ GW Address Home ‘a’ Home ‘b’ Query by patient id Query by uuid Home ‘a’ Home ‘b’ Retrieve GW Address Home GW Address

XDR & XDM What, if anything, should be said about XDR and XDM

29 More Information IHE Web site:  IHE official material  Technical Framework documents IHE Wiki site: wiki.ihe.net  IHE committee pages  Implementation Notes  Ongoing committee work IHE ITI technical committee mailing list

30