1. Cross-Enterprise Document Sharing-b (XDS.b)
Slides prepared by
Roberto Ruggeri, XDS.b
Slides Presented by
Vassil Peytchev, PIX/PDQ v3, Appendix V

2. 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

3. 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

4. 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

5. 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]

6. 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

7. 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

8. XDS.b Actors and Transactions
Patient Identity Source
Patient Identity Feed [ITI-8]
Patient Identity Feed HL7v3
Registry Stored Query [ITI-18]
Document Registry
Document Consumer
Register Document Set-b
Provide and Register Document Set-b
Document Source
Document Repository
Retrieve Document Set
Integrated Document Source/Repository

9. 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

10. 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

11. 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

12. Provide and Register Document Set-b Request
Same document metadata as XDS.a
Links the document to its metadata
Enables support for MTOM

13. Retrieve Document Set Request
Support for Cross Community Access (XCA)
Retrieve any number of documents
Enables Consumer to bind to actual Web Service

14. Retrieve Document Set Response
Error messages consistent with ebRS 3.0
Retrieve any number of documents
Links to Registry Response

15. XDS.b Document Registry Web 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
(*) Namespaces presented on multiple lines for readability purposes

16. XDS.b Document Repository Web 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-b Response
Retrieve Document Set Request
ihe:RetrieveDocumentSetRequest
urn:ihe:iti:2007: RetrieveDocumentSet
Retrieve Document Set Response
ihe:RetrieveDocumentSetResponse
urn:ihe:iti:2007: RetrieveDocumentSetResponse
(*) Namespaces presented on multiple lines for readability purposes

17. XDS.b Document Registry WSDL XDS.b Document Repository WSDL
Demo
XDS.b Document Registry WSDL
XDS.b Document Repository WSDL

18. Retrieve Document Set Request Sample
<s:Envelope xmlns:s=" xmlns:a="
<s:Header>
<a:Action s:mustUnderstand="1">
urn:ihe:iti:2007:RetrieveDocumentSet
</a:Action>
<a:MessageID>
urn:uuid:80b0b9c6-e bae5-7fcf994a9f25
</a:MessageID>
<a:ReplyTo>
<a:Address>
</a:ReplyTo>
<a:To s:mustUnderstand="1">
</a:To>
</s:Header>
<s:Body>
<RetrieveDocumentSetRequest xmlns="urn:ihe:iti:xds-b:2007"/>
</s:Body>
</s:Envelope>
Support for WS-Addressing
Synchronous request

19. Retrieve Document Set Response
<s:Envelope xmlns:s=" xmlns:a="
<s:Header>
<a:Action s:mustUnderstand="1">
urn:ihe:iti:2007:RetrieveDocumentSetResponse
</a:Action>
<a:RelatesTo>
urn:uuid:80b0b9c6-e bae5-7fcf994a9f25
</a:RelatesTo>
</s:Header>
<s:Body>
<RetrieveDocumentSetResponse xmlns="urn:ihe:iti:xds-b:2007"/>
</s:Body>
</s:Envelope>
Use of appropriate WSA action
Indicates reply to previous message

20. 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

21. Sample C# Code Use appropriate namespace and WSDL name
Define WS-Addressing Actions for both Request and Response
[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);
Action = "urn:ihe:iti:2007:RetrieveDocumentSet",
ReplyAction = "urn:ihe:iti:2007:RetrieveDocumentSetResponse")]
Message RetrieveDocumentSet(Message input); }
Evaluate use of un-typed development WSDL

22. 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

23. For questions: roberto.ruggeri@microsoft.com ititech@rsna.org
Thank You!
For questions: