Quick Start: Typical Usage Video Walk Through
Start here to get a quick tutorial of the interface. The interface is explained and demonstrated, though nuances are not covered by this quick start video. Readers are encouraged to refer to the detailed sections listed below.
If you are having trouble logging in, please see the FAQ.
Please note that tabs have been rearranged since mi2b2 1.3.0 .quickstart.png
...
so that Tab 3 is now the Request Log. Tab 4 is the Image Repository, and Tab 5 is for View Images. The main functionality and interface of the tabs remain the same, therefore despite the rearrangements, the following video should still be instructive.
Section |
---|
Column |
---|
DescriptionThis video demonstrates the basic features of mi2b2 in a typical walk through, includes searching for appropriate studies, requesting them to be retrieved from PACS (and stored in remote repository on the mi2b2 server), and download these studies from the mi2b2 repository (cache). Detailed video demonstration and nuances can be obtained via the *(more)* links. - Searching for and Transferring Studies from PACS
With Medical Record Numbers (MRNs) or Accession Numbers (NAs), users can search, refine, and select the studies that interest them them most and transfer to mi2b2 repository (cache) them from PACS. (more) - Downloading, Viewing, and Managing Studies
After studies have been moved into mi2b2 repository, users can then request to download these studies to their local machines. Additional actions such as "Move to XNAT" or "Move to Osirix" can be executed if the mi2b2 server is configured correctly. Once the studies have been downloaded onto users' machines, users can use mi2b2's to quickly examine the images. While the image viewer in mi2b2 is not designed for medical diagnostic purposes, it does provide rudimentary image controls, allowing users to decide if the images are what they want. (more) - Managing
|
|
...
- Repository
Users can interact with the
|
|
...
- repository of a mi2b2 server by deleting unnecessary studies to free up cache space, or
|
|
...
...
...