<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Loosely-Coupled Process Automation in Medical Environments</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>CAiSE'</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Doctoral Consortium</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Departement of Informatics, University of Zurich</institution>
          ,
          <addr-line>Binzmuhlestr. 14, 8050 Zurich</addr-line>
          ,
          <country country="CH">Switzerland</country>
        </aff>
      </contrib-group>
      <fpage>1185</fpage>
      <lpage>1192</lpage>
      <abstract>
        <p>We discuss a case study for the hospital scenario where work°ow model components are distributed across various computers or devices (e.g. mobile phones, PDAs, sensors, RFID tags). By using the concept of loosely-coupled processes we want to enable computerization of manually performed ad hoc medical tasks. That could decrease time, cost and resource consumption in a hospital. The challenges of loosely coupled process composition include: the requirement to manage °exibly the process logic, the need to overcome a heterogeneous software and hardware environment, and the management of the application domain (e.g. structure of organization, resources). The main question we address is what are the functional limitations and possibilities of current process composition approaches? In response to this question we describe and discuss the capabilities of Web service technologies. In addition, we sketch a plan to overcome these limitations. Finally, we propose a process composition approach based on BPEL4WS engine that satis¯es medical scenario requirements.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        Healthcare is one of the most complex and dynamic environments [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Its
complexity is related to the heterogeneity of medical processes, resource
management, frequently changing patient conditions, time constraints, variety of
medical records, and hospital organization structure. Traditional process-oriented
information systems support only homogeneous application-to-application or
application-to-consumer communication that operate over relatively simple
process execution schemes. These systems mainly support production work°ow
coordination with limited process composition and manipulation at run time [
        <xref ref-type="bibr" rid="ref14 ref2">2,
14</xref>
        ]. Interactions between heterogeneous distributed applications and processes
or sub-processes, via heterogeneous interfaces, can not be freely and quickly
established. In addition, any process-oriented system cannot support various (e.g.
relatively short) heterogeneous dynamic processes with distributed process logic
components that contain real-time constraints and frequent human interactions
[
        <xref ref-type="bibr" rid="ref1 ref8">1, 8</xref>
        ]. In Figure 1 we present an application scenario that illustrates the
composition and coordination complexity of processes that often occur in a medical
environment. The complexities relate to the work°ow composition semantics,
sub-process mapping, heterogeneous nature of tasks, composition veri¯cation,
and actors in a distributed environment. Each process (e.g. examination) may
consist of various heterogeneous distributed tasks. That makes it di±cult to
provide a fully automated system. In addition, issues like privacy or security should
be considered.
      </p>
      <p>Patients</p>
      <p>Consultation
Treatment</p>
      <p>Prescription
Medicine</p>
      <p>PDA,
Prescriptions</p>
      <p>Examination 2</p>
      <p>Examination 1</p>
      <p>Laboratory</p>
      <p>Workflow Engine
Workflow Engine:
Process Composition/
Semi-Automated
Treatment</p>
      <p>Investigation</p>
      <p>Laboratory
Examination 3</p>
      <p>Diagnosis Workflow</p>
      <p>Engine</p>
      <p>Prescription</p>
      <p>
        Process composition models based on message exchange (BPEL4WS,
ENSEMBLE, XLANG, Oracle BPEL, SAP) [
        <xref ref-type="bibr" rid="ref13 ref18 ref9">9, 18, 13</xref>
        ] require additional
speci¯cations to enable dynamic process interactions. Those standards will be described
in Section 2. Each process potentially consists of subparts that could operate
as autonomous units and perform distributed tasks. For instance, a diagnosis
in Fig.1 consists of a patient examination, patient health test, and diagnosis
generation. These sub processes could be reused by other applications (e.g.
consultation or examination). The full description of a process must de¯ne not only
the behavior of each participant, but the matching of sub process patterns, to
produce the overall process coordination.
      </p>
      <p>
        The main goal of our work is to provide business process composition and
coordination at run-time without the underlying coding complexities involved in
integrating and modifying the process model structure. We postulate that the
work°ow engine should be able to "read" these process models and execute them
in a platform independent manner. Our main motivation is to provide a highly
automated system for medical institutions that would enable various services
such as diagnosis, examinations and health monitoring using various devices
(e.g. for temperature, heart, and blood measurements)[
        <xref ref-type="bibr" rid="ref16">16</xref>
        ]. One of the available
perspectives is to look at how process logic (e.g. application) is distributed and
implemented. This will allow us to identify work°ow engine requirements where
process components are distributed on various computers and devices (e.g.
mobile devices, PDAs, sensors). Up till now most process-oriented systems, either
commercial products or research prototypes, support processes that mainly run
on centralized systems [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. In our work, processes are performed as autonomous
units and at the same time can invoke other heterogeneous distributed processes
to form a new process unit. This generates complex process control °ow
coordination and composition schemes.
      </p>
      <p>
        This paper investigates service-oriented technologies and outlines work°ow
engine requirements which could ensure dynamic health care process
composition. We start with a discussion of process composition technologies (Web
services). We identify the list of medical process features that require additional
work°ow engine functionalities. Section 3 summarizes the main requirements
of message-based work°ow engines [
        <xref ref-type="bibr" rid="ref13 ref22">22, 13</xref>
        ]. Then, we propose an approach for
extending the process execution paradigm [
        <xref ref-type="bibr" rid="ref19">19</xref>
        ]. Section 4 outlines the work to
be performed during this PhD and the research methodology we are planing to
employ.
2
      </p>
    </sec>
    <sec id="sec-2">
      <title>Background</title>
      <p>
        In this section a number of di®erent research projects and systems are studied
and some of the relevant issues in related work are discussed. First, we will de¯ne
the concept of a loosely-coupled process. Then we present research on various
work°ow engines (BPEL4WS, ENSEMBLE, SAP, Oracle BPEL) [
        <xref ref-type="bibr" rid="ref13 ref16 ref19">19, 13, 16</xref>
        ].
Finally, we discuss work°ow engine limitations which motivate the requirement for
the extensions for automation in loosely-coupled processes.
2.1
      </p>
      <sec id="sec-2-1">
        <title>Business Processes in Medical Environments</title>
        <p>
          The concept of a business process ¯nds wide applicability in areas such as
medicine, healthcare or rescue. Even if typically work°ow management systems
were mainly applied for operations in a bank or insurance company, the notion
of business process covers a wide spectrum of tasks. The concept of a business
process or process will be applied without regard to a speci¯c purpose of a task.
In the hospital scenario, Fig.1, a business process may consist of tasks such as
patient condition monitoring, consultation, or history report generation. In this
paper we consider a business process to be a collection of tasks which can be
performed by software systems, people, and groups of people, or a combination
of both [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ].
        </p>
        <p>
          Business processes can be classi¯ed according to repetition rates, business
value or complexity of process logic. In this paper we are focusing on ad hoc [
          <xref ref-type="bibr" rid="ref1">1</xref>
          ]
and loosely-coupled [
          <xref ref-type="bibr" rid="ref15">15</xref>
          ] processes which are prevalent in the medical
environment. The loosely-coupled process concept appeared recently in the content of
distributed system technologies (Web services). It does not have an agreed
de¯nition from the work°ow management technology perspective. This term will be
applied here to identify a collection of logically related tasks that can exchange
data, but can also operate independently. For example, multiple outputs could
be integrated into a single patient health monitoring process as inputs. We
specify the loosely coupled process as a subclass of the business process that might
encapsulate various collections of distributed tasks. A loosely coupled process
di®ers from other business process categories by having the capability to map
various independently implemented distributed tasks across distributed
computers and devices.
2.2
        </p>
        <p>
          Current Work°ow Engines Based on Web Services
Standard work°ow technologies date back to the 1980's and are based on the
Work°ow Coalition Model [
          <xref ref-type="bibr" rid="ref1 ref17 ref3 ref6 ref8">1, 3, 6, 8, 17</xref>
          ]. They were not designed for loosely
coupled process integration and composition in a dynamic environment. Current web
service composition languages including BPEL4WS, WSDL, WSFL, WS-CDL,
BPML, XLANG and WS-CDL [
          <xref ref-type="bibr" rid="ref10 ref12 ref20 ref21">10, 21, 20, 12</xref>
          ] have been developed to address
composition requirements. Some of these languages have well de¯ned
composition, while other provide strong work°ow features. These languages support
the imperative part of services composition, namely exception handling,
compensation and stateful context, and all possess the capability to compose more
complex structures and activities. The control structures of these languages are
su±cient to model sequence, parallel, synchronization, exclusive choice and
simple choice, while the BPEL4WS has the capability to model multiple choice and
synchronization merge. BPEL4WS de¯nes multiple service interactions and the
coordination of imported or exported functionality via web services interactions.
BPEL4WS has more powerful semantics on event handling than BPML. In
transaction and state alignment support, WS-CDL is ahead of BPEL4WS. Security
and reliability is not well handled in all these languages. Most recent approaches
that address interoperability issues of distributed processes and applications
support rather simple application-to-consumer and application-to-application
communication. Web services interact with each other using XML messages [
          <xref ref-type="bibr" rid="ref19 ref4 ref7 ref9">7, 4,
9, 19</xref>
          ]. Communication protocols (SOAP) can be used to transmit XML
messages. The interfaces of web services can be described in WSDL, which de¯nes
the ports that web services can connect-to. However, WSDL does not provide
any information about web service behavior. Process management could be
de¯ned using standards such as BPEL4WS or its predecessor languages, XLANG
and WSFL. However, the process composition, communication, coordination,
validation, veri¯cation and coordination are limited by work°ow engines (e.g.
BPEL4WS) that carry out static interactions. A loosely coupled work°ow
engine typically should assume peer-to-peer message exchanges in synchronous
and asynchronous modes, failure recovery, dynamic process composition with
long-running communications involving many heterogeneous parties. The
process composition models such as process-based, rule-based, transaction-based,
and arti¯cial intelligence-based [
          <xref ref-type="bibr" rid="ref11 ref15 ref18 ref7">15, 18, 11, 7</xref>
          ] are in early stages of development
and can not provide process model recon¯gurations at run-time in a dynamic
heterogeneous environment. In [
          <xref ref-type="bibr" rid="ref13 ref16">13, 16</xref>
          ] recon¯guration involves writing the code
which instructs the messaging engines about the process logic and conditions
for its execution. That limits integration possibilities of new heterogeneous
processes into the work°ow model. In addition, it requires designers to develop new
process model con¯gurations, which is time and cost consuming.
3
        </p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>PhD Proposal</title>
      <p>
        We are going to propose an improved process composition model for loosely
coupled process interaction. It will allow sub process mapping, synthesis,
optimization, and veri¯cation across heterogeneous environments. This approach
will enable extensions of BPEL4WS work°ow engine functionalities. Our model
will allow dynamic recon¯guration of subprocess interaction paths and optimize
resources by applying optimization algorithms. We will perform process
composition based on existing structural patterns supported by BPEL4WS [
        <xref ref-type="bibr" rid="ref22">22</xref>
        ] such
as sequence, loops, or parallel execution is °exible enough to generate complex
medical work°ow models for dynamic compositions [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. However, we are
focusing on work°ow engine extensions which are necessary to execute complex
real-time distributed processes. In Figure 2 we propose extended translation of
medical processes into a work°ow model. This model will provide not only
various medical services but will allow us to modify and integrate new services just
within a few steps. In addition, it could allow process model recon¯guration at
run-time.
3.1
      </p>
      <sec id="sec-3-1">
        <title>Our Main Objectives</title>
        <p>
          Our main target is dynamic composition of adaptive loosely-coupled medical
processes with time constraints. The system should support communication and
the sharing of information among medical personnel. The main goal is to enable
the mapping of distributed heterogeneous processes and provide the right data
to the right personnel at run-time. In addition, we are going to aim for optimal
composition and resource allocation. The system must allow easy recon¯guration
of sub-processes and correct execution °ow if sub-processes can not be executed
within the assigned time. To provide such interactions, °exible work°ow engines
are required. We will specify composition and communication of processes via
message exchange (via HL7) [
          <xref ref-type="bibr" rid="ref13 ref16">13, 16</xref>
          ] between users. One of the main challenges
is business process decomposition into sub processes that should be performed
in a platform-independent manner [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ] at run-time. Additionally, techniques
are required to handle distributed process model data dependencies, coordinate
inputs/outputs, specify exceptional conditions, synchronous and asynchronous
interactions and their consequences including recovery sequences, and to support
multiple nested process units.
3.2
        </p>
        <p>
          Process Composition and Coordination Approach
The primary challenge in a hospital environment is that, unlike in traditional
enterprise work°ow architectures [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ], there is no central authority that manages
the business process composition of participating heterogeneous healthcare
systems. Automated protocol engines [
          <xref ref-type="bibr" rid="ref13 ref19 ref9">9, 13, 19</xref>
          ] are able to track the state of simple
process instances and help enforce protocol correctness in a message °ow. Some
loose coupling is enabled using external protocols that de¯ne the roles of the
participants [
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. However, these protocols can not provide heterogeneous process
composition and communication for distributed mobile parties. Such processes
always involve a number of interactions with more than one heterogeneous
participant.
        </p>
        <p>
          Most of existing message-based engines [
          <xref ref-type="bibr" rid="ref13 ref19 ref9">13, 9, 19</xref>
          ] provide a subset of
composition operations. Such operations include sequential and parallel control °ow
constructs, long running transactions, correlation of messages, handling of
internal and external exceptions, dynamic service referral, and multi role contracts
[
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. These patterns o®er enough °exibility to de¯ne complex process models.
Work°ow engines restrict these execution schemes to rather simple static process
scenarios in order to keep correct execution °ow (BPEL4WS) [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. In addition,
process example diagnosis, as in Figure 1, illustrates the complexity of a
heterogeneous loosely coupled process model. Problems arise when changes must
be applied in a process °ow at run-time. Therefore, a new process composition
approach is required.
        </p>
        <p>We will extend BPEL4WS speci¯cations with additional process composition
features, including real-time and priority constraints applied within transactions,
rules, data sources, medical organization resources (e.g. medical equipment
availability), and access control. We de¯ne work°ow coordination as a process. This
extension is necessary in order to enable communication between processes of a
distributed and heterogeneous nature. Then we will propose a framework where
extended process model is translated to an intermediate representation. That
requires us to consider all execution paths of the de¯ned sub-processes and provide
optimal resource allocation. In addition, heterogeneous data formats should be
processed and mapped. Then, the BPEL4WS script is generated. Due to enriched
roles of personnel and a variety of medical tasks an extensions to the BPEL4WS
execution model will be implemented. Additional optimization is required, which
we apply on top of BPLE4WS scripts. This work will be based on algorithms
that can collect information about all sub-process execution paths, description</p>
        <p>Process
Description</p>
        <p>Designer</p>
        <p>Process Model</p>
        <sec id="sec-3-1-1">
          <title>Extended Process</title>
        </sec>
        <sec id="sec-3-1-2">
          <title>Composition</title>
          <p>Composition Model
Web Service Standarts
BPEL4WS Specifications
Extended Process-based
Composition Model: Time
Constraints, Transactions,
Priorities, Rules.</p>
          <p>Verification
BPEL Process Model</p>
        </sec>
        <sec id="sec-3-1-3">
          <title>Extended BPEL4WS Engine</title>
          <p>Compilation Stage 1
BPEL Script
Internal Model
Reconfiguration/
Optimization Model</p>
          <p>Script {BPEL
script</p>
          <p>MathMod}
Compilation Stage 2
Synthesis
Aggregation
Mapping</p>
        </sec>
        <sec id="sec-3-1-4">
          <title>Services</title>
          <p>Laptop
Propagation
to devices
PC</p>
          <p>PDA
Workflow Model</p>
          <p>Validation
Verification
of run-time modi¯cations, priorities, time constraints, monitored events and
recon¯guration history of the work°ow model. Then, a second compilation stage
will be performed and services provided. In case of failure, the work°ow model
returns to the initial process modeling stage. We believe this model will increase
°exibility of message-based work°ow engine functional capabilities for both static
and real-time operations.
4</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>Discussion, further work and conclusions</title>
      <p>
        The motivating objective for our work is to enable process coordination with
necessary quality-of-service required in a healthcare environment. We have reviewed
existing approaches for loosely coupled process composition. We have proposed
a new approach for process model recon¯guration at run time. We are going to
implement and test extensions of message-based work°ow engines [
        <xref ref-type="bibr" rid="ref13 ref9">9, 13</xref>
        ] that
could provide better distributed sub-process model con¯guration and
composition. We believe this model will increase °exibility of message-based work°ow
engine operations at run-time.
      </p>
      <p>
        In addition, we are considering the integration of processes that could be
easily redesigned by medical personnel without business analyst help.
Semiautomatic process matching engine will be accessed via a graphical interface.
We believe our recon¯guration approach, Fig.2, applied on top of BPEL engine
[
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] will optimize work°ow composition, veri¯cation and resource allocation.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <given-names>G.</given-names>
            <surname>Alonso</surname>
          </string-name>
          and et al.
          <article-title>WFMS: The next generation of distributed processing tools</article-title>
          .
          <source>In Advanced Transaction Models and Architectures</source>
          .
          <year>1997</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <given-names>P.</given-names>
            <surname>Dadam</surname>
          </string-name>
          and et al.
          <article-title>Clinical work°ows - the killer application for process-oriented information systems?</article-title>
          <source>In BIS 2000</source>
          , pages
          <fpage>36</fpage>
          {
          <fpage>59</fpage>
          ,
          <string-name>
            <surname>Poznan</surname>
          </string-name>
          , Poland,
          <year>2000</year>
          . Springer.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>P.</given-names>
            <surname>Dadam</surname>
          </string-name>
          and et al.
          <article-title>Towards a new dimension in clinical information processing</article-title>
          .
          <source>In Business Proc Management</source>
          , pages
          <volume>295</volume>
          {
          <fpage>301</fpage>
          ,
          <string-name>
            <surname>Hannover</surname>
          </string-name>
          ,
          <year>2000</year>
          . IOS Press.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <given-names>S.</given-names>
            <surname>Dustdar</surname>
          </string-name>
          .
          <article-title>Caramba - A process-aware collaboration system supporting ad hoc and collaborative processes in virtual teams</article-title>
          .
          <source>Dist and Parall Databases</source>
          ,
          <volume>15</volume>
          (
          <issue>1</issue>
          ):
          <volume>45</volume>
          {
          <fpage>66</fpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>S.</given-names>
            <surname>Dustdar</surname>
          </string-name>
          and et al.
          <article-title>Architectural concerns in distributed and mobile collaborative systems</article-title>
          .
          <source>In SEKE</source>
          , pages
          <volume>521</volume>
          {
          <fpage>522</fpage>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <given-names>R.</given-names>
            <surname>Filho</surname>
          </string-name>
          and et al.
          <article-title>A fully distributed architecture for large scale work°ow enactment</article-title>
          .
          <source>Int. J. Cooperative Inf. Syst</source>
          ,
          <volume>12</volume>
          (
          <issue>4</issue>
          ):
          <volume>411</volume>
          {
          <fpage>440</fpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>H.</given-names>
            <surname>Foster</surname>
          </string-name>
          and et al.
          <article-title>Using a rigorous approach for engineering web service compositions: A case study</article-title>
          .
          <source>In IEEE SCC</source>
          , pages
          <volume>217</volume>
          {
          <fpage>224</fpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>D.</given-names>
            <surname>Georgakopoulos</surname>
          </string-name>
          and et al.
          <article-title>An overview of work°ow management: From process modeling to work°ow automation infrastructure</article-title>
          .
          <source>Dist and Parall Databases</source>
          ,
          <volume>3</volume>
          :
          <fpage>119</fpage>
          {
          <fpage>153</fpage>
          ,
          <year>1995</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <surname>Houspanossian</surname>
          </string-name>
          and et al.
          <article-title>Extending a BPEL engine with AOP</article-title>
          .
          <source>In (ASSE'05)</source>
          , Rosario, Argentina,
          <year>August 2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <given-names>F.</given-names>
            <surname>Curbera Ibm</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Dholakia</surname>
          </string-name>
          , and et al.
          <article-title>Business process execution language for web services</article-title>
          ,
          <source>May</source>
          <volume>13</volume>
          2003.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          11.
          <string-name>
            <given-names>M.</given-names>
            <surname>Jaeger</surname>
          </string-name>
          and et al.
          <article-title>QoS aggregation for web service composition using work°ow patterns</article-title>
          .
          <source>In EDOC</source>
          , pages
          <volume>149</volume>
          {
          <fpage>159</fpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          12.
          <string-name>
            <given-names>N.</given-names>
            <surname>Kavantzas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Burdett</surname>
          </string-name>
          , and et al.
          <source>Web services choreography description language version 1</source>
          .0. World Wide Web Consortium,
          <source>Candidate Recommandation CR-ws-cdl-10-20051109</source>
          ,
          <year>November 2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          13.
          <string-name>
            <given-names>J.</given-names>
            <surname>Klein</surname>
          </string-name>
          .
          <article-title>Ensemble: Integrating electronic health records using HL7 clinical document architecture</article-title>
          .
          <source>Business Integration Journal</source>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          14.
          <string-name>
            <given-names>K.</given-names>
            <surname>Kuhn</surname>
          </string-name>
          and et al.
          <article-title>A conceptual approach to an open hospital information system</article-title>
          .
          <source>Technical report, Ulm</source>
          ,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          15.
          <string-name>
            <given-names>N.</given-names>
            <surname>Lakhal</surname>
          </string-name>
          and et al.
          <article-title>THROWS: An architecture for highly available distributed execution of web services compositions</article-title>
          .
          <source>In RIDE</source>
          , pages
          <volume>103</volume>
          {
          <fpage>110</fpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          16.
          <string-name>
            <surname>M. LaRocca.</surname>
          </string-name>
          <article-title>The overlooked role of abstraction and data persistence in service oriented architectures</article-title>
          .
          <source>Technical report</source>
          , InterSystems, May
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          17.
          <string-name>
            <given-names>S.</given-names>
            <surname>Rinderle</surname>
          </string-name>
          and et al.
          <article-title>Evaluation of correctness criteria for dynamic work°ow changes</article-title>
          .
          <source>In Business Proc Management</source>
          , pages
          <volume>41</volume>
          {
          <fpage>57</fpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          18. B.
          <article-title>Sha¯q and et al. A GTRBAC based system for dynamic work°ow composition and management</article-title>
          .
          <source>In ISORC</source>
          , pages
          <volume>284</volume>
          {
          <fpage>290</fpage>
          ,
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          19.
          <string-name>
            <given-names>S.</given-names>
            <surname>Tai</surname>
          </string-name>
          and et al.
          <source>Composition of coordinated Web services</source>
          . Springer LNCS:
          <volume>3231</volume>
          , pages
          <fpage>294</fpage>
          {
          <fpage>300</fpage>
          ,
          <year>2004</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          20.
          <string-name>
            <given-names>S.</given-names>
            <surname>Thatte</surname>
          </string-name>
          .
          <article-title>XLANG web services for business process design</article-title>
          ,
          <year>2001</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          21.
          <string-name>
            <given-names>S. A.</given-names>
            <surname>White</surname>
          </string-name>
          et al.
          <article-title>Business process modeling notation (BPML)</article-title>
          ,
          <source>working draft, version 0.9</source>
          ,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          22.
          <string-name>
            <given-names>P.</given-names>
            <surname>Wohed</surname>
          </string-name>
          and et al.
          <article-title>Pattern-based analysis of BPEL4WS</article-title>
          .
          <source>QUT Technical report, FIT-TR-2002-04</source>
          , Queensland University of Technology, Brisbane,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>