Presentation is loading. Please wait.

Presentation is loading. Please wait.

XDS.b – Cross-Enterprise Document Sharing XDS.b_Doc_Source_Stores_Document XDS.b_Consumer_Query_Retrieve XDR option tests: XDS.b_Source_Do_This_First XDS.b_Registry_Do_This_First.

Published byCecily Robinson Modified over 8 years ago

Similar presentations

Presentation on theme: "XDS.b – Cross-Enterprise Document Sharing XDS.b_Doc_Source_Stores_Document XDS.b_Consumer_Query_Retrieve XDR option tests: XDS.b_Source_Do_This_First XDS.b_Registry_Do_This_First."— Presentation transcript:

1 XDS.b – Cross-Enterprise Document Sharing XDS.b_Doc_Source_Stores_Document XDS.b_Consumer_Query_Retrieve XDR option tests: XDS.b_Source_Do_This_First XDS.b_Registry_Do_This_First XDS.b_Repository_Do_This_First XDS.b_Integrated_Source_Registers_Document XDS.b_Integrated_Repository_Retrieve XDS.b_Simple_HL7v2_Feed XDS.b_Simple_HL7v3_Feed

2 XDS.b option tests: Async tests Doc Addendum, Replace, Transformation Folder Management XDS.b_Delayed_Doc_Assembly XDS.b_On-Demand_Docs XDS.b_MU_DocEntry_Update XDS.b_MU_availabilityStat_Update XDS.b_MU_Delete_Metadata XDR_Source_Recipient_LtdMetadata BPPC_Source_Enforcement BPPC_Consumer_Enforcement & Proof (BPPC_1 st _Read_Privacy_Policy) XDS.b – (cont.)

3 XDR – Cross-Enterprise Document Reliable Interchange XDR_Doc_Source_Recipient MPQ_Registry_Setu p XDR option tests: XDR_MU_Doc_Entry_Update XDR_MU_Delete_Metadata XDR_Source_Recipient_LtdMetadata BPPC_Source_Enforcement BPPC_Recipient_Enforcement (BPPC_1 st _Read_Privacy_Policy)

4 MPQ – Multi-Patient Queries MPQ_Consumer_Queries_Registry MPQ_Query_Async_Option MPQ_Registry_Setup

5 DSUB – Document Metadata Subscription DSUB_Gateway_Notify (w/ XCA) DSUB_Registry_Notify (w/ XDS.b) DSUB_Publish DSUB_Subscribe

6 NAV – Notification of Document Availability NAV_Notification_Exchange NAV_Acknowledgement_Option (SMTP, POP3, IMAP) MPQ_Registry_Setu p

7 XPID – XAD-PID Change Management XPID_Notify_Link_Change Also see next slide…

8 Doc Registry ‘red’ assigning authority’ RED33333^^^&1.3.6.1.4.1.21367. 13.20.1000&ISO Doc Registry ‘red’ assigning authority’ RED33333^^^&1.3.6.1.4.1.21367. 13.20.1000&ISO PIX Manager Initially links these IDs under one “patient”: RED33333^^^&1.3.6.1.4.1.21367.13.20.1000&ISO GREEN33333^^^&1.3.6.1.4.1.21367.13.20.2000&ISO BLUE33333^^^&1.3.6.1.4.1.21367.13.20.3000&ISO PHN-18905^^^&1.3.6.1.4.1.21367.3000.1.6.&ISO …after the link-change RED11111^^^&1.3.6.1.4.1.21367.13.20.1000&ISO PHN-18905^^^&1.3.6.1.4.1.21367.3000.1.6.&ISO Doc Source w/ Local Patient ID: PHN- 18905^^^ &1.3.6.1.4.1. 21367.3000.1.6&ISO Doc Source submits to a Repository w/ a Registry using a “Red” XAD-PID RED33333 From the PIX Manager’s point of view, the “Red” Assigning Authority is the XAD-PID, so when a link-change is made to link local ID PHN-18905 to XAD-PID RED11111, it generates ITI-64 to notify the Registry Doc Repository ITI-41 ITI-64

9 XUA – Cross-Enterprise User Assertion NAV_Notification_Exchange NAV_Acknowledgement_Option (SMTP, POP3, IMAP) XUA_Service_Provider_Setup XUA_Transaction_with_Assertion XUA_Policy_Test XUA_Restrict_Access (Tiani-Spirit EHR) XUA option tests: XUA_AuthzConsent XUA_PurposeOfUse XUA_SubjectRole

Download ppt "XDS.b – Cross-Enterprise Document Sharing XDS.b_Doc_Source_Stores_Document XDS.b_Consumer_Query_Retrieve XDR option tests: XDS.b_Source_Do_This_First XDS.b_Registry_Do_This_First."

Similar presentations

IHE IT Infrastructure Domain Update

IHE IT Infrastructure Domain Update
What IHE Delivers Basic Patient Privacy Consents HIT-Standards – Privacy & Security Workgroup John Moehrke GE Healthcare.

What IHE Delivers Basic Patient Privacy Consents HIT-Standards – Privacy & Security Workgroup John Moehrke GE Healthcare.
IHE IT Infrastructure Outreach to Patient Care Coordination Domain Michael Nusbaum IT Infrastructure Planning Committee December 13 th, 2010.

IHE IT Infrastructure Outreach to Patient Care Coordination Domain Michael Nusbaum IT Infrastructure Planning Committee December 13 th, 2010.
EbXML and XDS ebXML Registry XDS Registry XDS Repository Validate Document Register Document Set XDS Validation Provide & Register Document Set XDS Patient.

EbXML and XDS ebXML Registry XDS Registry XDS Repository Validate Document Register Document Set XDS Validation Provide & Register Document Set XDS Patient.
September, 2005What IHE Delivers 1 IHE Quality Domain February 26, 2008.

September, 2005What IHE Delivers 1 IHE Quality Domain February 26, 2008.
IHE IT Infrastructure Domain Update

IHE IT Infrastructure Domain Update
Extending XDW in Cross-Community Editor: Charles Parisot Notes for the March 19 th, 2013 – ITI Tech Committee.

Extending XDW in Cross-Community Editor: Charles Parisot Notes for the March 19 th, 2013 – ITI Tech Committee.
Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.

Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.
Sept 13-15, 2004IHE Interoperability Worshop 1 Integrating the Healthcare Enterprise XDS Cross-Enterprise Document Sharing Integration Profile Standards.

Sept 13-15, 2004IHE Interoperability Worshop 1 Integrating the Healthcare Enterprise XDS Cross-Enterprise Document Sharing Integration Profile Standards.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.

Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Slide 1 Sharing Images without CDs, The Next Imaging Sea Change GE Healthcare Chris Lindop GE Healthcare Interoperability & Standards.

Slide 1 Sharing Images without CDs, The Next Imaging Sea Change GE Healthcare Chris Lindop GE Healthcare Interoperability & Standards.
January, 2009 1 Steve Moore Lynn Felhofer Connectathon Patient Identifiers.

January, Steve Moore Lynn Felhofer Connectathon Patient Identifiers.
Cross-Enterprise Document Networking (XDN) Problem – Legacy decommissioning produces large static collections of patient-related documents requiring long-term.

Cross-Enterprise Document Networking (XDN) Problem – Legacy decommissioning produces large static collections of patient-related documents requiring long-term.
Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.

Cross Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Bill Majurski National Institute of Standards and Technology (NIST)‏ IT Infrastructure: Profiles for Health Information Exchange.

Bill Majurski National Institute of Standards and Technology (NIST)‏ IT Infrastructure: Profiles for Health Information Exchange.
Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.

Cross-Enterprise Document Sharing Cross-Enterprise Document Sharing Bill Majurski National Institute of Standards and Technology IT Infrastructure Co-Chair.
NIST XDS Toolkit SOURCE NIST XDS Toolkit SOURCE VENDOR “ B ” RESPONDING GATEWAY VENDOR “ B ” RESPONDING GATEWAY BLUE REGISTRY REPOSITORY PIX/PDQ/XCPD/etc.

NIST XDS Toolkit SOURCE NIST XDS Toolkit SOURCE VENDOR “ B ” RESPONDING GATEWAY VENDOR “ B ” RESPONDING GATEWAY BLUE REGISTRY REPOSITORY PIX/PDQ/XCPD/etc.
Using 3 XDS Affinity Domains at the Connectathon Prior to the 2010 European connectathon, we chose to test with one Affinity Domain, with one Patient ID.

Using 3 XDS Affinity Domains at the Connectathon Prior to the 2010 European connectathon, we chose to test with one Affinity Domain, with one Patient ID.
Using 3 XDS Affinity Domains at the Connectathon Prior to the 2010 European connectathon, we chose to test with one Affinity Domain, with one Patient ID.

Using 3 XDS Affinity Domains at the Connectathon Prior to the 2010 European connectathon, we chose to test with one Affinity Domain, with one Patient ID.
Using 3 XDS Affinity Domains at the Connectathon At past North American connectathons, we chose to test with one Affinity Domain, with one Patient ID assigning.

Using 3 XDS Affinity Domains at the Connectathon At past North American connectathons, we chose to test with one Affinity Domain, with one Patient ID assigning.

Similar presentations

Ads by Google