On the one hand, Web services are increasingly gaining attention. Standardization efforts have improved their stability and range of applications. Composition and coordination techniques for Web services enable an application integration effort beyond loosely coupled systems. On the other hand, medical Web services are covered by the DICOM and HL7 communication protocols and are profiled by the IHE (Integrating the Healthcare Enterprise) technical framework. Standardization is more extensive, most workflows are well defined, and integration is tighter than in most other domains. Nevertheless, so far standardization focused on conventional workflow systems. In an Internet-based medical environment with high security standards, communication is strongly restricted and conventional systems fail to deliver. This paper proposes a modeling process for medical Web services. The IHE patient administration process flow serves as a well defined example. Furthermore, the paper defines requirements of a Web service based middleware for the execution of medical Web services by investigating currently relevant Web service protocols. The technique should enable building medical applications for Internet-based workflow execution. Finally, Biztalk 2004 is used to evaluate the implementation of the analyzed sample functionality.

Abstract. With the advent of Web services and orchestration specifications like BPEL it is possible to define workflows on an Internet-scale. In the health-care domain highly structured and well defined workflows have been specified in standard documents. To reduce the complexity of creating Web service orchestration specifications, we provide a model-driven design approach, consisting of manual and automatic transformations. Security and transaction requirements are covered additionally. The resulting Web services can be bound dynamically at run-time. Therefore, we gain the flexibility to integrate processes that are already established with specific business protocols. Parts of this approach should be applicable to other domains, too.

Abstract. On the one hand Web services are gaining increasing attention. A lot of standardization has improved their stability and range of application. Composition and coordination techniques for Web services enable an application integration effort beyond loosely coupled systems. On the other hand medical e-services are covered by the DICOM and HL7 communication protocols and profiled by the IHE (Integrating the Healthcare Enterprise) technical framework. Standardization is more extensive, most workflows are well defined and integration is tighter than in most other domains. Nevertheless standardization focused on conventional workflow systems. In an Internetbased medical environment with high security standards, communication is strongly restricted and conventional systems fail to deliver. This paper proposes a modeling process for medical Web services. The IHE patient administration process flow serves as a well defined example. Furthermore, the paper defines requirements of a Web service based middleware for the execution of medical e-services. The technique should enable building integrated medical applications for Internet-based workflow execution.

Web-Services can be seen as a newly emerging distributed computing model for the Web. They cater for the need to establish business-to-business (B2B) interactions on the Web. WebServices consider a loosely coupled component model encapsulating business logic and interact with other components using XML protocols. Based on one case study, this paper discusses architectural issues and requirements for software configuration, distribution, and deployment of web-services. General TermsDesign

Web-Services can be seen as a newly emerging distributed computing model for the Web. They cater for the need to establish business-to-business (B2B) interactions on the Web. WebServices consider a loosely coupled component model encapsulating business logic and interact with other components using XML protocols. Based on one case study, this paper discusses architectural issues and requirements for software configuration, distribution, and deployment of web-services. General TermsDesign