Fig 1 - uploaded by Stefan Schlichting
Content may be subject to copyright.
Exemplary request without second channel information that is send from a clinical application to a ventilator in order to modify the PS value.
Context in source publication
Context 1
... the WSDL using WS-Policy [13] and WS-PolicyAttachment [14]. This mechanism fulfils the requirements 3 and 4 which are not discussed hereinafter. The PS value can be modified remotely by calling the SetValue operation that is part of the ventilator service. The operation is invoked using a SOAP request/response message exchange scheme [15]. In Fig. 1 an exemplary request sent by the clinical application is depicted that does not contain information about a second ...
Similar publications
The literature on web service (WS) discovery recognizes a major problem in the requirements of service consumption. Current works on WS discovery focuses on WS discovery scenario and neglect the analysis of the intervention of service consumer. Therefore, the problem of service consumer needs must be solved to guarantee the pertinence of WS selecti...
Forced alignment tools such as the Munich Automatic Segmen-tation System (MAUS) [1] do not scale well with input size. In this paper, we present a preprocessor chunk segmentation tool to combat this problem. It dramatically decreases MAUS's run-time on recordings of duration up to three hours, while also having a slightly positive effect on segment...
Citations
... In summary, this guarantees that data is not compromised when being transmitted from one process to another. More information on dual channel transmission is given in [19]. ...
This paper presents a comprehensive solution to build a distributed system of medical devices in high acuity environments. It is based on the concept of a Service Oriented Medical Device Architecture. It uses the Devices Profile for Web Services as a transport layer protocol and enhances it to the Medical Devices Profile forWeb Service (MDPWS) to meet medical requirements. By applying the ISO/IEEE 11073 Domain Information Model, device data can be semantically described and exchanged by means of a generic service interface. Data model and service interface are subsumed under the Basic Integrated Clinical Environment Specification (BICEPS). MDPWS and BICEPS are implemented as part of the publically available openSDC stack. Performance measurements and a real world setup prove that openSDC is feasible to be deployed in distributed systems of medical devices. © David Gregorczyk, Stefan Fischer, Timm Busshaus, Stefan Schlichting, and Stephan Pöhlsen.
... Hierzu gehört u.a. eine Spezifikation, die es erlaubt, sicherheitskritische Kontextinformationen wie etwa den Wert eines zweiten Kanals zu übermitteln[5].Die entwickelte Referenzimplementierung von BICEPS wurde für die Java SE 6 implementiert und umfasst sowohl eine Bibliothek für Dienstnutzer als auch für Dienstanbieter. Das verwendete MDPWS-Framework verwendet als DPWS-Implementierung das JMEDS-Framework[6]. ...
The number of devices in an operation room (OR) and the complexity of the components and the overall system increases continuously. Today's vendor-dependent integrated ORs are expensive and not able to handle this complexity because they can only form isolated solutions. Thus a device communication for medical devices among each other and to medical information systems has to be based on open and vendor-independent standards. In this paper we will present new standards for networked Point-of-Care medical devices that will be part of the IEEE 11073 family of standards. A service-oriented device communication is defined by means of an architecture definition, a transport specification called Medical Devices Profile for Web Services (MDPWS), and a Domain Information & Service Model. The new system will make the complexity of a comprehensive OR integration manageable and thereby improve patient's safety. The focus of this paper is on MDPWS that enables a device communication for medical requirements and safety issues, like safe data transmission that will typically be used for safe remote control (dual channel and safety context), data streaming, and compact transmission. The suitability of the concept has been shown by a demonstrator with over 20 real world OR devices from more than 10 vendors.
