publication and discovery xds and dsub n.
Skip this Video
Loading SlideShow in 5 Seconds..
Publication and Discovery XDS and DSUB PowerPoint Presentation
Download Presentation
Publication and Discovery XDS and DSUB

Publication and Discovery XDS and DSUB

151 Vues Download Presentation
Télécharger la présentation

Publication and Discovery XDS and DSUB

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. Publication and DiscoveryXDS and DSUB IHE IT Infrastructure Webinar Series

  2. Cross-Enterprise Document Sharing XDS

  3. What is XDS ? The Cross-Enterprise Document Sharing (XDS) IHE Integration Profile facilitates the registration, distributionand accessacross health enterprises of patient electronic health records It provides a standards-based specification for managing the sharing of documents between any healthcare enterprise Currently only one XDS profile, based on Web Services - XDS.b (original XDS.a is now deprecated)

  4. XDS Affinity Domains Group of healthcare enterprises that have agreed to work together using a common set of policies and standards-based infrastructures for sharing patient clinical documents, using XDS: • Regional community of care • Nationwide EHR • Specialized or disease-oriented (cardio, diabetes, oncology) • Government-sponsored or federation of enterprises • Insurance provider supported communities XDS profile is designed to accommodate a wide range of policies on: • Patient identification and consent • Controlling access to information • Format, content, structure, and representation of clinical information

  5. Some Common Scenarios • Patient Care Summary (e.g. within a region) • Publishing of Care Summaries by providers • Access to patient’s Care Summary in an emergency • eReferral between primary and secondary care providers • Sharing of radiology reports and images between facilities • Sharing of laboratory reports by clinical laboratories with ordering physicians and other care providers • ePharmacybetween community pharmacy and ambulatory physicians

  6. Main Systemsand Responsibilities • A document Repositoryis responsible for storing documents in a transparent, secure, reliable and persistent manner and responding to document retrieval requests. • A document Registryis responsible for storing information or metadata about those documents so that the documents of interest for the care of a patient may be easily found, selected and retrieved irrespective of the repository where they are actually stored. • Any IT system (e.g. point of care) may act as a Document Sources or Document Consumers submitting documents for registration, or querying/retrieving relevant documents. Notes: • Analogous to a library (book repository) and catalog/index • The Registry does not have access to the documents – an important separation from security and privacy perspective • Multiple Repositories can be linked to one Registry

  7. XDS Flow and Interactions Registry • XDS Document (Metadata): • Class • Patient Id • Author • Facility • Date of Service • … Consumer 3. Consumers search for documents with specific information 2. Repository registers the documents metadata and pointer with the Registry Source of Documents Repository 4. Consumers retrieve selected documents from Repository (-ies) 1. Sources post document packages to the Repository

  8. Cross-Enterprise Document Sharing ProfileActors and Transactions XDS Technical Overview

  9. XDS.b Formal Diagram Patient Identity Source Patient Identity Feed [ITI-8] Patient Identity Feed HL7v3 [ITI-44] Registry Stored Query [ITI-18] Document Registry Document Consumer Register Document Set-b [ITI-42] Integrated Document Source/Repository Retrieve Document Set [ITI-43] Document Source Document Repository Provide&Register Document Set-b [ITI-41]

  10. XDS.b Actors • Document Source – producer and publisher of documents, responsible for sending documents and their metadata to a Document Repository actor • Document Repositoryis responsible for both the persistent storage of these documents as well as for their registration with the appropriate Document Registry • Document Registry maintains metadata about each registered document and a link to the Document in the Repository where it is stored. Responds to queries from Document Consumer actors about documents meeting specific criteria. • Document Consumer queries a Document Registry for documents meeting certain criteria, and retrieves selected documents from one or more Document Repository actors • Patient Identity Source provides unique identifier for each patient and maintaining a collection of identity traits. This facilitates the validation of patient identifiers by the Registry Actor in its interactions with other actors • Integrated Document Source/Repository combines the functionality of the Document Source and Document Repository actors into a single actor that does not expose the Provide and Register Document Set transaction

  11. XDS.b Transactions (1) • Provide and Register Document Set – For each document in the submitted set, the Document Source Actor provides both the documents as an opaque octet stream and the corresponding metadata to the Document Repository. The Document Repository is responsible to persistently store these documents, and to register them in the Document Registry using the Register Documents transaction. • Register Document Set allows a Document Repository Actor to register one or more documents with a Document Registry, by supplying metadata about each document to be registered. This document metadata will be used to create an XDS Document Entry in the registry.

  12. XDS.b Transactions (2) • Patient Identity Feed conveys the patient identifier and corroborating demographic data, in order to populate the Document Registry with patient identifiers that have been registered for the XDS Affinity Domains. (At least one of the options [ITI-8] or [ITI-44] should be supported.) • Registry Stored Query is issued by the Document Consumer Actor to a Document Registry. It will return registry metadata containing a list of document entries found to meet the specified criteria including the locations and identifier of each corresponding document in one or more Document Repositories. • Retrieve Document Set – initiated by a Document Consumer. The Document Repository shall return the document set that was specified by the Document Consumer.

  13. XDS Document Content Types XDS profile is content agnostic – it can be used with a variety of document types, e.g.: • XDS-SD: Scanned document, plain text or PDF/A, in HL7 CDA R2 format • XDS-MS: Medical summary in HL7 CDA format • XDS-I: Radiology report in plain text of PDF format, or reference to a collection of DICOM SOP Instances in a manifest document in the DICOM Key Object Selection format

  14. XDS.b – Actors and Options

  15. Security and Privacy Considerations • All actors be grouped with a ATNA Secure Node Actor resulting in each node (systems supporting XDS actors)of the XDS Affinity Domain should have audit and security mechanisms in place • Transactions used between different secure nodes (systems supporting XDS actors) shall use the ATNA Encryption Option • Each XDS Transaction will result in audit event records sent to an ATNA audit Repository Actor

  16. XDS Workflow Health Information Exchange Network Patient Identity XRef Mgr Patient Demographics Supplier A87631 A87631 14355 14355 M8354673993 M8354673993 L-716 L-716 Time server XDS Affinity Domain PIX or PDQ Query PIX or PDQ Query PMS ED Application Physician Office Document Registry Document Repository PACS Document Repository EHR System Provide & Register Query Document (using Patient ID) Register Document (using Patient ID) PACS Retrieve Document Maintain Time Record Audit Event Lab Info. System Maintain Time Teaching Hospital Maintain Time Community Clinic Audit record repository CT ATNA Record Audit Event

  17. Relevant Standards Infrastructure: use of Web Services Standards: • WS-* Specifications • WS-I Profiles • ITI TF-2x: Appendix V Document content • HL7 CDA • CEN ENV 13606 • ASTM 4400 CCR • DICOM

  18. Point-to-point Deployment Models 1 - Unknown partners, patient ID out-of-band, labelled document (with meta-data) ------------------------------------ 2 - Known partners, patient ID out-of-band, labelled document (with meta-data) ------------------------------------ 3 - Known partners, linked patient, labelled document (with meta-data) IHE Cross-Enterprise Document Exchange - Media Option (XDM): CD or USB-Key ---------------------------------------------------------------- IHE Cross-Enterprise Document Exchange - Email Option (XDM-Email) -------------------------------------------------------- IHE Cross-Enterprise Reliable Exchange (XDR) w Patient ID Reconciliation (PIX/PDQ) Moving to the next level

  19. Health Information Sharing Deployment Models 4 - Community HIE Many potential partners, linked patient, labelled (with metadata) documents Centralized services (registry/EMPI) ------------------------------ 5 – Region/Nation/cross-nation Health Information Network Exchange IHE Cross-Enterprise Document Sharing (XDS) (On-Demand Document Option and Document Subscription / Notification (DSUB)) IHE Patient ID Cross-reference (PIX) and Patient Demographics Query (PDQ) --------------------------------------------- IHE Cross-Community Exchange (XCA) IHE Cross-community Patient Discovery (XCPD) IHE addresses 5 transport use cases !

  20. Health Information Exchange and IHE Profiles XDS Metadata Light Client IHE XDM (e-mail) Pt-to-Pt Push Application Client IHE XDR (Web Service) IHE XCA (cross-HIE) Share & Pull IHE XDS (Intra-HIE)

  21. Flexible Infrastructure Send to Send to Switch Interchange Media Write Read Replace with agreed new version of this slide Health Information Exchange XDS Structuredobjects Pull Publish Pull XDR XDM

  22. IHE XDS adopted in National & Regional Projects (sample) Austria Lower Austria NETHERLANDS Friesland Natn’l Mamography Italy Conto Corrente Venetto - Friuli VITL-Vermont FranceDMP Quebec, Toronto,Alberta, British ColumbiaCanada Infoway SuisseSt Gallen Lausane Wales Imaging France Imaging IDF Boston Medical Center - MA For more complete list see: Philadelphia HIE Belgium Flemish-Leuven KeyHIE Pennsylvania CareSpark – TN & VA SHARP CA South Africa THINC- New York NCHICA – N. Carolina Providence Health System - OR CHINA-Shanghai Imaging Info Sharing CHINA-MoH Lab results sharing JAPAN-Nagoya Imaging Info Sharing, Nationwide PDI guideline 23 23

  23. Who Is Using XDS? • Stable specification since 2009 (See IHE ITI Technical Framework) • First implementation in clinical use in region of Genoa - Italy) since early 2006. • Several since: Lower Austria region, State of Vermont, Nagoya city, South Africa region, Dutch regions, etc. • Adopted by several national programs world-wide: France, Canada, Switzerland, USA, Slovenia, China, etc. • Numerous product implementations world-wide: Close to 100 EMR/Clinical Systems products shipping More than 20 Infrastructure products shipping

  24. Open Source ImplementationTools Open source implementations are available for XDS, XCA, XCPD, PIX, PDQ, ATNA, CT, and more: NIST under Source Forge HIE-OS under Source Forge Microsoft under codeplex FHA CONNECT OHT – IHE Profiles Charter OHT – Open Exchange Forge OHT – Model Driven Health Tools-Charter 25

  25. Document Metadata Subscription supplement DSUB

  26. DSUB Overview The Document Metadata Subscription (DSUB) supplement contains two related parts: • Publish/Subscribe Infrastructure: General framework for defining web-services based publish/subscribe interactions • Document Metadata Subscription (DSUB) Integration Profile: Use of subscriptions within an XDS Affinity Domain or across communities

  27. Publish/Subscribe Infrastructure • Presents a framework for building event-driven information exchange patterns using a publish/subscribe data exchange model (See ITI TF Volume 3 section 4.4 • Defines the transport of publish, subscribe and notify messages. • Supports IHE profiles which define the use case specific content to be carried in the publish, subscribe and notify messages  Document Metadata Subscription (DSUB) first profile to use this framework.

  28. Publish/Subscribe Infrastructure Actors and Transactions Publisher Publish NotificationBroker Subscribe Subscriber Notify NotificationRecipient

  29. Possible Combined Actors Publisher Publisher NotificationBroker Subscriber Subscribe Publish Notify NotificationBroker Subscribe NotificationRecipient Publisher Notify NotificationBroker Subscribe NotificationRecipient Subscriber Notify NotificationRecipient Subscriber

  30. Document Metadata Subscription (DSUB) Integration Profile • Defines a subscription which allows for the matching of metadata during the publication of a new document for a given patient, and results in the delivery of a notification. • Enabled within an XDS Affinity Domain or XCA environment • Use Cases • Emergency Department: Notification of new document availability during treatment • Primary Care Management: PCP receives notification when new documents for patient are available

  31. DSUB Actors and Transactions XDS Registry Document Metadata Publisher Document Metadata Subscriber Document Metadata Publish [ITI-54] Document Metadata Subscribe [ITI-52] Document Metadata NotificationBroker Document Metadata Notify [ITI-53] Document Metadata NotificationRecipient

  32. Transactions • Document Metadata Subscribe : start a subscription for a particular topic and filtering within that topic. Supports full and minimal notifications and where to send the notification. • Document Metadata Notify : send a notification about the availability of a document or documents of interest, based on the subscribers' filters on selected topics • Document Metadata Publish : notify that an event occurred for which there may be a subscription.

  33. DSUB Illustration of Use Notification Broker Subscriber Publisher Notification Recipient Subscribe Publish Notify Publish Notify Unsubscribe Publish

  34. DSUB Implementation • DSUB topic tree • ihe:FullDocumentEntry : subscribes to Document Entry registration events; the notification shall contain the full metadata describing each matching Document Entry • ihe:MinimalDocumentEntry : subscribes to Document Entry registration events; the notification shall contain a minimal set of data (identifiers only) describing each matching Document Entry • DSUB Standards • Web Services Standards • WS-BaseNotification 1.3 OASIS Standard • WS-BrokeredNotification 1.3 OASIS Standard • WS-Topics 1.3 OASIS Standard • ITI TF-2x: Appendix V • Filter expression • Registry Stored Query [ITI-18]