Cross-Enterprise Document Sharing-b (XDS.b)

Slides prepared bySlides prepared byRoberto Ruggeri, XDS.bRoberto Ruggeri, XDS.b

Slides Presented by Slides Presented by Vassil Peytchev, PIX/PDQ v3, Appendix VVassil Peytchev, PIX/PDQ v3, Appendix V

Introduction

• XDS.b is an evolution of the current XDS Integration Profile (XDS.a)

• Same business scenario as XDS.a

• Provides new transactions in line with current standards

• XDS.a and XDS.b can co-exist

2

What’s new in XDS.b

• Document metadata format is ebXML Registry Information Model, Version 3.0– Added new repositoryUniqueId attribute

• New Retrieve Document Set transaction with Web Services binding

• New transactions with updated Web Services bindings

• WSDL for Document Repository, Document Registry• Allows for either Patient Identity Feed HL7v2 or HL7v3

or both to accommodate different scenarios– E.g.: Canada focusing on HL7 v3, U.S. focusing on HL7

v2• No support for “off-line” mode

3

What is the Same in XDS.b

• Addresses same scenario as XDS.a providing new implementation mechanism

• Maintains the same options as XDS.a– Multiple document submission– Document Lifecycle management– Folder management

• Composes with other IHE content profiles

4

Document Metadata Changes

• New repositoryUniqueId allows for proper identification of location where document is stored– Document Consumers binds to appropriate

repository• Document URI becomes optional

– If present indicates support for Retrieve Document transaction [ITI 17]

5

Coexistence and Migration

• XDS.b allows the document URI metadata attribute to be present– Facilitates the use of XDS.b Document

Repository/Registry in legacy XDS.a environments

• XDS.b identifies rules for implementations claiming conformance against both XDS.a and XDS.b at the same time

• [ITI TF-1:10.7] in the supplement explains common scenarios

6

XDS.b Actors and Transactions

• Document Registry– Registry Stored Query [ITI-18]– Register Document Set-b– Patient Identity Feed (HL7v2/HL7v3)

• Document Repository– Provide and Register Document Set-b– Retrieve Document Set

7

XDS.b Actors and Transactions

Patient Identity Patient Identity SourceSource

Document Document RegistryRegistry

Document Document ConsumerConsumer

Document Document RepositoryRepository

Document Document SourceSource

Patient Identity Feed [ITI-8]Patient Identity Feed HL7v3

Registry Stored Query [ITI-18]

Register Document Set-b

Retrieve Document Set

Provide and Register Document Set-b

Integrated Document Source/Repository

8

Changes in Actor Behavior

• Document Repository populates repositoryUniqueId before calling Register Document Set-b

• Document Registry can support either Patient Identity Feed HL7v2 or HL7v3 or both to accommodate different scenarios and requirement

• Document Consumer needs to resolve the Document Repository endpoint before invoking the Retrieve Document Set transaction– Enables use of proxies for multiple Document

Repositories

9

XDS.b Transactions

• All transactions reference ebXML Registry Information Model 3.0

• All transactions support SOAP 1.2– Optionally support SOAP 1.1

• All transactions support WS-Addressing

• All transactions have WSDL defined– Appendix V: one WSDL per Actor per

Integration Profile

10

Changes in Transactions

• New XML schema types are defined – Provide and Register Document Set-b

Request– Retrieve Document Set

Request/Response

• Document content is within the s:Body in an element of type xs:base64Binary for MTOM support

11

12

Provide and Register Document Set-bRequest

Enables support for MTOM

Enables support for MTOM

Same document metadata as

XDS.a

Same document metadata as

XDS.a

Links the document to its

metadata

Links the document to its

metadata

13

Retrieve Document SetRequest

Support for Cross

Community Access (XCA)

Support for Cross

Community Access (XCA)

Retrieve any number of documents

Retrieve any number of documents

Enables Consumer to bind to actual Web Service

Enables Consumer to bind to actual Web Service

14

Retrieve Document SetResponse

Error messages consistent with

ebRS 3.0

Error messages consistent with

ebRS 3.0

Retrieve any number of documents

Retrieve any number of documents

Links to Registry Response

Links to Registry Response

XDS.b Document RegistryWeb Services Definitions

Transaction s:Body wsaw:Action (*)

Register Document Set-b Request lcm:SubmitObjectRequest urn:ihe:iti:2007:RegisterDocumentSet-b

Register Document Set-b Response

rs:RegistryResponse urn:ihe:iti:2007:RegisterDocumentSet-bResponse

Registry Stored Query Request query:AdhocQueryRequest urn:ihe:iti:2007:RegistryStoredQuery

Registry Stored Query Response query:AdhocQueryResponse urn:ihe:iti:2007:RegistryStoredQueryResponse

Patient Registry Record Added Request

hl7:PRPA_IN201301UV urn:hl7-org:v3:PRPA_IN201301UV

Patient Registry Record Revised Request

hl7:PRPA_IN201302UV urn:hl7-org:v3:PRPA_IN201302UV

Patient Registry Duplicates Resolved Request

hl7:PRPA_IN201304UV urn:hl7-org:v3:PRPA_IN201304UV

Patient Registry Transactions Response

hl7:MCCI_IN000002UV urn:hl7-org:v3:MCCI_IN000002UV

15(*) Namespaces presented on multiple lines for readability purposes

XDS.b Document RepositoryWeb Services Definitions

Transaction s:Body wsaw:Action (*)

Provide and Register Document Set-b Request

ihe:ProvideAndRegisterDocumentSetRequest urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b

Provide and Register Document Set-b Response

rs:RegistryResponse urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse

Retrieve Document Set Request

ihe:RetrieveDocumentSetRequest urn:ihe:iti:2007:RetrieveDocumentSet

Retrieve Document Set Response

ihe:RetrieveDocumentSetResponse urn:ihe:iti:2007:RetrieveDocumentSetResponse

16(*) Namespaces presented on multiple lines for readability purposes

Retrieve Document Set Request Sample

18

Support for WS-Addressing

Support for WS-Addressing

Synchronous request

Synchronous request

Retrieve Document Set Response

19

Use of appropriate WSA

action

Use of appropriate WSA

action

Indicates reply to previous message

Indicates reply to previous message

Tips and Tricks

• When generating Web Services proxy/stubs, evaluate using a development WSDL– Replaces typed definitions with un-typed

XML

• MTOM gives you binary attachments for free– Supports composition with WS-Security,

WS-Reliable Messaging

20

Sample C# Code

21

[ServiceContract(Namespace = "urn:ihe:iti:xds-b:2007", Name = "XDSRepository")]

public interface IXdsDocumentRepository{ [OperationContract(

Action = "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-b",ReplyAction = "urn:ihe:iti:2007:ProvideAndRegisterDocumentSet-bResponse")]

Message ProvideAndRegisterDocumentSet(Message input);

[OperationContract(Action = "urn:ihe:iti:2007:RetrieveDocumentSet",ReplyAction = "urn:ihe:iti:2007:RetrieveDocumentSetResponse")]

Message RetrieveDocumentSet(Message input);

}

Use appropriate namespace and

WSDL name

Use appropriate namespace and

WSDL nameDefine WS-

Addressing Actions for both Request and

Response

Define WS-Addressing Actions

for both Request and Response

Evaluate use of un-typed development

WSDL

Evaluate use of un-typed development

WSDL

What’s Next for XDS.b

• Cross Community Access (XCA) composes with XDS.b

• Cross-Enterprise User Assertion (XUA) composes with XDS.b via WS-Security 1.1

22

Thank You!

For questions:

roberto.ruggeri@microsoft.com

ititech@rsna.org