Presentation is loading. Please wait.

Presentation is loading. Please wait.

XDS.b (Cross-Enterprise Document Sharing)

Similar presentations


Presentation on theme: "XDS.b (Cross-Enterprise Document Sharing)"— Presentation transcript:

1 XDS.b (Cross-Enterprise Document Sharing)
Sungkee Lee

2 Agenda XDS.b Overview Register Document Set-b [ITI-42]
Retrieve Document Set [ITI-43] Registry Stored Query [ITI-18]

3 XDS.b ITI TF-1 Ch. 10 10.1 Actors/Transactions
XDS Document Contents Support 10.2 Integration Profile Options XDS Document Registry Data Model 10.5 Implementation Strategies

4 XDS.b Actors and Transactions
INFINITT Insung INFINITT GNSK MedicalStandard ezCaretech UCareSoft ezCaretech Insung INFINITT GNSK MedicalStandard ezCaretech

5 XDS.b Actors and Transactions

6 XDS.b Actors Document Source Document Repository Document Registry
Source of documents and metadata about documents Document Repository Stores documents, requests indexing in Document Registry, supports retrieval Document Registry Indexes documents, supports search Patient Identity Source Feeds identity of known patients to Document Registry Document Consumer Initiates search and retrieval for consumer of documents

7 Patient Identity Source
Patient Registration Patient Identity Source Patient Identity Feed Document Registry

8 Provide and Register Document Set
Document Submission Document Registry Register Document Set Provide and Register Document Set Document Source Document Repository

9 Query and Retrieve Query Documents Document Registry Document Consumer
Retrieve Document Document Repository

10 XDS Document Contents Support

11 Integration Profile Options

12 XDS Registry Data Model Entities
XDS Document Entry XDS Document XDS Folder XDS Submission Set XDS Submission Request

13 XDS Registry Submission Request

14 XDS Registry Submission Request

15 XDS Document Registry Data Model

16 XDS.b Implementation Strategies
Strategy 1 : Repository at the Source

17 XDS.b Implementation Strategies
Strategy 2 : Third Party Repository

18 XDS.b Implementation Strategies
Strategy 3 : Direct Patient Transfer-Referral

19 Register Document Set-b [ITI-42]
ITI TF-2b 3.42 Scope Use Case Roles Referenced Standards Interaction Diagram Register Document Set-b Request Register Document Set-b Response Protocol Requirements Sample Register Document Set-b SOAP Request Sample Register Document Set-b SOAP Response Message Semantics Security Considerations

20 Register Document Set-b [ITI-42]
Scope Metadata describing zero or more documents XDS Submission Set definition along with the linkage to new documents and references to existing documents An optional XDS Folder definitions along with linkage to new or existing documents

21 Register Document Set-b [ITI-42]
Use Case Roles

22 Register Document Set-b [ITI-42]
Referenced Standards ebRIM OASIS/ebXML Registry Information Model v3.0 ebRS OASIS/ebXML Registry Services Specifications v3.0 HL7v2 HL7 Version 2.5 Appendix V ITI TF-2x: Appendix V Web Services for IHE Transactions Contains references to all Web Services standards and requirements of use

23 Register Document Set-b [ITI-42]
Interaction Diagram

24 Register Document Set-b [ITI-42]
Protocol Requirements ITI TF-2x Appendix V: Web Services SOAP 1.2 ftp://ftp.ihe.net/TF_Implementation_Material/ITI/ WSDL schema examples

25 Message Structure SOAP Message ebXML Message

26 Sample Register Document Set-b SOAP Request
<s:Envelope xmlns:s= xmlns:a=" <s:Header> <a:Action s:mustUnderstand="1">urn:ihe:iti:2007:RegisterDocumentSet-b</a:Action> <a:MessageID>urn:uuid:1ec52e14-4aad-4ba1-b7d3-fc9812a21340</a:MessageID> <a:ReplyTo> <a:Address> </a:ReplyTo s:mustUnderstand="1"> <a:To > </s:Header> <s:Body> <lcm:SubmitObjectsRequest xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"> <!—Rest of SubmitObjectsRequest message goes here --> </lcm:SubmitObjectsRequest> </s:Body> </s:Envelope>

27 Sample Register Document Set-b SOAP Response
<s:Envelope xmlns:s=" xmlns:a=" <s:Header> <a:Action s:mustUnderstand="1">urn:ihe:iti:2007:RegisterDocumentSet-bResponse </a:Action> <a:RelatesTo>urn:uuid:1ec52e14-4aad-4ba1-b7d3-fc9812a21340</a:RelatesTo> </s:Header> <s:Body> <rs:RegistryResponse status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"/> </s:Body> </s:Envelope>

28 Register Document Set-b [ITI-42]
Message Semantics ITI TF-3 4.1 4.1.7 Document Definition Metadata 4.1.8 Submission Set Metadata

29 Retrieve Document Set [ITI-43]
ITI TF-2b 3.43 Scope Use Case Roles Referenced Standard Interaction Diagram Retrieve Document Set Request Retrieve Document Set Response Protocol Requirements Sample Retrieve Document Set SOAP Request Sample Retrieve Document Set SOAP Response Message Semantics Security Considerations

30 Retrieve Document Set [ITI-43]
Scope Obtains the following Ids from Document Registry XDSDocumentEntry uniqueId Document Repository repositoryUniqueId

31 Retrieve Document Set [ITI-43]
Use Case Roles

32 Retrieve Document Set [ITI-43]
Referenced Standard ebRIM OASIS/ebXML Registry Information Model v3.0 ebRS OASIS/ebXML Registry Services Specifications v3.0 Appendix V ITI TF-2x: Appendix V Web Services for IHE Transactions Contains references to all Web Services standards and requirements of use MTOM SOAP Message Transmission Optimization Mechanism XOP XML-binary Optimized Packaging

33 Retrieve Document Set [ITI-43]
Interaction Diagram

34 Retrieve Document Set [ITI-43]
Protocol Requirements ITI TF-2x Appendix V: Web Services SOAP 1.2 MTOM/XOP Message Transmission Optimization Mechanism XML-binary Optimized Packaging ftp://ftp.ihe.net/TF_Implementation_Material/ITI/ WSDL schema examples

35 Sample Retrieve Document Set SOAP Request
POST /tf6/services/xdsrepositoryb HTTP/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_DCD262C64C22DB ; type="application/xop+xml"; start-info="application/soap+xml"; action="urn:ihe:iti:2007:RetrieveDocumentSet" User-Agent: Axis2 Host: localhost: MIMEBoundaryurn_uuid_DCD262C64C22DB Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml" Content-Transfer-Encoding: binary 2945 Content-ID: <?xml version='1.0' encoding='UTF-8'?> <soapenv:Envelope xmlns:soapenv= <!—Rest of SOAP message goes here --> </soapenv:Envelope> --MIMEBoundaryurn_uuid_DCD262C64C22DB —

36 Sample Retrieve Document Set SOAP Request
<soapenv:Envelope xmlns:soapenv=" xmlns:wsa=" <soapenv:Header> <wsa:To> <wsa:MessageID>urn:uuid:DCD262C64C22DB </wsa:MessageID> <wsa:Action>urn:ihe:iti:2007:RetrieveDocumentSet</wsa:Action> </soapenv:Header> <soapenv:Body> <RetrieveDocumentSetRequest xmlns="urn:ihe:iti:xds-b:2007" xmlns:xsi=" <DocumentRequest> <RepositoryUniqueId> </RepositoryUniqueId> <DocumentUniqueId> </DocumentUniqueId> </DocumentRequest> </RetrieveDocumentSetRequest> </soapenv:Body> </soapenv:Envelope>

37 Retrieve Document Set Response Message Structure
SOAP Message ebXML Message CDA Document

38 Sample Retrieve Document Set SOAP Response
HTTP/ OK Server: Apache-Coyote/1.1 Content-Type: multipart/related; boundary=MIMEBoundaryurn_uuid_F862C3E04D9E35266C ; type="application/xop+xml"; start-info="application/soap+xml"; action="urn:ihe:iti:2007:RetrieveDocumentSetResponse" Date: Fri, 23 Oct :19:11 GMT 2975 --MIMEBoundaryurn_uuid_F862C3E04D9E35266C Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml" Content-Transfer-Encoding: binary Content-ID: <?xml version='1.0' encoding='UTF-8'?> <soapenv:Envelope xmlns:soapenv=" <!—Rest of SOAP message goes here --> </soapenv:Envelope> Content-Type: application/octet-stream Content-ID: This is the content of the document. --MIMEBoundaryurn_uuid_F862C3E04D9E35266C —

39 Sample Retrieve Document Set SOAP Response
<soapenv:Envelope xmlns:soapenv=" xmlns:wsa=" <soapenv:Header> 2985 <wsa:Action>urn:ihe:iti:2007:RetrieveDocumentSetResponse</wsa:Action> <wsa:RelatesTo>urn:uuid:DCD262C64C22DB </wsa:RelatesTo> </soapenv:Header> <soapenv:Body> <xdsb:RetrieveDocumentSetResponse xmlns:xdsb="urn:ihe:iti:xds-b:2007"> <rs:RegistryResponse xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0" status="urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Success"/> <xdsb:DocumentResponse> <xdsb:RepositoryUniqueId> </xdsb:RepositoryUniqueId> <xdsb:DocumentUniqueId> </xdsb:DocumentUniqueId> <xdsb:mimeType>application/pdf</xdsb:mimeType> <xdsb:Document> <xop:Include xmlns:xop=" </xdsb:Document> </xdsb:DocumentResponse> </xdsb:RetrieveDocumentSetResponse> </soapenv:Body> </soapenv:Envelope>

40 Retrieve Document Set [ITI-43]
Message Semantics ITI TF-3 4.1

41 Registry Stored Query [ITI-18]
ITI TF-2a 3.18 Scope Use Case Roles Referenced Standards Interaction Diagram Web Services Transport Sample Registry Stored Query SOAP Request Sample Registry Stored Query SOAP Response Sample Query Request Sample Query Response Security Considerations

42 Registry Stored Query [ITI-18]
Scope Query by patient (Id) for a time interval, by document type(s), by practice setting(s), by author person Query by Document Source Query for XDS Folders updated during a time interval Query for all documents in a Folder or Submission Set Query by time of submission All queries return: Metadata for one or more registry objects, or Object references for one or more registry objects (registry UUIDs)

43 Registry Stored Query [ITI-18]
Use Case Roles

44 Registry Stored Query [ITI-18]
Referenced Standards ebRIM OASIS/ebXML Registry Information Model v3.0 ebRS OASIS/ebXML Registry Services Specifications v3.0 HL7v2 HL7 Version 2.5 Appendix V ITI TF-2x: Appendix V Web Services for IHE Transactions Contains references to all Web Services standards and requirements of use

45 Registry Stored Query [ITI-18]
Interaction Diagram

46 Registry Stored Query [ITI-18]
Web Services Transport ITI TF-2x Appendix V: Web Services SOAP 1.2 ftp://ftp.ihe.net/TF_Implementation_Material/ITI/ WSDL schema examples

47 Sample Registry Stored Query SOAP Request
<s:Envelope xmlns:s= xmlns:a=" <s:Header> <a:Action s:mustUnderstand="1">urn:ihe:iti:2007:RegistryStoredQuery</a:Action> <a:MessageID>urn:uuid:def119ad-dc13-49c1-a3c7-e f9b3</a:MessageID> <a:ReplyTo s:mustUnderstand="1">> <a:Address> </a:ReplyTo> <a:To> </s:Header> <s:Body> <query:AdhocQueryRequest <!—Rest of Query message goes here --> </query:AdhocQueryRequest> </s:Body> </s:Envelope>

48 Sample Registry Stored Query SOAP Request
<query:AdhocQueryRequest xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0" xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:3.0" xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0"> <query:ResponseOption returnComposedObjects="true" returnType="LeafClass"/> <rim:AdhocQuery id=" urn:uuid:14d4debf-8f a74-a90016b0af0d "> <rim:Slot name="$XDSDocumentEntryPatientId"> <rim:ValueList><rim:Value>‟st ^^^& &ISO‟</rim:Value> </rim:ValueList></rim:Slot> <rim:Slot name="$XDSDocumentEntryStatus"> <rim:ValueList><rim:Value>('urn:oasis:names:tc:ebxml-regrep:ResponseStatusType:Approved')</rim:Value> <rim:Slot name="$XDSDocumentEntryCreationTimeFrom"> <rim:ValueList><rim:Value> </rim:Value> <rim:Slot name="$XDSDocumentEntryCreationTimeTo"> <rim:ValueList><rim:Value> </rim:Value> <rim:Slot name="$XDSDocumentEntryHealthcareFacilityTypeCode"> <rim:ValueList><rim:Value>(„Emergency Department‟)</rim:Value> </rim:AdhocQuery> </query:AdhocQueryRequest>

49 Sample Registry Stored Query SOAP Response
<s:Envelope xmlns:s=" xmlns:a=" <s:Header> <a:Action s:mustUnderstand="1">urn:ihe:iti:2007:RegistryStoredQueryResponse</a:Action> <a:RelatesTo>urn:uuid:def119ad-dc13-49c1-a3c7-e f9b3</a:RelatesTo> </s:Header> <s:Body> <query:AdhocQueryResponse xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:3.0"/> </s:Body> </s:Envelope>

50 Patient Identity Feed [ITI-8]
ITI TF-2a 3.8

51 Q & A


Download ppt "XDS.b (Cross-Enterprise Document Sharing)"

Similar presentations


Ads by Google