<!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>Ontology Driven Business Processes Integration - a Position Paper</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Per Backlund</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Benkt Wangler</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Eva Söderström</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anders Toms</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Rose-Mahrie Åhlfeldt</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Anne Persson</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Skövde</institution>
          ,
          <country country="SE">Sweden</country>
        </aff>
      </contrib-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>The aim of this paper is to describe our position in relation to the use of ontologies.
We will present our research in the areas of health care processes, B2B integration,
and web services. The paper will briefly introduce our work in those areas and we
will pose our stand as to how ontologies relate to and can be used in those two areas
of application. Hence we wish to focus our work towards the practical application of
ontologies.</p>
    </sec>
    <sec id="sec-2">
      <title>2. B2B integration</title>
      <p>Our areas of research involve business to business integration and the potential use
of ontologies to remedy some of the problems that we outline. In order to set the
scene we will briefly introduce the important themes in our research efforts: business
processes and standards. We will also relate these concepts to each other.</p>
      <p>A business process is a partially ordered set of action types that has been designed
in order to deliver some kind of value to someone, e.g. to receive and fulfill a
customer order</p>
      <p>A business is a collection of business processes that have been activated within a
certain organizational context in order to achieve some purpose, e.g. to conduct some
kind of enterprise.
2.1</p>
      <sec id="sec-2-1">
        <title>Standards and process integration</title>
        <p>
          A B2B standard is defined as guidelines for how communication and information
sent between companies should be structured and managed. Firstly, a standard can be
referred to as an approved model, to be used for comparison or judgment, and of
established authority
          <xref ref-type="bibr" rid="ref3">(Information Services, 2001)</xref>
          . Secondly, a standard can be
defined as a document that provides guidelines or characteristics for activities or their
results
          <xref ref-type="bibr" rid="ref4">(ISO-IEC, 1996)</xref>
          . There are a number of other concepts used in relation to
standards. In order to bring clarity to what the relationships between these concepts
are, we will present them in a concepts model (Figure 1). A standard is made up of a
number of specifications. A specification is most commonly defined as a thorough,
concrete document of requirements and definitions of a certain item
          <xref ref-type="bibr" rid="ref3">(Information
Services, 2001)</xref>
          .
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Process integration in the health care sector</title>
        <p>
          The health care sector is an example of an application area where the there exists
numerous interoperability problems to resolve. The VITA Nova project .
          <xref ref-type="bibr" rid="ref9">(Wangler et
al., 2003)</xref>
          is focusing on the patient process, and includes the communication between
the healthcare providers and healthcare units. The goals of the VITA Nova project are
to develop a methodology for and to investigate the potential of an IT architecture
based on process manager technology. Like most businesses of today, healthcare is
functionally organised in e.g. primary care units, hospitals, and home healthcare
units; each with its own more or less isolated information systems.
        </p>
        <p>More precisely, these systems are characterised by the fact that they: firstly,
support single organisational functions very well, but with little adaptation to a process
oriented way of viewing things, i.e. where the intra- and inter-organisational
processes can be efficiently co-ordinated; and secondly, have been created at widely
differing points in time and hence by using different development paradigms, and by
using different software and hardware platforms.</p>
        <p>In this context we identify an interoperability problem in terms of orchestrating the
different and heterogeneous parts of this process. The healthcare process is a partial
order of manual tasks, which are performed by human actors and based on (business)
rules, decided by the healthcare units. Examples of manual tasks are treating a patient,
or using a computer.</p>
        <p>
          A new type of process oriented integration architectures has been developed by
means of what may be referred to as process managers, which closely reflect the
business processes. These are software devices that visualise the integration by means
of graphical and easy to understand process models that also facilitate management
and monitoring of the processes and their integration requirements. A process
manager visualises, manages and executes the communication between IT systems and
human actors
          <xref ref-type="bibr" rid="ref5">(Linthicum, 2001)</xref>
          . In that way it is possible to study, model, simulate
and change the communication by using a graphical interface against process models
(Dayal, 1999).
        </p>
        <p>Although not yet finished, the VITA Nova project already offers important
insights concerning healthcare processes and the potential benefits of using process
manager technology for systems integration, for facilitating data transfer between
healthcare providing organisations, and for streamlining the patient process in
general.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Our Position Statement</title>
      <p>In this section we will present our research intentions in relation to the use of
ontologies. We are interested in applied ontologies, more specifically in the areas of
health care and B2B standards. In particular we aim at developing methodologies for
the integration of IT support. We pose the following questions: 1) In what ways can
ontologies aid business process integration in the health care sector? 2) In what ways
can enterprise modelling contribute to the evolution of ontologies which are useful in
the context of business process integration in the health care sector?</p>
      <p>In a broader sense, we aim to direct our efforts in the area of B2B standards. We
pose the following questions: 3) What (kinds of) ontologies, if any, are used in the
development of B2B standards, and what role do they have in this development? 4)
What role can ontologies play in the development of B2B standards? 5) What type of
tools are useful in the planning of B2B standard implementation?</p>
      <p>
        One purpose and a main advantage of having B2B standards is that they facilitate a
common language (
        <xref ref-type="bibr" rid="ref7">Söderström, 2004</xref>
        )1. If such a language is to become a reality, it
needs to be based on a common ontological basis.
      </p>
      <p>The implementation process for B2B standards is complex, with many links to
adjacent processes in the standards life cycle, and several potential problems that may
occur. Many organisations have a very little knowledge about standards and how to
use them. Successful implementation is a pre-requisite for a successful use of
standards and technology. A tool for assisting organisations in planning for their
implementation projects may therefore be valuable to increase the likelihood of
implementation success, and to raise the level of knowledge about standards in organisations.</p>
      <p>We propose the use of participative enterprise modelling as a powerful instrument
when negotiating enterprise concepts and processes. There are standardisation efforts
for certain parts of the health care sector. One such example is the VIPS standard for
health care documentation. However, we foresee problems when trying to agree on
such standards. From a national point of view we only see the possibility of creating
high level agreements. On the operational level we rather anticipate bilateral
agreements, which obviously have to be negotiated between the parties involved. It is in
this context that we find enterprise modelling efforts crucial.</p>
      <p>
        In the Eriksson and Penker methodology
        <xref ref-type="bibr" rid="ref2">(Eriksson and Penker, 2000)</xref>
        methodology, the enterprise model corresponds to four modelling views: the Business Vision
View, the Business Process View, the Business Structure View and the Business
Be1 www.serviam.se
haviour View. Each view comprises a set of modelling (diagramming) techniques
adapted from UML. The views get more technical as the modelling proceeds. The
goal of modelling the four views is to capture and describe the collective intention of
the software service stakeholders. The process of doing this is further de
        <xref ref-type="bibr" rid="ref7">scribed in
Wangler et al. (2003</xref>
        ).
      </p>
      <p>
        In particular, software development practitioners claim that EM is effective for
gathering business needs and high-level requirements. In the participative approach to
EM, the stakeholders in question collaboratively develop Enterprise Models in
facilitated group sessions. This type of participation is consensus-driven in the sense that it
is the stakeholders who “own” the model and hence decide on its contents. In
contrast, consultative participation means that analysts create models and that
stakeholders are then consulted in order to validate the models. The participative approach
to EM is described and discussed in
        <xref ref-type="bibr" rid="ref8">Wangler and Persson (2002)</xref>
        4.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <given-names>Dayal U.</given-names>
            ,
            <surname>Hsu</surname>
          </string-name>
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Ladin</surname>
          </string-name>
          <string-name>
            <surname>R.</surname>
          </string-name>
          ,
          <year>2001</year>
          . Business Process Coordination:
          <article-title>State of the Art, Trends, and Open Issues</article-title>
          .
          <source>In Proceedings of the 27th International Conference on Very Large Data Bases, september 11-14</source>
          ,
          <year>2001</year>
          , Roma, Italy, pp.
          <fpage>3</fpage>
          -
          <lpage>13</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Eriksson H-E.</surname>
            and
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Penker</surname>
          </string-name>
          , “
          <article-title>Business Modeling with UML: Business Patterns at Work”</article-title>
          , Wiley,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <given-names>Information</given-names>
            <surname>Services</surname>
          </string-name>
          (
          <year>2001</year>
          ), Information Services: Dictionary, URL: http://www.esi.es/.
          <source>European Software Institute (ESI)</source>
          .
          <source>Accessed</source>
          <year>2001</year>
          -
          <volume>08</volume>
          -14.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <source>ISO/IEC Guide 2</source>
          (
          <year>1996</year>
          ),
          <article-title>Standardization and related activities - General vocabulary, 7th edition</article-title>
          , ISO/IEC
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Linthicum S. D.</surname>
          </string-name>
          ,
          <year>2001</year>
          .
          <article-title>B2B Application Integration - e-</article-title>
          <string-name>
            <surname>Business-Enable Your Enterprise;</surname>
          </string-name>
          Addison-Wesley.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          <string-name>
            <surname>Perjons</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wangler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wäyrynen</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Åhlfeldt</surname>
            ,
            <given-names>R-M.</given-names>
          </string-name>
          (
          <year>2004</year>
          ),
          <article-title>Introducing a process manager in healthcare: An experience report</article-title>
          ,
          <source>ISHiMR</source>
          <year>2004</year>
          , Sheffield, UK.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          <string-name>
            <surname>Söderström</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          (
          <year>2004</year>
          ),
          <article-title>Business value literature summary</article-title>
          ,
          <source>Serviam project report, March</source>
          2004 Wangler,
          <string-name>
            <given-names>B.</given-names>
            ,
            <surname>Åhlfeldt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            and
            <surname>Perjons</surname>
          </string-name>
          ,
          <string-name>
            <surname>E.</surname>
          </string-name>
          (
          <year>2003</year>
          )
          <article-title>Process Oriented Information Systems Architectures in Healthcare, Health Informatics Journal</article-title>
          ,
          <year>December 2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          <string-name>
            <surname>Wangler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Persson</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2002</year>
          ), “
          <article-title>Capturing Collective Intentionality in Software Development”</article-title>
          , in Fujita, H. and
          <string-name>
            <surname>Johannesson</surname>
          </string-name>
          , P. (eds.),
          <source>New Trends in Software Methodologies, Tools and Techniques</source>
          , IOS Press, Amsterdam, Netherlands, pp
          <fpage>262</fpage>
          -
          <lpage>270</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          <string-name>
            <surname>Wangler</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Persson</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Johannesson</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ekenberg</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          (
          <year>2003</year>
          ),
          <article-title>“Bridging High-level Enterprise Models to Implemenation-Oriented Models”</article-title>
          , in Fujita, H. and
          <string-name>
            <surname>Johannesson</surname>
          </string-name>
          , P. (eds.),
          <source>New Trends in Software Methodologies, Tools and Techniques</source>
          , IOS Press, Amsterdam, Netherlands.
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>