1. Web Services Transactions
Vassil Peytchev, Epic

2. WS Overview What are Web Services? Why Web Services transactions?
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

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

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

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

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

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

8. Example: Adding Addressing
<soap:Envelope ...> <soap:Header> <wsa:MessageID> uuid:aaaabbbb-cccc-dddd-eeee-ffffffffffff </wsa:MessageID> <wsa:ReplyTo> <wsa:Address> </wsa:Address> </wsa:ReplyTo> <wsa:To> <wsa:Action>urn:hl7-org:v3:PRPA_IN101201</wsa:Action> </soap:Header> <soap:Body> <PRPA_IN xmlns="urn:hl7-org:v3" ...> </PRPA_IN101201> </soap:Body> </soap:Envelope>

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