System Directory for Document Sharing (SDDS)

Slides:



Advertisements
Similar presentations
Cross Community (XC) Profiles November 2006 ITI Planning committee meeting Karen Witting.
Advertisements

Website Designing & Development Designed By Steer Logix Private Limited.
Cross Community (XC) Profiles Karen Witting. Outline Vision – as described in 2006 IHE White Paper on Cross Community Exchange Existing – what has been.
UDDI v3.0 (Universal Description, Discovery and Integration)
Course 5: IHS NHIE Overview and Patient Data Viewer February 1, 2011.
Web Services Technology Stack (WSDL and UDDI)
T NAF & XML UDDI Sasu Tarkoma and Pekka Nikander Helsinki Institute for Information Technology.
Web Services: UDDI. What is UDDI? UDDI = The Universal Description, Discovery, and Integration A central element of the group of standards that comprise.
UDDI Overview Copyright © by Accenture, Ariba, Inc., Commerce One, Inc., Fujitsu Limited, Hewlett-Packard Company, i2 Technologies, Inc., Intel.
Web Services - Concepts, Architecture and Applications Part 7: Service Discovery (UDDI) Gustavo Alonso and Cesare Pautasso Computer Science Department.
UDDI Ashish Jain University of Colorado 3 October, 2001.
Livermore July Web Services Overview Francisco Curbera IBM T.J. Watson Research Center.
Discovery Robert Grimm New York University. The Problem: Naming (Or, How to Start a Religious War)  The Internet today  IP addresses  Strict location.
January, Steve Moore Lynn Felhofer Connectathon Patient Identifiers.
CONNECT as an Interoperability Platform - Demo. Agenda Demonstrate CONNECT “As an Evolving Interoperability Platform” –Incremental addition of features.
In Introduction to Web Services
WSTK Development toolkit for Java Implementation of Web Services By Keping Jia.
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.
UDDI Overview 9/6/2000 © Copyright 2000 By Ariba, Inc., International Business Machines Corporation and Microsoft Corporation. All Rights Reserved.
Cambridge, March 23 rd 2004 MobileMAN Project MobileMAN Project Web Service in Ad Hoc Network Veronica Vanni NETikos S.p.A.
UDDIe: An Extended registry for Web Services UDDIe: An Extended Registry for Web Services Ali Shaikhali, Omer F. Rana, Rashid J. Al-Ali and David W. Walker.
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.
Web Service Addressing CS409 Application Services Even Semester 2007.
1 Universal Description, Discovery, and Integration (UDDI) 大葉大學資工系.
Session I Part II: WS Standards Umesh Bellur IIT Bombay umesh[at]it.iitb.ac.in.
UDDI Jianguo Lu University of Windsor What is UDDI?  Universal Description, Discovery, and Integration  A project to encourage interoperability.
Qusay H. Mahmoud CIS* CIS* Service-Oriented Computing Qusay H. Mahmoud, Ph.D.
Sharing Value Sets (SVS Profile) Ana Estelrich GIP-DMP.
IBM Software Group ® WSRP-UDDI Straw Man Richard Jacob WSRP-PFB SC.
1 UDDI (Universal Description, Discovery, and Integration) An Overview – part II Version : Date : Pages Responsible Author : Co-Authors : Status : Confidentiality.
Implementing the XDS Infrastructure Bill Majurski IT Infrastructure National Institute of Standards and Technology.
Web Services Registries and UDDI INFOSYS290-3 Web Services: Concepts, Design and Implementation.
Helsinki, June 7 th 2004 IAB Meeting MobileMAN Project Web Service in Ad Hoc Network Veronica Vanni NETikos S.p.A.
Service provider service requestor application object (client) application object (service provider) SOAP-based middleware SOAP messages exchanged on top.
Integrating the Healthcare Enterprise Retrieve ECG for Display Profile Barry D. Brown, Mortara Instrument, Inc. ECG Profile co-editor IHE Cardiology Technical.
System Directory for Document Sharing (SDDS) Vassil Peytchev, Epic February 1, 2010.
Cross-Community Patient Identification (XCPI) Brief Profile Proposal for 2009 presented to the IT Infrastructure Technical Committee Karen Witting November.
Kemal Baykal Rasim Ismayilov
CP3024 Lecture 10 Web Services. What are Web Services?  “encapsulated, loosely coupled, contracted software objects offered via standard protocols” ZapThink.
Web Services Part 1 -- Qinwei Zhu Part 2 – Yongqun He.
Federation Karen Witting. Goals of “Federation” Show a vision for support of cross XDS Affinity Domain communication Show cooperation between IHE and.
System Directory for Document Sharing (SDDS) Vassil Peytchev, Epic February 1, 2010.
UDDI (Universal Description, Discovery and Integration) Dr. SVL Narasimham.
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.
Visit amzsoftech.com Click Here. Type the User name Type the password Click Login First time user Click Sign Up.
Visit amzsoftech.com Click Here. Type the User name Type the password Click Login First time user Click Sign Up.
IBM Software Group ® WSRP-UDDI Straw Man Richard Jacob WSRP-PFB SC.
1 G52IWS: Universal Description, Discovery and Integration (UDDI)‏ Chris Greenhalgh
PIX/PDQ – Today and Tomorrow Vassil Peytchev Epic.
WSTK Development toolkit for Java Implementation of Web Services By Keping Jia.
DISCO/UDDI -Ketan Reddy Peddabachi. Agenda Web Service Disco UDDI Disco Vs UDDI.
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.
Active Directory Domain Services (AD DS). Identity and Access (IDA) – An IDA infrastructure should: Store information about users, groups, computers and.
Service Discovery: UDDI COMP6017 Topics on Web Services Dr Nicholas Gibbins –
Access to Radiology Information Paul Seifert Agfa HealthCare Co-chair, IHE Radiology Technical Committee.
IT Infrastructure Plans
Federation Karen Witting.
Connectathon Patient Identifiers
System Directory for Document Sharing (SDDS)
Integrating the Healthcare Enterprise (IHE) IHE-EUROPE
Affiliate Advantage How to
UDDI Best Practices.
Connectathon Patient Identifiers
Universal Description, Discovery and Integration (UDDI)
Presentation transcript:

System Directory for Document Sharing (SDDS) Vassil Peytchev, Epic April 28, 2010

UDDI Structures

UDDI Structures Containment is different from reference Business Entity vs. Business Service Business Entity represents a group of IHE actors Business Service corresponds to an IHE actor Binding Template HPD will point to Business Entities

UDDI Structures Categorizations External Identifiers IHE defined categorizations for Business Services (IHE Actors in a profile) Is there a need to define categorizations for Business Entities? Anything regarding the link from HPD? (NHIN has state here). External Identifiers Business Entities corresponding to actors with specific identifiers: Affinity Domain use case: source ID(s), Repository Unique ID(s), Home Community ID(s) --- open issue for multiple Source Ids – is it supported in UDDI? Cross Community use case: Home Community ID(s)

Categorizations IHE Actors Categorization: Other IHE Categorizations: Custom categorization: uddi:uddi.org:categorization:ihe:actors Use an urn, similar to the rules presented in Appendix V: urn:ihe:{committee}:{profile abbreviation}:{year}:{actor} Give example (image manager example) Open issue – (what is year, need to clearly define year) Other IHE Categorizations: Patient Identity Domain (business entity) Add example of Audit repository as a service end point which is not a web service

UDDI API find_business get_businessDetail find_service get_serviceDetail

NHIN Examples <find_business> <!-- uddi:nhin:nhie:homecommunityid is an identifierBag --> <identifierBag> <keyedReference tModelKey="uddi:nhin:nhie:homecommunityid" keyValue="home community id 1"/> <keyedReference tModelKey="uddi:nhin:nhie:homecommunityid" keyValue="home community id 2"/> </identifierBag> <categoryBag> <!-- uddi:nhin:nhie:publickey is a categoryBag --> <keyedReference tModelKey="uddi:nhin:nhie:publickey" keyValue="public key value (base64)"/> <!-- uddi:uddi.org:ubr:categorization:iso3166 (state) is a categoryBag --> <keyedReference tModelKey="uddi:uddi.org:ubr:categorization:iso3166" keyValue="US-NY"/> <keyedReference tModelKey="uddi:uddi.org:ubr:categorization:iso3166" keyValue="US-VT"/> <keyedReference tModelKey="uddi:uddi.org:ubr:categorization:iso3166" keyValue="US-MA"/> <keyedReference tModelKey="uddi:uddi.org:ubr:categorization:iso3166" keyValue="US-WI"/> </categoryBag> </find_business>

NHIN Examples <businessList > <businessInfos> <businessInfo businessKey="business key value - we use this in the follow-up get_businessDetail"> <name>Organization Name</name> <!-- We'll ignore this since we're following up with a get_businessDetail --> <serviceInfos> <serviceInfo serviceKey="" businessKey=""></serviceInfo> </serviceInfos> </businessInfo> </businessInfos> </businessList>

NHIN Examples <get_businessDetail> <businessKey>business key returned by find_business query</businessKey> <businessKey>business key returned by find_business query</businessKey> <businessKey>business key returned by find_business query</businessKey> <businessKey>business key returned by find_business query</businessKey> <businessKey>business key returned by find_business query</businessKey> </get_businessDetail>

NHIN Examples <businessDetail> <businessEntity businessKey="uddi:testnhieonenode:um:oid.2.16.840.1.113883.3.166.4"> <name xml:lang="en">Test NHIE One</name> <contacts> <contact useType=""> … </contact> </contacts> <businessServices> <businessService serviceKey="uddi:testnhieonenode:PatientDiscovery" businessKey="uddi:testnhieonenode:urn:oid:2.16.840.1.113883.3.166.4"> <name>PatientDiscovery</name> <bindingTemplates> <bindingTemplate bindingKey="uddi:00f27b20-c31e-11de-a851-5adf7990a84c" serviceKey="uddi:testnhieonenode:PatientDiscovery"> <accessPoint URLType="https">https://testonenhie.com/RespondlngGatewayService</accessPoint> …

Add examples of connectathon configuration