OpenREM Release Notes version 0.6.0¶
- Preview of DICOM Store SCP functionality
- Exports available to import into openSkin
- Modalities with no data are hidden in the user interface
- Mammography import compression force behaviour changed
- Import of Toshiba planar RDSRs fixed
Changes for 0.6.2¶
Minor update due prevent new installs from installing a non-compatible version of
The link to openSkin has also been updated in the fluoroscopy detail page.
There is no advantage to updating to this version over 0.6.0
Release 0.6.1 was just a documentation only change to update the link to openSkin.
Preparing for the upgrade¶
Convert to South¶
Make sure you have converted your database to South before attempting an upgrade
Quick reminder of how, if you haven’t done it already
# Linux: Debian/Ubuntu and derivatives python /usr/local/lib/python2.7/dist-packages/openrem/manage.py convert_to_south remapp # Linux: other distros. In a virtualenv replace all up to lib/ as appropriate python /usr/local/lib/python2.7/site-packages/openrem/manage.py convert_to_south remapp # Windows, assuming no virtualenv python C:\Python27\Lib\site-packages\openrem\manage.py convert_to_south remapp
OpenREM requires two additional programs to be installed to enable the new features: Numpy for charts, and pynetdicom for the DICOM Store Service Class Provider. Note that the version of pynetdicom must be later than the current pypi release!
sudo apt-get install python-numpy # If using a virtualenv, you might need to also do: pip install numpy
For Windows, there are various options:
Download executable install file from SourceForge:
- Download a pre-compiled Win32 .exe NumPy file from http://sourceforge.net/projects/numpy/files/NumPy/. You need to
download the file that matches the Python version, which should be 2.7. At the time of writing the latest version was
1.9.2, and the filename to download was
numpy-1.9.2-win32-superpack-python2.7.exe. The filename is truncated on SourceForge, so you may need to click on the i icon to see which is which. It’s usually the third superpack.
- Run the downloaded binary file to install NumPy.
- Download a pre-compiled Win32 .exe NumPy file from http://sourceforge.net/projects/numpy/files/NumPy/. You need to download the file that matches the Python version, which should be 2.7. At the time of writing the latest version was 1.9.2, and the filename to download was
Or download a
pipinstallable wheel file:
Download NumPy from http://www.lfd.uci.edu/~gohlke/pythonlibs/#numpy -
numpy‑1.9.2+mkl‑cp27‑none‑win32.whlis likely to be the right version, unless you have 64bit Python installed, in which case use the
Install using pip:
pip install numpy‑1.9.2+mkl‑cp27‑none‑win32.whl
pip install https://bitbucket.org/edmcdonagh/pynetdicom/get/default.tar.gz#egg=pynetdicom-0.8.2b2
Upgrading from versions prior to 0.5.1¶
You must upgrade to 0.5.1 first. Instructions for doing this can be found in the OpenREM Release Notes version 0.5.1.
Upgrading from version 0.5.1¶
Back up your database
- For PostgreSQL you can refer to Backing up a PostgreSQL database (Windows)
- For a non-production SQLite3 database, simply make a copy of the database file
The 0.6.0 upgrade must be made from a 0.5.1 (or later) database, and a schema migration is required:
pip install openrem==0.6.0 # Linux: Debian/Ubuntu and derivatives python /usr/local/lib/python2.7/dist-packages/openrem/manage.py schemamigration --auto remapp python /usr/local/lib/python2.7/dist-packages/openrem/manage.py migrate remapp # Linux: other distros. In a virtualenv replace all up to lib/ as appropriate python /usr/local/lib/python2.7/site-packages/openrem/manage.py schemamigration --auto remapp python /usr/local/lib/python2.7/site-packages/openrem/manage.py migrate remapp # Windows: python C:\Python27\Lib\site-packages\openrem\manage.py schemamigration --auto remapp python C:\Python27\Lib\site-packages\openrem\manage.py migrate remapp
Restart the services
- Restart the webserver
- Restart Celery
Summary of new features¶
Release 0.6.0 has a range of charting options available for CT and radiographic data. These charts allow visualisation of trends and frequencies to inform surveys and monitor performance. For more information, please see Charts.
DICOM Store Service Class Provider¶
OpenREM can now act as the DICOM Store service, allowing direct sending of DICOM objects from modalities to OpenREM without needing to use Conquest or any other DICOM Store SCP. This feature is a preview as it hasn’t been extensively tested, but it is expected to work. For more information, please see Direct from modalities.
Exports for openSkin¶
Fluoroscopy studies can now be exported in a format suitable for importing into Jonathan Cole’s openSkin software. The export link is on the fluoroscopy study detail page. The software for creating the exposure incidence map can be downloaded from https://bitbucket.org/openskin/openskin/downloads (choose the zip file), and information about the project can be found on the openSkin wiki. The software allows the user to choose between a 2D phantom that would represent the dose to a film laying on the couch surface, or a simple 3D phantom made up of a cuboid and two semi-cylinders (these can be seen on the Phantom design section of the wiki). For both options the output is an image of the dose distribution in 2D, along with calculated peak skin dose information.
Automatic hiding of unused modality types¶
A fresh install of OpenREM will no longer show any of the four modality types in the tables or in the navigation bar at the top. As DICOM objects are ingested, the appropriate tables and navigation links are created.
Therefore a site that has no mammography for example will no longer have that table or navigation link in their interface.
Mammography import compression force change¶
Prior to version 0.6, the compression force extracted from the mammography image header was divided by ten before being stored in the database. This was because the primary author only had access to GE Senograph DS units, which store the compression force in dN, despite claiming using Newtons in the DICOM conformance statement.
The code now checks for the term senograph ds contained in the model name. If it matches, then the value is divided by ten. Otherwise, the value is stored without any further change. We know that later GE units, the GE Senograph Essential for example, and other manufacturer’s units store this value in N. If you have a case that acts like the Senograph DS, please let us know and we’ll try and cater for that.
If you have existing non-GE Senograph mammography data in your database, the compression force field for those studies is likely to be incorrect by a factor of ten (it will be too small). Studies imported after the upgrade will be correct. If this is a problem for you, please let us know and we’ll see about writing a script to correct the existing data.
Import of Toshiba Planar RDSRs fixed¶
Toshiba include Patient Orientation and Patient Orientation Modifier information in their cath lab RDSRs. The extractor code was deficient for this as the RDSRs previously used didn’t have this information. This has now been fixed. There might however be an issue with Station Name not being provided - it is not yet clear if this is a configuration issue.