1. Bill Majurski National Institute of Standards and Technology (NIST)‏ IT Infrastructure: Profiles for Health Information Exchange

2. Support Profiles “Infrastructure for XDS”

3. XDS Support Collection of profiles that support XDS Globally Consistent Time (CT profile)‏ Patient Management (PIX/PDQ profiles)‏ Node Authentication (ATNA profile)‏ Audit Logging (ATNA profile)‏ Authorization Assertions (XUA profile)‏ Notification of Availability (NAV)‏ Digital Signature (DSG)‏

4. Support Profiles Consistent Time (CT)‏

5. Consistent Time Profile XDS describes a distributed system - time synchronization is critical Network Time Protocol ( NTP) version 3 (RFC 1305) for time synchronization Actor must support manual configuration Required accuracy: 1 second Optionally Secure NTP may be used

6. Support Profiles Patient Identifier Cross-referencing (PIX)‏

7. Patient Identifier Cross-referencing (PIX)‏ Allow all enterprise participants to register the identifiers they use for patients in their domain Participants retain control over their own domain’s patient index(es)‏ Support domain systems’ queries for other systems’ identifiers for their patients Optionally, notify domain systems when other systems update identifiers for their patients

8. Patient Identifier Cross-referencing (PIX)‏ Maintain all systems’ identifiers for a patient in a single location Use any algorithms (encapsulated) to find matching patients across disparate identifier domains Lower cost for synchronizing data across systems –No need to force identifier and format changes onto existing systems

9. Patient Identity Feed [ITI-8] ­ PIX Query [ITI-9] ­ PIX Update Notification [ITI-10] Patient Identity Source Patient Identity Cross reference Manager Patient Identity Consumer PIX Transaction Diagram

10. XDS: PIX integration Patient Identity Source Document Registry Document Repository Document Source Document Consumer Patient Identity Feed Query Documents Retrieve Document Provide and Register Document Set Register Document Set PIX XREF Manager PIX Query

11. Patient Identification Domain A Other IHE Actor Identity Patient Cross References Patient Identity Consumer Patient Identification Domain C Patient Identity Feed Patient Identity Source Patient Identity Cross-reference Manager Patient Identification Cross-reference Domain Patient Identity Feed & Patient Identity References Internal Domain transactions Other IHE Actor Patient Identity Cross References Patient Identity Consumer Patient Identification DomainB Patient Identity Feed Patient Identity Source Internal Domain transactions PIX: Process Flow Showing ID Domains & Transactions

12. Patient Identification Domain A Patient Identification Domain C Id=X456 Id=Y921 Id=D456 Id=DF45 Patient Identification Cross-reference Domain Patient Identification Domain B Id=123 Id=235 Id=3TY Id=2RT Patient Identity Cross-reference Manager B:X456 =C:2RT A:123 =B:Y921 =C:3TY B:D456 A:235 =B:DF45 A:678 Patient Identity Consumer B:X456 C: 2RT Patient ID Cross-Refs B:X456 C: ? Patient Identifier Cross-referencing (PIX)‏

13. PIX Actors Patient Identity Source –Definition Assigns patient identities within its own domain Notifies Patient Identifier Cross-reference Manager of all events related to patient identification (creation, merge, etc.)‏ Example: Registration (ADT) Actor in IHE Radiology Scheduled Workflow (SWF) Profile –Transaction Supported - Required Patient Identity Feed [ITI-8] (as sender)‏

14. PIX Actors Patient Identifier Cross-reference Consumer –Definition Requires information about patient identifiers in other domains Requests patient identifier information from Patient Identifier Cross-reference Manager –Transaction Supported - Required PIX Query [ITI-9] (as sender)‏ –Transaction Supported - Optional PIX Update Notification [ITI-10] (as receiver)‏

15. PIX Actors Patient Identifier Cross-reference Manager –Definition Serves a well-defined set of Patient Identifier Domains Receives patient identifier information from Patient Identity Source Actors Manages cross-referencing of identifiers across domains –Transactions Supported - Required Patient Identity Feed [ITI-8] (as receiver)‏ PIX Query [ITI-9] (as receiver)‏ PIX Update Notification [ITI-10] (as sender)‏

16. PIX: Standard Used HL7 Version 2.5 –ADT Registration and Update Trigger Events A01: inpatient admission A04: outpatient registration A05: pre-admission A08: patient update A40: merge patient –Queries for Corresponding Identifiers (ADT^Q23/K23)‏ –Notification of Identifiers Lists Updates (ADT^A31)‏

17. PIX Summary Patient ID management Translation of Patient IDs across Patient ID domains Patient ID feed Query & Notification of Cross Referencing

18. PIX as seen from XDS NOT a requirement XDS Affinity Domain allows only a single Assigning Authority for Patient IDs Implication: do your complex Patient ID management outside of the XDS environment To 'do' XDS, translate your Patient IDs to the Patient ID Domain (Assigning Authority) defined for the Affinity Domain.

19. Patient ID Responsibilities Who must manage? Document Source Document Consumer (known as Edge Systems)‏ Registry and Repository only see Assigning Authority defined for Affinity Domain (known as Infrastructure Systems)‏

20. Edge Systems Must translate local Patient ID to Affinity Domain Patient ID Use request to PIX Cross-Reference Manager –Translate PID X in local domain –To domain Affinity Domain –Return is PID in Affinity Domain

21. Edge Systems Management of healthcare information always starts with a Patient Identified by name and demographics PDQ query translates name/demographics to pick-list of matching Patients Produces Patient ID in a domain

22. Registry Registry has two uses for Patient ID What are valid Patient IDs –Consistency check against submitted documents Handle request to Merge two Patient IDs PIX profile supplies both of these to Registry

23. Discovering Patient IDs Discover Patient ID from Patient Demographics Patient Demographics Query profile Not required by XDS

24. Support Profiles Patient Demographic Query (PDQ)‏

25. Patient Demographics Query (PDQ)‏ Allow quick retrieval of a patient list including common patient names, identifiers, contacts, and visit information Enable selection of correct patient when full identification data may not be available Limits access to only a subset of demographic and visit information

26. Patient Demographics Query (PDQ)‏ Enables access on demand to diverse systems and devices –Participants that do not need continual synchronization of patient registration information –Devices that cannot participate in monitoring of ADT feeds, e.g.: Small-footprint devices Low-memory devices

27. Patient Demographics Query (PDQ)‏ Allow search on full or partial data Retrieve information from any domain to which the client has query access Allows use of matching algorithm (e.g., soundex) to find near matches

28. Patient Demographics Supplier Patient Demographics Consumer Patient Demographics Query Patient Demographics and Visit Query A departmental system that is connected on demand to the registration system. Diverse systems including bedside monitors, physician office systems, lab applications, mobile blood bank registries; might be any system at the point of contact. PDQ Transaction Diagram

29. PDQ Standards Used Employs HL7 Conformance Based Queries –Defined in HL7 Version 2.5, Chapter 5 –Profiles Query by Parameter (QBP^Q22) with Segment Pattern Response (RSP^K22)‏

30. PDQ Actors Patient Demographics Consumer Definition –Requestor of patient demographic (and perhaps current visit) information –Allows user to associate information with a patient at the point of care Transaction Supported – Required –Patient Demographics Query (as sender)‏ Transaction Supported – Optional –Patient Demographics and Visit Query (as sender)‏

31. PDQ Actors Patient Demographics Supplier Definition –Repository of patient information that can be searched on demographic or visit-related fields Transaction Supported – Required –Patient Demographics Query (as receiver)‏ Transaction Supported – Optional –Patient Demographics and Visit Query (as receiver)‏

32. PDQ Operation Patient Demographics Query User enters full or partial demographic information (e.g., partial last name and first initial) for patients of interest Application associated with Patient Demographics Consumer sends HL7 QBP^Q22 to Patient Demographics Supplier to find matching information –May request specific domains from which to return identifier information

33. XDS: PIX/PDQ integration Patient Identity Source Document Registry Document Repository Document Source Document Consumer Patient Identity Feed Query Documents Retrieve Document Provide and Register Document Set Register Document Set Patient Demographics Supplier PIX XREF Manager PIX Query Patient Demographics Query

34. Support Profiles Audit Trail and Node Authentication (ATNA)‏

35. Content Profiles

36. Definition XDS defines a mechanism for sharing ‘Documents’ ‘Document’ defined as a byte stream with a size, hash, and mime type Content Profiles are standardized document formats defined within IHE

37. Domains The following IHE Domains have defined XDS Content Profiles IT Infrastructure (ITI)‏ Radiology Laboratory Patient Care Coordination (PCC)‏

38. IT Infrastructure XDS-SD Scanned document Stored in PDF format Wrapped in CDA/R2 Basic Patient Privacy Consents (BPPC)‏ More than a Content Profile Includes privacy processing rules enforced by the Document Registry in queries

39. Radiology XDS-I (XDS for Imaging)‏ Normal XDS actors plus –Image Document Source (extension to XDS Document Source)‏ –Image Document Consumer (extension to XDS Document Consumer)‏ –Image Document Source stores Radiology images locally in Image Archive –Image Manifest Document stored in XDS Repository –Manifest (also called Key Object Select - KOS) references specific DICOM content in Image Archive

40. Retrieving Radiology Content Query Registry, receive metadata –Metadata describes Image Manifests Choose and retrieve Image Manifest(s) from Document Repository Decode Manifest and retrieve Image content from Image Archive

41. Laboratory Lab Report

42. Patient Care Coordination Many, many Clinically oriented Content Profiles

43. XDR / XDM Point-to-point transmission of documents

44. XDM Cross-Enterprise Document Media Interchange

45. XDM Big Picture Documents and XDS Metadata shared via media

46. XDM Cross-Enterprise Document Media Interchange (XDM)‏ Options USB CD-R ZIP over email

47. XDM Imposes File/Directory structure on the media Transport Multiple XDS Submission Sets Each Submission Set has –Metadata describing documents –Documents Protocol structure of XDS imposed on file/directory organization

48. XDM Uses Release of documents to patient Manual (in pocket or email) transfer of documents Local display after receipt –Index.htm file required to support display These are manual operations!

49. XDS Family of Profiles XDS - the base XDM - exchange of XDS metadata and documents on Media XDR - exhange of XDS metadata and documents over reliable protocols XD* - refers to XDS, XDM, XDR together

50. XDR Cross-Enterprise Document Reliable Interchange

51. XDR Cross-Enterprise Document Reliable Interchange (XDR)‏ Point-to-point transmission of XDS content over reliable communications Uses Provide and Register transaction (from XDS)‏ A new profile but really just documents how to use Provide and Register to perform point-to-point transfers.

52. XDR Reliable asynchronous point-to-point transfer of XDS metadata and documents Reliable transfer comes from ebMS Messaging Services Specification v2.0

53. XDR Single Submission Set per transfer –More like XDS than XDM Optionally identify intended recipients

54. XDS + XDR + XDM How do XDR and XDM work with XDS? XDS Query/Retrieve can feed XDR/XDM transmission Point-to-point transfer via XDR/XDM can feed XDS submission

55. XCA Cross-Community Access

56. XCA Big Picture XDS defines the operation of an Affinity Domain (single Registry +...)‏ XCA defines interchange between multiple communities. An Affinity Domain is one type of community.

57. XCA Features of an XCA community Accept Query and Retrieve transactions from other communities –Allows sharing of local documents A community could be an Affinity Domain...or not.

58. XCA A few details Uses Stored Query and XDS.b Retrieve to access foreign community content A query can be broadcast to multiple communities (document discovery)‏ Introduces homeCommunityId to identify/address communities Uses ebRIM/ebRS 3.0 (like XDS.b)‏

59. XCA Tough problems still to be solved Patient ID management –How to manage translation between communities –PIX/PDQ provide some of the necessary features Configuration Management –How to translate/manage coding

60. Community Network B Document Registry Practice Clinic Hospitals Hospital Diag Test Other Practice Hospital Community Network C Document Registry Practice Clinic Hospitals IHE transactions (future) Cross Community Gateway Cross Community Gateway Cross Community Gateway National Network A Non-IHE National EHR Which community holds records for a patient ? XDS Cross Community…Access Cross-Community Gateways query and retrieve records (2007 & future)‏ National or Regional Networks not required to be IHE-based Mapping to & from IHE Transactions performed by X-Community Gateways

61. Regional Network B Acute Care (Inpatient)‏ PCPs and Clinics (Ambulatory)‏ Long Term Care Other Specialized Care or Diagnostics Services Document Registry Document Repository Longitudinal Record as used across-encounters Regional Network C Acute Care (Inpatient)‏ PCPs and Clinics (Ambulatory)‏ Long Term Care Other Specialized Care or Diagnostics Services Document Registry Document Repository Longitudinal Record as used across-encounters Regional Network A Acute Care (Inpatient)‏ PCPs and Clinics (Ambulatory)‏ Long Term Care Other Specialized Care or Diagnostics Services Document Registry Document Repository Longitudinal Record as used across-encounters Cross Community Gateway Which community holds records for a patient ? Cross Community Gateway Gateway Community Locator service IHE Transactions (future)‏ Cross-Community…Location Each region notifies Community Location Service when new patient is registered or first data is stored. Cross Community Gateways query Community Locator Service (future)‏ Cross-Community Gateways query and retrieve records (2007 & future)‏

62. Other Cross-community Issues… Management of Patient IDs –Normally managed within Affinity Domain Clinical Coding –Normally managed within Affinity Domain

63. Cross Community Access: Value Proposition Sharing of documents beyond the XDS Affinity Domain (community) boundary. Part of a larger vision for regional and national sharing – 2006 whitepaper on Cross Community Information Exchange –Cross Community Access (2007)‏ –Cross Community Location (2008)‏ Scoped to document sharing between XDS Affinity Domains. Future goal to define sharing with other types of communities.

64. Cross Community Access: Technical Solution Cross Community Gateway –A new actor which supports all inter-community communications. Encapsulates in one actor all activities required to communicate outside the community. –Every community would have one cross community gateway which would interact with actors within the community and remote cross community gateways. Cross Community Consumer –Initiator of a request for information beyond the community. Technical Issues: –Need for asynchronous transactions in the cross community environment –Interaction with existing XDS actors –Reliable identification of the patient

65. Community Network B Document Registry Practice Clinic Hospitals Hospital Diag Test Other Practice Hospital Community Network C Document Registry Practice Clinic Hospitals 18 edge systems 4 infrastructure systems 5 edge systems 4 infrastructure systems 13 edge systems 3 infrastructure systems 3 infrastructure Systems Community Network A Document Registry Practice Clinic Hospitals Diag Test HIMSS Interoperability Showcase The largest multi-vendor prototype ever built !

66. XDS Transaction Diagram Patient Identity Source Document Registry Document Repository Document Source Document Consumer Patient Identity Feed Query Documents Retrieve Document Provide and Register Document Set Register Document Set

67. Patient Information Options PIX Feed to Document Source/Consumer PDQ queries from Document Source/Consumer Use of Patient ID Cross-Referencing by Document Source/Consumer These are all optional within XDS!

68. Patient ID Merge

69. Merge Issues Patient Management is an imperfect art Documents get assigned to the wrong Patient ID Multiple Patient IDs identify single Patient Single Patient ID identifies content for multiple Patients

70. Merge Merge Supplement starts to offer tools to manage these issues in XDS Relies on PIX notification of Patient ID related problem Current scope is to merge two Patient IDs that are found to represent same Patient Early work... still evolving