NIST XDS Toolkit CONSUMER

Slides:

Advertisements

Similar presentations

Advertisements

EbXML and XDS ebXML Registry XDS Registry XDS Repository Validate Document Register Document Set XDS Validation Provide & Register Document Set XDS Patient.

Asynchronous Web Services Exchange Teddy Bachour Microsoft Corporation August 11, 2008.

IHE IT Infrastructure Domain Update

June 28-29, 2005IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Cross-enterprise Document Sharing for Imaging (XDS-I) Rita Noumeir.

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

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

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

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

RSNA 2011 Image Sharing Demonstration Transaction Sequence Diagram Nov 21st, 9am CDT, 2011.

Use Cases 1)A Clinical outpatient facility providing images to a shared image repository. 2) Sending images and other clinical documents to a referring.

IHE IT Infrastructure mHealth access to Document Sharing Profile John Moehrke June 6, 2012.

Distributing Images: Cross-enterprise Document Sharing for Imaging (XDS-I) Access to Radiology Information (ARI) Retrieve Information for Display (RID)

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.

Mobile Patient Discovery ITI Proposal Brief. The Problem Data Repositories A eCharts MPI Integration Service Data Repository eRxmyPHR B Integration Service.

September, 2005What IHE Delivers 1 Document Registry and Repository Implementation Strategies IHE Vendors Workshop 2006 IHE IT Infrastructure Education.

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.

XDS Testing for new Connectathon monitors Bill Majurski NIST.

Use Cases 1)A Clinical outpatient facility providing images to a shared image repository. 2) Sending images and other clinical documents to a referring.

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.

Publication and Discovery XDS IHE IT Infrastructure Webinar Series.

Cross-Enterprise User Assertion IHE Educational Workshop 2007 Cross-Enterprise User Assertion IHE Educational Workshop 2007 John F. Moehrke GE Healthcare.

Afdasfdasfd Adfasdfasfd asd Connectathon Timeline Connectathon Manager Training Steve Moore Mallinckrodt Institute of Radiology.

CS 493 Project Definition The project assignment is a simplified version of the Integrating Healthcare Enterprise (IHE) Cross-Enterprise Document Sharing.

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

XDW in a multi-community environment and back-linking to Workflow Documents A high-level analysis to avoid design choices that would make XDW Trial Implementation.

Dynamic Document Sharing Detailed Profile Proposal for 2010 presented to the IT Infrastructure Technical Committee Karen Witting November 10, 2009.

Implementing the XDS Infrastructure Bill Majurski IT Infrastructure National Institute of Standards and Technology.

1 Healthcare Information Technology Standards Panel Care Delivery - IS01 Electronic Health Record (EHR) Laboratory Results Reporting July 6, 2007.

XDW Proposal for a generic technical specification Shown by Pharmacy use-case as an example Jürgen Brandstätter.

XDStarClient Presentation of a suite of tools developed by IHE Europe for healthcare community Abderrazek Boufahja Mai 25, 2012.

XCA Transaction Diagram minimum required

Publication and Discovery XDS and DSUB IT Infrastructure Planning Committee Ilia Fortunov - Microsoft.

1 IHE ITI White Paper on Authorization Rough Cut Implementation Opportunities for BPPC Dr. Jörg Caumanns, Raik Kuhlisch, Olaf Rode Berlin,

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

Korea Connectathon 2011 Briefing Kyungpook National University IT Building #4 Room #106.

The new Secure Retrieve (SeR) profile provides Access Control to the documents in an IHE XDS environment. Refer to the diagram on the next slide to see.

Federation Karen Witting. Goals of “Federation” Show a vision for support of cross XDS Affinity Domain communication Show cooperation between IHE and.

Document Consumer Patient Identity Source Document Registry Document Repository Document Source MHD Document Recipient MHD Document Responder MHD Document.

IHE IT Infrastructure Domain Update Karen Witting – IBM IT Infrastructure Technical Committee co-chair.

September, 2005What IHE Delivers 1 IT Infrastructure Planning Committee Karen Witting – Ready Computing XDS & XCA: On-Demand Documents.

Sept 13-15, 2004IHE Interoperability Workshop 1 Integrating the Healthcare Enterprise Cross Enterprise Document Sharing Details Keith W. Boone – Dictaphone.

© 2016 California Association of Health Information Exchanges Licensed under a Creative Commons Attribution Share-Alike 3.0 LicenseCreative Commons Attribution.

Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.

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.

Cross-Enterprise Document Sharing (XDS) Bill Majurski IT Infrastructure National Institute of Standards and Technology.

September, 2005What IHE Delivers 1 Patient Index and Demographic Implementation Strategies IHE Vendors Workshop 2006 IHE IT Infrastructure Education Rick.

XUA – Circle of Trust (e.g. XDS Affinity Domain) St. Johns North Clinic Auth Prov ID Prov Auth Prov ID Prov Rad Reporting PACS XDS Registry XDS PIX Rad.

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.

PIX/PDQ – Today and Tomorrow Vassil Peytchev Epic.

XDS Security ITI Technical Committee May, XDS Security Use Cases Prevent Indiscriminate attacks (worms, DOS) Normal Patient that accepts XDS participation.

RFD Profile Examine Security Compare to XDS Node Security.

Cross Community Access Profile Karen Witting IBM Co-chair ITI technical committee.

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

Publish Subscribe for XDS-b Vassil Peytchev Epic Systems Corporation.

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

Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.

Patient Demographics Query (PDQ) Didi Davis Director, Eclipsys Corporation Co-Chair, IT Infrastructure Planning Committee.

Cross Enterprise TeleHomeMonitoring Workflow Definition (XTHM-WD)

IHE USA Certification Input PCD and Government Focus March 26, 2014

IT Infrastructure Plans

IHE Security XDS as a case study

Federation Karen Witting.

Connectathon Patient Identifiers

ebXML and XDS XDS Patient Identifier Source XDS Validation:

System Directory for Document Sharing (SDDS)

Connectathon Patient Identifiers

Presentation transcript:

NIST XDS Toolkit CONSUMER XCA Test Environment BLUE Ass. Authority/Aff. Domain - 3 DIFFERENT COMMUNITIES (Red, Green, Blue). Could be an XDS Affinity Domain, or not. 3 DIFFERENT Patient ID ASSIGNING AUTHORITIES (Red, Green, Blue) BLUE REGISTRY VENDOR “B” RESPONDING GATEWAY REPOSITORY NIST XDS Toolkit CONSUMER INITIATING GATEWAY VENDOR “A” RED Ass. Authority/Aff. Domain PatientID: IHERED-1039^^^&1.3.6.1.4.1.21367.13.20.1000&ISO PatientID: IHEBLUE-1039^^^&1.3.6.1.4.1. 21367.13.20.3000&ISO NIST XDS Toolkit SOURCE GREEN Ass. Authority/Aff. Domain GREEN REGISTRY RESPONDING GATEWAY VENDOR “C” REPOSITORY PIX/PDQ/XCPD/etc. PatientIDs used: IHERED-1039^^^&1.3.6.1.4.1.21367.13.20.1000&ISO IHEBLUE-1039^^^&1.3.6.1.4.1.21367.13.20.2000&ISO IHEGREEN-1039^^^&1.3.6.1.4.1.21367.13.20.3000&ISO PatientID: IHEGREEN-1039^^^&1.3.6.1.4.1.21367.2000&ISO NIST XDS Tookit SOURCE

- Support for XCA Testing in XDS toolkit: 3 different patient ID assigning authorities (Red, Green, Blue) XDS Toolkit has an XDS Document Consumer and XDS Document Source to assist with test setup and execution XDS Toolkit Doc Source can submit a document belonging to the test patient to a Repository in the Responding community XDS Toolkit Doc Consumer can send query and retrieve requests in the Initiating Community if the Initiating Gateway can respond to ITI-41 and ITI-43 transactions (future) 3 different affinity domains with 3 different “coding systems” (Red, Green, Blue): 3 copies of NIST Registry/Repository Vendors: each XCA Gateway is assigned to a precise color affinity patient identification domain. He must set up only 1 assigning authority and only 1 Affinity Domain set of codes.

XCA TESTING OVERVIEW A. XCA PRELIMINARY SETTINGS Responding Gateway Setup: correct setting of homeCommunityId and of the XDS rTegistry/Tepository pair behind the Responding Gateway. B. XCA QUERY: X-GW Query Request – findDocuments – from Initiating Gateway to Responding Gateway contains the patientID valid in the responding community (with the color of the responding community); X-GW Query Response – findDocuments – is consolidated at the Initiating Gateway and arrives at the Document Consumer with the list of the documents uuids and contains the related homeCommunityIDs. (so, the Responding Gateway puts the homecommunityId in the response) X-GW Query Request – getDocuments – uses the same document uuid contained in the findDocuments response and is addressed to the right homeCommunityID. X-GW Query Response – getDocuments – in the metadata of the response is present the patientID valid in the responding community; this response contains documentUniqueId, repositoryUniueId and homeCommunityid that will be used in the retrieve. C. XCA RETRIEVE: X-GW Retrieve – request – uses the same document uniqueId, repository UniqueId and homeCommunityID contained in the getDocuments response. D. OTHER ISSUES Every transactions is to be made over TLS ATNA logging to any Audit Record Repository

Initiating Community “A” XDS.b Doc Reg XDS.b Doc Rep XCA-I expands the XCA Test Environment ITI-18 XCA Resp GW ITI-43 Responding Community “B” XCA-I Init Img GW XCA Init GW XDS.b Doc Reg XDS.b Doc Rep XDS.b Doc Cons XCA-I Img Doc Cons Initiating Community “A” ITI-18 RAD-69 ITI-43 XCA-I Init Img GW XCA-I Img Doc Source RAD-69 ITI-43 XDS.b Doc Rep XDS.b Doc Reg XCA Resp GW XCA-I Init Img GW XCA-I Img Doc Source ITI-38 & 39 ITI-18 ITI-43 Responding Community “C” RAD-75 RAD-69 XDS.b or XCA transaction XDS-I.b or XCA-I transaction