Research in the area of process modeling and analysis has a long-established tradition. Process modeling is among others used in the medical domain to de ne an ideal work ow in order to ensure an e cient treatment of patients. These processes are often de ned and maintained by multiple persons. Furthermore, multiple persons are interested in these de ned processes to compare them with own de ned processes for improvements purposes. Current solutions provide tools to model processes locally and export them in standard formats in order to exchange them. Besides, there are some collaboration tools available to model processes collaboratively and see changes dynamically. However, these solutions do not publish the data according to the Linked Data principles. Enriching processes with semantic information is useful in order to perform enhanced analysis. However, di erent users can only provide particular meta-information on same process steps. To address these problems we 1) developed an intuitive, open-source extension for Semantic MediaWiki that supports the graphical modeling of processes and stores the information in a structured way; 2) enable to enrich the processes with semantics from ontologies and knowledge graphs with references to external data sources 3) provide adapted views on meta-information in order to not overwhelm users with unnecessary information.
According to the process de nition from ISO 9000:2015 [
These clinical guidelines support physicians by
recommending the sequence and timing of actions that is necessary to
achieve an e cient treatment of patients [
Each clinic has their own pathways based on their
evidences and experiences. Therefore, there are multiple
pathways available that target di erent problems and care needs [
Besides the structure of processes, there are also many semantic information about processes available. There are many ontologies and semantic information in di erent data sources like e.g. DBpedia1 available that can be used for analyzing purposes. In addition, there are further semantic information about processes available that cannot be captured with current standard formats for storing process models.
Another important aspect that occurs nowadays is that processes become more complex and that they are usually maintained by multiple persons. These persons do not necessarily share the same location but are located in di erent countries. This is often the case in international projects. Therefore, a collaborative tool that allows to capture, annotate and share information about processes collaboratively is preferable in order to allow a simpli ed acquisition and exchange of processes and respective meta-information.
Linked Data is a method to publish data in a structured way2. Publishing data according to these principles facilitates the exploration and interlinks between di erent documents. Thus information can be looked up by a HTTP URI and are provided in a structured way. Additional links to other URIs o er the possibility to explore even more information and enrich further knowledge.
Applying the Linked Data principles on processes would allow to 1) model processes and its set of activities with unique HTTP URIs; 2) provide useful information about processes in a standard format like the Resource Description Framework3 (RDF); and 3) interlink processes with information from other data sources.
During the acquisition of semantic information from users, one has to consider di erent views on processes and its elements. Thereby, di erent users can provide and are interested in di erent meta-information for same process elements. Considering this aspect, in order to not overwhelm users with meta-information that is not relevant for him, is an important aspect while acquiring corresponding metainformation about processes.
In order to address these problems, we present a collaborative platform that allows to acquire processes, applying the Linked Data principles on them, capture meta-information and enable di erent views on these meta-information.
We demonstrate the applicability of our solution by modeling a concrete perioperative process and enable users with di erent roles to see di erent views on provided forms, which they can use to annotate the elements. The used methods and an overview of the system are described in section 2. Overall, we address the following research questions: 1. How can we model processes and publish them according to the Linked Data principles? 2. How can we implement the infrastructure necessary for storing, accessing, and processing processes and the corresponding meta-information? 3. How can we introduce di erent views for entering metainformation?
We show that our approach is easy to use and extensible to capture multiple processes and semantic information, as well as applicable to other domains (Section 2). The used materials and methods are shown in section 3. The concrete implementation of our approach is shown in section 4. Furthermore, we show that our approach is su cient to capture processes and meta-information, and allow di erent views on the entered information. For this purpose we will model a perioperative process and enrich it with meta-information from users that use di erent views (section 5). The evaluation of the system includes showing the application of the Linked Data principles on the modeled processes, demonstrating the functionality of the system and enable di erent views on the meta-information. A short discussion and lessons learned is given in section 7.
A major shortcoming of current process modeling languages is that they cannot capture semantic information. They concentrate on representing the structure of processes but do not include speci cation of a formal semantic. This is e.g. the case for the Business Process Model and Notation (BPMN) [19].
Capturing processes and semantics is nowadays usually done by multiple persons. Projects and work ows are currently by no means proceeded in one place and by one person. The work ows of processes are usually de ned collaboratively, as well as the analysis of processes. Moreover, not only analysts are interested in process models but also people who actually performing the processes as well as people 3https://www.w3.org/RDF/, visited 24 January 2016 who are not performing the processes but working in the same domain. Hence, clinics are for example interested in clinical pathways from other clinics to get insights from their processes and treatments of patients. This exchange of information allows to improve own processes by the insights of other clinics.
However, processes do not store semantic information. Current formats like e.g. BPMN 2.0 XML4, proposed by the OMG as standard format for storing Business Process Model and Notation (BPMN) diagrams, do not allow to capture semantic information like e.g. references to medical guidelines, responsible persons and conditions. Therefore, useful metainformation that can be used for analyzing processes gets lost. However, these information can be used to improve healthcare services in planning resources and improving the outcome of clinical pathways.
Therefore, we would like to provide a possibility to capture processes, semantics in processes and the accruing metainformation in a collaborative platform. Thus, multiple person can access the platform, add, edit and view processes, semantics in processes and meta-information collaboratively. This collaborative manner supports among others also the exchange of processes. Thus people from the same domain has access to these information at any time. Following this, the entered information are available for querying and performing process analysis. The vision of the collaborative platform is given in gure 1. publish process data. These principles are particular useful for linking, exchanging and exploring information .
Thereby, the platform will publish the entered information according to the Linked Data principles. Thus, unique HTTP URIs will represent process elements. In addition, the information provided by the platform will be available in a standard, machine-readable format. This allows to query the entered information for analyzing purposes. Entered information includes meta-information as well as useful references to external data sources like e.g. DBpedia6, PubMed7 or Medscape8. This allows to lookup further facts and information about entities and concepts, discover more things and connect the data from the collaborative platform with other data to avoid of having an unbounded web.
Information about the hierarchy of ow objects and
connecting objects can be modeled with the collaborative
platform. Meta-information like a responsible person for a
speci c task in a process, runtime, descriptions or references to
external data sources, can be added to an element. These
additional information, published according to the Linked
Data principles, can be queried and used for enhanced
analysis and can i.e. allow improved comparisons between
processes [
The semantic information can be used to enhance analysis and providing additional information to users. However, an extensive provision of attributes that are shown to the users may overrun them and is therefore not feasible, because it prevents users more from entering meta-information instead of supporting them. In addition, not every user can provide all meta-information or rather is interested in them. Hence, we would like to introduce views on process metainformation that is relevant and useful for the user. Thus, the platform provides those meta-information to the user that is relevant to him without overwhelming him.
The information, provided by the platform, as well as the information from the referenced external data sources, allows performing analysis such as runtime analysis and similarity analysis of processes. By the variety of semantics and meta-information, provided by the platform and referenced from external data sources, are enhanced process analysis feasible that were not possible before.
Our approach is based on several components that are part of a common collaborative platform that stores the data in a knowledge base. Section 3.1 describes the idea of the collaborative platform that publishes information using the Linked Data principles in more detail.
The collaborative platform should provide a possibility to model processes and reuse existing standards (section 3.2). Thereby, we have to consider that modeling processes should be as simple as possible due to the fact that domain experts will use the system and they may have no experience in using modeling tools.
Besides modeling processes, we are interested in capturing meta-information. Therefore, we need an approach to capture these information from the domain experts. In adited 24 January 2016 6http://wiki.dbpedia.org, visited 24 January 2016 7http://www.ncbi.nlm.nih.gov/pubmed/, visited 24 January 2016 8http://www.medscape.com, visited 24 January 2016 dition, we want to provide di erent views on same elements so users are not overwhelmed with unnecessary information (section 3.3). 3.1
The infrastructure to model and annotate processes, providing di erent views on entering data and publishing the entered data according to the Linked Data principles, consists of multiple components. Figure 2 shows a high level overview of the planned infrastructure.
The needed infrastructure has to ensure an e cient data input and exchange that follows the Linked Data principles. However, the data entry has to abstract from the provision of standard formats like RDF. We have to consider already available standard formats for process models like e.g. BPMN 2.0 XML. Therefore, we need an infrastructure that allows to model and enter data in di erent ways and formats and provide the entered information automatically in a standard format like e.g. RDF.
Users can enter processes and meta-information into the collaborative platform. For entering meta-information, the system provides di erent views according to roles that are assigned to the user (see section 3.3). The entered data should be available according to the Linked Data principles so accessing the unique identi ers returns information in a standard format and it is possible to query the data.
The entered data will be stored in a knowledge base. The knowledge base consists of entered data, as well as linked data from external sources. Thus the knowledge stores modeled processes, meta-information about the modeled processes and information from other data sources like e.g. DBpedia9 and PubMed10 that is referenced. 3.2
There are multiple modeling languages available in order to model processes. We would like to provide the possibility in our platform to capture processes in multiple modeling languages. Modeling languages are visual representations of work ows and architectures. They de ne a structure how di erent elements are linked. However, they do not store semantic information.
Usually, domain experts are not familiar with semantic technologies and with modeling processes. Therefore, we have to provide a tool that allows domain expert to enter processes in a very simple way. Most of the modeling languages are a graphical representation, therefore a graphical user interface that allows to enter processes in a very simple way is preferable.
There are already formats available in order to store processes like e.g. BPMN 2.0 XML11 proposed by OMG12 as standard format for BPMN or EPML that de nes a XML schema to store event-driven process chains [13]. The process modeler should reuse such standards.
Reusing standards allows to import and export processes so that these processes do not have to be modeled from scratch. Therefore, the reuse of standards allows the exible exchange of modeled processes. Besides the import and export functionality of processes, the modeler should also allow to add new processes into the platform and edit existing processes.
Processes can be described by using di erent process modeling languages. Currently there are among others Business Process Model and Notation (BPMN), Petri Nets and Event-driven process chain available to model processes. Each process modeling language tackles a speci c depiction of a process. This circumstance of describing one work ow by using multiple process modeling languages should be supported by the collaborative platform. Hence, users can enter processes using di erent modeling languages. 3.3
Annotating processes with semantic information allows to use these information among others for analyzing purposes. This can improve e.g. the comparison between processes and allows to nd biomarkers in processes that have not been known before. Biomarkers in processes are indicators that have signi cant in uence on the output of a clinical pathways.
However, di erent users have di erent perspectives on same tasks. Therefore, they can only provide particular information and will probably only use speci c information. Forms allow a structured and easy input of semantic information for users. Providing one giant form, in which users 9http://wiki.dbpedia.org, visited 24 January 2016 10http://www.ncbi.nlm.nih.gov/pubmed/, visited 24 January 2016 11http://www.omg.org/spec/BPMN/2.0/, visited 24 January 2016 12http://www.omg.org, visited 24 January 2016 can enter all information they have and view all available information in the system, may deter them in using the system. Di erent views on the task for entering semantic information allows to not overwhelm users with information which they cannot know and do not need. Figure 3 illustrates the idea of providing di erent views.
We would like to introduce roles into the system and assign them to users. Each role contains information which attributes are interested by the user group and should be displayed to the them. Hence, the system checks which roles are assigned to the user and shows only these attributes to him.
The relationship between users and roles follow a m : n relationship. So multiple roles can be assigned to one user and di erent users may have same roles. According to the assigned roles, the user will only see speci c information.
The di erent views can be used to o er the possibility to secure information from unauthorized access. However, we will not focus on the security aspect but more on providing useful views for users.
We implemented our approach by using a use-case scenario from the medical domain. The medical domain is very suitable for our approach, because in this domain are many experts that can provide di erent information about same clinical pathways. Furthermore, clinics are interested in clinical pathways from other clinics in order to improve their own clinical processes. Providing processes and metainformation as Linked Data allows to exchange clinical pathways across clinics and link them to already existing information to discover more things. The implementation of the infrastructure for the collaborative platform is described in section 4.1.
The realization of how processes are modeled in the collaborative platform is shown in section 4.2. We focused on BPMN as modeling language, however the approach can be adapted in order to capture processes in other modeling languages like e.g. Event-driven process chain and Petri net.
We also allow to capture meta-information about the process elements by providing forms. Users with di erent assigned roles get di erent views on same forms, so they are not overwhelm with redundant information (section 4.3). 4.1
In order to allow users to create, edit and view processes and process meta-information according to the Linked Data principles collaboratively, we need a collaborative platform that supports this feature. For this purpose we use Semantic MediaWiki13 (SMW) as platform for modeling processes, capturing meta-information and publishing these information according to the Linked Data principles.
Semantic MediaWiki is a powerful collaborative knowledge management system to store and query data. Data resources, concepts and properties can be annotated internally, as well as linked to external data sources like e.g. DBpedia14). The possibility of linking concepts and properties enables the integration of well-known ontologies such as Dublin Core15 and SNOMED16. Each wiki page has its own HTTP URI, provides its data in RDF and, if entered, provides useful links to other data sources.
Hence, the information, stored in SMW, is available as Linked Data on the web. We used existing tools and extended them in order to capture processes within SMW (section 4.2) and capture meta-information by providing di erent views (section 4.3).
Figure 4 illustrates the infrastructure for capturing processes, annotating them by users that use di erent views on same processes and query all available information in SMW by using the RDF export functionality of SMW. 13https://www.semantic-mediawiki.org/wiki/Semantic MediaWiki, visited 24 January 2016 14http://wiki.dbpedia.org, visited 24 January 2016 15http://dublincore.org, visited 24 January 2016 16http://www.ihtsdo.org/snomed-ct, visited 24 January 2016 The Semantic MediaWiki o ers an infrastructure that allows to capture information and link it to other data sources in a very easy way. Flexible inputs and modi cations of the entered data is possible. Furthermore, SMW takes care of publishing the data in RDF and according to the Linked Data principles. Thus the entered processes and meta-information is available in a structured way that can be used for analyzing purposes. 4.2
Currently SMW does not support graphical inputs of process modeling languages. However, due to the fact that domain experts will enter process models, we want to facilitate the input as much as possible by providing a graphical user interface for modeling processes. As modeling language we chose BPMN 2.0.
For modeling BPMN diagrams, we used bpmn-io17 as graphical user interface. bpmn-io is a graphical web modeler, based on JavaScript that allows to view, create and edit BPMN 2.0 diagrams. It is part of the business process management platform Camunda18.
We extended bpmn-io with further functionality in order to embed it as process modeler in SMW. Each BPMN element (nodes and edges) is represented by an own wiki page. The wiki page contains all information about the BPMN element like e.g. the type of the element, labels, comments and entered semantic information by the user (see section 4.3).
bpmn-io allows to import processes in the standard format BPMN 2.0 XML19 proposed by OMG20. Thus existing processes that are available in BPMN 2.0 XML can directly be imported via drag&drop into SMW using the process modeler. In addition, bpmn-io allows to export modeled processes in BPMN 2.0 XML and as an image in Scalable Vector Graphics (SVG) format. Thereby, we support standards and allow to reuse modeled processes.
Besides the provided functionality from bpmn-io, we allow to reload already depicted BPMN diagrams from SMW and allow to modify them. The following list describes the mapping between the process modeler and SMW.
Create BPMN element: Creates a new wiki pages that represents the BPMN element and allows to store corresponding information of the element on this wiki page.
Edit BPMN element: The modi cation of a BPMN element leads to modi cations of information on the wiki page. Modi cation comprises among others shifting the position of an element, reconnecting ow elements and de ning labels and comments for a BPMN element.
Delete BPMN element: The deletion of a BPMN element leads to a deletion of the corresponding wiki page. 4.3
Once processes are captured, we would like to enrich them with meta-information. For this purpose, we use Semantic Forms21, which is an extension to SMW that provides forms for adding and editing data.
We use Semantic Forms to provide useful forms that help users to annotate process elements. Multiple forms can be created and used to annotate BPMN elements. The forms can include information like Responsible Person, Goal, Condition and links to Guidelines. These meta-information can be used to analyze processes and its elements. In addition users can use these information to get a closer look on the process and its tasks.
We imported the FOAF Ontology22 and Dublin Core Schema23 to model and describe the used properties. These properties are used in the forms to annotate the processes.
Forms can be arranged in a hierarchical model. So a form can inherit attributes from a superclass. However, the relationship between the superclass and its subclasses is 1 : n. Hence, a subclass does not inherit from multiple superclasses, but a superclass can be used as a generalization for multiple subclasses [18].
We extended the functionality of Semantic Forms in order to provide di erent views on same forms. Therefore, admins can assign attributes to roles in the local settings le of Semantic MediaWiki. Each role stores attributes that are allowed to be viewed by the user that has the assigned role. Besides de ning the roles, are the roles assigned to users. As the default setting, each attribute in a created form is allowed to be viewed for every user, independent from assigned roles. However, if adding the attribute role with the value true into the div element of the form, are the assigned roles for the user checked.
This check is done by a JavaScript le. Users are only allowed to view attributes that are de ned in the assigned roles. Other attributes in the form are hidden. For this purpose we use the hide functionality from jQuery24. The corresponding HTML form is then presented to the user with hidden elements that he is not allowed to see.
The user uses these forms to enter additional information about the process element into the Semantic MediaWiki. The entered information are stored on the corresponding wiki page that represents the BPMN 2.0 element and is available according to the Linked Data principles. 5.
We evaluated the system according to its functionality and show the proof of concept. Therefore, we used an existing process in the medical domain. We imported an existing perioperative process that was modeled in BPMN 2.0 and enriched it with meta-information. The meta-information are entered by two users that use the same form, however with di erent views due to di erent assigned roles.
We successfully imported the perioperative process into the Semantic MediaWiki. Figure 5 shows the graphical representation of the process in the web modeler. Each element in the BPMN 2.0 process is represented by a wiki page that 17http://bpmn.io, visited 24 January 2016 18https://camunda.org, visited 24 January 2016 19http://www.omg.org/spec/BPMN/2.0/, visited 24 January 2016 20http://www.omg.org, visited 24 January 2016 21https://www.mediawiki.org/wiki/Extension:Semantic Forms 22http://www.foaf-project.org, visited 24 January 2016 23http://dublincore.org, visited 24 January 2016 24https://jquery.com, visited 24 January 2016 stores the information about this element.
We use Semantic Forms to annotate the BPMN 2.0 elements and allow users to enrich them with meta-information. A role system allows to hide information from users that is not relevant for them. To demonstrate the functionality, we assigned two di erent roles to two di erent users and called up the form to annotate the task for radiography in the perioperative process. We called the roles physician and radiologist. Figure 6 shows the di erent views for the same form.
Although, users have di erent views on form, it is the same form. In some parts they can view the same information like label and comment, but some attributes can only be viewed by the radiologist like e.g. the used device to capture the X-ray image, which the doctor in charge might not know and is also not relevant for him.
However, the attributes are only hidden in the form. The information is still in the HTML code available but not presented to the user. Our approach hides the attributes on the client side and is therefore not suitable to prevent users from unauthorized access. For this case, a server side processing of the information is more suitable. However, we focused more on providing aligned forms for users without creating for each user group a particular form but assigning roles to them that hides speci c parts of the forms.
With this approach we can create one giant form, instead of multiple forms that may only di er slightly. However, by using the roles, each user has a di erent view and perceive the same forms in a di erent way.
All the entered information into the SMW, which includes the perioperative process and the entered meta-information is available in RDF. The information can be accessed and queried by using the RDF export from SMW and is available according to the Linked Data principles. 6.
Process modeling tools like Visio25 allow to model processes on a local machine. However,a collaborative creation and maintenance of processes is not possible.
Collaborative modeling tools like Blueworks Live26, BPMN Modeler27, jBPM28 and gluu29 provide a web-based solution in order to allow modeling processes collaboratively. In addition these tools allow to import and export diagrams in various formats. Although these tools support a collaborative modeling of tools, the captured information are not published according to the Linked Data principles.
Flowchart30 is an extension for SMW that allows to model diagrams by using owchart elements. Each owchart element is represented by a wiki page. Flowchart allows to model e.g. event-driven process chains. However, a graph can be displayed that shows the interlinks, it does not provide an interactive modeler. Modi cations in the process must be done directly on the wiki pages, using the wiki syntax.
The modeling and capturing of information in a formal
representationm using a Semantic MediaWiki, were done
before in other projects [
SPUD is an environment to catalog, explore and process
urban information based on semantic technologies and
publish the data according to the Linked Data principles [
Roles to restrict users from accessing speci c data had
been developed long time ago [
Annotations are used in di erent scenarios like e.g.
annotating television and radio news with semantic
information [
Besides annotating data, there are also approaches
available to annotate web services [
We showed an approach to capture processes and annotate them with meta-information by using a collaborative platform and providing di erent views for entering metainformation in order to not overwhelm users. The published information follows the Linked Data principles.
SMW provides the basis for storing the data and publishing them according to the Linked Data principles. Therefore, the captured and annotated processes are available in a machine-readable format that can be queried for analyzing purposes.
We used an existing modeler to model BPMN 2.0 diagrams, extended it with further functionality and embedded it in SMW. Each element in the BPMN 2.0 diagrams is represented by an own wiki page that stores the corresponding information. A modeler for modeling other diagrams like e.g. event-driven process chain can be implemented with the same approach as presented.
Role based forms support the annotation of BPMN elements so that redundant information is not shown to users that are not assigned to speci c roles. The assigned roles focus on not overwhelming users with unnecessary information rather than on security purposes.
We evaluated the system according to its working functionality. We could import existing BPMN 2.0 XML diagrams, edit BPMN diagrams and enrich them with metainformation. The entered information is available in RDF and follows the Linked Data principles. Di erent views on forms allow speci c entry of data by users.
Future work comprises among others the input of multiple processes and corresponding meta-information in order to use these data for performing process similarity and analysis. The entered meta-information helps especially in using them for comparing the processes on a semantic level. The consequent bene ts helps to get new insights into processes like e.g. clinical pathways in order to improve them.
In conclusion, we have taken a rst step towards capturing, annotating and processing processes according to the Linked Data principles that can be shared and used in order to analyze and re ne processes collaboratively. Role based forms allows speci c views on the data that are particularly interesting for users with the assigned roles. 31http://www.w3.org/TR/sawsdl, visited 24 January 2016 8. 23 countries { an international survey by the european pathway association. International Journal of Care Coordination, 10(1):28{34, 2006. [13] J. Mendling and M. Nuttgens. Epc markup language (epml): An xml-based interchange format for event-driven process chains (epc). Information Systems and e-Business Management, 4(3):245{263, 2005. [14] M. Panella, S. Marchisio, and F. Di Stanislao.
Reducing clinical variations with clinical pathways: do pathways work? International Journal for Quality in Health Care, 15(6):509{521, 2003. [15] V. Singh, N. Gu, and X. Wang. A theoretical framework of a bim-based multi-disciplinary collaboration platform. Automation in Construction, 20(2):134 { 144, 2011. Building Information Modeling and Changing Construction Practices. [16] F. Steimann. The role data model revisited. Appl.
Ontol., 2(2):89{103, Apr. 2007. [17] H. H. Wang, N. Gibbins, T. R. Payne, and D. Redavid. A formal model of the semantic web service ontology (wsmo). Information Systems, 37(1):33 { 60, 2012. [18] T. Weller and M. Maleshkova. Towards a process meta-model. In Proceedings of the second Karlsruhe Service Summit Workshop - Advances in Service Research, Karlsruhe, Germany, 2016. KIT Scienti c Publishing. [19] P. Wong and J. Gibbons. A process semantics for bpmn. In S. Liu, T. Maibaum, and K. Araki, editors, Formal Methods and Software Engineering, volume 5256 of Lecture Notes in Computer Science, pages 355{374. Springer Berlin Heidelberg, 2008. [20] H. N. Yadav and R. V. Patel. Dbpedia based sawsdl for semantic web services. In Computing for Sustainable Global Development (INDIACom), pages 35{39. IEEE, 2015. [21] Z. Yan, D. Chakraborty, C. Parent, S. Spaccapietra, and K. Aberer. Semantic trajectories: Mobility data computation and annotation. ACM Trans. Intell. Syst.
Technol., 4(3):49:1{49:38, July 2013. [22] K. Zander. Integrated care pathways: eleven international trends. International Journal of Care Coordination, 6(3):101{107, 2002.