2 WS Overview What are Web Services? Why Web Services transactions? SOAP XML transactionsWSDL description of servicesWhy Web Services transactions?Improve ease of implementationCommon transaction infrastructureBuilt-in securityExtensibilityLong 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 standardsSOAP 1.1 (possibly SOAP 1.2 binding as an option)WSDL 1.1WS-I Basic Profile 1.1WS-I SOAP Binding 1.0WS-Addressing
4 How to incorporate WS transactions in the ITI framework Add the WS requirements to the individual transactionsAdd the WS requirements as separate transactionsProvide WS requirements in an Appendix.Mix and match
5 Current approachesATNA specifies the syslog transport mechanism by referring to the RFCsTransactions in XDS include the SOAP envelope and describe protocol bindingHL7 V2.x transactions don’t specify an underlying protocol (assume HL7 MLLP)
6 Specific Approaches: PDQ/PIX PDQ/PIX – reuse the HL7 WS profileBasic Profile – very simple SOAP envelopeAddressing profile – adds end-point informationSecurity profile – future use (currently security is handled through ATNA)Include the SOAP requirements within the transaction descriptionWrapper in V3 – is it stable enough?Add WSDL in an Appendix
9 Specific Approaches: XDS Stored Query Starting point: WSDL for ebXML registry services v 3.0Constrain to only XDS Stored QueryConstrain to satisfy WS-I Basic ProfileAdd WS-Addressing constraintsBring in line with the PDQ/PIX approachKeep the SOAP requirements as part of the transactionAdd constrained WSDL to an Appendix
Your consent to our cookies if you continue to use this website.