VITAL: use and implementation of a medical communication standard in practice

Abstract

IntroductionVITAL [1] describes the design of communication specifications for the transmission of device and vital parameters, independent of device type or manufacturer as well. Additionally, this open communication standard defines a general data and communication model enabling access to required data -even under real-time conditions. VITAL also enables the automatic configuration and coordination of networked devices. As an example, VITAL can be used to log the bio signals gathered on one diagnostic device and to produce a real-time curve with the data on a separate display. Such technology is ideal for intensive care, sleep research centres, or at an intracardiac catheter measuring station. VITAL also enables the simultaneous accumulation, monitoring, and when needed, the graphical representation of diverse bio signals from several patients.VITAL enables users to operate systems consisting of pieces of equipment from different manufacturers with little additional input. VITAL also simplifies the expansion of manufacturers' equipment portfolios. Due to straightforward software and hardware extensions, standalone measuring devices can be made networkcompatible and therefore can be integrated into existing networks in a manner that enables them to recognize the correlation between patient data and to detect critical states of patients. For the user in the medical field, improvements can be realized concerning multiparameter analysis, long-term monitoring and finally, advanced compliance. Economical and high quality disease management is also now possible. Patients' benefit due to expanded possibilities for individually optimised, more reliable diagnostics and therapies. MethodsThe VITAL communication architecture [2] is based on the »Agent/Manager« concept of the ISOManagement-System and therefore defines the user specific layers in the ISO/OSI Layer Model (figure 1), especially the »Application Layer«.

Method and system for standardized and platform independent medical data information persistence in telemedicine

“…In order to handle with all those requirements, the interface was mainly separated into four abstract methods (realized in C++, we call them pure virtual methods) [6]: The first method determines the Medical Device System (MDS) from the VITAL object hierarchy stored in the socalled Medical Data Information Base (MDIB) [1,2]. This information is mandatory to organize the file structures.…”

“…It is completely based on the VI-TAL CEN ENV 13734/35 [1] and is also a standard: ENV 14271 [11]. FEF uses the same nomenclature and Domain Information Model (DIM) [2] as the VITAL standard. That is the reason why persistence using FEF enables mapping of all the vital objects to the storage medium without information loss.…”

“…Both issues are realized by CEN ENV 13734/35 "Vital Signs Information Representation" (VITAL) [1]. The standard was implemented and integrated into a generic framework with different interfaces allowing integration of extensions [2]. In order to guarantee readability of vital signs communicated with the VITAL framework in the future, standardized storing methods are indispensable.…”