An updated toolkit for security strategies.
Explore the source record for details and available documents.
SEARCH · PubMed Health
Explore indexed PubMed citations for clinical trials, systematic reviews and public health research. Read source abstracts and follow each citation to its original PubMed record.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
Explore the source record for details and available documents.
The number of standards for client-server computing almost equals the number of client-server applications. Although there are some standardization efforts, there is hardly any experience with applying these solutions to (medical) practice. The layering approach of the integration architecture HERMES anticipates the inclusion of commercial standards (when available and evaluated); it currently supports already the development of client-server applications. The toolkit provides support for the development of the communication between client and server through a callback mechanism. Stubs created with the HERMES toolkit contain a number of built-in callbacks that manage sessions between clients and services. An important feature of HERMES is the ability to include existing legacy systems as if they are true open services. In this way, the growth path from stand-alone to client-server computing can be shortened and the implementation of the client-server architecture can begin immediately. Moreover, the existing legacy systems remain available as a stand-alone solution for daily practice. Clients and services are connected through the HERMES kernel. This kernel uses a database to find the best server match for a request from a client. Moreover, it completes requests with mandatory data and tries to optimize performance. Special features are included to minimize the memory burden of the session-oriented client-server model. Currently, a system for the outpatient clinic cardiology, occupational health care, and clinical data analysis is available.
The integration and evolution of existing systems represents one of the most urgent priorities of health care information systems in order to allow the whole organisation to meet the increasing clinical organisational and managerial needs. The CEN ENV 12967-1 'Healthcare Information Systems Architecture'(HISA) standard defines an architectural approach based on a middleware of business-specific common services, enabling all parts of the local and geographical system to operate on the common information heritage of the organisation and on exploiting a set of common business-oriented functionality. After an overview on the key aspects of HISA, this paper discusses the positioning of the authorization and security aspects in the overall architecture. A global security framework is finally proposed.
Explore the source record for details and available documents.
Ubiquitous information is currently one of the most challenging slogans in medical informatics research. An adequate architecture for shared electronic patient records is needed which can use data for multiple purposes and which is extensible for new research questions. We introduce eardap as architecture for using routine data for nationwide clinical research in a multihospital environment. eardap can be characterized as terminology-based. Main advantage of our approach is the extensibility by new items and new research questions. Once the definition of items for a research question is finished, a consistent, corresponding database can be created without any informatics skills. Our experiences in pediatric oncology in Germany have shown the applicability of eardap. The functions of our core system were in routine clinical use in several hospitals. We validated the terminology management system (TMS) and the module generation tool with the basic data set of pediatric oncology. The multiple usability depends mainly on the quality of item planning in the TMS. High quality harmonization will lead to a higher amount of multiply used data. When using eardap, special emphasis is to be placed on interfaces to local hospital information systems and data security issues.
The development of healthcare systems in accordance to the "Shared Care" paradigm results in co-operative health information systems across the boundaries of organisational, technological, and policy domains. Increasingly, these distributed and heterogeneous systems are based on middleware approaches, such as CORBA. Regarding the sensitivity of personal and medical data, such open, distributed, and heterogeneous health information systems demand a high level of data protection and data security, both with respect to patient information and with respect to users. The security concepts and measures available and additionally needed in health information systems based on CORBA architecture are described in this paper. The proposed security solution is also open to other middleware approaches, such as DHE or HL7.
Data security is an essential requirement in all health care applications. Developers of medical information systems should utilize the existing security development and evaluation methods to foresee as many of the technical and human factors that may endanger data security as possible and apply appropriate precautions. Modern smart card technology facilitates the building of robust security framework for interorganizational shared care systems. In this article, we describe the way we utilized the existing security evaluation criteria in developing the security concept of our electronic prescription system.
Healthcare is no longer one patient and one physician. Many people and services are involved, and they all need access to the same accurate, complete data to provide excellent care. The onus is on healthcare providers to come up with information security solutions that don't hinder patient care while still providing the confidentiality of patient information.
As patient's medical data is disseminated in different health structures, developing a medical or epidemiological patient-oriented data warehouse has some specific requirements compared to intra healthcare structure data-warehousing projects. The difference is that the healthcare structures implicated in a patient-oriented data warehouse project require some considerations about the confidentiality of the patient data and of the activities of healthcare structures. Building a data-warehousing system at a regional level, for example in cancerology, requires the participation of all concerned health structures, as well as different health professionals. The heterogeneity of sources medical data of has to be taken into account for choosing between several organizational configurations of the data warehousing system. In top of data warehousing, we propose a concept of Virtual Intranet, which provides a solution to the problem of medical information security arising from heterogeneous sources.
Explore the source record for details and available documents.
In the wake of the Internet, E-commerce, and particularly the Health Insurance Portability and Accountability Act, data security has risen to the top of health care information technology priorities. What is the correct mix of data security tools, policies, and technologies for the doctor, the hospital, the insurer, the vendor, and everyone else who does business in the health care industry?