Vassil peytchev epic
This presentation is the property of its rightful owner.
Sponsored Links
1 / 10

Web Services Transactions PowerPoint PPT Presentation


  • 98 Views
  • Uploaded on
  • Presentation posted in: General

Vassil Peytchev, Epic. Web Services Transactions. WS Overview. What are Web Services? SOAP XML transactions WSDL description of services Why Web Services transactions? Improve ease of implementation Common transaction infrastructure Built-in security Extensibility

Download Presentation

Web Services Transactions

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Vassil peytchev epic

Vassil Peytchev, Epic

Web Services Transactions


Ws overview

WS Overview

What are Web Services?

SOAP XML transactions

WSDL description of services

Why Web Services transactions?

Improve ease of implementation

Common transaction infrastructure

Built-in security

Extensibility

Long term benefits, long term plans


2006 2007 use of ws

2006 – 2007 use of WS

PIX/PDQ HL7 V3

XDS Stored Query

White Paper on WS Roadmap?

Versions of standards

SOAP 1.1 (possibly SOAP 1.2 binding as an option)

WSDL 1.1

WS-I Basic Profile 1.1

WS-I SOAP Binding 1.0

WS-Addressing


How to incorporate ws transactions in the iti framework

How to incorporate WS transactions in the ITI framework

Add the WS requirements to the individual transactions

Add the WS requirements as separate transactions

Provide WS requirements in an Appendix.

Mix and match


Current approaches

Current approaches

ATNA specifies the syslog transport mechanism by referring to the RFCs

Transactions in XDS include the SOAP envelope and describe protocol binding

HL7 V2.x transactions don’t specify an underlying protocol (assume HL7 MLLP)


Specific approaches pdq pix

Specific Approaches: PDQ/PIX

PDQ/PIX – reuse the HL7 WS profile

Basic Profile – very simple SOAP envelope

Addressing profile – adds end-point information

Security profile – future use (currently security is handled through ATNA)

Include the SOAP requirements within the transaction description

Wrapper in V3 – is it stable enough?

Add WSDL in an Appendix


Example basic profile

Example – Basic Profile

<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="..." xmlns:hl7="..." ...> <soap:Body> <PRPA_IN101201 xmlns="urn:hl7-org:v3"> ... </PRPA_IN101201> </soap:Body></soap:Envelope>


Example adding addressing

Example: Adding Addressing

<soap:Envelope ...> <soap:Header> <wsa:MessageID> uuid:aaaabbbb-cccc-dddd-eeee-ffffffffffff </wsa:MessageID> <wsa:ReplyTo> <wsa:Address>http://placerlocation/PRPA_AR101201 </wsa:Address> </wsa:ReplyTo> <wsa:To>http://fulfillerlocation/PRPA_AR101202</wsa:To> <wsa:Action>urn:hl7-org:v3:PRPA_IN101201</wsa:Action> ... </soap:Header> <soap:Body> <PRPA_IN101201 xmlns="urn:hl7-org:v3" ...> ... </PRPA_IN101201> </soap:Body></soap:Envelope>


Specific approaches xds stored query

Specific Approaches: XDS Stored Query

Starting point: WSDL for ebXML registry services v 3.0

Constrain to only XDS Stored Query

Constrain to satisfy WS-I Basic Profile

Add WS-Addressing constraints

Bring in line with the PDQ/PIX approach

Keep the SOAP requirements as part of the transaction

Add constrained WSDL to an Appendix


  • Login