System Directory for Document Sharing (SDDS) Vassil Peytchev, Epic February 1, 2010.

Slides:



Advertisements
Similar presentations
ITI Publish/Subscribe Infrastructure Profile Proposal for 2008/09 presented to the IT Infrastructure Technical Committee Vassil Peytchev November 18, 2008.
Advertisements

September, 2005What IHE Delivers 1 Key Image Notes Evidence Documents Simple Image & Numeric Report Access to Radiology Information IHE Vendors Workshop.
Async XDS.b.
Asynchronous Web Services Exchange Teddy Bachour Microsoft Corporation August 11, 2008.
September, 2005What IHE Delivers 1 IHE Quality Domain February 26, 2008.
IHE IT Infrastructure Domain Update
Cross Community (XC) Profiles November 2006 ITI Planning committee meeting Karen Witting.
IHE Profile Proposal: Dynamic Configuration Management October, 2013.
Cross Community (XC) Profiles Karen Witting. Outline Vision – as described in 2006 IHE White Paper on Cross Community Exchange Existing – what has been.
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.
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.
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 Domain Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Mobile Patient Discovery ITI Proposal Brief. The Problem Data Repositories A eCharts MPI Integration Service Data Repository eRxmyPHR B Integration Service.
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.
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.
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.
1.View Description 2.Primary Presentation 3.Element Catalog Elements and Their Properties Relations and Their Properties Element Interfaces Element Behavior.
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.
September, 2005What IHE Delivers 1 Key Image Notes Evidence Documents Simple Image & Numeric Report Access to Radiology Information IHE Vendors Workshop.
CS 493 Project Definition The project assignment is a simplified version of the Integrating Healthcare Enterprise (IHE) Cross-Enterprise Document Sharing.
Defining the 2016 CAS-2 cycle Timeline Slides used by the CAsC Committee on its July 23 rd T-con to establish the timeline for the main activities related.
Cross-enterprise Document Workflow (XDW)
Dynamic Document Sharing Detailed Profile Proposal for 2010 presented to the IT Infrastructure Technical Committee Karen Witting November 10, 2009.
Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Cross-enterprise Basic eReferral Workflow Definition (XBeR-WD)
IHE IT Infrastructure Domain Update Karen Witting – IBM IT Infrastructure Planning Committee co- chair.
Cross-Enterprise User Authentication John F. Moehrke GE Healthcare IT Infrastructure Technical Committee.
System Directory for Document Sharing (SDDS) Vassil Peytchev, Epic February 1, 2010.
XDStarClient Presentation of a suite of tools developed by IHE Europe for healthcare community Abderrazek Boufahja Mai 25, 2012.
XCA Transaction Diagram minimum required
Patient Identity Management Eric Heflin Dir of Standards and Interoperability/Medicity.
Cross-Community Patient Identification (XCPI) Brief Profile Proposal for 2009 presented to the IT Infrastructure Technical Committee Karen Witting November.
Dynamic Data Brief Profile Proposal for 2009/10 presented to the IT Infrastructure Planning Committee Karen Witting September 30, 2009.
Agenda  Planning Update status OHSU and Epic discussion Workflow design meetings  Implementation & Testing – Status Review progress against work plan.
Bill Majurski National Institute of Standards and Technology (NIST)‏ IT Infrastructure: Profiles for Health Information Exchange.
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.
IT Infrastructure Planning Committee Use Case Enhanced SVS Nikolay Lipskiy, MD, DrPH, Centers for Disease Control (CDC), USA Sundak Ganesan, MD, Northrop.
IT Infrastructure Planning Committee Service Model Task Service Layer Entity Service Layer Utility Service Layer Logical service abstraction layers categorize.
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.
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 User Authentication Year 2 March 16, 2006 Cross-Enterprise User Authentication Year 2 March 16, 2006 John F. Moehrke GE Healthcare IT.
May, 2014What IHE Delivers 1 IT Infrastructure Planning Committee XDS Metadata Update.
PIX/PDQ – Today and Tomorrow Vassil Peytchev Epic.
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.
June-September 2009www.ihe.net North American 2010 Connectathon & Interoperability Showcase Series Paul Seifert/ Kinson Ho Solution Architects Agfa HealthCare.
Dynamic/Deferred Document Sharing (D3S) Profile for 2010 presented to the IT Infrastructure Technical Committee Karen Witting February 1, 2010.
IT Infrastructure Plans Karen Witting – IBM IT Infrastructure Technical Committee co-chair.
NIST XDS Toolkit CONSUMER
Federation Karen Witting.
System Directory for Document Sharing (SDDS)
System Directory for Document Sharing (SDDS)
Connectathon Patient Identifiers
Presentation transcript:

System Directory for Document Sharing (SDDS) Vassil Peytchev, Epic February 1, 2010

IT Infrastructure Planning Committee Scope Scope is around Document SharingScope is around Document Sharing –Cross-Community document sharing –Cross-Enterprise document sharing Initial use cases provided the general Actor-Transaction DiagramInitial use cases provided the general Actor-Transaction Diagram Updater Service Directory Requestor

IT Infrastructure Planning Committee Scope Expand use cases to show how the different Document Sharing actors can be grouped with the Updater and Requester actorsExpand use cases to show how the different Document Sharing actors can be grouped with the Updater and Requester actors

IT Infrastructure Planning Committee Use Cases XDSXDS –Document Consumer – a new consumer joins an affinity domain. As an updater, the consumer provides information about the entity it represents (ID, certificate, link to provider registry entry/entries)As an updater, the consumer provides information about the entity it represents (ID, certificate, link to provider registry entry/entries) As a requestor, needs to know the registry entity and the RSQ service information; list of repositories and their RDS service information; or, alternatively, the initiating gateway entity and its RSQ and RDS service informationAs a requestor, needs to know the registry entity and the RSQ service information; list of repositories and their RDS service information; or, alternatively, the initiating gateway entity and its RSQ and RDS service information –Document Source – a new document source joins an affinity domain; a document source switches repositories As an updater, the source provides information about the entity it represents (ID, certificate, link to provider registry entry/entries)As an updater, the source provides information about the entity it represents (ID, certificate, link to provider registry entry/entries) As a requestor, the source needs to know the repository entity/entities and their PnR service informationAs a requestor, the source needs to know the repository entity/entities and their PnR service information

IT Infrastructure Planning Committee Use Cases XDS (continued)XDS (continued) –Document Registry – A new participant joins the affinity domain As an updater, the registry provides information about the entity it represents (ID (no ID), certificate); the services it supports (R, RSQ); the affinity domain configurationAs an updater, the registry provides information about the entity it represents (ID (no ID), certificate); the services it supports (R, RSQ); the affinity domain configuration As a requestor, needs to know the repository and consumer entities; the responding gateway entityAs a requestor, needs to know the repository and consumer entities; the responding gateway entity –Document Repository – a new document repository joins an affinity domain; a new document source is added to the repository. As an updater, the repository provides information about the entity it represents (ID, certificate, (link to provider registry entry/entries) list of sources); the services it supports (PNR, RDS).As an updater, the repository provides information about the entity it represents (ID, certificate, (link to provider registry entry/entries) list of sources); the services it supports (PNR, RDS). As a requestor, the repository needs to know the registry entity/entities and their R service information.As a requestor, the repository needs to know the registry entity/entities and their R service information.

IT Infrastructure Planning Committee Use Cases XDS with XCAXDS with XCA –Initiating gateway – A new participant (source, consumer, repository) joins the affinity domain As an updater, the initiating gateway provides information about the entity it represents (Home Community ID, certificate) and the services it supportsAs an updater, the initiating gateway provides information about the entity it represents (Home Community ID, certificate) and the services it supports As a requestor, may need to know the document consumers, and the entities they representAs a requestor, may need to know the document consumers, and the entities they represent –Responding gateway – A new participant (source, consumer, repository) joins the affinity domain As an updater, the responding gateway provides information about the entity it represents (ID, certificate)As an updater, the responding gateway provides information about the entity it represents (ID, certificate) As a requestor, the repository needs to know the registry entity, the repository and their services information.As a requestor, the repository needs to know the registry entity, the repository and their services information.

IT Infrastructure Planning Committee Use Cases XCA (and XCPD)XCA (and XCPD) –Initiating gateway – A new participant joins a group of networked communities As an updater, the initiating gateway provides information about the entity it represents (Home Community ID, certificate, location)As an updater, the initiating gateway provides information about the entity it represents (Home Community ID, certificate, location) As a requestor, needs to know the responding gateways, the entities they represent, and the services they supportAs a requestor, needs to know the responding gateways, the entities they represent, and the services they support –Responding gateway – A new participant joins a group of networked communities As an updater, the responding gateway provides information about the entity it represents (ID, certificate); the services it supports.As an updater, the responding gateway provides information about the entity it represents (ID, certificate); the services it supports. As a requestor, the repository needs to know the initiating gateway entities that may use its services.As a requestor, the repository needs to know the initiating gateway entities that may use its services.

IT Infrastructure Planning Committee Transactions ITI-Y1 RequestITI-Y1 Request ITI-Y2 UpdateITI-Y2 Update ITI-Y3 Notifications (cost of notification)ITI-Y3 Notifications (cost of notification)