scispace - formally typeset
Search or ask a question
Journal ArticleDOI

IHE cross-enterprise document sharing for imaging: interoperability testing software.

21 Sep 2010-Source Code for Biology and Medicine (BioMed Central)-Vol. 5, Iss: 1, pp 9-9
TL;DR: A software is described that is used to test systems that are involved in sharing medical images within the EHR to test the Cross Enterprise Document Sharing for imaging (XDS-I) integration profile.
Abstract: With the deployments of Electronic Health Records (EHR), interoperability testing in healthcare is becoming crucial. EHR enables access to prior diagnostic information in order to assist in health decisions. It is a virtual system that results from the cooperation of several heterogeneous distributed systems. Interoperability between peers is therefore essential. Achieving interoperability requires various types of testing. Implementations need to be tested using software that simulates communication partners, and that provides test data and test plans. In this paper we describe a software that is used to test systems that are involved in sharing medical images within the EHR. Our software is used as part of the Integrating the Healthcare Enterprise (IHE) testing process to test the Cross Enterprise Document Sharing for imaging (XDS-I) integration profile. We describe its architecture and functionalities; we also expose the challenges encountered and discuss the elected design solutions. EHR is being deployed in several countries. The EHR infrastructure will be continuously evolving to embrace advances in the information technology domain. Our software is built on a web framework to allow for an easy evolution with web technology. The testing software is publicly available; it can be used by system implementers to test their implementations. It can also be used by site integrators to verify and test the interoperability of systems, or by developers to understand specifications ambiguities, or to resolve implementations difficulties.

Content maybe subject to copyright    Report

Citations
More filters
01 Jan 2011
TL;DR: This Digital Imaging And Communications In Medicine tends to be the representative book in this website.
Abstract: Spend your few moment to read a book even only few pages. Reading book is not obligation and force for everybody. When you don't want to read, you can get punishment from the publisher. Read a book becomes a choice of your different characteristics. Many people with reading habit will always be enjoyable to read, or on the contrary. For some reasons, this Digital Imaging And Communications In Medicine tends to be the representative book in this website.

64 citations

Journal ArticleDOI
TL;DR: In this article, the UMLS Metathesaurus was used to retrieve all nursing diagnoses across four nursing terminologies where the concept was also represented in SNOMED CT.

42 citations

Journal ArticleDOI
TL;DR: A toolkit to support federating multiple image data resources such that clients can interact with them as if they are stored in a centralized PACS, and makes it easy to use existing DICOM client applications for data access.
Abstract: Collaborations in biomedical research and clinical studies require that data, software, and computational resources be shared between geographically distant institutions. In radiology, there is a related issue of sharing remote DICOM data over the Internet. This paper focuses on the problem of federating multiple image data resources such that clients can interact with them as if they are stored in a centralized PACS. We present a toolkit, called VirtualPACS, to support this functionality. Using the toolkit, users can perform standard DICOM operations (query, retrieve, and submit) across distributed image databases. The key features of the toolkit are: (1) VirtualPACS makes it easy to use existing DICOM client applications for data access; (2) it can easily be incorporated into an imaging workflow as a DICOM source; (3) using VirtualPACS, heterogeneous collections of DICOM sources are exposed to clients through a uniform interface and common data model; and (4) DICOM image databases without DICOM messaging can be accessed.

23 citations

01 Dec 2011
TL;DR: This study proposed a design of an integrated cloud-based e-medical record which uses ICD-10 and HL7, which is based on integrated model of patient medical record information system using health care standard information format for data exchange.
Abstract: This study conducted a research on the implementation of cloud computing in health care organizations, focused on integrated model of patient medical record information system using health care standard information format for data exchange. Health care organizations use variety of IT applications and infrastructures which always need to be updated as a result of rapid growth in health care services. The diversification on how health care organizations maintaining their operations, especially on maintaining patient's medical information resulted the difficulty of accessing patient's data. This study then proposed a design of an integrated cloud-based e-medical record which uses ICD-10 and HL7.

22 citations

Journal ArticleDOI
TL;DR: Interoperability impediments in healthcare are analyzed by first defining them and providing concrete healthcare examples, followed by discussion of how specifications can be defined and how verification can be conducted to eliminate those impediments and ensure interoperability in healthcare.
Abstract: Interoperability is a requirement for the successful deployment of Electronic Health Records (EHR). EHR improves the quality of healthcare by enabling access to all relevant information at the diagnostic decision moment, regardless of location. It is a system that results from the cooperation of several heterogeneous distributed subsystems that need to successfully exchange information relative to a specific healthcare process. This paper analyzes interoperability impediments in healthcare by first defining them and providing concrete healthcare examples, followed by discussion of how specifications can be defined and how verification can be conducted to eliminate those impediments and ensure interoperability in healthcare. This paper also analyzes how Integrating the Healthcare Enterprise (IHE) has been successful in enabling interoperability, and identifies some neglected aspects that need attention.

10 citations

References
More filters
01 Jan 1999
TL;DR: In this paper, the authors acknowledge the assistance of contacts in the U.S. automotive supply chain who provided information for the study of automotive supply chains and their role in the automotive industry.
Abstract: iii Acknowledgments We would like to acknowledge the assistance of contacts in the U.S. automotive supply chain who provided information for this study.

165 citations


"IHE cross-enterprise document shari..." refers background in this paper

  • ...Such losses, in the billions each year, are incurred due to: 1- the lack of information flows; 2- the flow of incomplete, inaccurate, or improperly represented data; 3- or the misinterpretation of received data [19]....

    [...]

01 Jan 2011
TL;DR: This Digital Imaging And Communications In Medicine tends to be the representative book in this website.
Abstract: Spend your few moment to read a book even only few pages. Reading book is not obligation and force for everybody. When you don't want to read, you can get punishment from the publisher. Read a book becomes a choice of your different characteristics. Many people with reading habit will always be enjoyable to read, or on the contrary. For some reasons, this Digital Imaging And Communications In Medicine tends to be the representative book in this website.

64 citations

DOI
01 Feb 2003

42 citations


"IHE cross-enterprise document shari..." refers background or methods in this paper

  • ...For defining the specifications of our testing system, we based our analysis on: 1- a detailed study of the XDS-I integration profile specific requirements in terms of additional communication constraints, semantic and business requirements; 2- the integration concerns as identified by a study [18] whose objective was to analyze the losses encountered in the U....

    [...]

  • ...In an attempt to analyze and study potential automations for this particular integration problem, a NIST report [18] has identified several integration concerns; these concerns are based on the Model for Open Distributed Processing (RM-ODP) [20]....

    [...]

  • ...For each type of concerns a list of conflicts as identified in [18] are given in the first column; a brief definition of each conflict is provided in the second column along with examples from the healthcare domain for clarifications when necessary; in the third column we describe how testing for the specific conflict has influenced the specifications of our system....

    [...]

Journal ArticleDOI
01 May 2009
TL;DR: A complete test execution framework for HL7-based systems that provides high-level constructs allowing dynamic set up of test scenarios involving all the layers in the interoperability stack, and the computer-interpretable test description language developed offers a configurable system with pluggable adaptors.
Abstract: Health Level Seven (HL7) is a prominent messaging standard in the eHealth domain, and with HL7 v2, it addresses only the messaging layer. However, HL7 implementations also deal with the other layers of interoperability, namely the business process layer and the communication layer. This need is addressed in HL7 v3 by providing a number of normative transport specification profiles. Furthermore, there are storyboards describing HL7 v3 message choreographies between specific roles in specific events. Having alternative transport protocols and descriptive message choreographies introduces great flexibility in implementing HL7 standards, yet, this brings in the need for test frameworks that can accommodate different protocols and permit the dynamic definition of test scenarios. In this paper, we describe a complete test execution framework for HL7-based systems that provides high-level constructs allowing dynamic set up of test scenarios involving all the layers in the interoperability stack. The computer-interpretable test description language developed offers a configurable system with pluggable adaptors. The Web-based GUIs make it possible to test systems over the Web anytime, anywhere, and with any party willing to do so.

42 citations


"IHE cross-enterprise document shari..." refers background or methods in this paper

  • ...more than one message between more than one system as in [14], it still suffers from the lack of business level testing that can be achieved with the actor based testing....

    [...]

  • ...In [14], a test framework is proposed to design and execute testing of HL7 communication, document, and business layers....

    [...]

  • ...The framework described in [14], as well as our system, propose tests for HL7 communication, document and business Noumeir and Renaud Source Code for Biology and Medicine 2010, 5:9...

    [...]

Journal Article
TL;DR: An actor-based testing framework is discussed in detail and an architecture that extends this framework to support testing of integrated healthcare systems using multiple messaging and document data exchange standards is presented.
Abstract: Correct data exchange is critical for ensuring reliable healthcare systems. Standards based systems are the foundation for achieving this goal. However, standards alone are not enough to ensure this promise; conformance and interoperability testing are essential. We present and compare conformance testing strategies for a widely used healthcare clinical data exchange messaging standard. We discuss in detail an actor-based testing framework and give insight on the approach used in developing the framework. We present an architecture that extends this framework to support testing of integrated healthcare systems using multiple messaging and document data exchange standards.

25 citations


"IHE cross-enterprise document shari..." refers background or methods in this paper

  • ...It follows the Upper-Lower Tester model described by [15] and tests only HL7 interoperability, as opposed to our system that is based on an actor approach [15] to test a specific interoperability profile using several communication standards for information exchange....

    [...]

  • ...As mentioned earlier, two different approaches for testing are identified and discussed in [15]....

    [...]