We have developed a breast ultrasound image retrieval system for the decision support of classification of breast lesions on ultrasound. Biopsy-proved direct-digital 1,034 data were used to construct the main DB engine.The image database is constructed by about 1,034 cases (malignant cases are about 400. Benign cases are about 600.) And all cases were biopsy-proven. Two kinds of retrieval images of full size image and ROI image can be executed. Computer-generated malignant likelihood is calculated based on the retrieved images. So, user can infer what's the basis of computer's malignancy likelihood
The IHE initiative sponsored by the RSNA and HIMMS defines a Technical Framework designed to advance the state of data integration in a healthcare environment. This Technical framework defines a set of actors and the roles they must perform for each Integration Profile. Each role consists of a well-defined set of electronic transactions that are based on existing healthcare information standards, namely: DICOM and HL7. IHE brings together the major vendors in the healthcare information and imaging systems industry to agree upon and demonstrate standard interfaces and data architectures at the annual meetings of the RSNA and HIMSS since 1999. We have implemented grouping actors, namely Image Manager, Image Archive and MPPS Manager and selected PGP Integration Profile for IHE Year3 Demonstration at the annual meetings of the RSNA 2001 and HIMSS 2002. Storage Service, Query/Retrieve Service, Storage Commitment Service, and Modality Performed Procedure Step Service of DICOM Standard and also A02, A03, A06, A07, A08 and A40 Event of ADT Messages and ORM Message among lots of messages of HL7 Standard in accordance with IHE Technical Framework have developed in our system. We passed vendor interoperability testing at IHE Connectathon on October and demonstrated successfully with other vendors at the IHE Demonstration of RSNA 2001.
Seoul National University Hospital (SNUH) is composed of two buildings and has more than 1500 beds for patients needing hospitalization. Marotech has provided full PACS to SNUH with total HIS Integration in this year. In this paper, the installation process and management experience for seven months will be presented. At SNUH, 1643.8 exams were held per day during seven month after PACS installation. It is about 40 Gigabytes per day. Two acquisition servers (ACQ 1, 2), two database servers (DB 1, 2), two storage servers (LTA, network attached storage-NAS), one backup server (DLT) totally 8 servers were installed. SNUH has 11 CRs, 4 CTs, 3 MRIs, 9 NMs, 4 RFs, 20 USs, 7 ESs, 4 SCs, 5 XAs, and 5 Film Ditigers. All these modalities were integrated with PACS. DICOM 3.0 standard was conformed for images. DICOM Gateways were installed for modalities that do not support DICOM. The doctor can query and view Endoscopes, pathologic and anatomic data as well as radiological data. All the past five years exams is accessed less than 10 Seconds via on-line. Through the cooperation with SNUH and Marotech, HIS and PACS work together in stable state. These systems were integrated with HL7 standards and IHE.
Structured Report (SR) is new standard of interchanging diagnostic report between medical devices. SR is encoded as traditional DICOM (Digital Imaging and Communications in Medicine) format. There are two types of SR, which are Basic Text SR and Enhanced SR. Enhanced SR includes more information, such as measurement information, than Basic Text SR. In the system point of view, SR can be classified as Report Creator, Report Repository, Report Manager, Report Reader, External Report Repository Access, and Enterprise Result Repository. Specific system transactions are defined at IHE Year3 Technical Framework (Fig1). This paper is an implementation note for Report Creator and Report Reader of the Basic Text SR. The Report Creator has a tree structure for the user interface. The tree structure is converted to DICOM SR. This DICOM SR can be transferred to Report Manager. Report Reader gets SRs through DICOM SR Query/Retrieve Service. Report Reader saves the SR at local Database. The SR is converted to XML and the XML is combined with XSL to be displayed at the SR Browser. Microsoft Internet Explorer is utilized for the SR Browser.