mi2b2
Space shortcuts
Space Tools
mi2b2 mi2b2

Versions Compared

Old Version 18

changes.mady.by.user Taowei David Wang

Saved on

compared with

New Version 19

changes.mady.by.user Taowei David Wang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Search for Studies

Section
Column

Image Added

Column
Section
Column

Image Removed

Column

Users can search for patients via Medical Record Numbers (MRNs), and search for studies via these patients or, alternatively, Accession Numbers (ANs). Both of these search tasks follow the same communication diagram

...

to the left.

In mi2b2 client's Tab 1, users can enter a list of MRNs and search on the PACS to find the list of corresponding patients. Once the list of patients is found, users can use these patients to find a set of DICOM studies corresponding to these patients. Alternatively, if the users already have a list of ANs, they can enter them in Tab 2 and search on the PACS for these studies. Finally, after a list of studies is obtained, users can select the desired ones and request the studies to be copied to the remote cache . The request adhers to the following diagram(below).

Request Studies

Section
Column

Column

The mi2b2 client sends requests to the mi2b2 server, which, in turn, asks the PACS to copy these studies into mi2b2 server's own cache. The copying of studies is done via the DICOM C-Move directive, and is executed asynchronously by the mi2b2 server. Because accessing clinically utilized PACS may impact their performance, mi2b2 is typically configured to only access these PACS during downtime (when volume of clinical use is low). As such, the time it takes to fulfill each request is highly dependent upon the mi2b2 server's configuration, PACS access policy, load, and availability. Once the studies are available in the mi2b2 cache, users can later download them onto their own local machine.

...

mi2b2 mi2b2