Modeling and implementing medical Web services

Abstract

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.

Design and Implementation of an Ontology-Based Clinical Reminder System to Support Chronic Disease Healthcare

“…Service-oriented architectures (SOA), i.e. Web service, offers a framework and implementation that promotes interoperability, integration and reuse of data and functionalities that has potentials of being applied to the healthcare domain [14], [15]. We adopted the Web service architecture in implementing clinical reminder system as a medical knowledge service.…”

Semi-automatic Generation of Web Services and BPEL Processes – A Model-Driven Approach

“…Therefore, the table also lists the mapping between message attributes and BPEL sections and tags. Conversions of IHE activity diagrams into BPEL flows have been covered in detail in an earlier paper (see [7]). There is also a paper that covers UML conversions in general [22].…”

“…Substep 4: Apply security requirements: Next, security requirements between business partners are defined. In [8] we defined security zones and boundaries to represent groups of applications that trust each other. The organizational trust information might be modelled using WS-Trust and stored globally in a database for all modelled processes.…”

Sharing of Medical Information on Cloud Platform-A Review

“…The records can be shared by the patient with any stockholders interested in those. In [23], authors proposed a modeling process for medical web service, furthermore they defines requirements of a web service based middleware for the execution of medical web service basis protocols. They also focused on the composition of web service using BPEL and define requirements to model IHE transactions as medical web service.…”