<?xml version="1.0" encoding="UTF-8"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
<title>European Conference on eHealth</title>
<link href="http://dl.gi.de/handle/20.500.12116/23983" rel="alternate"/>
<subtitle/>
<id>http://dl.gi.de/handle/20.500.12116/23983</id>
<updated>2026-07-21T13:36:53Z</updated>
<dc:date>2026-07-21T13:36:53Z</dc:date>
<entry>
<title>Information need and IT demands for business process reengineering in operationroom management</title>
<link href="http://dl.gi.de/handle/20.500.12116/24010" rel="alternate"/>
<author>
<name>Zoeller, Anja</name>
</author>
<author>
<name>Denz, Christof</name>
</author>
<author>
<name>Baumgart, Andre</name>
</author>
<author>
<name>Bender, Hans-Joachim</name>
</author>
<author>
<name>Badreddin, Essameddin</name>
</author>
<author>
<name>Heinzl, Armin</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/24010</id>
<updated>2019-07-11T11:29:01Z</updated>
<published>2006-01-01T00:00:00Z</published>
<summary type="text">Information need and IT demands for business process reengineering in operationroom management
Zoeller, Anja; Denz, Christof; Baumgart, Andre; Bender, Hans-Joachim; Badreddin, Essameddin; Heinzl, Armin
Stormer, Henrik; Meier, Andreas; Schumacher, Michael
As the economic importance of operation room (OR) management is increasing, the aim of this paper is to analyse the information need for business process reengineering (BPR) in OR management and to reveal the need for corresponding IT support. The information on OR processes available in clinical standard documentation schemes proves fragmentary and insufficient for the needs of process analysis in BPR. Therefore a precise, detailed OR process model is analysed on relevant process interdependencies and influencing variables to reveal the crucial information need for OR management. The analysis includes empiric data, collected in a field study and shall form the basis for developing an adequately comprehensive documentation scheme. Its purpose is to uncover and pin-point where the need for information and respective IT support lead to an improvement of BPR for OR management.
</summary>
<dc:date>2006-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Intermediation in the healthcare system: the example of Switzerland</title>
<link href="http://dl.gi.de/handle/20.500.12116/24009" rel="alternate"/>
<author>
<name>Walser, Konrad</name>
</author>
<author>
<name>Myrach, Thomas</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/24009</id>
<updated>2019-07-11T11:29:00Z</updated>
<published>2006-01-01T00:00:00Z</published>
<summary type="text">Intermediation in the healthcare system: the example of Switzerland
Walser, Konrad; Myrach, Thomas
Stormer, Henrik; Meier, Andreas; Schumacher, Michael
The paper analyzes the situation of intermediaries and their business models in the Swiss health system. Various intermediary roles are positioned within the value-added chain of the healthcare system. Particular attention is paid to cost-benefit relationships of intermediation for partners of the intermediary and for the intermediary itself. With regard to the connection between healthcare providers and health insurers, three intermediaries – namely the Trust Centers, Medidata, and H-Net – are featured in greater detail and studied in terms of differences of their business and revenue model.
</summary>
<dc:date>2006-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Anonymity preserving authorization granting in medical information networks</title>
<link href="http://dl.gi.de/handle/20.500.12116/24008" rel="alternate"/>
<author>
<name>Eskeland, Sigurd</name>
</author>
<author>
<name>Oleshchuk, Vladimir</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/24008</id>
<updated>2019-07-11T11:29:00Z</updated>
<published>2006-01-01T00:00:00Z</published>
<summary type="text">Anonymity preserving authorization granting in medical information networks
Eskeland, Sigurd; Oleshchuk, Vladimir
Stormer, Henrik; Meier, Andreas; Schumacher, Michael
Due to the sensitivity of personal medical information, this paper addresses the need of hiding patient identities - in contrast to only keeping their medical data confidential. Thus, it is desirable that personal and meaningful patient identity information like names, addresses, personal identity numbers, etc., are not to be linked to disclosed electronic patient records (EPR). To achieve this, we propose a scheme that enables patients to anonymously grant medical teams authorization to access their EPRs without revealing their identities to the teams providing medical care. An essential benefit is that it enables patients to exert control over their own medical data. A security evaluation is included.
</summary>
<dc:date>2006-01-01T00:00:00Z</dc:date>
</entry>
<entry>
<title>Information flow analysis based security checking of health service composition plans</title>
<link href="http://dl.gi.de/handle/20.500.12116/24007" rel="alternate"/>
<author>
<name>Hutter, Dieter</name>
</author>
<author>
<name>Klusch, Matthias</name>
</author>
<author>
<name>Volkame, Melanie</name>
</author>
<id>http://dl.gi.de/handle/20.500.12116/24007</id>
<updated>2019-07-11T11:29:00Z</updated>
<published>2006-01-01T00:00:00Z</published>
<summary type="text">Information flow analysis based security checking of health service composition plans
Hutter, Dieter; Klusch, Matthias; Volkame, Melanie
Stormer, Henrik; Meier, Andreas; Schumacher, Michael
In this paper, we present an approach to solve the problem of provably secure execution of semantic web service composition plans. The integrated components of this approach include our OWL-S service matchmaker, OWLS- MX, the service composition planner, OWLS-XPlan, and the security checker module for formally verifying the compliance of the created composition plan to be executed with given data and service security policies using type-based information flow analysis. We demonstrate this approach by means of its application to a use case scenario of health service composition planning.
</summary>
<dc:date>2006-01-01T00:00:00Z</dc:date>
</entry>
</feed>
