Page History

...

A user wants to provide medical conclusion for a study.

Working with AIM:

1. Create an image annotation instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances.
3. Create InferenceEntity and store the related question and medical conclusion. See InferenceEntity.
4. Create ImageAnnotationHasInferenceEntityStatement to link an image annotation (subject) to the inference entity (object).

...

...

ImageAnnotationHasTextAnnotationEntityStatement

An image annotation can have a text annotation associated with it. 

A use case:

A user creates a text markup on an image from a set of CT axial series. 

Working with AIM:

1. Create an image annotation instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances using DICOMImageReferenceEntity.
3. Create a text markup on a mass.
4. Create TextAnnotationEntity to store information in step 3.
5. Create ImageAnnotationHasTextAnnotationEntityStatement to link the image annotation (subject) with the text annotation entity (object).

2.65 ImageAnnotationHasThreeDimensionGeometricShapeEntityStatement

One or more three-dimensional graphic drawings may be associated with an instance of an image annotation. ImageAnnotationHasThreeDimensionGeometricShapeEntityStatement represents a direct relationship between an instance of image annotation and a drawing. If you have two drawings on an image, you will need to create two statements. 

A use case:

A user creates a three-dimensional markup on an image from a set of CT axial series. 

Working with AIM:

1. Create an image annotation instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances using DICOMImageReferenceEntity.
3. Create a three-dimensional polyline markup on a mass.
4. Create ThreeDimensionPolyline to store information in step 3.
5. Create ImageAnnotationHasThreeDimensionGeometricShapeEntityStatement to link the image annotation (subject) with the ThreeDimensionPolyline entity (object).

...

ImageAnnotationHasTwoDimensionGeometricShapeEntityStatement

An instance of image annotation may have one or more two-dimensional graphical drawings associate with it. ImageAnnotationHasTwoDimensionGeometricShapeEntityStatement represents a direct relationship between an instance of image annotation and a drawing. If you have two drawings on an image, create two statements. 

A use case:

A user creates a two-dimensional markup on an image from a set of CT axial series.

Working with AIM:

1. Create an image annotation instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances using DICOMImageReferenceEntity.
3. Create a two-dimension polyline markup on a mass.
4. Create TwoDimensionPolyline to store information in step 3.
5. Create ImageAnnotationHasTwoDimensionGeometricShapeEntityStatement to link the image annotation (subject) with the TwoDimensionPolyline entity (object).

...

...

ImageAnnotationHasUriImageReferenceEntityStatement

An image annotation can have a URI reference that directs to the actual storage location of the image used in the image annotation.

A use case:

A user views a set of CT axial series from URI sources. 

Working with AIM:

1. Create an image annotation instance.

...

3. Create ImageAnnotationHasUriImageReferenceEntityStatements to link the image annotation (subject) with each UriImageReferenceEntity (object). 2.68

ImagingObservationEntityIsIdentifiedByThreeDimensionGeometricShapeEntityStatement

An instance of imaging observation entity can be identified by one or more three-dimensional graphical drawings associate with it. ImageObservationEntityIsIdentifiedByThreeDimensionGeometricShapeEntityStatement represents a direct relationship between an instance of imaging observation entity and a markup. If you have two markups on an image, create two statements. 

A use case:

A user creates a three-dimensional markup on an image from a set of CT axial series. 

Working with AIM:

1. Create an imaging observation entity instance.
2. Create a DICOM image reference instance and its associated image study, image series and image instances using DICOMImageReferenceEntity.
3. Create a three-dimensional polyline markup on a mass.
4. Create ThreeDimensionPolyline to store information in step 3.
5. Create ImagingObservationEntityIsIdentifiedByThreeDimensionGeometricShapeEntityStatement to link the imaging observation entity (subject) with the ThreeDimensionPolyline entity (object).

...

...

ImagingObservationEntityIsIdentifiedByTwoDimensionGeometricShapeEntityStatement

An instance of imaging observation entity can be identified one or more three-dimensional graphical drawings associated with it. ImageObservationEntityIsIdentifiedByThreeDimensionGeometricShapeEntityStatement represents a direct relationship between an instance of an imaging observation entity and a markup. If you have two markups on an image, create two statements. 

A use case:

A user creates a three-dimensional markup on an image from a set of CT axial series. 

Working with AIM:

1. Create an imaging observation entity instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances using DICOMImageReferenceEntity.
3. Create a two-dimensional polyline markup on a mass.
4. Create TwoDimensionPolyline to store information in step 3.
5. Create ImagObservationIsIdentifiedByTwoDimensionGeometricShapeEntityStatement to link the imaging observation entity (subject) with the TwoDimensionPolyline entity (object).

...

ImagingObservationEntityIsIdentifiedByTextAnnotationEntityStatement

An imaging observation can be identified by a text annotation. 

A use case:

A user wants to create a text markup for a mass found on an image. 

Working with AIM:

1. Create an image annotation instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances.
3. Create an imaging observation containing mass, RID3874, RadLex.
4. Create a text markup on a mass.
5. Create a text annotation entity based on information from step 4.
6. Create an ImagingObservationEntityIsIdentifiedByTextAnnotationEntityStatement to link the imaging observation (subject) with the text annotation entity (object).

...

...

ImagingPhysicalEntityHasThreeDimensionGeometricShapeEntityStatement

An instance of imaging physical entity may have one or more three-dimensional drawings associate with it. ImagePhysicalEntityHasThreeDimensionGeometricShapeEntityStatement represents a direct relationship between an instance of an imaging physical entity and a markup. If you have two markups on an image, you create two statements.

A use case:

A user creates a three-dimensional markup on an image from a set of CT axial series. 

Working with AIM:

1. Create an imaging physical entity instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances using DICOMImageReferenceEntity.
3. Create an imaging physical entity containing left upper lobe, RID1327, RadLex.
4. Create a three-dimensional polyline markup on a mass.
5. Create ThreeDimensionPolyline to store information in step 3.
6. Create ImagingPhysicalEntityHasThreeDimensionGeometricShapeEntityStatement to link the imaging physical entity (subject) with the ThreeDimensionPolyline entity (object).

...

...

ImagingPhysicalEntityHasTwoDimensionGeometricShapeEntityStatement

An instance of imaging physical entity may have one or more two-dimensional drawings associate with it. ImagePhysicalEntityHasTwoDimensionGeometricShapeEntityStatement represents a direct relationship between an instance of an imaging physical entity and a markup. If you have two markups on an image, you create two statements. 

A use case:

A user creates a two-dimensional markup on an image from a set of CT axial series. 

Working with AIM:

1. Create an imaging physical entity instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances using DICOMImageReferenceEntity.
3. Create an imaging physical entity containing left upper lobe, RID1327, RadLex.
4. Create a two-dimensional polyline markup on a mass.
5. Create a TwoDimensionPolyline to store information in step 3.
6. Create ImagingPhysicalEntityHasTwoDimensionGeometricShapeEntityStatement to link the imaging observation entity (subject) with the TwoDimensionPolyline entity (object).

...

ImagingPhysicalEntityHasTextAnnotationEntityStatement

An image physical entity can have a text annotation. 

A use case:

A user creates a text markup to label the imaging physical entity from a set of CT axial series.

Working with AIM:

1. Create an image annotation instance.
2. Create a DICOM image reference instance and its associated image study, image series, and image instances using DICOMImageReferenceEntity.
3. Create an imaging physical entity containing left upper lobe, RID1327, RadLex.
4. Create a text markup on a mass.
5. Create TextAnnotationEntity to store information from step 4.
6. Create ImagingPhysicalEntityHasTextAnnotationEntityStatement to link the imaging physical entity (subject) with the text annotation entity (object).

...

...

ThreeDimensionGeometricShapeEntityIsComprisedOfThreeDimensionGeometricShapeEntityStatement

Two or more drawings captured as ThreeDimensionGeometricShapeEntity instances have a direct relationship to other drawings when these drawings are placed on the same physical entity or thing.

A use case:

A user draws two different markups on the same lesion. This lesion is the same thing that appears on the same image.

Working with AIM:

1. Create an image annotation instance.
2. Create a markup of the first area of a mass.
3. Create ThreeDimensionGeometricShapeEntity to store information in step 2.
4. Calculate area from step 3 (optional).
5. Create a markup of the second area of the same mass.
6. Create a ThreeDimensionGeometricShapeEntity to store information in step 5.
7. Calculate the area from step 5.
8. Create ThreeDimensionGeometricShapeEntityIsComprisedOfThreeDimensionGeometricShapeEntityStatement to link the first markup (subject) to the second markup (object).

...

ThreeDimensionGeometricShapeEntityExcludesThreeDimensionGeometricShapeEntityStatement

Two or more graphical drawings captured as ThreeDimensionGeometricShapeEntity instances have a direct relationship with other drawings when these drawings are placed on the same physical entity or thing.

A use case:

A user draws two different markups on the same lesion. This lesion is the same thing that appears on the same image.

...

1. Create an image annotation instance.
2. Create a markup of the first area of a mass.
3. Create ThreeDimensionGeometricShapeEntity to store information from step 2.
4. Calculate the area from step 3 (optional).
5. Create a markup of the second area of the same mass.
6. Create ThreeDimensionGeometricShapeEntity to store information in step 5.
7. Calculate the area from step 5.
8. Create ThreeDimensionGeometricShapeEntityExcludesThreeDimensionGeometricShapeEntityStatement to link the first markup (subject) to the second markup (object).

...

TwoDimensionGeometricShapeEntityIsComprisedOfTwoDimensionGeometricShapeEntityStatement

Two or more graphical drawings captured as TwoDimensionGeometricShapeEntity instances have a direct relationship with other graphical drawings when these drawings are placed on the same physical entity or thing.

A A use case:

A user draws two different markups on the same lesion. This lesion is the same thing that appears on the same image.

Working with AIM:

1. Create an image annotation instance.
2. Create a markup of the first area of a mass.
3. Create TwoDimensionGeometricShapeEntity to store information from step 2.
4. Calculate the area from step 3 (optional).
5. Create a markup of the second area of the same mass.
6. Create TwoDimensionGeometricShapeEntity to store information in step 5.
7. Calculate the area from step 5.
8. Create TwoDimensionGeometricShapeEntityIsComprisedOfTwoDimensionGeometricShapeEntityStatement to link the first markup (subject) to the second markup (object).

...

...

TwoDimensionGeometricShapeEntityExcludesTwoDimensionGeometricShapeEntityStatement

Two or more graphical drawings captured as TwoDimensionGeometricShapeEntity instances have a direct relationship with other drawings when these drawings are placed on the same physical entity or thing.

A use case:

A user draws two different markups on the same lesion. This lesion is the same thing that appears on the same image. 

Working with AIM:

1. Create an image annotation instance.
2. Create a markup of the first area of a mass.
3. Create TwoDimensionGeometricShapeEntity to store information from step 2.
4. Calculate the area from step 3 (optional).
5. Create a markup of the second area of the same mass.
6. Create TwoDimensionGeometricShapeEntity to store information from step 5.
7. Calculate the area from step 5.
8. Create TwoDimensionGeometricShapeEntityExcludesTwoDimensionGeometricShapeEntityStatement to link the first markup (subject) to the second markup (object).

...

...

UriImageReferenceEntityHasImagingObservationEntityStatement

A URI image reference can have an imaging observation. It is used in conjunction with UriImageReferenceHasImagingPhysicalEntityStatement. 

A use case:

A user wants to state that a mass is found on an image.  

Working with AIM:

1. Create an image annotation instance.
2. Create UriImageReferenceEntity instance with the image location.
3. Create an imaging observation containing mass, RID3874, RadLex.
4. Create UriImageReferenceEntityHasImagingObservationEntityStatement to link the UriImageReferenceEntity (subject) with imaging observation (object).

...

...

UriImageReferenceEntityHasImagingPhysicalEntityStatement

An URI image reference can have an imaging physical entity associated with it. 

A use case:

A user wants to label left upper lobe of lung on an image.  

Working with AIM:

1. Create an image annotation instance.
2. Create a UriImageReferenceEntity instance with the image location.
3. Create an imaging physical entity containing left upper lobe, RID1327, RadLex.
4. Create UriImageReferenceEntityHasImagingPhysicalEntityStatement to link the UriImageReferenceEntity (subject) with the imaging physical entity (object).

...

UriImageReferenceEntityHasCalculationEntityStatement

A URI image reference can have a calculation associated with it. 

A use case:

A user wants to compute and store a size of the mass from an image.

Working with AIM:

1. Create an image annotation instance.
2. Create a UriImageReferenceEntity instance with the image location.
3. Create a markup to measure the size of a mass.
4. Create CalculationEntity and store the size of the mass.
5. Create UriImageReferenceEntityHasCalculationEntityStatement to link the UriImageReferenceEntity (subject) with the calculation entity (object).

3. We renamed the following classes.

...

Renamed Classes

AnatomicEntity was renamed as ImagingPhysicalEntity

...

ImagingPhysicalEntity is an entity or object that can be identified on an image. For medical imaging, it may represent anatomical location of an organ or body structure. Terms from controlled vocabulary such as RadLex, SNOMED CT, DCIOM, etc. are used to record the type of entity.

 

...

AnatomicEntityCharacteristic was renamed as ImagingPhysicalEntityCharacteristic

...

An ImagingPhysicalEntityCharacteristic is a characteristic of imaging physical entities. It is in contradistinction to ImagingObservationCharacteristic. In a medical area, for example, "dilated" might be an imaging physical entity characteristic of the "colon" imaging physical entity. 3.3

ImagingObservation was renamed as ImagingObservationEntity

...

An ImagingObservationEntity is the description of things that are seen in an image. "Mass", "Pleural Effusion", "Foreign Body", and "Artifact", are all examples of imaging observation entity. 3.4

Inference was renamed as InferenceEntity

...

A conclusion derived by interpreting images and/or other supplemental information related to the images such as medical history, geographic history, etc. 3.5

AnnotationRole was renamed as AnnotationRoleEntity

...

AnnotationRoleEntity describes the role of referenced annotation.

 

...

ImageReference was renamed as ImageReferenceEntity

...

ImageReference is an abstract class that references the image which is being annotated. 3.7

WebImageReference was renamed as UriImageReferenceEntity

...

UriImageReferenceEntity is a source image for the annotation. It can be accessed via Intranet, Internet, local computer and/or file sharing systems.

 

...

DICOMImageReference was renamed as DICOMImageReferenceEntity

...

DICOMImageReferenceEntity is a source image for the annotation.

 

...

Annotation was renamed as AnnotationEntity.

AnnotationEntity captures information that can be described, measured, calculated, and drawn on images either by a human or machine observer. 3.10

TextAnnotation was renamed as TextAnnotationEntity.

TextAnnotationEntity represents the text and the markup of text intended to be rendered on the image.

...

GeometricShape was renamed as GeometricShapeEntity.

GeometricShapeEntity is the shape of a region of interest (ROI). 3.12

Segmentation was renamed to DICOMSegmentation.

DICOMSegmentation is a multi-frame image representing a classification of pixels in one or more referenced images. Segmentations are either binary or fractional. See DICOM part 3 Segmentation IOD for more information. 3.13

PresentationState was renamed to ReferencedDICOMObject.

ReferencedDICOMObject is a collection of related DICOM objects created from the image(s), e.g. presentation state, SR document, radiotherapy objects, waveform, encapsulated document, etc.  

The old association between PresentationState and DICOMImageReferenceEntity was removed. It was replaced by an association between ReferencedDICOMObject and ImageStudy. 

Deleted Classes

4. Four classes were deleted since AIM statements and new classes cover the concepts represented by the deleted classes. 4.1

• ReferencedGeometricShape is represented by ImagingObservationEntityIsIdentifiedByGeometricShapeEntityStatement.

...

• AimStatus is represented by AuditTrail.

...

• ReferencedAnnotation is represented by AnnotationOfAnnotationHasAnnotationRoleEntityStatement and ImageAnnotationHasAnnotationRoleEntityStatement.

...

• ReferencedCalculation is represented by CalculationEntityReferencesCalculationEntityStatement.

...

New Attributes

5. New attributes have been added to the following classes. 5.1

Inference

    - questionTypeCode is used to collect coded entry data that describes the question being asked that is related to the typeCode attribute.

...

- comment is a free text about inference. 5.2

GeometricShapeEntity

    - label is a human readable description of the geometric shape.

...

- comment is free text about a geometric shape entity. 5.3

ImageSeries

    - modality is the equipment used to acquire images of subjects or  things, such as human and animal bodies. 5.4

CalculationEntity

 - questionTypeCode is used to collect coded entry data that describes the question being asked that is related to the typeCode attribute.

...

- questionIndex is used to store an index value that identifies the order of the question in an AIM Template. 5.5

ImageStudy

   - procedureDescription is information about the procedure being performed on a subject. 5.6

Scale

   - type represents different types of scales that are Nominal, Ordinal or Ratio. 5.7

AnnotationRole

   - questionTypeCode is used to collect coded entry data that describes the question being asked that is related to the typeCode attribute. 5.8

ImageReference

   -  imageIdentifier is a unique number within an ImageAnnotation object that uniquely identifies this object. 5.9

ImagingObservation

   - imageIdentifierReference is a number that refers to an existing image identifier from ImageReference.  

- questionIndex is used to store an index value that identifies the order of the question in an AIM template. 5.10

Annotation

   -  templateUid is a UID that references to an AIM template used to capture semantic meaning of pixel data, markup and calculation. 5.11

CalculationResult

  - dataType is coded entry data used to describe or capture a type of parameter. A coded data type can be a primitive programming data type such as integer, double, etc. as well as other data types such as URI. 5.12

Equipment

  - deviceSerialNumber is manufacturer’s serial number of the equipment that produced the sources. 5.13

ImagingPhysicalEntity

- questionIndex is used to store an index value that identifies the order of the question in an AIM Template. 5.14

Quantile

- bins is a number representing the dividing ordered data into an equal-sized data subsets. For example, maxValue is 100. It's divided by four. Four is the value for the bins.

...

- maxValue is a maximum value of the largest value in a range. 5.15

CharacteristicQuantification

- comment is free text about characteristic quantification.

...

- valueDescription is a human readable description. 5.16

ImagingPhysicalEntity

- comment is free text about imaging physical entity. 5.17

ImagingPhysicalEntityCharacteristic

- comment is free text about imaging physical entity characteristic.

6. Attribute name change.

Attribute Name Change

The6.1 typeCode attribute replaces a set of coded term attributes as a single attribute in a class. The replaced attributes include:-         

• codeValue

...

• codeMeaning

...

• codingSchemeDesignator

...

• codingSchemeVersion

...

These attributes are mapped to a single CD ISO 21090 data type. The effected AIM classes include:-         

• AnnotationEntity (formerly known as Annotation)

...

• AnnotationRoleEntity (formerly known as AnnotationRole)

...

• CalculationEntity (formerly known as Calculation)

...

• ImagingPhysicalEntity (formerly known as AnatomicEntity)

...

• ImagingPhysicalEntityCharacteristic (formerly known as AnatomicEntityCharacteristic)

...

• ImagingObservationEntity (formerly known as ImagingObservation)

...

• ImagingObservationEntityCharacteristic (formerly known as ImagingObservationCharacteristic)

...

• InferenceEntity (formerly known as Inference)

...

• NonQuantifiable

...

6.2 The name attribute in CharacteristicQuantification has been change changed