From PACS to integrated EMR

Ratib, Osman; Swiernik, Michael A.; McCoy, John J.

doi:10.1016/s0895-6111(02)00075-7

Cited by 64 publications

(39 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…8 Based on the UID information from DC-IAN images can be displayed on a standard HIS-PC using an either proprietary or DC-WADO (Web Access to DICOM Objects) based Visual Integration between the HIS Client-SW and the PACS Web-Client-SW. In some installations, image access is only granted when at least a preliminary report is available to the HIS, but since clinical departments like ER, OR or ICU demand an immediate image access, the described approach is becoming increasingly common.…”

Section: Dicommentioning

confidence: 99%

“…With the introduction of large-scale PACS and the capability for web-based image distribution [1][2][3], this impression began to change. The need for integration with the Hospital Information System (HIS) [4][5][6][7] and the Electronic Patient Record (EPR) [8][9][10] became evident, although the latter is still not seen too often [11], making PACS a well perceived part of the hospital's IT-landscape.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Enterprise imaging and multi-departmental PACS

Bergh

2006

Eur Radiol

View full text Add to dashboard Cite

The aim of this review is to present the status of digital image acquisition and archiving outside of radiology and to describe the technical concepts and possibilities of how a "radiology" Picture Archiving and Communication System (PACS) can become a multi-departmental (MD-)PACS. First the principles of system integration technology are explained and illustrated by the description of a typical radiology system integration. Then four types of modality integration approaches are defined: the direct modality integration (Type-I), the integration via DICOM acquisition software (Type-II) the integration via specialised systems either with (Type-III) or without PACS connection (Type-IV). The last section is dedicated to the presentation of the PACS requirements of selected interdisciplinary modality types [Endoscopy, Ultrasound and Electrocardiography (ECG)] and clinical disciplines (Pathology, Dermatology, Ophthalmology and Cardiology), which are then compared with the technical possibilities of a MD-PACS.

show abstract

Section: Dicommentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Enterprise imaging and multi-departmental PACS

Bergh

2006

Eur Radiol

View full text Add to dashboard Cite

show abstract

“…Because of their special storage, network and processing performance requirements RIS and PACS [55][56][57]71] systems are very important departmental services. Company related information on these systems can be found in [12][13][14][15][16][17][18], more theoretical work in [19][20][21].…”

Section: Medical Information Systemsmentioning

confidence: 99%

“…However, it is architecture, infrastructure and modeling related and helps understanding medical services requirements. Another paper on KIS/RIS/PACS integration [71] helps understanding the ''large picture'' of medical services and the IHE framework but does not focus on modelling services based on Web service technology.…”

Section: Related Workmentioning

confidence: 99%

Modeling and implementing medical Web services

Anzböck

Dustdar

2005

Data & Knowledge Engineering

View full text Add to dashboard Cite

On the one hand, Web services are increasingly gaining attention. Standardization efforts have improved their stability and range of applications. Composition and coordination techniques for Web services enable an application integration effort beyond loosely coupled systems. On the other hand, medical Web services are covered by the DICOM and HL7 communication protocols and are profiled by the IHE (Integrating the Healthcare Enterprise) technical framework. Standardization is more extensive, most workflows are well defined, and integration is tighter than in most other domains. Nevertheless, so far standardization focused on conventional workflow systems. In an Internet-based medical environment with high security standards, communication is strongly restricted and conventional systems fail to deliver. This paper proposes a modeling process for medical Web services. The IHE patient administration process flow serves as a well defined example. Furthermore, the paper defines requirements of a Web service based middleware for the execution of medical Web services by investigating currently relevant Web service protocols. The technique should enable building medical applications for Internet-based workflow execution. Finally, Biztalk 2004 is used to evaluate the implementation of the analyzed sample functionality.

show abstract

“…It is also not unusual in large medical institutions to implement different Picture Archiving and Communications System (PACS) archives in deferent departments or sections. The compliance of cardiology, nuclear medicine, and radiology systems with standards such as the Digital Imaging and Communications in Medicine (DICOM) standard ensures that image data can be exchanged and retrieved from different systems into a single point of review [1]. (Roger Bauman, et al suggested PACS for the first time.…”

Section: Introductionmentioning

confidence: 99%

The Information Security Needs in Radiological Information Systems—an Insight on State Hospitals of Iran, 2012

Farhadi¹,

Ahmadi

2013

J Digit Imaging

View full text Add to dashboard Cite

Picture Archiving and Communications System (PACS) was originally developed for radiology services over 20 years ago to capture medical images electronically. Medical diagnosis methods are based on images such as clinical radiographs, ultrasounds, CT scans, MRIs, or other imaging modalities. Information obtained from these images is correlated with patient information. So with regards to the important role of PACS in hospitals, we aimed to evaluate the PACS and survey the information security needed in the Radiological Information system. First, we surveyed the different aspects of PACS that should be in any health organizations based on Department of Health standards and prepared checklists for assessing the PACS in different hospitals. Second, we surveyed the security controls that should be implemented in PACS. Checklists reliability is affirmed by professors of Tehran Science University. Then, the final data are inputted in SPSS software and analyzed. The results indicate that PACS in hospitals can transfer patient demographic information but they do not show route of information. These systems are not open source. They don't use XML-based standard and HL7 standard for exchanging the data. They do not use DS digital signature. They use passwords and the user can correct or change the medical information. PACS can detect alternation rendered. The survey of results demonstrates that PACS in all hospitals has the same features. These systems have the patient demographic data but they do not have suitable flexibility to interface network or taking reports. For the privacy of PACS in all hospitals, there were passwords for users and the system could show the changes that have been made; but there was no water making or digital signature for the users.

show abstract

From PACS to integrated EMR

Cited by 64 publications

References 7 publications

Enterprise imaging and multi-departmental PACS

Enterprise imaging and multi-departmental PACS

Modeling and implementing medical Web services

The Information Security Needs in Radiological Information Systems—an Insight on State Hospitals of Iran, 2012

Contact Info

Product

Resources

About