Table 7.
MIM | MIRADA | Raystation | Velocity | |
---|---|---|---|---|
Version | 6.8 | RTX1.8 | 6.0 | 3.2 |
TG132 recommended metrics for evaluation | ||||
TRE | 3 | 0 | 2 | 2* |
MDA | 3 | 1 | 2 | 2 |
DSC | 3 | 1 | 2 | 2 |
Jacobian determinant | 3 | 1 | 2 | 2 |
Consistency | 3 | 1 | 2 | 2 |
TG132 vendor recommendations (7.B) | ||||
Disclose basic components of their registration algorithm | Yes | Yes | Yes | Yes |
Provide the ability to export the registration matrix or deformation vector field | Yes | Yes† | Yes† | Yes† |
Provide tools to qualitatively evaluate the image registration | Yes | Yes | Yes | Yes |
Provide the ability to identify landmarks on 2 images and calculate TRE | See row 1 | No | See row 1 | See row 1 |
Provide the ability to calculate the DSC and MDA | See row 2–3 | No | See row 2–3 | See row 2–3 |
Support the integration of a request and report system | Yes‡ | Yes‡ | Yes | Yes‡ |
Abbreviations: DSC = Dice similarity coefficient; MDA = mean distance to agreement; TG132 = task group 132; TRE = target registration error.
Level 3: Compliant with direct display of the results.
Level 2: Compliant with using scripting provided by the system.
Level 1: Support Digital Imaging and Communications in Medicine export, and users can calculate metrics using a third party software.
Level 0: Not compliant, not able to export.
Velocity has a separate workspace for defining TRE points. Importing points as part of the structure set allows for calculation of TRE but through using surface distance metrics, which does not provide the error in each direction.
DVF files exported from the tested systems are not in a standard Digital Imaging and Communications in Medicine format.
Most systems support the integration of a report generation but do not fully support the integration of the request.