Browse Prior Art Database

Publication Date: 2004-Nov-10
Document File: 15 page(s) / 76K

Publishing Venue

The Prior Art Database


The present invention is directed towards a system and a method for managing the modality worklist in medical diagnostic and imaging systems. The system includes a modality, a modality worklist server, a HIS/RIS server and a database system. The HIS/RIS server is queried by the modality worklist server for schedule of patients. Scanning protocol corresponding to schedule of each patient is identified by the modality worklist server by utilizing the protocol mappings stored in the database system. The identified scanning protocol is transferred to the modality for scanning purposes. The system automatically selects the scan protocol corresponding to a patient schedule thereby preventing the possibility of human errors.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 11% of the total text.

MEthod and system for minimizing operator intervention in

Modality worklists management

Field of the Invention

[0001]              The present invention relates to the field of medical diagnostic and imaging systems. More specifically, the invention relates to modality worklist management in medical diagnostic and imaging systems.


[0002]                     There are a number of well known non-invasive imaging techniques for the diagnosis and treatment of patients. These techniques are used to obtain high-quality images of the human anatomic structure. The images are obtained using scanners that are based on multiple facets of medical imaging technology. These images provide useful diagnostic information for treating medical ailments.

[0003]                     Currently, a number of member technologies (a.k.a. modalities) exist for medical diagnostic and imaging systems. These systems include, without limitation, computed tomography (CT), X-ray, magnetic resonance (MR), positron emission tomography (PET), ultrasound, and nuclear medicine. When a patient’s anatomical structure, or a limb thereof, is scanned using technology from one of these modalities, that portion of the patient's anatomy is imaged. The resulting anatomic image can be stored in an imaging database for later use.

[0004]                     In addition to storing images internally, the imaging systems need to be able to transfer images to various types of remote devices via communication networks. This requires that the data transferred by the imaging system be in a format, which is supported by the destination remote device. This is achieved by application layer standards such as DICOM (Digital Imaging and Communications in Medicine).

[0005]                     The DICOM standard is intended for use in communicating medical digital images among printers, workstations, scanners (i.e., CT-scanner, MRI scanner, PET scanner) and file servers. The DICOM standard facilitates communication of digital images of different types such as X-ray, CT, MR, and ultrasound images. The technology of each modality is programmed to transfer data in a format, which complies with the DICOM standard. Similarly, the destination remote device is programmed to receive data, which complies with the DICOM standard.

[0006]                     The fundamental concept employed in DICOM is "Services on Objects". One example of an "Object" is an ultrasound image. Examples of a "Service" are the "Store" and "Query/Retrieve" functions. In DICOM, methods of operating on information objects are referred to as "Service Object Pair Classes" (SOP Classes). Examples of SOP Classes are "Store an ultrasound image", "Print an ultrasound image", "Find which studies there are for a certain patient", "Retrieve all studies of a certain patient" and "Retrieve a worklist".

[0007]                     The DICOM communication system is based on a client-server architecture that uses the above-described concept. The device using a service (on objects) is the client device, while the device providing the service is the server dev...