 |
Page History
...
| Note |
|---|
The AIM Toolkit consists of the AIM C++ software library and a program called ANIVATR. The ANIVATR software application validates AIM annotations and transcodes them between AIM XML documents and AIM DICOM SR objects. ANIVATR does not have a capability to convert any XML documents or DICOM SR objects to AIM XML documents and AIM DICOM SR objects. |
Features in the AIM 4.1 Toolkit
This release makes AIM Toolkit 4.1 a cross-platform set of tools. New CMake support enables developers on Windows, Linux, and OS X operating systems to create native executable components. By supporting all three major operating systems, generating and using AIM data becomes universally available. The AIM Toolkit provides the AIM Library 4.1 for incorporating AIM model and data into third-party applications, and the AIM converter tool ANIVATR for direct manipulation of AIM documents in AIM 4.0 XML and AIM 4.0 DICOM SR formats.
The following issues were fixed. Links open the issue in NCI Tracker.
| Issue | Description |
|---|---|
| Fixed UID validation | Fixed UID validation routine to check for zero-padded UID component values, e.g. 1.2.009.02 is invalid because non-zero UID component cannot start with 0. |
| Fixed time value validation | Fixed time value validation to allow for 00:00 time values. This issue showed up with de-identified dates. |
| Improved consistency of AIM Converter parameters | Improved consistency of the AIM Converter parameters. Now the parameter for XML documents is "XML" instead of the old "AIM" . |
| Improved error reporting by AIM Converter | Improved error reporting by the AIM Converter by not silently ignoring some of library error messages. |
| Implemented validation for allowed length of every component of a coded element | Implemented validation for allowed length of every component of a coded element (code value, code meaning, coding scheme designator and coding scheme version). |
Features in the AIM 4.0 Toolkit
The Annotation and Image Markup (AIM) information model version 4.0 has evolved in response to the feedback and changing requirements from the imaging community. The model has become more flexible and expressive. It defines AIM statements that describe a finding found on an image or series of images. These statements represent a relationship between the subject and object entities in the AIM foundation model. A class name that ends with “entity” can be used to create an AIM statement.
...
