ATS 5820:2010

$36.40

E-health web services profiles

Published By	Publication Date	Number of Pages
AS	2010-03-05	81

Guaranteed Safe Checkout

Category: AS

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

Description

Defines profiles of the SOAP Web services specifications. It defines a base set of specifications for Web services, so that interoperable Web services can be defined for e-health. It also defines profiles for securing the Web services transport.

Scope

This Technical Specification defines profiles of the SOAP Web services specifications. It defines a base set of specifications for Web services, so that interoperable Web services can be defined for e-health. It also defines profiles for securing the Web services transport.
This Technical Specification does not define any service interfaces. The profiles in this document can only be implemented when there is a service interface specification, but this document does not define any. Each service interface is defined to meet a specific set of requirements, and it is outside the scope of this document to know what those requirements might be. Instead, these profiles provide a set of mechanisms that the service interface author can use to meet their particular requirements.
The profiles defined in this Technical Specification have been designed with the goal of achieving interconnectivity between implementations using Web services toolkits. Compared to the Web services specifications and other Web services profiles, it provides details that improve interconnectivity. For example, a comparison between this Technical Specifications and how the Integrating the Healthcare Enterprise (IHE) specifies Web services is shown in Appendix B.
Intended audience
This Technical Specification is intended for:
(a) Authors of service interface specifications, who incorporate the profiles into the service interface specifications they produce.
(b) Solution architects, who incorporate the service interface specifications into the system specifications they design.
(c) Software developers, who create software programs which conform to the system specification and service interface specification.
NOTE: Developers will usually use existing toolkit or libraries to implement Web services and the security mechanisms. They will not normally implement them from scratch.
(d) Conformance testers, who test software to determine how it conforms to the service interface specifications and the profiles that it uses.
The primary user of these profiles is the service interface specification author. The solution architects, software developers and conformance testers use these profiles because they are referenced by the service interface specifications they are working with.
The reader is expected to have a detailed knowledge of SOAP Web services, WSDL, WS-Addressing, WS-Policy, TLS, WS-Security and PKI.